Cookieless analytics and EU cookie banners: what actually changes

What cookieless analytics changes for EU cookie banners: the ePrivacy rule, how France, the Netherlands and the UK treat analytics, and the 2026 EU plan.

Wholetally team Blog

Short answer

Cookieless analytics changes what your cookie banner has to cover, not whether the law applies. In the EU, the consent rule is about storing or reading information on a visitor’s device, and the GDPR applies to any personal data you collect. A tool that sets no cookies, uses no local storage, creates no visitor ID and keeps no IP addresses often means no consent banner is needed for the analytics itself. That depends on your country and setup; check with your legal advisor. Your banner may still be needed for ad pixels, chat widgets or embedded videos.

What is cookieless analytics?

Cookieless analytics counts visits without leaving anything behind in the browser. Classic Google Analytics sets a cookie with a random client ID, so it can recognise the same browser on the next visit. A cookieless tool skips that step. It receives a small request per pageview, keeps the page, the referrer, the country and the device type, and adds those up into daily totals.

The term is used loosely, so look for four separate properties:

  • No storage on the device. No cookies, and also no localStorage, sessionStorage or IndexedDB, which can do the same job as a cookie.
  • No persistent identifier. No user ID, device ID or browser fingerprint that follows a person across days or sites.
  • Minimal server data. IP addresses dropped or never stored, query strings trimmed, and no data shared with an ad network.
  • Aggregated output. Reports on pages and sources, not on individual people.

A tool can be cookieless on the first point and still fingerprint browsers on the second. That is why the label alone does not answer the banner question.

Why do EU sites show cookie banners for analytics at all?

Because of Article 5(3) of the ePrivacy Directive. It says that storing information on, or reading information from, a user’s device is only allowed with consent, unless it is strictly necessary to transmit a communication or to provide a service the user explicitly asked for. Every EU country wrote this into its own law, which is why the details differ from country to country.

Analytics is useful for the site owner, but it is not what the visitor asked for. So in most countries, analytics that sets cookies has to wait for a click on “accept”. The GDPR sits on top of that: it sets the bar for what valid consent is, and it applies to any personal data you process, cookie or not.

Does the rule only cover cookies?

No, and this is the part many “no banner” promises skip. The European Data Protection Board adopted Guidelines 2/2023 on the technical scope of Article 5(3) in October 2024. They say the rule is technology-neutral. Tracking pixels, tracking links, unique identifiers and some forms of IP-based tracking can fall under it, even when no cookie is set, because the site instructs the browser to send information back.

In plain terms: removing cookies helps, but a JavaScript tag that sends data from the visitor’s browser can still be inside the scope of the rule. What then matters is whether an exemption applies, and that is where national regulators differ. The questions they ask are about purpose and data: is it only for your own audience measurement, are the results anonymous and aggregated, and does anything leave for other uses?

How do France, the Netherlands and the UK treat analytics?

Three regulators show the range. None of this is legal advice; it is what their own guidance says.

  • France (CNIL). Audience-measurement trackers can be exempt from consent if they serve only to measure the audience of the site for the publisher, produce anonymous statistics only, do not track people across sites and are not combined with other data or passed to third parties. The CNIL also recommends telling visitors in your privacy policy, and keeping data for at most 25 months. It notes that tools whose vendor reuses the data for its own purposes fall outside the exemption.
  • Netherlands (Autoriteit Persoonsgegevens). If you only use functional and limited analytical cookies, you do not have to ask for consent, according to the AP’s banner rules of thumb. You must still inform visitors, make it easy to object, and base any personal data processing on legitimate interest.
  • United Kingdom (ICO). Since the Data (Use and Access) Act 2025, UK rules include a “statistical purposes” exception: storage or access only to collect statistics about how your service is used, with a view to improving it. You must give clear information and a simple, free way to object.

Germany, Austria and other countries apply their own versions, and their regulators read the exemptions in their own way. A setup that is fine in Amsterdam may need a different answer in Munich. That is the reason every honest answer to “do I need a cookie banner” ends with: it depends on your country and setup; check with your legal advisor.

What is changing in the EU in 2026?

The European Commission proposed the Digital Omnibus in November 2025. Among many other things, it would add consent exemptions for cookies and similar techniques, including one for audience measurement. On 21 October 2026 the Council agreed its negotiating mandate. It keeps the cookie rules in the ePrivacy Directive and lists purposes that need no consent, among them first-party audience measurement that creates anonymous, aggregated information about the use of a service, also when a vendor does it on the site’s behalf, as long as the data is not used for other purposes, shared or combined with third-party data.

This is a direction, not the law. The European Parliament still has to adopt its position, then the three institutions negotiate, and the Council text gives member states time to transpose the result. Until then, today’s national rules apply. The direction does tell you what regulators care about: first-party, aggregated, anonymous and single-purpose. Picking a tool that already works that way is a reasonable bet either way.

What actually changes when you switch to cookieless analytics?

Four practical things, assuming your advisor agrees your setup qualifies for an exemption in your country:

  1. The banner gets smaller, or goes away. If analytics was the only reason for your banner, you may be able to remove it. If you also run Meta or Google Ads pixels, YouTube embeds or a chat widget, the banner stays, just with one category fewer.
  2. Your numbers go up. Behind a banner, GA4 only sees visitors who click “accept”, plus modelled data if you use Consent Mode. A cookieless tool without a consent gate counts the people who would have declined. Expect a jump on the day you switch, and compare trends, not totals.
  3. Returning visitors become fuzzy. Without a stored ID, a tool cannot know for sure that Monday’s visitor came back on Friday. Unique visitors are estimated per day or per visit, not across months. Cohorts and long user journeys are where cookieless tools are weakest.
  4. Your privacy notice still needs an update. Describe the tool, what it collects, where the data is stored and how to object. Regulators in France, the Netherlands and the UK all expect visitors to be informed.

How do you check whether your analytics setup qualifies?

Run through this list with your vendor’s documentation open, then bring the answers to your legal advisor:

  • Does the script set cookies or use localStorage, sessionStorage or IndexedDB? Check in your browser’s developer tools.
  • Does the vendor create a user, device or browser ID, or a fingerprint? How long does any hash live?
  • Are IP addresses stored, truncated or never kept?
  • Is the data used only for your site’s statistics, or also for the vendor’s own products or advertising?
  • Is data combined across sites or with other data sources?
  • Where is the data stored, and which subprocessors handle it?
  • Is there a data processing agreement, and can visitors object in a simple way?
  • Which other scripts on your site still set cookies or load third-party tags?

If the vendor cannot answer these on a public page, that is an answer too. For comparison, our what we collect page lists every field the Wholetally script and edge collector send, what is stored, and what is never stored. Our cookie statement covers the website itself.

How does Wholetally handle this?

Wholetally is built around the conditions regulators keep coming back to. The script sets no cookies and uses no localStorage, sessionStorage or other device storage. It creates no visitor, user or device ID and does not fingerprint browsers. IP addresses are not stored; when you serve the script through the first-party proxy, they do not reach us at all. Page URLs are trimmed to the path and UTM tags. Data is not sold or used for advertising, and the analytics database sits in Cloudflare’s EU jurisdiction. The script is open source under the MIT licence, so you or your advisor can read every line.

There is an optional daily hash mode for better unique-visitor counts within one day. It is off by default, uses a salt that is thrown away every 24 hours, and the strict compliance mode does not allow it. If you want the smallest possible footprint, leave it off.

Cookieless does not mean blind. The edge collector for Cloudflare or Vercel counts page loads on the server side, which also catches visitors whose ad blocker stops the script and AI crawlers such as GPTBot. And because there is no consent gate on analytics, the dashboard is not missing the share of people who would have clicked “decline”. Whether you can run it without a banner in your country is still a question for your legal advisor; we give you the facts to answer it.

If you are still choosing a tool, our guide to the best Google Analytics alternatives for EU sites compares the usual shortlist, and the comparison table goes row by row.

What to do next

Open your site with developer tools, list every cookie and tag, and write down which ones exist only for analytics. That is the part cookieless analytics can replace. Then try Wholetally next to your current setup for a month: new accounts get a 30-day trial, no card needed. See plans on Pricing, or go straight to the app sign-up linked from there.

Wholetally is cookieless web analytics with an AI report, edge collection and revenue per source. Built in the Netherlands. This article is general information, not legal advice. Regulator guidance and the Digital Omnibus status were checked on 13 November 2026 and may change.

FAQ

What is cookieless analytics?
Web analytics that counts pageviews, sources and events without setting cookies or using local storage on the visitor’s device. It usually also avoids visitor IDs and fingerprinting, and reports aggregated numbers instead of profiles of individual people.
Do I need a cookie banner if my analytics is cookieless?
Often no consent banner is needed for the analytics itself, but that depends on your country and setup; check with your legal advisor. The ePrivacy rule covers reading and storing information on a device, not only cookies, and the banner question covers every script on your site, including ad pixels and embeds.
Is cookieless analytics automatically allowed under the GDPR?
No. The GDPR applies whenever you process personal data, with or without cookies. A cookieless tool that stores no IP addresses and no visitor IDs keeps that processing small, but you still need a legal basis, a privacy notice and a processing agreement with the vendor where personal data is involved.
Does the EU Digital Omnibus remove cookie banners for analytics?
Not yet. In its 21 October 2026 mandate the Council proposed a consent exemption for first-party audience measurement that produces anonymous, aggregated statistics. The European Parliament still has to adopt its position and negotiations follow, so the current national rules keep applying.
Will cookieless analytics show more visitors than GA4?
Usually yes, when GA4 runs behind a consent banner. Visitors who decline are not counted by GA4 unless you rely on Consent Mode modelling, while a cookieless tool without a consent gate counts them. Ad blockers and visitors without JavaScript still create gaps unless you also collect at the edge.
What should I check before removing my cookie banner?
List every script that runs on your site, check which ones store or read anything on the device, read what your analytics vendor collects, and ask your legal advisor how your national rules treat analytics. Remove the banner only for what it no longer has to cover.

Sources

Count the visitors you’ve been missing.

30-day free trial, no card needed. Create an account with your email and add your first site.

Start 30-day trial