What the Realtime report shows
The Realtime report is a rolling window over the most recent half hour of activity in a GA4 property. It counts the people active in that window, breaks them down minute by minute, and lets you look at where they came from, which country and city they are in, which pages they are on and which events they have fired.
It is built for speed rather than accuracy. Standard reports go through processing that resolves sessions, applies your attribution rules and settles the day’s figures; Realtime skips most of that so it can show something immediately. There is also a user snapshot that follows a single anonymous visitor through their events, which is useful when you want to see a journey rather than a total.
Because the window keeps moving, nothing in Realtime is a record. Whatever you were looking at is gone half an hour later, and there is no way to go back to it. If a number matters, it has to come from a standard report or an exploration the following day.
Why the Realtime report matters
Its honest job is confirmation. You have pushed a new landing page, published a campaign, changed a form, or sent an email: Realtime tells you within a minute that traffic is arriving and that the events you expected are firing. That turns a nervous launch into a checked one.
It is also the quickest sanity check when something looks wrong. If a client says the site is dead and Realtime is full of visitors, the problem is somewhere else. If Realtime is empty on a day that should be busy, you have a real incident and you know immediately rather than tomorrow morning.
Common mistakes with the Realtime report
The biggest is using it as a source of numbers. Realtime figures are unprocessed and will not match the standard report for the same period, and that is expected rather than a fault. Screenshotting a live count into a client report creates an argument you cannot win.
The second is watching it. It is genuinely compelling and it tells you almost nothing about a business — half an hour of traffic is weather, not climate. The third is testing tag changes here instead of in DebugView, which shows the parameters that Realtime leaves out.
How to act on it
Use it deliberately and briefly. Open it right after a launch, check that sessions are landing on the page you expect from the source you expect, fire your own enquiry or sign-up and confirm the event appears, then close it.
Keep the deeper questions for the reports built to answer them. Trends, channel performance and conversion rates belong in standard reports and explorations, where the data has been processed and the comparison is fair. If you want live numbers on a screen for the team, build that properly in a reporting dashboard with clear definitions, rather than leaving Realtime open all day.
