Skip to main content
← Back to the blog

Guides

Cookieless web analytics: what it measures and what you lose

Published November 5, 2026 · 8 min read

FFlowgrationGUIDESCookieless web analytics:what it measures and whatyou lose

"Cookieless analytics" sounds like the perfect answer: you measure your site, you don't bother visitors with yet another banner and the legal question goes away. Reality is more nuanced. Measuring without cookies is possible and useful, but it costs you some of what you can know, and it does not automatically exempt you from informing visitors or, in some cases, from asking for consent.

This guide is for small businesses deciding between cookieless measurement and measurement with consent. It covers what you get, what you lose and how to decide.

Key takeaways

  • Without cookies you can count page views, scroll depth, clicks per page, form submissions and custom events, all anonymously.
  • You lose everything that needs to recognise the same person: sessions, bounce rate, unique visitors, funnels, live visitors and contact identification.
  • No cookies does not mean no consent: European guidance on Article 5(3) of the ePrivacy Directive also covers other ways of accessing a device. Disclose it and check with your adviser.
  • If you want to know which pages work, cookieless is usually enough. If you want to know who visits and what they did before getting in touch, you need consent mode.

What does "cookieless analytics" mean?

Cookieless web analytics stores no identifier in the visitor's browser: no cookies, no local storage, no number that would recognise them on the next page. Each page view reaches the server as a standalone fact: "someone saw this page, on this kind of device, and scrolled halfway".

That has a clear upside: the data cannot be attributed to a specific person. And an equally clear downside: you can't join up the pages one person saw either.

Some tools call "cookieless" techniques that still recognise the visitor by other means, such as combining browser characteristics. Always ask which identifier a tool uses, if any.

What can you measure without cookies?

MetricCookielessWith consent
Page views per pageYesYes
Scroll depth (25, 50, 75 and 100%)YesYes
Clicks and heatmaps per pageYes, aggregatedYes
Form submissions per pageYesYes
Custom eventsYesYes
Sessions, bounce and exitsNoYes
Unique and new visitorsNoYes
Session-based source reportsNoYes
Conversion funnelsNoYes
Live visitorsNoYes
Identifying a contact and seeing their historyNeverYes, if they consented
Journeys and segments based on visitsNoYes, for identified contacts

The left-hand column answers questions like "which pages get read?", "do people reach the price?" or "which button gets clicked most?". It doesn't answer "how many different people came?" or "what did this lead do before asking for a quote?".

What exactly do you lose?

Sessions and everything built on them

A session is the sequence of pages one person sees in one visit. Without an identifier there is no way to know that the pricing page and the contact page were seen by the same person. So bounce rate, exit pages, visit duration and funnels all disappear.

Unique visitors

Without cookies, ten page views could be one person or ten. Tools that show "unique visitors" without an identifier are estimating, not counting.

Contact identification

This is the point that matters most for a business that sells through a CRM. In consent mode, when a visitor who accepted cookies submits a form, their browsing lands on the contact record and you can start journeys from their visits. In cookieless mode that never happens: the data stays at page level. If that part interests you, read how identifying website visitors and turning them into contacts works.

Not necessarily. The European rule that requires consent (Article 5(3) of the ePrivacy Directive, transposed into each EU country's law) is not only about cookies: it is about storing information on the user's device or accessing information already stored there. In 2023 the European Data Protection Board published guidelines (2/2023) explaining that the rule can also apply to techniques that don't use cookies.

In practice, for a small business this comes down to three things:

  1. Always disclose it. Explain in your privacy and cookie policy that you measure your site, with which tool and what is stored.
  2. Ask your adviser whether your specific case needs consent or can rely on an exemption. Each country's authority has its own view on analytics.
  3. Minimise. Keep only what you need, for as short a time as possible.

What does change without cookies is the risk: if you store no identifiers and delete raw data quickly, there is far less personal information to protect.

When does cookieless mode suit a small business?

It suits you if:

  • Your site is mostly informational and you want to know which content gets read.
  • You don't want to add another tool to your cookie banner, or your acceptance rate is so low you barely measure anything.
  • You won't use each contact's browsing in the CRM.

Consent mode suits you if:

  • You sell services or products and want to know what a lead looked at before getting in touch.
  • You want to send automatic emails when a contact visits a specific page.
  • You need funnels, bounce rate or session-based sources.

A sensible path is to start cookieless so you have data from day one, and move to consent mode when you need identification, with your banner properly set up. Keep in mind that data from one mode does not turn into the other: session history starts on the day you switch.

Checklist before you turn it on

  1. Decide which questions you want answered and check in the table that cookieless covers them.
  2. Add the tool to your privacy and cookie policy, even though it uses no cookies.
  3. Ask your adviser whether your case needs consent.
  4. Exclude sensitive page elements from measurement.
  5. After a week, check that the data actually helps you decide something.

Frequently asked questions

Is cookieless analytics anonymous?

In Flowgration, yes: no identifier is stored, events are kept with no visitor or session, IP addresses are not stored and raw data is deleted once aggregated, within 48 hours at most.

Can I have heatmaps without cookies?

Yes. Clicks are aggregated per page and device without knowing whose they are. Heatmaps depend on your plan (they start on Growth).

Do I need a cookie banner in cookieless mode?

The script writes no cookies, but that alone doesn't settle whether you need consent. Disclose it and confirm with your adviser. If you also run other tools that use cookies, you'll still need the banner for those.

Can I switch modes later?

Yes, the mode is chosen per site. Earlier data is not converted: sessions and identification start counting from the switch.

How Flowgration does it

Flowgration's web analytics has two modes per site. In cookieless mode no identifier is used, the server stores events with no visitor or session, never links anyone to a contact and deletes raw data as soon as it is aggregated (48 hours at most); daily roll-ups are kept for up to 26 months. URLs are stored without query strings, form field values are never read and the script switches off with Do Not Track or GPC.

You are the controller of your visitors' data. Settings includes sample policy texts in English and Spanish, matched to the mode you choose, which you should review with your adviser. Anonymous page analytics starts on the Essential plan; there is a free plan and a 14-day trial with no card on the pricing page. For consent mode, the guide to web analytics with consent and GDPR walks through the setup.

Build your WooCommerce CRM in 60 seconds

Flowgration turns your store's orders into a living CRM and runs email, SMS and WhatsApp on autopilot. Free up to 500 contacts.

Start free