Is there a Google Analytics alternative without a cookie banner?
What cookieless analytics actually measures, what it can't, and what it showed one client that a consent-based tool was hiding.

Search for “Google Analytics alternative” and page one is a list of tools: Plausible-shaped products, comparison articles, a Reddit thread arguing about which one is best. All of them are software you install and run yourself. None of them answer the question a lot of people searching that phrase actually have, which is smaller and more practical: can I stop showing a cookie banner, and still know what is happening on my site?
The short answer is yes, and it does not need a new tool bought off a list. It needs a different kind of measurement.
Why does Google Analytics need a cookie banner in the first place?
Google Analytics identifies a visitor with a cookie, a small file it stores in the browser so it can recognise the same person on a later visit. Under GDPR and the ePrivacy rules, that kind of identifying cookie needs the visitor’s consent before it is set, which is what the banner is asking for. Refuse it, and Google Analytics has nothing to measure that visit with.
This is the general rule, not legal advice. Your own site’s setup should be checked against the exact rules for the businesses and visitors it serves.
Can you use Google Analytics without cookies?
Not in the way most sites run it. Google Analytics is built around that cookie-based visitor identity, so switching it to “no cookies” is not really an option inside the tool itself. The alternative is not a setting, it is a different kind of analytics that was never built to identify a visitor in the first place: it looks at the traffic and the pages, not at the person.
What cookieless analytics actually measures, and what it does not
A cookieless platform can still show which pages get read, where visitors came from, which campaigns brought them, and where a page is slow or breaking. What it gives up, deliberately, is the ability to recognise one specific visitor across two different sessions. There is no profile building up behind the scenes to consent to in the first place, which is exactly why no banner is needed: nothing is being stored that identifies a person.
That is a real trade-off, not a free upgrade. A business that genuinely needs to track an individual customer’s journey across visits (a login-based product, for instance) is asking a different question than “how is our traffic and content doing,” and cookieless analytics is not built to answer it.
The numbers a cookie banner hides
Here is what a cookie-based tool is actually missing, not in theory: cookie rejection alone can hide around a third of real visitors from a tool that depends on consent, before bots are even excluded. Every one of those visitors is real traffic, on the site, doing something. A report built only from cookie-based analytics is working from an undercount of its own audience, and it is the visitors who cared enough to think about the cookie prompt (rather than not noticing it) who are the ones going missing.
What it showed for a real client
A Bordeaux tanning studio had a website and an active social presence, but the numbers behind both were thin: pageviews and follower counts, with little sense of who was actually interested or which content was landing. Reading the same traffic through a cookieless platform surfaced the detail that had been missing, not just how many people showed up, but which pages and content were actually earning attention. That is what now shapes what the studio posts and promotes, instead of guesswork.
Where this fits
This is the platform behind Doppio’s own analytics work: SEO decisions, campaign attribution and content strategy all get checked against it, for the same reason it mattered for the tanning studio. If your own reporting is running on a tool that needs a cookie banner, that gap is worth knowing about before the next decision gets made from it.