Troubleshooting

Why GA4 Realtime Users Show 0

Updated 2026-09-043 min read

Short answer

Realtime counts people active in a recent window. Zero means nobody has been active in that window — which is normal for a small app — unless events are also missing from DebugView, in which case the SDK is the problem.

Realtime showing zero feels like a failure, but it is a measurement, and most of the time it is an accurate one. The question worth asking is not "why is it broken" but "is anyone actually using the app right now".

What realtime actually counts

Realtime reports activity inside a recent time window rather than a running total. Someone who used the app this morning does not appear in it this afternoon. For an app with a handful of daily users, the honest expectation is that realtime is zero most of the time and briefly non-zero when somebody opens the app.

A small app across one day
40 people open the app over 24 hours
Each session lasts a few minutes
Total active minutes: roughly 2 hours out of 1,440
So at any random moment, realtime is very likely to be 0

Note: Realtime being zero and your daily user count being healthy are perfectly consistent. They measure different things.

Telling "quiet" apart from "broken"

There is one reliable test. Put a device into debug mode and use the app yourself while watching DebugView. This removes the guesswork, because you know for certain that someone — you — is active.

  1. Enable debug mode on a test device

    Follow the platform instructions for your app so the device reports as a debug device.

  2. Open DebugView in the console

    Keep it visible on a second screen while you use the app.

  3. Move between screens and trigger an event

    Navigate, tap something meaningful, and watch for entries to appear.

  4. Interpret the result

    Events appearing means the SDK works and realtime was simply reporting a quiet app. Nothing appearing means the SDK is not sending, and the problem is in setup.

When realtime is genuinely wrong

  • The SDK never initialises, so no events are sent at all
  • The build you are testing is not the one configured with Firebase
  • The Firebase project is not linked to the GA4 property you are watching
  • You are watching a different property, or a different data stream, from the one the app feeds

Careful: A debug device is deliberately separated from ordinary reporting so your own testing does not distort the numbers. Do not conclude from an empty realtime view while you are in debug mode that nothing is being recorded — check DebugView instead.

How this looks in Appnaly

Appnaly reads the same realtime figures from Google, so a quiet app reads as zero live users there too. It also shows completed windows — yesterday, the last seven days, the last thirty — precisely because a single realtime number is a poor way to judge whether an app is alive. If live users is zero but the finished windows have numbers in them, the app is working and simply idle at this moment.

The case that deserves attention is the opposite one: finished windows that are also empty, several days in a row, for an app you know people are using. That points at collection, not at quietness.

Setting Firebase up for the first time? The setup guide walks through what has to be in place before any of these numbers appear.

Firebase Analytics setup guide

Related reading