Measuring
Privacy mode
Two modes
Every site runs in one of two modes. Both are cookie-free and neither mints a persistent identifier; strict mode goes further by refusing to store several additional things.
| Standard | Strict | |
|---|---|---|
| Country (from proxy header) | stored | discarded |
| Screen size | stored | discarded |
| Referrer query string | kept | stripped |
identify() | works | ignored |
| Do Not Track | on by default, site can opt out | always enforced |
| Custom event properties | up to 24 | up to 8 |
What strict mode costs you
This is a real trade, and we would rather you knew before switching:
- The country breakdown will be empty.
- Screen sizes are not recorded.
- Retention cannot be computed — without identity there are no cohorts.
- Campaign attribution gets coarser, because referrer query strings are gone.
A toggle that quietly kept collecting would be worse than no toggle at all.
It is enforced on the server
Strict mode is applied during ingest, not in the browser script. Anyone can edit the script; a guarantee made in the client is not a guarantee. The same rule runs through the rest of ingest: the client proposes, the server decides.
Turning it on
Dashboard → Install → the site's privacy mode. It takes effect on the next event; data already collected is not rewritten.