Does your website use third-party services? Get GDPR compliant in minutes.
Try FlowConsentFree plan · 10-min setup
Avizi is a web analytics and visitor tracking platform that uses JavaScript and first party cookies to measure traffic, engagement, and conversions.
Avizi is a web analytics platform aimed at digital marketers who need traffic, conversion, and behaviour insights. The service runs a lightweight JavaScript snippet that fires page views, custom events, and conversion goals back to the Avizi servers. Persistent identifiers stored in cookies make it possible to recognise returning visitors and stitch sessions across pages.
Avizi sets first party cookies such as _avz_vis (visitor identifier, twelve months) and _avz_sess (session identifier, thirty minutes). It collects IP address (truncated where possible), user agent, referrer, viewed pages, and custom event parameters. Because these cookies identify a specific browser, they fall under Article 5(3) of the ePrivacy Directive and require consent.
The default legal basis is consent under Article 6(1)(a) of the GDPR combined with Article 5(3) of the ePrivacy Directive. Some EU regulators (CNIL, DPC Ireland) accept a strict analytics exemption when the tool collects no identifiers reusable across sites and limits retention. Confirm with Avizi whether their EU mode meets the CNIL exemption criteria.
Get GDPR compliant in 10 minutes
Free plan available · No credit card required
Avizi hosts data in EU data centres. If your contract references sub processors outside the EEA (CDN, monitoring), document them and ensure SCCs are in place. Inform users of any international transfer.
Block the Avizi tag until your CMP captures consent for the analytics category. Avizi supports a privacy mode that anonymises IPs and disables cross domain identifiers; activate it as a fallback when consent is denied to obtain aggregate, non identifying data without consent.
Sign a DPA with Avizi, declare every cookie in your policy, configure retention to no more than thirteen months, and review the configuration when adding event tracking. Use privacy friendly mode for non consenting users and full mode after consent.
Websites using Avizi must obtain user consent under GDPR regulations.
DPIA considerations
A DPIA may be required when Avizi is configured with user identification, behavioural session replay, or large scale combination with first party CRM data.
Sample consent text
We use Avizi to measure traffic and improve the user experience. With your consent, Avizi may set cookies to identify your visit and record analytics events.
Third-party domains contacted
avizi.comcollect.avizi.comcdn.avizi.comCookies placed
| Name | Type | Duration | Purpose |
|---|---|---|---|
| _avz_vis | first_party | 12 months | Pseudonymous visitor identifier for analytics |
| _avz_sess | first_party | 30 minutes | Session identifier for the current visit |
| _avz_src | first_party | 30 days | Stores UTM source attribution data |
Avizi places tracking cookies for advertising — comply with GDPR using FlowConsent.
First party cookies _avz_vis (visitor identifier, twelve months), _avz_sess (session, thirty minutes), and _avz_src (UTM source, thirty days).
Yes, in most cases. Avizi sets identifiers that are not strictly necessary, so Art. 5(3) ePrivacy applies. Some regulators allow a strict analytics exemption if cross site IDs are disabled and retention is capped.
Consent (Art. 6(1)(a) GDPR plus Art. 5(3) ePrivacy). Strict analytics exemption may apply with limitations.
No, by default. Avizi hosts in EU data centres. Check the DPA for sub processors.
Generally no for standard analytics, but yes when using session replay or combining with CRM data at scale.
Gate the tag behind your CMP, enable privacy mode for non consenting users, cap retention, and document cookies.
Matomo (self hosted), Plausible Analytics, Fathom, and Pirsch are privacy first alternatives.
Add Avizi cookies with names, purposes, and durations. Link to the Avizi privacy policy.