Guide

Web analytics that does not need a cookie banner

The banner is not required by analytics. It is required by storing something on the visitor's device, and by what you then do with it. Both are choices a tool makes for you.

Updated

Where the banner comes from

In the EU, consent is tied to reading or writing information on somebody's device, whatever that information is, and separately to processing personal data under the GDPR. A tool that drops an identifier in a cookie or in local storage is doing the first. A tool that builds a profile which follows somebody between sites is doing the second.

An analytics script that does neither has nothing to ask permission for, which is why several products in this category ship with no banner at all. The question to ask any of them is not "are you GDPR compliant", which is a sticker, but "what exactly do you store, where, and for how long".

How a cookieless visitor id works here

There is no cookie by default and nothing is written to the browser. A visitor is a hash of their IP address, their user agent and the site they are on, salted with a secret that rotates every day.

Three consequences follow from that, and they are the whole trade. Nobody can be followed from one day to the next, because yesterday's salt is gone and the same person hashes to a different id this morning. Nobody can be followed between two sites, because the site is part of the hash. And there is no identifier to hand over or to leak, because what is stored cannot be turned back into an IP address by us or by anyone who takes the database.

The IP address itself is never written anywhere. It is an ingredient of a hash and is gone before the row is stored.

What you give up

A returning visitor is a new visitor the next day. Cohort retention and "how long from first visit to payment" are still measured, because a payment carries the visit it belongs to, but the day boundary is real and it is the price of the property above.

If cross-day identity matters more to you than that property, there is a per site switch for a first-party cookie, which changes the trade deliberately and tells you that it has. A tool that does this quietly is the one to be suspicious of.

The second thing you give up is nothing to do with privacy: ad blockers stop a third-party script whatever it stores. Serving the script from your own domain with one rewrite rule recovers most of those visits, and the instructions are on the install page.

What to check in any tool, including this one

Does it set a cookie or write to local storage, by default and not after you change a setting. Does an identifier survive across sites. Is the raw IP address stored anywhere, including in logs. Where does the data physically live, and what is the retention. Can you export everything and delete everything, without asking.

Those five answers decide whether you need a banner far more reliably than any badge on a pricing page. Ours are on the privacy page, written as mechanics rather than as reassurance.

What that looks like

The dashboard this is describing

Live demo, real queries, generated traffic. No sign-up.

NNimbus ‹Last 30 days ›Daily LiveUpdated just now
Visitors
5,221
540% ↑
Revenue
$6,987
710% ↑
Conversion rate
1.02%
18% ↑
Revenue/visitor
$1.34
27% ↑
Bounce rate
61%
0% ↓
Session time
1m 15s
3% ↑
Online
12
View on map →
ChannelReferrerCampaignKeyword
Visitors · Revenue
  • Organic Social2,412$3,120
  • Direct1,072$1,240
  • Referral771$960
  • Organic Search720$580
  • AI246$310
CountryRegionCity
Visitors · Revenue
  • 🇺🇸United States885$2,410
  • 🇮🇳India887$140
  • 🇬🇧United Kingdom427$980
  • 🇩🇪Germany427$760
  • 🇧🇷Brazil451$210

Questions

Is this legal advice?

No. It is a description of what the software does, which is the input to a decision your own counsel makes. Jurisdictions differ, and so do the other scripts on your page: one ad pixel elsewhere in your HTML can put you back in banner territory regardless of what your analytics does.

Does a cookieless setup still let me see a customer's journey?

Yes, within the day for the browsing, and across the whole history for the money. A payment is attached to the visit that produced it, and a customer's payments, goals and the visits they came from are on one screen. What you lose is linking two anonymous browsing sessions on different days to the same person.

What about the Do Not Track and Global Privacy Control headers?

Neither is read. Both signals were written for advertising profiles and the sale of data; cookieless analytics stores nothing on the device and sells nothing, so there is nothing for them to opt out of, and Plausible, Fathom and DataFast ignore them for the same reason. A person who wants out of one site visits it once with ?ml_ignore=true and is never counted there again.

Stop guessing which traffic pays.

Add the script, connect the payments you already take, and every channel on the dashboard carries the revenue it produced.

14 days free · no commitment · cancel anytime