Cookieless tracking

Statiz works without cookies in both modes — but Cookieless / privacy mode goes one step further and stores nothing on your visitors' devices at all. Here's what changes, what it costs, and when to turn it on.

How it works

Enable Cookieless / privacy mode in Settings → General (it's off by default). Statiz swaps your install snippet to the cookieless script:

The regular script already sets no cookies — it keeps one random visitor ID in localStorage. The cookieless script doesn't touch localStorage, sessionStorage or cookies at all.

Without an ID on the device, the server derives one per request: an anonymous hash of the visitor's IP address, user agent and your site — mixed with a salt that rotates every 24 hours (UTC). The same visitor on the same day is one visitor; on the next day they get a new, unlinkable ID. Their IP is only ever an input to the hash — it is never stored.

Salts older than yesterday are deleted, so yesterday's IDs can never be recomputed — not even from the same IP.

Enable it

  • Open Settings → General and check Cookieless / privacy mode.
  • Replace the script tag on your site with the updated snippet — it now loads /js/script.cookieless.js.
  • That's it. Events are counted the same way; the visitor identity behind them is what changed.
Toggling the mode doesn't rewrite history: visitors counted before the switch keep their IDs, and the server-side hashing applies to the site from the moment you enable it — even beacons from an old snippet still get a hashed ID, so nothing is double-counted.

Trade-offs

Everything cookieless analytics gives up comes from not recognizing visitors across days:

  • New vs returning — a visitor who came back tomorrow looks new again. Long-term loyalty trends read flat.
  • Revenue attribution — payments still attribute to the visitor who made them that day (and payer name/email from the checkout still work — see /docs/track-revenue), but a first touch weeks before the purchase can't be linked to it.
  • statiz.visitorId() returns null — there is no ID to stamp into checkout metadata.
  • Visit counts are per-day accurate; cross-day journey and funnel windows get shorter effective memories.

If those matter to you, keep the regular mode: it sets no cookies, stores one random ID in localStorage, and needs no consent banner in most jurisdictions (check yours — this is not legal advice).