When Cloudflare Web Analytics isn't enough

Cloudflare Web Analytics is free, stores nothing in the browser and measures page speed well. It also drops UTM tags, counts arrivals rather than people and keeps six months of data, and each of those gaps points to a different kind of replacement.

7 min read

Summarize with

In this article
  1. 1First, check which Cloudflare numbers you mean
  2. 2What Cloudflare Web Analytics does well
  3. 3What it leaves out
  4. 4Visits aren't visitors
  5. 5Match the gap to the tool
  6. 6Before you switch

Cloudflare Web Analytics is free, sets no cookies and, if your site already runs through Cloudflare, takes a few clicks to switch on. That makes it an easy first choice for a small site. It's also easy to outgrow, and the reason is often one specific thing it doesn't do.

Before you move, it's worth naming that thing. Some of the gaps are real limits of the product. Others come from reading the wrong Cloudflare dashboard, and a new tool won't fix those. Everything about Cloudflare below comes from its own documentation, as of November 2026. Cloudflare updates the product regularly, so check the current docs before you decide.

First, check which Cloudflare numbers you mean

Cloudflare shows traffic in two places, and they count different things.

Web AnalyticsYour domain's Analytics tab
How it countsA JavaScript beacon that runs in the visitor's browserRequests that reach Cloudflare, for sites proxied through it
Bots and crawlersMostly missing, since they rarely run JavaScript, and there's an Exclude Bots filterIncluded. On the Free plan, Cloudflare says the numbers include crawlers and threats
PeopleVisits and page views, with no unique-visitor countUnique visitors, based on unique IP addresses
Ad blockersCan block the beacon, which Cloudflare acknowledgesCan't block it, because every request is counted

Cloudflare's own documentation says the visitor numbers on the Analytics tab will probably be higher than what other analytics services report. So if the problem is that Cloudflare shows far more visitors than anything else, you're almost certainly looking at that tab. The explanation is in why no two analytics tools agree, and switching tools won't change it.

The rest of this article is about Web Analytics, the beacon.

What Cloudflare Web Analytics does well

Setup in a few clicks

On a site proxied through Cloudflare, adding it under Web Analytics turns on automatic setup, which injects the beacon for you. Cloudflare Pages projects have a switch that adds it on the next deployment. Anywhere else, you paste one script tag into your pages.

Nothing stored in the browser

Cloudflare says the beacon uses no client-side state, such as cookies or localStorage, and doesn't fingerprint visitors by IP address or user agent. It describes the product as free and privacy-first.

Page speed from real visits

It reports Largest Contentful Paint, Interaction to Next Paint and Cumulative Layout Shift, rated against Google's thresholds. It splits LCP and INP into their phases and lists the page elements that hurt each score most.

Single-page apps

It notices route changes on its own, using the browser's Soft Navigations or Navigation API where they exist and the History API where they don't.

You can also filter by country, path, referrer, device, browser and operating system, and get a weekly summary email with visits, page views and median load time. If a free, cookie-free count of page views plus a clear view of page speed is all you need, there may be nothing to switch to.

What it leaves out

These are the limits in Cloudflare's own FAQ and limits pages. Two of them, UTM tags and custom events, are marked “not yet”, so they may change.

LimitWhat it means in practice
No query strings, so no UTM tagsCloudflare doesn't log query strings, to avoid collecting potentially sensitive data. A link tagged with utm_campaign is counted by its referrer alone, or as direct traffic if there is none. Links in newsletters, PDFs and chat apps often arrive with no referrer, so those campaigns blur into one another.
No custom eventsYou can't count signups, button clicks or purchases. Cloudflare says it may add this later.
Sampling after seven daysBeacon data is kept unsampled for seven days, then aggregated down to around 10%. Dashboard and API queries also pick a sampling level based on your filters and the amount of matching data.
Six months of historyCloudflare gives access to the previous six months only, so you can't compare this spring with last spring.
Ten sites, unless proxiedSites not proxied through Cloudflare have a soft limit of ten per account, which support can raise. Proxied sites have no limit.
Rules need a proxied site and a paid planRules that include or exclude hostnames and paths only work on proxied sites, and the Free plan allows none. Automatic setup then measures every subdomain in the zone, including a staging subdomain if you have one.
Referrers by site, not by pageThe dashboard shows which site sent a visit. The page on that site is only available through the GraphQL API.

The query-string limit matters more than it looks. It also covers any utm_source tag on a link that an AI assistant shows, so those visits can only be recognised by their referrer, when the browser sends one. There's a separate guide on finding visits from ChatGPT and other assistants in any tool.

Visits aren't visitors

This gap is easy to miss. Cloudflare defines a visit as a page view whose referrer doesn't match your hostname: someone arrived from another site, or from no site at all. Page views after that, inside your site, belong to the same visit.

There's no person in that definition. Someone who finds you through search in the morning and comes back from a bookmark at lunch is two visits. Most other tools report unique visitors as well, and they get there in one of two ways:

  • A cookie. Google Analytics keeps an ID in its _ga cookie, which lasts two years by default. It recognises a returning browser, and in the EU that normally means asking for consent first.
  • A daily key. Many cookie-free tools combine a few details of the request with a value that is thrown away every day. One person counts once per day, and the tool can't link them from one day to the next.

Neither will line up with Cloudflare's visits. When you compare tools, compare page views, which they all count in roughly the same way.

A visit in Cloudflare Web Analytics is an arrival, not a person. Read every number on its dashboard with that in mind.

Match the gap to the tool

You probably don't need a tool that does everything. You need one that fills the gap you actually have.

If you're missingLook for
Campaign tagsA tool that records utm_source, utm_medium and utm_campaign. Google Analytics and Umami both do, per their docs. A naming convention keeps the reports readable.
A count of peopleA unique-visitor count, and a plain statement of how it's counted: a cookie or a daily key.
Signups and purchasesCustom events or goals, and funnels if you want to see where people drop off. Google Analytics, Matomo, Plausible and Umami all document custom events. Check the funnel docs of the one you pick, since plans and plugins differ.
More than six monthsA tool whose documentation states its data retention and whether it samples. Read both before you move.
Data on your own serversA self-hosted tool. Matomo On-Premise, Plausible Community Edition and Umami are open source and can run on your own server.
Visitors who block scriptsAnother script won't reliably fix this, because blockers list many analytics scripts, not just one. Only server-side counts avoid it, like Cloudflare's own edge numbers, bots and all.

Page speed is the one thing worth keeping Cloudflare for after you add something else. Nothing stops you running its beacon for Core Web Vitals next to a second script for traffic. If your site sends a Content Security Policy, both need entries. For Cloudflare that means static.cloudflareinsights.com in script-src, plus cloudflareinsights.com in connect-src with manual setup, or 'self' with automatic setup.

Before you switch

  1. Check how the beacon is set up. Automatic setup can be set to skip visitors in the EU, which makes the numbers look low for a European audience. A Cache-Control: public, no-transform header stops Cloudflare injecting the beacon at all.
  2. Know whether it's automatic or manual. Automatic setup covers every page and subdomain in the zone. Manual setup only covers the pages with the snippet. The same site can show more under automatic.
  3. Write down a baseline. Page views for the last full week, from Web Analytics, not the Analytics tab.
  4. Run both for two weeks. Compare page views day by day and note the ratio between the tools. A steady ratio means both are working, even if the totals differ.
  5. Check what the new tool stores. If it sets cookies, find out whether you now need a consent banner.
  6. Save what you want to keep. Cloudflare keeps six months, so note any figures you'll want later before they age out.
  7. Start a new trend line on the day you switch. Last month in Cloudflare next to this month in another tool shows a jump or a drop that is only the tools disagreeing.

Cloudflare Web Analytics is a good free tool with a narrow job. Most reasons to leave it are one of the gaps above, and each one points to a different kind of tool.


Lomen is one of the cookie-free, script-based tools described above. Beyond what Cloudflare Web Analytics shows, it reads UTM tags, counts unique visitors with a daily anonymous key, counts every pageview without sampling and recognises visits from nine AI assistants by referrer and by utm_source. It doesn't measure page speed, and it has no custom events, funnels or self-hosting. For page speed, keep Cloudflare running next to it. For events, funnels or your own servers, pick one of the tools above instead.

Numbers you can ask questions

Lomen is one cookie-free script: sources, campaigns and AI referrals on one dashboard, and an AI that answers from your own figures. Free during the beta, no credit card.