Count visits without cookies
A business needs to know whether its site is being read. It doesn't need to follow anyone to find out. Start with a count that asks nothing of the visitor, and add more only when there's a reason.
Three ways to count, least intrusive first
| Way | What it tells you | What it asks of the visitor | Banner |
|---|---|---|---|
| 1. A cookie-free script (Umami) | Page views, visits, where people came from, which pages, and counts of things done: an enquiry sent, a page printed | Nothing. No cookies, no personal data, and it honours Do Not Track | None |
| 2. The host's own count (Cloudflare, shown in Somnia CMS) | Page views and visits by day, country, page, device and hour, and which programs are reading the site | Nothing. There is no script on the site at all | None |
| 3. Google Analytics | What the business's other tools expect: advertising, conversions, a dashboard it already uses | Consent. It sets cookies | Yes: the cookie banner |
How it works
- Every site starts with the first. One setting (
analytics.umami). It loads only on the live site, so the studio's and the client's own visits to staging aren't counted. - A site on Cloudflare gets the second for nothing. Somnia CMS's Visitors page shows it to the people who run the site, where they already are, with no other account to sign in to.
- The third is added only when the business needs it (
analytics.ga). Then, and only then, the banner appears, with Accept all and Reject all given equal weight. Nothing from Google loads until Accept. The choice is asked for again after twelve months, and can be changed at any time from Cookie settings in the footer. - The legal pages write themselves from the same settings. The cookie and privacy pages describe what that site really uses, so they can't fall out of step with it.
People, not programs
A host counts every request, and most requests aren't people. On Headland's holding page, a week's 566 page requests were about 55 people. Somnia CMS counts a request as a person only when it is a current browser, on a modern connection, that also loaded the page's styles; everything else is listed apart, by name where it gives one (search engines, AI assistants, link previews, scanners). It is a rule of thumb, and the page says so.
What a cookie-free count can't tell you
- Whether two visits were the same person.
- Anything about a person beyond country and kind of device.
- From the host's count alone: where visitors came from.
For most small businesses that is enough to answer the real questions: is anyone reading, which pages, and did they get in touch.
Do and don't
Do
- Count what the site is for: enquiries sent, not just pages viewed
- Say on the privacy page exactly what is counted and by whom
- Give Reject the same size and place as Accept
Don't
- Add Google Analytics "in case"
- Load anything that sets a cookie before consent
- Quote a host's raw request count as visitors
Accessibility
- With no banner there is nothing to dismiss before reading. That is the most accessible consent design there is.
- Where there is a banner, see the cookie banner's own page for its keyboard and screen reader behaviour.
- The Visitors page writes every figure beside its mark and never tells two things apart by colour alone.
Evidence
Where it's used
| Where | For |
|---|---|
| mediadreams.co.uk | Umami only. No cookies, so no banner. |
| Headland Yachting | Umami, and Google Analytics behind the cookie banner. Its visits as Cloudflare served them are in Somnia CMS’s Visitors page. |
What we saw, and what changed
| When | What we saw | What changed |
|---|---|---|
| Somnia counted visits with Umami only, and a client site may need Google Analytics. | It is a setting beside Umami. The banner, a Cookie settings link and the wording of the cookie and privacy pages appear only on sites that turn it on (1.18.0). | |
| Cloudflare’s own count for Headland was ten times Umami’s: 566 page requests in a week against 48 page views. Most were programs, many calling themselves browsers. | A request counts as a person only if it is a current browser, on a modern connection, that also loaded the page’s styles. That left 55, against Umami’s 48. | |
| Fourteen days showed fewer visits than seven. Over a long period Cloudflare answers from a sample, and small groups vanish. | Every question is asked a week at a time and added up. | |
| Umami’s free plan has no way for another program to read its figures, so Somnia CMS could not show them. | The CMS shows the host’s count instead; Umami keeps its own dashboard. |
From building and using it on real sites, each entry taken from the changelog or the build's own notes. This is observation by the studio and its clients, not research sessions with users.
What we don't know yet
- The rule for telling people from programs is a rule of thumb, checked against one site for one week.
- Where visitors came from is not known to the host’s count: the plan doesn’t give referrers.