Home/Cloudflare Web Analytics alternative

A Cloudflare Web Analytics alternative that keeps every visit

Cloudflare Web Analytics is free, cookie-free and one checkbox away if your site already sits behind Cloudflare. It is also, by its own documentation, sampled down to around 10 % after seven days, limited to six months of history, and unable to record a custom event or read a UTM parameter. Those three sentences decide whether you need something else.

Cloudflare figures read on its own documentation, September 2026.

In short: both are cookie-free and need no consent banner. Cloudflare wins on price (free) and, on proxied paid plans, on measuring visits that ad blockers would drop. Kipstats wins the moment you need exact numbers, events, campaigns, revenue, or a guarantee that the data stays in the European Union — which Cloudflare's own data-localization matrix does not give for Web Analytics.

Kipstats vs Cloudflare Web Analytics, line by line

Everything in the Cloudflare column comes from their documentation, including the parts that favour them.

Price

Kipstats

Free 1 site / 10K views, then 9€/mo

Cloudflare Web Analytics

Free on all plans

Cloudflare account required

Kipstats

No

Cloudflare Web Analytics

Yes

Cookies

Kipstats

None

Cloudflare Web Analytics

None

Sampling

Kipstats

None

Cloudflare Web Analytics

~10% beyond 7 days

History kept

Kipstats

No limit today

Cloudflare Web Analytics

6 months

Custom events

Kipstats

Yes

Cloudflare Web Analytics

No

UTM campaigns

Kipstats

Yes

Cloudflare Web Analytics

Query strings not logged

Revenue and purchases

Kipstats

Yes

Cloudflare Web Analytics

No

Server-side events

Kipstats

Yes

Cloudflare Web Analytics

No

Rage clicks, dead clicks, JS errors

Kipstats

Yes

Cloudflare Web Analytics

No

Humans separated from robots

Kipstats

Yes

Cloudflare Web Analytics

No

AI assistants as a channel

Kipstats

Yes

Cloudflare Web Analytics

No

Guaranteed EU storage

Kipstats

Yes

Cloudflare Web Analytics

Not compatible with their EU boundary

Measured at the edge (ad-blocker proof)

Kipstats

No

Cloudflare Web Analytics

Paid proxied plans

Core Web Vitals

Kipstats

No

Cloudflare Web Analytics

Yes

Script, gzipped

Kipstats

4.2 KB

Cloudflare Web Analytics

9.9 KB

REST API

Kipstats

1000 req/hour

Cloudflare Web Analytics

GraphQL

Cloudflare Web Analytics figures read on its own pricing and documentation pages, September 2026. Prices move — check theirs before deciding.

The three limits that matter

1. Your numbers are estimates after a week

Cloudflare's FAQ is explicit: unsampled beacon data is kept for the past 7 days, after which it is aggregated down to around 10 %, and the dashboard itself picks a sampling level between 0.0001 % and 100 % depending on the query. For a month-over-month comparison, or for a page with a handful of visits a day, that is the difference between a figure and an impression. Kipstats stores every session and every pageview, and shows you what it stored.

2. No events, no UTM

"Not yet, but we may add support for this in the future" is Cloudflare's answer on custom events, and query strings are not logged, so campaign parameters are invisible. You can count pageviews; you cannot count signups, checkouts or sales, and you cannot tell which campaign brought them.

3. EU residency is not on the menu

In Cloudflare's Data Localization compatibility matrix, Web Analytics and Real User Monitoring are marked as not compatible with the Customer Metadata Boundary — the feature that keeps data in the EU — with the suggestion to exclude EU visitors from RUM instead. Kipstats stores everything in the European Union, for every plan, without excluding anybody.

What Cloudflare does better

It is free, it requires no extra vendor if you are already there, and on proxied paid plans it can measure at the edge — which counts the visitors whose ad blocker drops our script, and theirs. Cloudflare acknowledges the blocking of its own JavaScript beacon; we have the same exposure. If your priority is a free rough count with the fewest moving parts, stay.

Which one is for you

Pick Kipstats if…

  • You need exact counts, not a 10 % sample, on pages with modest traffic.
  • You want to count signups, checkouts and sales, not only pageviews.
  • Your campaigns use UTM parameters.
  • You need the data to stay in the European Union, in writing.
  • You want to see where visitors get stuck, not only how many arrived.

Stay on Cloudflare Web Analytics if…

  • Free matters more than exact.
  • Your site is already proxied through Cloudflare and you want zero extra vendors.
  • You mainly want Core Web Vitals next to your traffic.
  • Measuring visitors whose ad blocker drops JavaScript is your priority.

Questions

Does Cloudflare Web Analytics really sample?

Yes, and it says so: unsampled data for the last 7 days, then aggregation down to about 10 %, with a display-time sampling rate between 0.0001 % and 100 %. It is a reasonable trade-off at Cloudflare scale; it is a problem when you are comparing two weeks on a page with 40 visits.

Can I keep Cloudflare and add Kipstats?

Yes. They do different jobs: Cloudflare gives you a free traffic count and Core Web Vitals, Kipstats gives you events, revenue and friction. Two tags, no conflict.

Is Kipstats blocked by ad blockers too?

Sometimes, like every JavaScript analytics script, including Cloudflare's own beacon. We do not claim otherwise. Only edge or server-side measurement avoids it, and for sales the server-side ingest API does exactly that.

Do I need a cookie banner for either?

Neither sets cookies, so neither requires one on its own account. Whether your site as a whole needs a banner depends on your other scripts.

Run both for a week

Two script tags, same visitors, and you will see the gap yourself. Free for one site, no card.

Start for free