Troubleshooting
Why GA4 Data Can Be Delayed
Updated 2026-09-043 min read
Short answer
Standard reports are processed in batches rather than continuously, so recent data arrives late and can still change after it appears. Realtime is separate and immediate, which is why the two disagree.
A number that is missing at 9am and present at 3pm has not been fixed by anything you did. Processing delay is normal behaviour, and knowing its shape saves you from debugging a system that is working.
Why there is a delay at all
Realtime is built for immediacy and covers a short window. The standard reports are built for completeness: events are gathered, attributed, deduplicated and aggregated in batches. That work is what makes the reports trustworthy, and it is also what makes them late.
| Surface | Timing | Stability |
|---|---|---|
| DebugView | Seconds | One device only |
| Realtime | Continuous, short window | Does not revise |
| Standard reports | Batched, hours | Can change after first appearing |
What delay looks like
- Today looks far too low early in the day, then fills in
- Yesterday changes slightly when you check it again later
- A dimension breakdown appears after the total it belongs to
- Realtime shows activity while the daily figure has not moved yet
Note: The last one is the most reassuring pattern in this list. Realtime showing activity proves collection is working, whatever the daily report is doing.
Thresholds are not delay
Sometimes a figure never arrives rather than arriving late. Analytics withholds some figures when the counts behind them are small enough that reporting them could identify individuals. The result looks like missing data but is a deliberate privacy behaviour, and waiting will not change it.
This is most visible when you slice a small audience — a single country, a single app version, a narrow date range — and get an empty cell next to a total that clearly is not empty.
Careful: A breakdown that does not sum to its own total is usually thresholding, not a bug. Adding the visible rows and reporting that as the total will understate it.
Telling delay from a real problem
Delay resolves. A real collection problem does not. The distinction is a question of time and consistency rather than of any single screen.
- Check DebugView — if events arrive, collection is fine and you are waiting on processing
- Compare several completed days — steady numbers with only the newest day lagging is normal
- Look for a run of empty days on an app you know is being used — that is not delay
How Appnaly deals with it
Appnaly reads what Google has at the moment it asks. It does not estimate, interpolate, or fill a gap with a plausible number, because a figure invented to look complete is worse than an honest blank — you would have no way to tell the two apart later.
This is also why Appnaly labels completed windows separately from live ones. Yesterday and the last seven days are stable enough to compare; the current day is still being written, and treating it as final is how people conclude their app collapsed overnight.
If figures are still missing after a full day has completed, the cause is more likely to be setup than timing, and the troubleshooting checklist is the better place to look.