The APIs.io network has a new page in the More dropdown across every site — apis.io/analytics — and it does something most sites keep private: it publishes our own web traffic, in the open, every week.
The twist is that it publishes traffic from two independent sources at once — Cloudflare at the edge and Google Analytics 4 in the browser — and shows them next to each other rather than picking one “official” number. The two never agree, and the gap between them is the whole point.
What the page shows
Every Monday a snapshot is collected and appended to the history. The page renders three things:
- The most recent week, as two cards — Cloudflare’s edge metrics (page views, unique visitors, total requests, bandwidth, threats blocked, top countries) beside GA4’s browser metrics (page views, sessions, users, new users, bounce rate, average session, top countries).
- Page views over time, charting both sources across every week collected so far.
- A weekly history table, with a
Views ratiocolumn that divides Cloudflare page views by Google Analytics page views — the single number that captures how far apart the two layers sit.
For the week ending June 10, 2026, the two sources reported:
| Metric | Cloudflare | Google Analytics 4 |
|---|---|---|
| Page views | 1,127,784 | 48,367 |
| Unique / Users | 50,705 | 44,508 |
| Requests / Sessions | 2,359,591 | 45,731 |
| edge / CDN layer | browser / session layer |
That’s a 23.3× gap in page views between the two. Both numbers are correct. They’re just measuring different things.
Why the numbers differ
Cloudflare counts more. It sees every HTTP request that hits the edge — including bots, crawlers, feed readers, and API clients; cached responses served before they ever reach the origin; browser prefetch and pre-connect; and every request that loads before any JavaScript runs, plus users with JavaScript disabled entirely.
Google Analytics counts less. Its tag only fires when JavaScript loads and executes successfully. Ad blockers and privacy extensions suppress it — and on a developer-heavy audience like ours, that’s a large slice. So GA4 is a floor of engaged human browser sessions, while Cloudflare is a ceiling of everything that touched the network.
Neither is the “true” number. The reality lives between them, and watching both move week over week tells you more than either could alone — a spike in Cloudflare with flat GA4 is crawler and agent traffic; a rise in both is real human growth.
Why publish it at all
The network is built on the premise that API metadata should be open and machine-readable — providers, APIs, schemas, workflows, all out in the open. Our own traffic should be held to the same standard. Twenty-three weeks in, the page also tells a quiet growth story: the first snapshot back in January logged 14,235 Cloudflare page views in a week; the latest logged 1,127,784. The catalog is being read — increasingly, it turns out, by agents and crawlers as much as by people, which is exactly the gap the two-source view makes visible.
The underlying data lives in network/_data/analytics.json and refreshes weekly. See it at apis.io/analytics.