Why GA4 DebugView is not showing events and how to fix it
Google Analytics™ 4 DebugView is the built-in tool to inspect events as they arrive. When events do not show up, the issue can be in the browser, in the network, or in the GA4 settings. This guide shows how to find the cause.
Check the browser in DevTools
- Open DevTools (F12), go to the Network tab and type
collectin the filter. - Perform the action that triggers the event. Look for a request to a
/g/collectpath. - Check the measurement ID: The
tidparameter must match the measurement ID of the intended GA4 web data stream (e.g.,G-XXXXXXXXXX). - Check the debug signal: Enable debug mode using Tag Assistant or
debug_mode: truein the relevant gtag/GTM configuration. Inspect the outgoing debug signal, commonly_dbg=1. Its presence does not guarantee that the event will appear in DebugView. - Check the consent state: Inspect
gcsandgcdwhen present. If analytics storage is denied (for example,gcs=G100), the event might not appear in DebugView depending on your consent mode configuration.G110also indicates denied analytics storage. A cookieless ping does not establish DebugView visibility. - Check the network status: Ensure the request returns a 200 (OK) or 204 (No Content) status. An HTTP success response does not prove processing in GA4, especially when the destination is a tagging server. If something blocks it, like an ad blocker or browser privacy settings, it will not reach GA4.
Causes outside the browser
If the request leaves the browser correctly, Google’s documentation points to these causes within GA4:
- Data filters: Check whether an active internal traffic filter excludes your test traffic. The developer traffic filter excludes debug traffic from reports while keeping it available in DebugView.
- Selected device: In DebugView, verify that you have selected your specific testing device in the Debug Device drop-down menu in the top left corner.
- Processing delays: While DebugView is designed to be real-time, there can sometimes be short delays.