Cookie-free analytics is web analytics that never stores an identifier on the visitor’s device. No cookie, no localStorage, nothing a later page can read back. It still counts visitors, pages, sources and sales, but it does so with a different method and a different set of limits. This page is the overview: how the counting works, what it measures and what it gives up, what the consent rules actually say, how to judge a privacy-friendly analytics tool before you install it, and how Vero does it. Each part links to a longer post if you want the detail.
What is cookie-free analytics?
Classic web analytics writes an id into a cookie on the first visit and reads it back on every later one. That id is how the tool knows a pageview on Tuesday belongs to the same person as a pageview on Monday. It is also the part that needs storage on the visitor’s device, and in many places it is what triggers the consent question.
Cookie-free analytics drops that id. The script sends what it sees on the page, such as the path, the referrer, the campaign tags and the screen size, and the server turns those requests into visits and visitors. Nothing is written to the browser, so nothing is left behind for the next page or the next day to find.
The trade is simple to state. You lose long-term memory of individual visitors. You keep every visit that loads the script, including the ones a consent banner would have filtered out of a cookie-based tool.
How does analytics without cookies count unique visitors?
If nothing is stored on the device, the server has to recognise a visitor from the request itself. The usual method, and the one Vero uses, is a hash: the IP address, the user agent, the date and, in Vero, the site go into SHA-256 together with a secret salt that only the server knows. The output is an anonymous id that is the same for every request a person makes that day.
The IP is used in memory to compute the hash and is never stored. Because the date is part of the input, the id changes at midnight UTC: tomorrow the same person produces a different hash, and yesterday’s cannot be linked to today’s. Without the salt, nobody can recompute it from an IP either.
Visits come from that id plus time. In Vero, a visit ends after 30 minutes without activity, and it is also cut at midnight UTC, when the hash rotates. Inside a page, the tracker holds a session id in memory for as long as the page is open. It is never written to disk.
What can cookie-free analytics not measure?
Returning visitors across days. A person who comes back tomorrow has a new hash, so they count as a new visitor. Unique visitors within a day are exact. Over a week or a month, the same person on three different days counts as three visitors.
Journeys that span several days. Someone who reads a post on Monday and buys on Friday shows up as two unrelated visits. Attribution credits how Friday’s visit began, not Monday’s. The same goes for anything that needs a long memory of one person: cohorts by first visit, lifetime paths, or a funnel someone completes over a week.
Cross-device behaviour, and anything a person explicitly hides. A visit on a phone and a visit on a laptop are different visitors. A browser that sends Do Not Track or Global Privacy Control is not tracked by Vero at all, by design. And an ad blocker can stop any analytics script from loading, cookies or no cookies.
Payments are the exception that matters most. A sale does not need the device to remember anything if the visit travels with the checkout itself, which is how revenue attribution without cookies works.
Do cookie-free analytics need a consent banner?
That depends on your site, and it is your legal team’s call, not an analytics vendor’s. What follows is where the rules live, so you can read them yourself.
In the EU the starting point is article 5(3) of the ePrivacy Directive, as amended in 2009. It requires consent for storing information on a user’s device, or reading information already stored there, unless that is strictly necessary for a service the user asked for. Each country turns it into national law, so the exact wording you are bound by is your country’s.
Regulators read that article as wider than cookies. The European Data Protection Board’s guidelines on the technical scope of article 5(3) cover other techniques too, including scripts that make the browser send information. So “no cookies” on its own does not settle the question.
Some regulators publish when audience measurement can go without consent. France’s CNIL sets out the conditions an audience-measurement tool must meet to be exempt. Spain’s AEPD explains how it applies the rule in its guide on the use of cookies. Neither page decides anything about your site, which may also run ad pixels, chat widgets or embedded videos that need consent on their own.
What a vendor can do is give your legal team facts to check. The facts for your legal team lists what Vero writes to the device (nothing), what it sends, what it stores and what it never keeps.
What a consent banner costs the analytics behind it
A cookie-based tool that waits for consent only counts the visitors who accept. The ones who decline are not a random sample, so the loss bends your sources, your conversion rate and the revenue you can credit to a channel. What a consent banner costs your analytics walks through the mechanics.
We publish no rejection rate, because we have no source we would stand behind for one. The cookie tax calculator lets you put your own share in and see what it means in visits, conversions and revenue a month.
How do you choose privacy-friendly analytics?
Ask where the data is stored and where it is processed, and expect both answers. Storage in one region and computation at the edge worldwide are different claims. A tool that only names the first is leaving something out.
Ask what happens to the IP address. Kept, truncated, hashed once, or used only in memory and dropped: each one is a different product. Then ask whether anything is written to the device, and whether the tool fingerprints the browser to make up for it.
Weigh the script. Every byte competes with your page for the network and the main thread, and the figure that matters is the gzipped size your visitors actually download, with the features you turn on. What your analytics script costs your Core Web Vitals shows how to measure it on your own site.
Finally, check that you can verify the claims instead of trusting them. A tool should list every field it sends and every sub-processor it uses. Vero’s transparency page is where it does that.
Does cookie-free analytics get past ad blockers?
No, and nothing about cookies changes that. A blocker decides whether a script loads based on where it comes from and what it looks like, not on what it stores. A blocked script sends nothing.
The fix is to count page loads where there is no script to block: in your edge middleware or on your server. That covers pageviews and sources for visits whose browser blocked the script. How to measure past ad blockers explains the setup and what it still cannot see.
How Vero does cookie-free analytics
Vero sets no cookies, uses no localStorage and never stores the IP. Visitors are a salted SHA-256 hash that rotates daily, and nothing stored identifies anyone. The core tracker weighs 1.2 KB gzipped, and the full bundle with all 9 optional modules weighs 2.7 KB. Each of the 320 module combinations is measured, so you know the exact size of the one you load.
Events, sessions and revenue are stored in a single database in the EU, in Ireland. The API and the tracker run on Cloudflare’s edge, at the location nearest each visitor, and stats responses are cached at the edge location that served them. Storage is in the EU. Computation and cache are global.
The point of all this is the money. Because the visit is counted from the request, with nothing on the device to depend on, the checkout module can carry it into your Stripe or Lemon Squeezy checkout, and the sale comes back credited to the source that started it. Revenue attribution, from model to webhook covers how that works end to end.
Unsure of a term? Read the glossary

Vero is built by one person in Spain. I read every waitlist entry and pick the beta accounts myself.