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 collect in the filter. Perform the action that triggers the event. Look for a request to a…
When events do not display in Google Analytics™ 4 DebugView, the root cause may lie within the browser, network, or GA4 settings. To diagnose the issue, first inspect the browser using DevTools. Open DevTools by pressing F12 and navigate to the Network tab. Use the filter feature and type "collect" to identify any request to the /g/collect path.
Then, verify the measurement ID to ensure it aligns with the intended GA4 web data stream. Next, enable debug mode through Tag Assistant or by setting debug_mode: true in the relevant gtag/GTM configuration. Look for the debug signal "_dbg=1" in the outgoing debug signal; its presence does not guarantee the event will appear in DebugView.
Additionally, examine the consent state by checking gcs and gcd. If analytics storage is denied (e.g., gcs=G100), the event may not appear in DebugView depending on your consent mode configuration. A cookieless ping also does not ensure DebugView visibility. Confirm the network status by ensuring the request returns a 200 (OK) or 204 (No Content) status.
If the request encounters issues due to ad blockers or browser privacy settings, it will not reach GA4. If the request leaves the browser correctly, the issue may originate within GA4 itself. Google's documentation indicates two possible causes: data filters and selected devices. Data filters may exclude test traffic from reports, while a selected device in DebugView must match your testing device.
Lastly, note that processing delays may occur despite DebugView's real-time design. Tracklint is a Chrome DevTools panel that captures GA4 requests sent to /g/collect paths, including batches and server-side tagging endpoints, displaying decoded parameters and events. It also checks the measurement ID and debug signal, helping users identify any issues within their GA4 implementation. Tracklint is available for free, with a Pro version offering additional features for US$19/month.
Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.
