---
title: Cookieless analytics: what you can measure without a banner
description: What European cookie rules actually require, when visitor statistics can run without consent, and what you give up when analytics stop using cookies.
url: https://ironhelmsuite.com/blog/cookieless-analytics/
---

# Cookieless analytics: what you can measure without a banner

What European cookie rules actually require, when visitor statistics can run without consent, and what you give up when analytics stop using cookies.

Published 2026-06-17 in Analytics.

Many site owners added a cookie banner because "the law says so" and then watched half their visitors vanish from Google Analytics, because people who decline are not counted. That leaves two bad options: pressure people into clicking Accept, or run the business on a guess.

There is a third option for the basic questions, and it is worth understanding what the rules actually say before deciding.

## What the rules require

In the European Union the relevant rule is Article 5(3) of the ePrivacy Directive. It is not really about cookies. It requires consent before a site *stores or reads information on the visitor's device*, unless that is strictly necessary for a service the visitor asked for. Cookies, local storage and device fingerprinting all fall under it.

The GDPR then governs what you do with personal data such as IP addresses, whether or not anything is stored on the device.

## When analytics can run without consent

Regulators have recognised that a site counting its own visitors is not the same as advertising tracking. France's CNIL publishes the most precise guidance: audience measurement can be exempt from consent if, among other conditions:

- it serves only the site's own audience measurement, producing anonymous statistics;
- the data is not combined with other processing or passed on, and the analytics provider does not reuse it;
- visitors are told about it and can object;
- trackers have a limited life, with the CNIL suggesting 13 months.

The CNIL also says plainly that most large analytics offerings do not fall within the exemption, whatever settings you choose. Rules and their interpretation differ between countries, so treat this as an orientation, not legal advice.

## How cookieless counting works

A cookieless counter stores nothing on the visitor's device. When a page loads, a small script sends the page address, the referrer and basic facts like screen size. On the server, visits are grouped without a persistent identifier, often with a short-lived hash that changes every day, so the same person cannot be followed across days.

That answers most of what a business owner asks:

- How many people visited, and which pages they read
- Where they came from: search, social, other sites, email, and now AI assistants
- Which campaigns and links brought visitors
- Phones versus desktops, and which countries

## What you give up

Honesty matters here. Without a persistent identifier you lose:

- **Returning visitors over long periods.** You know how many visits there were this week, not how many of them came back from last month.
- **Cross-device journeys.** Someone who reads on a phone and buys on a laptop counts as two visitors.
- **Advertising audiences and remarketing.** Those need consent anyway.

For most small and medium sites, those losses are smaller than the hole consent banners already leave in cookie-based data.

## In Ironhelm

Visitor statistics count visitors without cookies and keep the data in your own WordPress database. They leave out bots and, if you choose, logged-in people, show sources including AI assistants, and keep daily statistics for as long as you set. When you do run advertising tags, the consent banner asks first, records each answer and passes it to Google Consent Mode.

## Sources

- EUR-Lex, [Directive 2002/58/EC (ePrivacy Directive), Article 5(3)](https://eur-lex.europa.eu/legal-content/EN/ALL/?uri=CELEX:32002L0058)
- CNIL, [Sheet n°16: Use analytics on your websites and applications](https://www.cnil.fr/en/sheet-ndeg16-use-analytics-your-websites-and-applications)
- European Data Protection Board, [Guidelines 2/2023 on the technical scope of Art. 5(3) of the ePrivacy Directive](https://www.edpb.europa.eu/our-work-tools/documents/public-consultations/2023/guidelines-22023-technical-scope-art-53-eprivacy_en)
