Edge comparison (Cloudflare)

Place Cloudflare edge data beside GA4 and GSC to estimate bot share and review cache and threat blocking.

Overview#

The Edge comparison page (/dashboard/mkit/traffic/edge-comparison) places Cloudflare edge data beside GA4 and GSC to help spot bots and cache behaviour.

The K5 cards#

Five comparison cards at the top:

CF Pageviews
GA4 Sessions
GSC Impressions
Cache Hit Rate
Threats Blocked

Bot estimate#

Bot share is estimated from the gap between CF pageviews and sessions:

bot_estimate_pct = (CF_pageviews - GA4_sessions) / GA4_sessions * 100

Note: Country dimension: CF uses ISO codes and GA4 uses English full names, so a mapping is applied first; per country bot_est = cf_share - ga4_share.

Cloudflare token#

The Cloudflare connection is not OAuth — you paste an API Token (stored encrypted). The token needs these four permissions:

Permission	Purpose
Account.Settings:Read	Read account settings
Account.Account Analytics:Read	Read account-level analytics
Zone.Zone:Read	List domain zones
Zone.Analytics:Read	Read edge analytics

Verification flow:

POST /user/tokens/verify to validate the token
GET /zones?per_page=50 to list zones

Limits#

History and connection limits:

Item	Limit
CF history (product copy)	Free/Pro 14 days, Business/Enterprise 30 days
CF history (real query)	Fixed at 14 days; the zone plan is not queried
Non-CF DNS sites	Cannot bind a zone
Cloudflare not connected	Returns CONNECTION_REQUIRED (service=cf)

Note: The page states "CF data requires DNS hosted on Cloudflare"; a failed token check returns CF_TOKEN_INVALID (400).

Bot traffic: /bots
Search dimension: /dimensions-search
Data latency & metric definitions: /data-latency