The Realtime report in Google Analytics 4 shows activity on your website or app over roughly the last 30 minutes: how many people are active, where they came from, which pages they are viewing and which events they are triggering. It is a live check that tracking works, not a place to judge performance.
How the Realtime report works
Events reach GA4 within seconds of being sent, and the Realtime report reads them before the slower processing that feeds the standard reports. The overview shows active users across the last 30 minutes with a minute-by-minute chart, then cards for users by traffic source, by audience, by page title, by event name and by key event, along with a map of locations.
You can add comparisons, such as mobile against desktop, and click into an event name to see the parameter values that came with it. That makes it a quick way to confirm that a tagged campaign link, an enquiry form or a purchase is arriving with the details you expect.
Treat the figures as a rough preview. They show what GA4 has received so far, before full processing is applied, so the same half hour can look slightly different in the standard reports a day later.
Why it matters
Realtime is the fastest answer to the question “is it working right now?”. When a campaign email goes out at 10am, you can watch the visits arrive and see whether the UTM parameters on the links are producing the right source and medium. When a developer releases a new checkout, you can place a test order and see the purchase event appear within a minute or two instead of waiting for the next day’s data.
For UK sites it is also a simple consent check. Open the site in a private window, reject cookies on the banner and browse a few pages. If you show up in Realtime as an active user, analytics is probably running without consent, which is a PECR problem. Then accept cookies in a fresh window and confirm you do appear. If the site uses consent mode in advanced mode, Google tags still send cookieless pings after a rejection, so also open your browser’s developer tools and confirm no _ga cookie was set; that is the firmer test.
Common mistakes
- Leaving Realtime open as a dashboard and reacting to dips that are just normal minute-to-minute variation.
- Using Realtime numbers in reports. They cover a 30-minute window and can change once processing finishes.
- Testing a new tag while your own visits are excluded by an active internal traffic filter, then concluding the tag is broken.
- Confusing Realtime with DebugView, which lists the events from your own debug-enabled browser one by one and is the better place to check parameters.
- Assuming no Realtime activity means no visitors, when the tags are simply waiting for consent or being stopped by ad blockers.
How to act on it
Use Realtime at three moments: straight after any tracking or website change, when a campaign or email goes out, and whenever you suspect something has broken, such as orders arriving in your shop with no matching purchases in GA4. For a detailed check of event names and parameters, run GTM preview mode and watch DebugView instead.
Keep performance judgements for the standard reports and explorations, looked at over weeks rather than minutes. I check Realtime as part of the launch routine for campaigns in performance marketing, because the first hour after launch is the cheapest time to find a broken tag.