GA4 Events Not Showing in Reports: A Troubleshooting Guide

GA4 Reporting Delays and Event Visibility

The first thing to know: GA4 standard reports have a data processing delay of 24-48 hours. Events that fired today will not appear in standard reports until tomorrow or the day after. Use DebugView (Admin → DebugView) for real-time event monitoring during development and QA, not standard reports.

Check 1: Is the Event in DebugView?

With GTM Preview Mode active, trigger the event and check GA4 DebugView simultaneously. If the event appears in DebugView:

• The event IS being received by GA4
• Wait 24-48 hours for it to appear in standard reports
• If it is a custom event: it needs to be added to custom dimensions or marked as a conversion for it to appear in most reports

If the event does NOT appear in DebugView after 60 seconds:

• The event is not reaching GA4
• Check Measurement ID in the GA4 Configuration tag (wrong ID sends to a different property)
• Check network requests in browser DevTools → Network tab → filter for "collect" or "g.co/g" — see if the GA4 request is being sent

Check 2: Is the Measurement ID Correct?

A wrong Measurement ID is the most common reason events "fire" (appear in GTM as sent) but never appear in reports. The Measurement ID format is G-XXXXXXXXXX. Verify:

• GTM → GA4 Configuration tag → Measurement ID value
• GA4 → Admin → Data Streams → your stream → Measurement ID
• These must match exactly. If you have multiple GA4 properties (dev vs prod), ensure you are checking the right one.

Check 3: Custom Event Visibility in Reports

Custom events (events with names you defined, not GA4 automatically collected events) need to be explicitly registered to appear in most reports:

• To see custom events in the Events report: wait 24 hours — they appear automatically once data is processed
• To use a custom event as a conversion: GA4 → Admin → Events → Mark as conversion
• To use a custom event parameter in reports: GA4 → Admin → Custom Definitions → Custom Dimensions → create a dimension for the parameter
• Note: custom dimensions only capture data going forward from the date they are created — historical events do not retroactively populate custom dimensions

Check 4: Internal Traffic Filter

If you have an internal traffic filter configured in GA4 (Admin → Data Filters), your own IP address traffic may be excluded from reports. If you only tested from your office network, all your test events might be filtered out.

Diagnosis: in DebugView, check if events appear under "Debug traffic" (which bypasses most filters). If events appear in Debug traffic but not in the Events report, internal traffic filtering is excluding your test data.

Check 5: Consent Mode

If Consent Mode is implemented and analytics consent is denied, GA4 events are sent in cookieless mode or not at all. In a denied-consent state, DebugView may not show events. Test with analytics consent granted to verify the tracking setup, then separately verify the consent-denied state behavior.

Summary

GA4 event troubleshooting flow: DebugView first (real-time) → Measurement ID verification → custom event/dimension registration → internal traffic filter check → consent state. Standard reports have 24-48h delay — always use DebugView during development. Custom parameters need custom dimensions registered before they appear in reports. Internal traffic filters exclude test events by IP.

See our Conversion Tracking Fix service for GA4 event diagnosis.

Need GA4 reporting issues fixed? Contact Adslytics.