CONCEPT Cited by 1 source
Cloudflare zone analytics¶
Definition¶
Cloudflare zone analytics is the per-zone (per-customer- domain) record of which URLs received traffic over a recent window, visible to Cloudflare as a side effect of proxying requests for that zone.
Exposed to customers via the Cloudflare dashboard + API; aggregated across zones in Cloudflare Radar. The 2026-02-24 vinext launch adds a new consumption path: deploy-time automated query by the deploying framework itself.
Load-bearing role in TPR¶
Traffic-aware
Pre-Rendering queries zone analytics at vinext deploy
--experimental-tpr time and uses the top-N-by-request-count
URLs to decide which pages to pre-render. The result:
TPR (experimental): Analyzing traffic for my-store.com (last 24h)
TPR: 12,847 unique paths — 184 pages cover 90% of traffic
The signal is CDN-native — a build tool running offline has no access to it without a separate analytics integration.
Why this is a CDN-exclusive capability¶
Any CDN has this data as a side effect of being in the request path. An offline build tool does not. Coupling a build to the production database to fetch the equivalent data (an enumerated list of pages + their popularity) has production-operations costs (auth, permissions, data residency, staging parity) that the CDN-native approach sidesteps.
Seen in¶
- sources/2026-02-24-cloudflare-how-we-rebuilt-nextjs-with-ai-in-one-week — canonical wiki instance of zone analytics being used as a deploy-time signal by the framework itself (rather than as a human-facing dashboard).
Related¶
- concepts/traffic-aware-prerendering — the primary deploy-time consumer surfaced in the wiki.
- concepts/power-law-url-traffic — the traffic shape zone analytics actually measures.
- systems/cloudflare-workers — the platform where TPR runs.
- systems/cloudflare-radar — the sibling public-facing aggregation surface for cross-zone traffic data.
- systems/vinext — canonical consumer.