Data latency & metric definitions

Latency per source, metric definitions, quotas and limits, and why your numbers may differ from other tools.

Latency per source#

Source	Delay	Notes
GA4	24-48 hours	Realtime is visible within ~30 minutes
GSC	1-2 days	Same-day search data is never complete upstream either
AdSense	24-48 hours	Console revenue also stabilises the next day
PageSpeed Insights	Refreshed ~6 hours	Lab data is re-run each time; field data comes from CrUX (traffic threshold)
Bing Webmaster	Daily	Crawl and inbound-link data also update daily
Cloudflare edge	Near realtime, short history	Free/Pro 14 days, Business+ 30 days

Note: Gaps in reports within the first 48 hours of connecting are normal; the system backfills as data arrives.

Source	Core metrics	Definition
GA4	Sessions / users / pageviews / engagement rate / avg engagement time	Native GA4 definitions; channels use Default Channel Group
GSC	Clicks / impressions / CTR / average position	Broken down by query, page, country, device; position is an average
AdSense	Estimated earnings / impressions / clicks / page views / RPM	RPM = revenue per thousand impressions; figures are estimates
PSI	Performance score / lab metrics / field data	Lab = one controlled run; field = real visitors P75 (CrUX)
Bing	Clicks / impressions / average position / crawl / inbound links	No period-over-period view, so no fabricated movers
Cloudflare	Requests / bandwidth / cache hit / bot share	Page titles and referrers are unavailable (Cloudflare limitation)

Item	Limit
URL Inspection (GSC)	Free 0 / Pro 50 / Business 200 per day (Google hard cap 2000/day per project)
PSI refresh	Roughly every 6 hours; upstream quota or timeouts can drop a single score — the next run restores it
Cloudflare history	Free/Pro 14 days, Business+ 30 days; Cloudflare keeps nothing older
GA4 realtime	A window of roughly the last 30 minutes
AdSense page-level	PAGE_URL has a minimum-impression threshold and cannot be combined with a domain filter

Different time windows: GA4 attributes by session date, GSC by click date — day boundaries differ naturally.
Different definitions: GSC "clicks" are not GA4 "sessions"; AdSense revenue is an estimate.
Sampling and thresholds: GA4 samples at high volume; AdSense page-level has an impression threshold; CrUX needs enough traffic.
Time zones and currencies: each upstream has its own settings; we display what upstream returns.
Bot filtering: tools filter bots differently, so edge request counts usually exceed analytics sessions.

Tip: For trend decisions, compare within one source and one time window; across sources, treat differences as directional only.