invisit
Compare

Cloudflare Web Analytics alternative: invisit vs Cloudflare

Cloudflare Web Analytics is free on every Cloudflare plan, sets no cookies and installs itself in one click on proxied sites. It has no custom events or campaigns, and keeps six months of data, sampled to about 10% after a week. invisit adds events, funnels, revenue and visit timelines, and keeps data forever.

.mdllms.txt

Written by the invisit team. Facts about Cloudflare Web Analytics checked on , from their own pages.

Choose invisit if

  • You need custom events, goals or funnels. Cloudflare Web Analytics has no custom events.
  • You want data kept forever and unsampled, not six months thinned to about 10% after the first week.
  • You run campaigns: Cloudflare logs no query strings, so it has no UTM reports.
  • You want revenue from Stripe or Paddle, per-visit timelines, heatmaps and JavaScript errors in the same dashboard.
  • You want EU visitors counted and stored in the EU: on free proxied sites, Cloudflare leaves EU visitors out by default.

Choose Cloudflare Web Analytics if

  • You want analytics that cost nothing at any volume: Web Analytics is free on every Cloudflare plan, with no usage pricing.
  • Your site is proxied through Cloudflare: one click injects the beacon, and edge analytics count every request with no script at all.
  • Page speed is the point: Cloudflare splits LCP and INP into their sub-parts and names the page elements that hurt each vital.
  • Page views, referrers, countries and devices are all you need, and six months of history is enough.
  • You want AI crawler activity on a proxied site with no code: AI Crawl Control is included on every Cloudflare plan.

What a month costs

Monthly billing, cheapest plan step that covers the volume. invisit bills events (page views and custom events); Cloudflare Web Analytics bills nothing: it is free on every Cloudflare plan. It needs a Cloudflare account, and Cloudflare documents no volume limit. Data older than 7 days is kept as a sample of about 10%.

Monthly price, invisit and Cloudflare Web Analytics
A month ofinvisitCloudflare Web Analytics
10KFreeFree
100K$14Free
1M$49Free
10M$199Free

Feature by feature

Features, invisit and Cloudflare Web Analytics
FeatureinvisitCloudflare Web Analytics
Privacy and setup
No cookies, no consent banner neededDaily-rotating hashNo cookies, localStorage or fingerprinting
Data stored in the EUFalkenstein, Germany (Hetzner)Not covered by the Customer Metadata Boundary for the EU
Lightweight script (under 10 KB)About 9.8 KB gzipped; extras load on demandAbout 10.3 KB gzipped
Serve from your own domain@invisitdev/server proxyProxied sites report to your domain; the script loads from Cloudflare's
Open sourceTracker and SDKs, MITClosed service, no self-hosting
Import history from another toolNoNo
Analytics
Realtime viewYesNo live view; the default range is the last 24 hours
Custom events and goalsYesNot yet, per its FAQ
FunnelsYesNo
Per-visit timelinesEvery visit step by step at any age: in the dashboard, the API and MCPNo per-visit view; the beacon collects page timings
Retention cohortsNoNo
HeatmapsClicks, rage and dead clicks, scroll depthNo
Session recordingsNoNo
Web vitalsNever billedLCP, INP and CLS with sub-parts and the elements behind them
JavaScript error trackingGrouped, tied to visits, with its own allowance: 5K reports a month on FreeTiming metrics only; no JavaScript error capture
AI assistant referralsChatGPT, Claude, Perplexity, Gemini and moreNot in Web Analytics; AI Crawl Control shows AI referrals on paid plans
Crawler reads (search and AI bots)Recorded server-side, never billed; by bot and by page, with AI training and AI answers apartAI crawlers in AI Crawl Control, proxied sites only; 24 hours on Free
RevenueRead from Stripe, Polar, Paddle, Dodo Payments, Creem and Lemon SqueezyNo revenue reports or custom events
Revenue by sourcePaid plans: by source, campaign, landing page and short linkNo revenue reports
Queries from Google Search ConsoleEvery plan: clicks, impressions, CTR and position, per site and pageNot among its dimensions
Beyond the dashboard
Traffic alertsSpikes, drops, silence and error spikes, to Slack, Discord, ntfy or a webhookEdge traffic spike and drop alerts on Enterprise only
Email reportsEvery plan: what changed, on MondaysWeekly summary email: visits, page views, load time
Public dashboardsYesNo
Short linksYesNo
On-page feedbackYesNo
APIREST, with an OpenAPI documentGraphQL Analytics API, sampled per query
MCP server for AI assistantsYesGeneral Cloudflare API MCP server; no Web Analytics tools of its own
Plans
Free plan20K events a month, nearly every featureFree on every Cloudflare plan, with no usage pricing
Free trial14 days on monthly plans, card requiredNo trial needed: Web Analytics is free
Sites4 free, unlimited on paid plans10 sites outside Cloudflare (a soft limit); unlimited proxied sites
Team membersUnlimited, on every planCloudflare account members, with an Analytics read role
Data keptForever, on every planSix months; unsampled for 7 days, then about 10% is kept

Is Cloudflare Web Analytics data sampled, and how long is it kept?

Cloudflare Web Analytics keeps six months of data, and only the last 7 days of it unsampled. After a week, Cloudflare aggregates the data down to about 10% of its volume for long-term storage. invisit stores every event, unsampled, and keeps it forever on every plan.

As of November 2026, Cloudflare’s FAQ says the beacon fires on every page view and the ingestion pipeline records every beacon it receives. Sampling comes after: when you open the dashboard or query the GraphQL API, Cloudflare picks a sampling level between 0.0001% and 100% based on your filters and the number of matching rows, and the API’s sampleInterval field tells you which one it used. Cloudflare calls this Adaptive Bit Rate: it trades exact counts for fast answers. Low-traffic sites are sampled at higher rates to keep the totals reliable.

For the headline numbers on a busy site, that works well. It matters when you filter down to a small slice, such as one page from one country last quarter, and when you want to compare this month with the same month last year: Cloudflare’s six-month window has no last year.

Can Cloudflare Web Analytics track custom events or campaigns?

No. As of November 2026, Cloudflare answers “not yet” to both custom events and UTM parameters: it logs no query strings, to avoid collecting sensitive data. invisit tracks custom events with up to 32 properties, conversions and funnels, and reports campaigns and UTM source and medium on every plan, its free plan included.

What Cloudflare reports is set by its high-level metrics and dimensions: visits, page views, page load time and Core Web Vitals, broken down by country, host, path, referrer, device type, browser and operating system, with a switch to exclude bots. A visit is a page view whose referrer is another site. There is no unique-visitor count among those metrics, and no sign-ups, purchases or button clicks.

With invisit you send events from code or from HTML attributes (events), build funnels from pages or events, and see each visit’s pages and events in order, at any age (visits). Revenue comes straight from Stripe, Paddle and other providers, and Google Search Console queries sit beside your traffic on every plan.

Proxied or not: how Cloudflare Web Analytics collects data

Cloudflare Web Analytics works on any site, but it works best on sites proxied through Cloudflare. There, one click injects the beacon, data reports to your own domain, and there is no site limit. Elsewhere you paste a snippet, and an account tracks up to 10 such sites unless support raises the limit. invisit works the same on any host.

From Cloudflare’s setup guide and limits, as of November 2026:

Sites outside Cloudflare Sites proxied through Cloudflare invisit
Setup Paste the snippet Automatic injection, on by default Script tag or @invisitdev/web
Data sent to cloudflareinsights.com Your own domain, /cdn-cgi/rum api.invisit.dev, or your own domain
Sites 10, a soft limit No limit 4 free, unlimited on paid plans
Path rules No 0 on Free, 5 on Pro, 20 on Business, 100 on Enterprise excludePaths, on every plan
EU visitors No EU setting documented Left out by default on the Free plan Counted

The script itself always loads from static.cloudflareinsights.com, and Cloudflare’s FAQ notes that ad blockers such as Adblock Plus, Brave and the DuckDuckGo extension block it. For proxied sites, Cloudflare’s answer is edge analytics: the Analytics tab counts every request Cloudflare serves, with no script at all, and Pro, Business and Enterprise plans break that traffic down by URL. invisit has no script-free mode, but @invisitdev/server serves the tracker and its data from your own domain.

Core Web Vitals and script size: Cloudflare vs invisit

Both record Core Web Vitals from real visitors at no extra cost, and Cloudflare goes deeper on debugging. Its Core Web Vitals view splits LCP into four phases and INP into three, and lists the five page elements that hurt each vital most, by CSS selector, with P50 to P99 values. invisit records LCP, INP, CLS, FCP and TTFB by page, device, country and browser, and never bills them.

Cloudflare’s beacon.min.js (version 2026.10.1) measured 10,253 bytes with gzip -9, about 10.3 KB, and Cloudflare served it as 10,264 bytes of gzip (our script size test). invisit’s core script is about 9.8 KB, and its web vitals module loads separately at 1.1 KB, so with vitals on, an invisit visitor downloads about 11 KB: slightly more than Cloudflare’s single file. Either way the difference is a few milliseconds on a slow connection.

Cloudflare’s beacon does one job, performance. invisit’s core script also records custom events, outbound link and download clicks, and events from HTML attributes. Heatmaps (1.5 KB) and the feedback widget are separate modules that load only when you turn them on.

Does Cloudflare Web Analytics use cookies, and where is the data stored?

Cloudflare Web Analytics sets no cookies and uses no localStorage, and Cloudflare says it does not fingerprint visitors by IP address or User-Agent (product page). invisit sets no cookies either, and tells visitors apart with a hash that rotates every day (privacy).

Where the data lives is less clear on Cloudflare’s side. Its RUM beacon docs say beacon data is processed at the nearest Cloudflare data center, and the Data Localization Suite compatibility table marks Web Analytics as not compatible with Customer Metadata Boundary, the feature that keeps analytics and logs in the EU. Cloudflare’s alternative is to leave EU and EEA visitors out of RUM, which is the default for free proxied sites.

invisit stores analytics data in Falkenstein, Germany, and counts EU visitors like any others. It sits behind Cloudflare itself for DNS and CDN, so Cloudflare, a US company, handles invisit’s traffic in transit. invisit offers a DPA, can honour Global Privacy Control and Do Not Track, and has an optional consent mode.

When Cloudflare Web Analytics is the better choice

If you want to know how many people read which pages, from which sites and countries, and your budget is zero at any volume, Cloudflare Web Analytics is hard to beat. It is free on every Cloudflare plan with no usage pricing, while invisit’s free plan stops at 20,000 events a month.

If your site is already proxied through Cloudflare, setup is one click, and the edge analytics in the Analytics tab count every request with no script to block. invisit always needs its script for visitor analytics.

For performance work, Cloudflare’s sub-parts and element-level debug view tell you which image or handler slowed a page. AI Crawl Control shows which AI crawlers read a proxied site, on every plan with no code, though the free plan shows only the last 24 hours of metrics. invisit records search and AI crawler reads too, kept like everything else, but needs @invisitdev/server or a Cloudflare Worker in front of your site.

Switching from Cloudflare Web Analytics to invisit

  1. Create a site in invisit and add its script tag next to Cloudflare’s beacon (installation). Run both for a few weeks so you can compare the numbers. Expect invisit to count more on free proxied sites, where Cloudflare leaves EU visitors out.
index.html
<!-- Before: Cloudflare Web Analytics, manual setup -->
<script
  type="module"
  src="https://static.cloudflareinsights.com/beacon.min.js"
  data-cf-beacon='{"token": "<site token>"}'
></script>

<!-- After: invisit -->
<script
  async
  src="https://api.invisit.dev/invisit.js"
  data-site="<site id>"
  data-collector="https://api.invisit.dev"
></script>
  1. If your site is proxied through Cloudflare, put the invisit Worker in front of it. It serves the tracker from your own domain and records crawler reads, without touching the site itself, and a deploy button sets it up from a template.
  2. Add the events Cloudflare could not record: track('signup', { plan: 'pro' }) from @invisitdev/web, or data-invisit-event attributes with no JavaScript (events). Then connect your payment provider and Google Search Console.
  3. Save your history. invisit cannot import it, and Cloudflare has no CSV export in its Web Analytics docs; the GraphQL Analytics API returns the same aggregates as the dashboard, within the six-month window and sampled as described above.
  4. Remove the beacon. On a proxied site, open the site’s Manage site page in Web Analytics and choose Disable.

Why teams pick invisit

invisit starts from a simple question: who actually came to your site, and what brought them there? So it leads with people, not only totals. Each visit keeps its pages and events in order, next to where it came from, including the AI assistants that now send real visitors.

It also covers the jobs that usually need a second tool. Revenue arrives straight from your payment provider, and paid plans split it by the source behind each payment. Crawler reads show which search engines and AI bots read your pages, Google Search Console queries show what people searched, and heatmaps, web vitals, short links and feedback sit in the same dashboard. Every paid plan has every feature, so there is no tier to outgrow.

And it stays out of your visitors’ way: no cookies, no banner, nothing that follows anyone from one day to the next.

invisit or Cloudflare Web Analytics? Common questions

Is invisit cheaper than Cloudflare Web Analytics?

At 1M events a month invisit costs $49 a month, and Cloudflare Web Analytics is free. invisit bills page views and custom events; Cloudflare Web Analytics bills nothing: it is free on every Cloudflare plan. Prices checked against Cloudflare Web Analytics's pricing page on November 16, 2026.

Does Cloudflare Web Analytics have a free plan?

Yes, Cloudflare Web Analytics has a free plan: free on every Cloudflare plan, with no usage pricing. invisit is free up to 20K events a month with no time limit, and its free plan has nearly every feature.

What does invisit have that Cloudflare Web Analytics does not?

invisit includes data stored in the EU, lightweight script (under 10 KB), realtime view, custom events and goals, funnels, per-visit timelines, heatmaps, javaScript error tracking, revenue, revenue by source, queries from Google Search Console, public dashboards, short links, and on-page feedback; Cloudflare Web Analytics does not, as of November 16, 2026.

When should I choose Cloudflare Web Analytics over invisit?

Cloudflare Web Analytics suits you better than invisit when one of these is true. You want analytics that cost nothing at any volume: Web Analytics is free on every Cloudflare plan, with no usage pricing. Your site is proxied through Cloudflare: one click injects the beacon, and edge analytics count every request with no script at all. Page speed is the point: Cloudflare splits LCP and INP into their sub-parts and names the page elements that hurt each vital. Page views, referrers, countries and devices are all you need, and six months of history is enough. You want AI crawler activity on a proxied site with no code: AI Crawl Control is included on every Cloudflare plan.

When should I choose invisit over Cloudflare Web Analytics?

invisit suits you better than Cloudflare Web Analytics when one of these is true. You need custom events, goals or funnels. Cloudflare Web Analytics has no custom events. You want data kept forever and unsampled, not six months thinned to about 10% after the first week. You run campaigns: Cloudflare logs no query strings, so it has no UTM reports. You want revenue from Stripe or Paddle, per-visit timelines, heatmaps and JavaScript errors in the same dashboard. You want EU visitors counted and stored in the EU: on free proxied sites, Cloudflare leaves EU visitors out by default.

Is Cloudflare Web Analytics really free?

Yes. As of November 2026, Cloudflare Web Analytics is free on every Cloudflare plan, the free plan included, with no price per page view. It needs a Cloudflare account, not a proxied domain: sites outside Cloudflare use a JavaScript snippet, up to a soft limit of 10 per account. invisit is free up to 20,000 events a month on 4 sites, then $14 a month for 100K events up to $199 for 10M.

Is Cloudflare Web Analytics data sampled?

Partly. As of November 2026, Cloudflare records every beacon it receives and keeps the unsampled data for 7 days. After that it aggregates the data down to about 10% of its volume for long-term storage, and the dashboard and GraphQL API pick a sampling level between 0.0001% and 100% per query. invisit does not sample: every event is stored and kept forever.

How long does Cloudflare Web Analytics keep data?

Six months. As of November 2026, Cloudflare's Web Analytics FAQ says you can access data for the previous six months, and only the last 7 days are unsampled. invisit keeps data forever on every plan, the free one included.

Does Cloudflare Web Analytics support custom events or UTM parameters?

No. As of November 2026, Cloudflare answers "not yet" to both in its Web Analytics FAQ: there are no custom events, and query strings are not logged, so UTM parameters are dropped. invisit tracks custom events with up to 32 properties, conversions and funnels, and reports campaigns and UTM source and medium on every plan.

Do I need to proxy my site through Cloudflare to use Web Analytics?

No. Cloudflare Web Analytics works on any site with a JavaScript snippet that loads from static.cloudflareinsights.com and reports to cloudflareinsights.com. Proxied sites get a one-click setup that injects the snippet and reports to their own domain, unlimited sites, and path rules on paid plans. invisit works on any host, and @invisitdev/server can serve it from your own domain.

Does Cloudflare Web Analytics count visitors from the EU?

Not always. As of November 2026, Cloudflare enables its RUM beacon automatically on free proxied sites with EU and EEA traffic excluded, and any proxied site can choose that setting. Web Analytics is not covered by Cloudflare Customer Metadata Boundary. invisit counts every visitor and stores data in Germany.

More comparisons