Collect limited anonymous measurement
This is one of three consent methods described in the privacy and consent overview. Choose it when you want a middle ground: full analytics for users who consent, and very limited measurement for users who don't.
This method is appropriate only when your legal team confirms that this kind of limited audience measurement is allowed in your jurisdictions. This page shows you how to implement a decision your team has already made; it doesn't replace legal advice.
How it works
Keep this method limited to anonymous or strongly minimized audience measurement, such as total traffic or page views. Don't let it turn into user-level behavioral analysis.
Rules can vary across Europe, so treat local regulatory guidance as part of the implementation decision. France is one well-known example: the cookies and consent management guide describes the CNIL exemption as a narrow case for anonymous statistical audience measurement without consent, not full analytics. It's a useful reference point, but don't treat it as the default rule for every European market.
CNIL self-certification requirement
Qualifying for the CNIL exemption requires completing a formal self-certification process with CNIL. If you're pursuing this route, work with your legal team to confirm your setup meets the certification criteria before relying on this exemption.
Set it up in Amplitude
For the limited anonymous flow, reduce or remove persistent identity:
- Set
identityStoragetononeif you don't want persistent browser identity. - Set
identityStoragetosessionif you want to track users within a single session but not across sessions. This is a useful middle ground for some implementations. - Avoid sending a stable
userId. - Keep the event set small and focused on aggregate traffic measurement.
amplitude.init('AMPLITUDE_API_KEY', {
identityStorage: 'none',
});
You can also shorten cookie duration if your policy allows cookies but you want a more conservative setup.
Separate the two data streams
If you collect both consented analytics data and a limited non-consented measurement stream, always keep them in separate Amplitude projects. Mixing them into a single project creates reporting and identity problems that are difficult to untangle later.
Refer to Keep consented and non-consented data in separate projects for the project setup, access restrictions, and the routing rules to document.
What to do outside Amplitude
Decide exactly which events belong in the anonymous flow. Keep that list short. For most teams, that means page views, traffic totals, and other high-level measurement only.
If you need stronger control, send data through your own proxy before it reaches Amplitude. A domain proxy can help you filter, block, or anonymize data before forwarding it.
Keep the anonymous flow narrow
If you choose this method, be disciplined. Don't quietly turn a "limited anonymous measurement" flow into full behavioral analytics over time. The more your anonymous flow starts to look like user analysis, the weaker your privacy position becomes.
Was this helpful?
For AI agents: a documentation index is available at /docs/llms.txt. Append .md to any page URL for markdown, or send Accept: text/markdown.