The realtime report
The Realtime report surfaces events and users from approximately the last 30 minutes, refreshing continuously. It is built for spot-checking that tracking fires after a deploy or campaign launch — not for analysis. Its short window and live nature mean its totals will never reconcile with processed historical reports.
What this means
The Realtime report visualizes activity from roughly the last 30 minutes — users by source, events, conversions, and a snapshot of where they are. It refreshes continuously, so it is a live monitor rather than a settled report.
What it is and is not for
Use it to verify: did my new event fire, is the campaign sending traffic, did the deploy break tracking. Do not use it for analysis or to forecast a day's totals — the window is tiny, the dimensions are limited, and the figures are pre-processing estimates that will not match the fully processed historical reports.
- Window is roughly the last 30 minutes
- Best for verifying tracking after a change
- Never reconciles with processed historical data
How it appears in analytics and logs
Realtime numbers describe a rolling ~30-minute window of live activity. They are provisional and limited in dimensions; do not expect them to equal the same period once data is fully processed.
Diagnostic use case
Confirm tracking works right after a release, watch a campaign or launch land, or debug whether a specific event fires — using a short live window, not for trend analysis.
What WebmasterID can help detect
WebmasterID's Event Explorer lets you watch first-party events arrive to confirm instrumentation, without exposing cross-site identifiers.
Common mistakes
- Extrapolating a day's total from the realtime window.
- Expecting realtime counts to match processed reports.
- Using realtime for analysis instead of verification.
Privacy and accuracy notes
The Realtime report shows aggregated live activity and applies thresholds; it does not expose individual identities. Use it to verify tracking, not to watch people.
Related pages
- GA4 standard reports overview
Standard reports are GA4's fixed, pre-aggregated reports — grouped into collections like Life cycle and User — that load fast because they read from aggregate tables. Unlike explorations they are not generally sampled, but they apply (other) row grouping and can differ from exploration numbers, which query event-level data with their own scope.
- Acquisition reports in GA4
GA4's acquisition collection has two reports: User acquisition attributes by the channel that first brought a user, and Traffic acquisition attributes by the channel of each session. They answer different questions and rarely sum the same way, because one is keyed to first touch and the other to per-session source.
- Data thresholding in GA4
Data thresholding is a GA4 privacy mechanism: when a report could let someone infer the identity of individual users from low-volume rows (especially with Google Signals or demographics enabled), GA4 hides some data. The result is missing rows and report totals that do not reconcile. This page explains when thresholding applies and how to recognize it.
- Event Explorer
Watch first-party events arrive to verify tracking.
Sources and verification notes
Last reviewed 2026-06-24. Facts are checked against primary/official sources where available; uncertain specifics are marked “Data not yet verified” rather than guessed.