Why GA4 DebugView is not showing events and how to fix it

Montherion Labs — Sat, 26 Sep 2026 03:21:08 +0000

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 /g/collect path.
Check the measurement ID: The tid parameter 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: true in 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 gcs and gcd when present. If analytics storage is denied (for example, gcs=G100), the event might not appear in DebugView depending on your consent mode configuration. G110 also 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.

How Tracklint helps

Tracklint is a Chrome DevTools panel that lists the GA4 requests it captures to a /g/collect path (including batches and server-side tagging endpoints that keep that path), with decoded parameters, items and consent state. It shows the measurement ID and whether the events have the debug signal (an informational finding, "GA4 debug mode is on"). Its automatic checks flag page views or standard conversions (purchase, lead and sign-up) sent twice with identical data within 1.5 seconds.

Free: the event inspector, the consent timeline, the automatic checks and a preview of the validation against your plan (the summary, the status of each row and one first finding). Pro: every finding of the validation against your plan, the GA4 vs Meta Pixel comparison and the exports, for US$19/month plus applicable taxes.

Tracklint captures GA4 requests sent to paths ending in /g/collect and Meta Pixel requests sent to facebook.com/tr; it doesn’t cover other endpoints. It checks the requests your browser sends during the journey you record, not processing inside Google Analytics or Meta, server-to-server integrations or legal compliance.

Tracklint in the Chrome Web Store · Website and more guides

Google Analytics and Google Tag Manager are trademarks of Google LLC. Meta is a trademark of Meta Platforms, Inc. Tracklint is not affiliated with, endorsed or sponsored by Google or Meta.

This article was written with AI assistance (#ABotWroteThis). It was first published on the Tracklint website: Why GA4 DebugView is not showing events and how to fix it.

DEV Community: Montherion Labs

Why GA4 DebugView is not showing events and how to fix it

Check the browser in DevTools

Causes outside the browser

How Tracklint helps