Cookieless analytics: how it works and what you give up

"Cookieless analytics" sounds like a contradiction: how do you count unique visitors if you don't remember them? The short answer is that you count them for a short time and on one site only — and accept a few trade-offs.

Why analytics used cookies in the first place

Classic tools like Google Analytics and Yandex Metrica store an ID in a cookie. When the visitor comes back next week, the same ID is read again, so the tool can say "this is a returning visitor" and stitch sessions together.

That ID is also what makes analytics a privacy and consent topic: a persistent identifier on the visitor's device.

How cookieless counting works

Cookieless tools replace the stored ID with a value computed on the server for each request. A common approach — used by LightMetrica — looks like this:

visitor = hash( daily_salt + site + IP address + browser )

• The salt is a random value that changes every day and is deleted afterwards.
• The IP address is used only for this calculation and is not stored.
• The result identifies "the same browser on the same site today" — nothing more.

Because the salt changes daily, the same person tomorrow gets a different value, and the same person on another site gets a different value too. Nobody — including the analytics provider — can follow them over time.

What you still get

• pageviews, visits and daily unique visitors;
• traffic sources, UTM campaigns and referrers;
• top pages, entry and exit pages, time on page, scroll depth;
• devices, browsers, operating systems, countries;
• goals and conversions within a visit.

For most content sites, landing pages and small businesses, that covers everyday questions.

What you give up

• New vs returning visitors and long-term retention.
• Cross-device journeys — the same person on phone and laptop counts twice.
• Multi-day attribution — "first touch three weeks ago" is not available.
• Precision behind shared IPs — several people in one office using the same browser can occasionally merge into one visitor.

If your business depends on cohort retention or multi-touch attribution, you still need a tool with persistent identifiers (and proper consent).

Is cookieless analytics automatically compliant?

Not automatically. Not using cookies removes one major reason for consent banners in many jurisdictions, but rules differ between countries and depend on your whole setup. Treat "cookieless" as a strong privacy improvement, check your local requirements, and keep your privacy policy honest about what you collect.

Trying it

LightMetrica is a free, cookie-free counter: around 2 KB of JavaScript, no cookies, IP addresses never stored. You can run it next to your current analytics for a couple of weeks and compare — and see the live stats of our own site to judge the reports first.