A classic confusion: you clearly see an event in GA4 DebugView and realtime, but in standard reports it's either missing or shows different numbers. Before treating it as a measurement bug, know that most often it's about how GA4 processes data.
Symptoms
- The event is in DebugView / realtime but not yet in a standard report.
- Report counts differ from what you see in realtime.
- Numbers keep changing over the following hours to days.
Why it happens (and usually isn't a bug)
- Processing delay. DebugView and realtime are instant, but standard reports need time to process — data usually catches up over hours and can fully stabilize over a day or two.
- Thresholding. At small volumes GA4 may hide some data for privacy, so a report shows less than reality.
- Filters and date range. The report has a different date range, filter or segment set than you think.
- Conversion definition. For the event to appear in conversion reports, it must be marked as a key event.
What to check
- 1. Wait for processing — don't compare realtime with today's standard report immediately.
- 2. Check the report's date range and filters.
- 3. Verify the event is set as a key event if you expect it in conversions.
- 4. At small volumes, expect thresholding.
When it really is a bug
If the event doesn't reach DebugView at all, it's not report lag but a measurement problem — see GA4 not showing server-side conversions. The general verification routine is in how to verify server-side tracking works.