Cloudflare Web Analytics alternative

Cloudflare Web Analytics is the most popular free analytics option for small sites, and it is easy to understand why. If your domain already sits behind Cloudflare, turning it on is a checkbox. It is cookie-free, has no published traffic cap and costs nothing. For a hobby site or a simple brochure site, that is hard to argue with.

It also has real limits, and those limits start to bite as a site grows. This article covers when Cloudflare Web Analytics is enough, when it is not, and what a dedicated tool gives you in exchange for the bill.

What Cloudflare Web Analytics does well

At its core it shows pageviews, referrers, paths, browsers, countries and basic web-vitals signals. It is privacy-friendly, it is fast, and it requires almost no setup if you are already a Cloudflare customer. For answering the question 'is anyone reading this, and where did they come from?', it is entirely adequate.

Where it stops

The first limit is structural: Cloudflare Web Analytics only works when your domain is proxied through Cloudflare. Adopting it can mean moving your DNS, which is a much bigger commitment than adding a script tag. If you are not on Cloudflare and have no interest in moving, it is simply not an option.

The second limit is depth. Custom events are limited, campaign and UTM reporting is basic, retention is a short window, and the data is tied to Cloudflare's platform with limited export. It is a good free floor, not a full analytics product. For a marketing site that needs to understand campaigns, custom events and longer trends, you will hit the ceiling quickly.

When a dedicated tool is worth it

• You need custom events with properties — signups, purchases, feature use.
• You want UTM and campaign reporting that is actually readable.
• You need data retention measured in months or years, not weeks.
• You want an API and CSV export so the data is yours.
• You do not want your analytics tied to your CDN or DNS provider.

Lumenlytic is a dedicated alternative: cookie-free, one script tag, custom events, campaign reporting, two-year retention on paid plans and an API, without requiring you to move your DNS. It costs money, but the free tier covers 200k events a month and paid plans start at $15. Plausible and Umami are also strong options if you want a dedicated tool, with Plausible offering a smaller script and Umami offering self-hosting.

The practical recommendation

If you are already on Cloudflare and only need the basics, use Cloudflare Web Analytics and spend the money elsewhere. If you are not on Cloudflare, or if you need custom events, campaign depth or longer history, pick a dedicated tool. The migration is one script tag, and you can run both in parallel for a week to see whether the extra detail is worth it for your site.

When free stops being free

Free is genuinely free here, so the question is not a hidden bill but a hidden limit. The limit is usually a question Cloudflare cannot answer: which campaign drove a signup, which page a specific segment read, or what traffic looked like this month last year. Those gaps tend to appear when a site starts caring about growth, and at that point the cost of a dedicated tool has to be measured against the decisions you are currently making blind. It is not that the free tool becomes bad; it is that your questions outgrow it. Recognising that moment early is worth more than squeezing another year out of a tool that no longer fits.

There is also a dependency cost. Keeping your analytics inside Cloudflare means your measurement is tied to your CDN and DNS choices. If you later move for performance, cost or reliability reasons, your history and dashboards do not come with you. That is not a reason to avoid Cloudflare today, but it is a reason to understand the lock-in before you build workflows on top of it. A standalone tool makes the CDN choice reversible, which is valuable when your infrastructure needs change faster than your analytics needs do.

A sensible migration path

If you decide to move, do it incrementally. Add the new script alongside Cloudflare Web Analytics and leave both running for a week. Compare pageviews and referrers on a few pages you know well, and check that the new tool's numbers are plausible against the old ones. Then remove the old tag and import or note anything you need for continuity. Because both tools are cookie-free, there is no consent interaction to manage during the test, which makes the parallel period low-risk. A week of overlap is usually enough to catch a misconfiguration before it becomes your only source of data. If the numbers diverge more than you expect, check the obvious causes first: whether the new tag is on every page, whether the tracking identifier is correct, and whether an ad blocker or a staging domain is skewing the test. A small difference is normal; a large one usually points to a missing page or a misfired event, not a fundamental flaw in either tool. Write down the difference you observe so you can decide later whether it matters, and keep both tags until you are confident enough to remove the free one. If you are not ready to commit, leave the free tag in place and revisit in a quarter; the cost of waiting is small as long as you know what you are waiting for. What you should not do is keep a tool that cannot answer your questions simply because it is free, while quietly making decisions from incomplete data. The moment a missing number changes a decision, the paid tool has already paid for itself. That is the honest test, and it is a better guide than any feature table or free-tier allowance. Use the tools for what each does best, and review the split as your site grows.