Cloudflare
×
Papercrane
Cloudflare sees triple the traffic GA4 reports. Which is real?
Some of the gap is bots Cloudflare serves, some is humans GA4 never sees, and neither dashboard can tell you the split. Papercrane's AI agent reads both counters, reconciles them, and builds a live hosted dashboard of traffic, cache, and security numbers you can defend.
Connect in about a minute with a read only token you create in your Cloudflare dashboard. Free to connect and ask. Paid plans start when you publish a dashboard. See pricing
One article, one week, both counters audited
We ran this on a real publisher's site. Cloudflare and GA4 were both wrong, in opposite directions, and neither dashboard could show it.
The recount
What Cloudflare counted
Requests to the article, one week
2,504
Minus Cloudflare's own infrastructure: Worker subrequests, preloads
−1,726
Served to real browsers
778
What GA4 reported
Pageviews reported
993
Minus a consent tool and an ads plugin double firing the tag
−361
Real tag fires
632
778
vs
632
The remaining gap is bots that never run JavaScript, ad blockers, and visitors who left before the tag loaded.
GA4 looked 28% high. After the recount it was 19% low. Neither side's dashboard could see it; the answer needed the edge data and the tag data side by side.
Real numbers from a real investigation. Yours will differ, which is the point: the agent runs the recount on your site.
Where the Cloudflare dashboard stops
The 24 hour window
On Free and Pro plans, security events older than a day are gone and the richer analytics keep 7 days. The Monday writeup of a Saturday attack has nothing left to screenshot.
The dropdown is the query
Preset ranges, top 15 lists, and stats sampled from 1 to 10% of requests. “Compare this launch to the last one” is not on the menu.
A dashboard only you can open
Zone analytics live behind your Cloudflare login, and the 2026 custom dashboards still chart only Cloudflare, inside the Cloudflare admin. The client or exec who asks for numbers gets a screenshot.
Ask the edge what the tag can't see
What share of my Cloudflare traffic ever shows up in GA4, by page?
Which paths and countries drove this morning's WAF event spike?
What is my cache hit ratio by content type, and what did the misses cost in bandwidth?
Which pages do bots hammer hardest, and how much of that reaches my origin?
Did yesterday's DNS change move query volume or response codes?
Which landing pages have heavy edge traffic but almost no GA4 sessions: blocked tags, or bots?
Every answer comes back as a chart on a live dashboard, not a number you have to re pull next week.
Built by Papercrane's agent. Refreshes on its own.
1. Create a read only analytics token in your Cloudflare dashboard
2. Ask a question
3. The agent plans the queries and builds a hosted dashboard
4. It stays live and refreshes on a schedule
Read access only. Nothing changes in your zones, your rules, or your DNS.
Three ways to see your edge data
| The job | Cloudflare dashboard | Exporter + Prometheus + Grafana | Cloudflare + Papercrane |
|---|---|---|---|
| Investigate last weekend's attack on Monday | Security events expire in 24 hours on Free and Pro | Only if your scraper was already running | A dashboard that refreshes daily keeps each day's numbers as they happen |
| Compare an arbitrary date range | Preset ranges only | Works, over the history you've collected | Ask for the range; the agent queries what Cloudflare still serves and keeps it from there |
| Put edge traffic beside GA4 and revenue | Cloudflare data only | Grafana can, if you wire and maintain every source | The agent joins Cloudflare, GA4, Search Console, and your store |
| Share with a client or exec | Behind your Cloudflare login | Run and secure a Grafana instance for them | Send a link to a hosted dashboard |
| Keep it running | Nothing to run | An exporter, a Prometheus, and a Grafana to babysit | Hosted; errors route back to the agent |
When you don't need us
If what you want is paging and alerting on edge metrics, Grafana with the community Cloudflare exporter is built for waking you up at 3am and we are not; Cloudflare's own blog documents that stack. If you're on Enterprise with Logpush shipping full request logs to your own storage, that is the right forensic foundation, and Papercrane can sit on the warehouse those logs land in. Papercrane is worth paying for when the answer spans Cloudflare and the counters around it, or when the result needs to live somewhere a client or exec can watch it without a Cloudflare login.
Questions Cloudflare users ask us
The recount needs the other counter, and the edge numbers get more useful next to what the site earned: GA4 for the tag side, Search Console for what Google actually indexed, your store for revenue.
Create a token, connect your zones, and run the recount on your own traffic. The answer comes back as a dashboard.
Free to connect and ask. Paid plans start at publishing. See pricing
Papercrane
Integrations: