Guide · Privacy

Do you need a cookie banner for website analytics?

Cookie banners annoy readers, and plenty of people click No, which leaves holes in your stats. Whether you need one for analytics depends on the tool you use and where your readers are. This is the plain English version of the rules for the UK and the EU.

By Paul O’Brien, who makes ReaderCount

This guide explains the rules as I understand them, for people running blogs and small websites. It isn't legal advice. If your site handles a lot of personal data, check with the ICO in the UK or your own country's regulator in the EU.

The short answer

What you useUKEU
Google Analytics or other stats that set cookiesUsually yes, because Google also uses the data for its own purposesYes, in almost every country
Your own first-party stats that set cookies, only to improve your siteOften no, under the new statistics exception, but you must let people opt outUsually yes, with a few national exceptions
Cookie-free stats that store nothing on the reader's deviceNo banner for the statsNo banner for the stats in most cases

A banner is about what your site stores on, or reads from, the reader's device. Other things on your pages, such as adverts, embedded videos or social buttons, may need one even if your stats don't.

The rule behind cookie banners

The banner rule isn't really about cookies. In the UK it's in the Privacy and Electronic Communications Regulations, known as PECR, and in the EU it's in the ePrivacy Directive. Both say the same thing at heart: you need the reader's consent before you store anything on their device or read anything from it, unless it's strictly necessary for something they asked for.

That covers cookies, local storage, tracking pixels and fingerprinting alike. A cookie that keeps someone signed in is strictly necessary. A cookie that counts them for your stats traditionally isn't, which is why analytics needed consent and why banners appeared everywhere.

Data protection law, the UK GDPR and the EU GDPR, sits alongside this. It applies to personal data however you collect it, cookies or not, and needs a lawful reason such as legitimate interests. For simple stats that don't identify anyone, that part is usually straightforward.

The UK since 2026

The Data (Use and Access) Act 2025 changed PECR, and the changes to the cookie rules came into force in early 2026. The ICO has published guidance on them. The one that matters for bloggers is a new exception for statistics.

You can now store or read information on a reader's device without consent if the only purpose is to collect statistics about how your site is used, so you can improve it. The conditions, in short:

  • It must be the sole purpose. If the same cookie also feeds advertising, or the provider uses the data for its own ends, the exception doesn't apply and you need consent.
  • You must tell people clearly what you're doing, usually in your privacy or cookie policy.
  • You must give them a simple way to object, such as an opt-out link, and respect it.
  • Advertising is never covered. Ad and remarketing cookies still need consent.

The ICO's guidance says a third-party analytics provider should be acting for you, not using the data for itself. That's the sticking point for Google Analytics, where Google can use the data for its own purposes too. Check the ICO's page on the exceptions before you drop your banner.

The EU

Nothing equivalent has become law across the EU yet. Under the ePrivacy Directive, analytics cookies still need consent in most countries. A few regulators, France's CNIL being the best known, let you measure your audience without consent if you meet strict conditions: first-party only, statistics only, no cross-site tracking and limited data kept.

The EU has proposed changing the rules as part of what it calls the Digital Omnibus, including a consent exception for simple audience measurement. At the time of writing that's still being negotiated and isn't in force, so plan on today's rules.

Which tools need a banner

Type of toolExamplesStores anything on the device?Banner for stats?
Advertising-linked analyticsGoogle AnalyticsYes, cookiesYes in the EU; in the UK, usually yes
Self-hosted analytics with cookiesMatomo with cookies onYes, first-party cookiesEU: usually yes; UK: may fall under the statistics exception
Cookie-free analyticsPlausible, Fathom, Simple Analytics, ReaderCount, Matomo with cookies offNoGenerally no
Server logsYour web host's statisticsNoNo, but they count robots as visitors

A cookie-free stats tool has to tell one reader from another without leaving anything on their device. Most do it the same way. When a page loads, the server mixes a few things it already receives, such as the reader's internet address and browser, with a secret value that changes every day, and turns the result into a scrambled code. Visits with the same code that day count as one visitor.

Done properly, the internet address is never stored, the code can't be turned back into it, and the daily change means nobody can be followed from one day to the next. The trade-off is that someone who reads you on Monday and again on Tuesday counts as a visitor on each day, and there's no way to say they came back.

For a blog, that trade-off is usually worth it. You lose a returning visitors figure. You gain stats on every reader, including the ones who would have clicked No on a banner, and a site with no pop-up in the way.

A checklist for your site

  1. List everything that loads on your pages: stats, adverts, embedded videos, social buttons, chat widgets and fonts. Your browser's developer tools show what each page loads.
  2. For each one, ask whether it stores or reads anything on the reader's device. Most tools say so in their documentation.
  3. Swap what you can for versions that don't, such as cookie-free stats or privacy-enhanced video embeds.
  4. Write it down in your privacy policy: what you use, why, and how readers can object.
  5. Keep a banner only for what still needs consent, and make No as easy as Yes.

Where ReaderCount fits

I built ReaderCount to count readers without cookies, local storage or anything else on their device, using the daily scrambled code described above. Internet addresses are only used to make that code and are never stored. It also leaves out robots and cloud servers, so the figures are people. The cookie-free counting guide explains exactly how, and the privacy policy lists what's kept. It's free to use.

Questions

If my stats are cookie-free, do I still need a privacy policy?

Yes. You should still say which stats tool you use and what it collects, even if it collects very little.

Does a cookie-free tool count more readers than Google Analytics?

Usually, yes. Readers who refuse cookies, and many who use ad blockers, never show up in Google Analytics. The guide to why the numbers differ goes into this.

Is fingerprinting the same as cookie-free?

No. Fingerprinting builds a lasting identity from lots of details about a device, so it can follow someone around. Regulators treat it like a cookie, and it needs consent. A daily code that can't be reversed and resets every day is a different thing.

My site is in the UK but most readers are in the EU. Which rules apply?

Generally the rules where your readers are. If a lot of your readers are in the EU, plan for the EU rules.

Sign up freeSee the live demo

Free for one website. No card needed.