TRACKING SPECIALIST — BARIS ASA · LONDON
Synctag
Start the check → TRACKING SPECIALIST — BARIS ASA · LONDON

READING ROOM › SYMPTOM FILES › SYM-052

SYMPTOM FILE SYM-052 FILED 09 NOV 2026 · REVISED 09 NOV 2026

GA4 DebugView is empty: what to check before you assume tracking is broken.

ALSO FILED AS
  • “GA4 DebugView not working”
  • “GA4 DebugView not showing events”
  • “DebugView shows no devices”
  • “GA4 DebugView empty but Realtime shows data”
  • “events in GTM Preview but not in DebugView”
  • “GA4 debug mode not working”
  • “Measurement Protocol events not in DebugView”

Baris Asa, tracking consultant, London · Last checked: 9 November 2026

An empty GA4 DebugView rarely means your tracking is broken. DebugView is GA4’s live test screen, separate from your reports, and it only shows events sent in debug mode. When it’s blank, the event usually left the browser without debug mode, went to a different GA4 property, or was held back by consent or an ad blocker. The browser’s Network tab tells you which.

DebugView shows the last 30 minutes, for one device at a time, and only debug-mode events. Miss any of those three and the screen stays blank while Realtime and your reports fill up normally. So before anyone changes a tag, read the request.

If you don’t run the tags yourself, pass this page to whoever does. Each check below takes a few minutes.

How do I check whether GA4 received the event?

On a desktop, open Chrome, right-click the page, Inspect, Network tab. Type collect in the filter box, reload, and do what you’re testing: a page view, an add to cart, a test order. GA4 requests go to a google-analytics.com/g/collect address, or to your own subdomain if you run server-side tagging. Click one and read its parameters.

Two of them matter here. tid is the measurement ID the event went to (G- followed by letters and numbers). _dbg is the debug flag, usually _dbg=1. Google doesn’t document the request format; _dbg=1 is the marker MeasureSchool’s guide checks for, and it’s the one I look for. Don’t confuse it with the _dbg Tag Assistant adds to the page address. Google says that one helps you view events in other debugging surfaces, and its DebugView help lists Tag Assistant as a way in; the request is where you see whether it worked.

WHAT YOU SEEWHAT IT MEANSGO TO
No collect requestThe tag didn’t sendConsent and blockers
Request, unfamiliar tidSent to another propertyProperty and device
Request, no _dbgSent, but not in debug modeDebug mode
_dbg=1 and your tidBrowser did its jobFilter and timing
WHAT THE NETWORK TAB SHOWS · and where it sends you · diagnostic map, from Google's Analytics and Tag Assistant help

If the request has _dbg=1 and your G- ID, the browser did its job and the cause is inside GA4: the device selector, a data filter, or the 30-minute window. That last row is the one that wastes afternoons.

Is debug mode actually on?

Google’s DebugView help lists two ways in. For your own browser: GTM Preview or Tag Assistant. For everyone: a debug_mode parameter on the Google tag, or on single event tags in GTM.

Four things go wrong here.

  • You’re testing in a different tab. Without the Tag Assistant Chrome extension, only the window Tag Assistant opened carries the debug signal. Test there, or install the extension: Google’s Tag Assistant help says it debugs pop-ups and new tabs opened from that window.
  • You’re relying on the GA Debugger extension. Google’s current DebugView help doesn’t list it. If you use it, check for _dbg=1 in the request rather than trusting the icon.
  • The site has a hard-coded gtag.js and no GTM. GTM Preview has no container to work with. Use Tag Assistant directly, or add debug_mode: true to the config command while you test.
  • Someone set debug_mode: false to switch it off. Google says false doesn’t disable it. The field has to be deleted. What that does to your reports is in the internal and bot traffic note.

Realtime with data and an empty DebugView is this section. Realtime shows every event GA4 receives. DebugView shows only the debug-mode ones.

On Shopify, Shopify’s help says Tag Assistant’s Troubleshoot tag feature isn’t compatible with custom pixels and doesn’t detect Google tags in them, so don’t count on a Tag Assistant session flagging events sent from a custom pixel. Shopify’s own test tool is Pixel Helper. To see the events in DebugView, set debug_mode on the tag for the test, read the collect request, then remove the field. The custom pixel note covers what else the sandbox hides.

Are you looking at the right property and device?

Read tid. If it’s a G- ID you don’t recognise, the site sends to another property: an old one, an agency’s, or a staging stream. DebugView in your property stays empty however correct the tag is. I see this most after a rebuild, when the theme still carries the old site’s G- ID alongside the new container’s. Your own ID is in GA4 Admin, Data streams.

Then the device. If several people have debug mode on, Google’s help says the Debug Device selector in the top left picks which device you see. Your events may be arriving under another entry. If the selector lists no devices, nothing in debug mode has reached this property recently.

Google’s DebugView help is direct: events don’t appear in debug mode if the site uses client-side privacy controls, or uses consent mode and the user hasn’t consented to analytics cookies.

So test after clicking Accept on the banner, in a clean window. If DebugView fills only after Accept, consent is behaving as configured. Whether it’s configured correctly is a separate test: how to check Consent Mode v2 is working. A tag that never fires, even after Accept, is on file as F-201 .

Google’s Tag Assistant help says ad blockers and other extensions can stop the Google tag running. If the collect request is missing or marked blocked, test in a Chrome profile with no extensions. If it works there, the tag is fine and your extensions blocked it. Visitors with blockers are still a real gap in your data, but it’s not the reason your test is empty.

Is a data filter removing you?

Two filters, and they behave differently.

  • Developer traffic removes debug-mode events from reports. Google says DebugView keeps working with it on, so it doesn’t explain a blank screen.
  • Internal traffic removes events from IP addresses you marked as internal. Google’s DebugView and data filter pages don’t say what it does to DebugView. Analytics Mania and MeasureSchool report that, when it’s Active, your own events can disappear from DebugView. MeasureSchool adds that the cause isn’t confirmed.

The test: move your laptop to a phone hotspot, or any network outside your IP rules, and send the event again. If it appears, the filter was removing you.

Don’t switch the filter off to debug. Google says an Active filter’s effect is permanent and excluded data is never processed, so switching it off lets real staff traffic into reports for that window. If your office IP needs DebugView every day, use a separate test property.

The filter setup itself, and the order to switch it on, is in the internal and bot traffic note. A filter that’s missing or wrong is on file as F-602 , explained in the Atlas entry for F-602.

Is it just timing?

DebugView isn’t a history. Google’s help says the Seconds stream holds the last 60 seconds and the Minutes stream the last 30 minutes. Test an order at 10:00, open DebugView at 10:40, and it’s empty. Send the event again with DebugView open.

If the request carried _dbg=1 and the right tid, the device is selected and you’re off the filtered network, give it a few minutes before concluding anything.

Server-side tagging and Measurement Protocol

If collect goes to your own subdomain, the browser hands the event to a server container, which sends it on to GA4. The debug signal has to survive that second trip. Open the server container’s Preview and read the outgoing GA4 request. If server-side Preview is itself empty, see server-side GTM errors. If GTM Preview won’t connect at all, start with why GTM Preview won’t connect.

Events your backend sends through the Measurement Protocol (a refund, an offline sale) never pass through the browser, so no Preview session flags them. Google’s Measurement Protocol guide says to put "debug_mode": true (or 1) and a positive engagement_time_msec in the event’s params, then check Realtime and DebugView. Then take debug_mode out again: left in, production events go on showing in DebugView, and a developer traffic filter drops them from reports.

The check, in order

  1. Network tab, filter collect. No request: consent, a blocker, or a tag that didn’t fire.
  2. Read tid. Unfamiliar G- ID: fix the tag or look in that property.
  3. Look for _dbg=1. Missing: turn debug mode on in the window you test in.
  4. Debug Device selector: pick your device.
  5. Another network: if the events appear, the internal traffic filter was likely removing them.
  6. Send a fresh event with DebugView open. It only looks back 30 minutes.

If all six pass and DebugView is still empty, email me the page URL and your G- ID. If DebugView is fine and the report numbers look wrong, that’s a different question: why GA4 numbers change after a few days and custom parameters not showing in reports cover the two usual causes.

Common questions

Why is my GA4 DebugView empty?

Usually one of four things: the event was sent without debug mode, it went to a different GA4 property, consent or a privacy control held it back, or an ad blocker stopped it. Practitioners also report an active internal traffic filter hiding your own events. Open the browser’s Network tab, filter for collect, and read the request: no request, a different G- ID, or no debug flag each points to a different fix.

Realtime shows my events but DebugView is empty. Why?

Realtime shows every event GA4 receives. DebugView only shows events sent in debug mode, for the device you select. Data in Realtime with an empty DebugView almost always means debug mode isn’t on for your browser, or you’re looking at another device in the Debug Device selector.

Events show in GTM Preview but not in DebugView. Why?

GTM Preview shows that a tag fired in the browser. DebugView shows what GA4 received in debug mode. If the tag fired and nothing arrived, the request was blocked, sent to another measurement ID, or held by consent. Google’s DebugView help says events won’t appear in debug mode if consent mode is in use and the user hasn’t consented to analytics cookies.

Does an internal traffic filter hide my events from DebugView?

Google’s DebugView and data filter pages don’t say. Analytics Mania and MeasureSchool report that an active internal traffic filter can remove your own events from DebugView, and MeasureSchool notes the cause isn’t confirmed. Test from a phone hotspot before you touch the filter: Google says data an active filter excludes is never processed.

Does setting debug_mode to false turn debug mode off?

No. Google’s DebugView help says setting debug_mode to false does not disable it; the field has to be removed. Left on the Google tag, it puts every visitor’s events in debug mode. Left on one event tag, it flags that event for everyone.

My events are in DebugView but not in reports. Is that the same problem?

No. That is a reporting question: processing time, an unregistered custom parameter, or a developer traffic filter doing its job. Standard reports take longer to fill than DebugView, so check them the next day before changing anything.

Sources

Read on 9 November 2026:

  • Google Analytics Help, Monitor events in DebugView (debug mode through Tag Assistant or GTM preview, or debug_mode on the Google tag for all events or on event tags for some; setting it to false does not disable it, the field must be removed; Seconds stream 60 seconds, Minutes stream 30 minutes; Debug Device selector; events don’t appear with client-side privacy controls, or with consent mode when the user hasn’t consented to analytics cookies)
  • Google Analytics Help, Filter out developer traffic (excludes debug-mode activity from reports while DebugView keeps working; Testing, Active and Inactive states; an applied filter is permanent and excluded data is never processed)
  • Google Analytics Help, Data filters (internal traffic filter excludes IP addresses or ranges; filters apply from creation forward)
  • Tag Assistant Help, troubleshoot with Tag Assistant (Tag Assistant adds _dbg to the page URL, which helps you view events in other debugging surfaces; the Chrome extension debugs pop-ups and new tabs opened from the current window; ad blockers, other extensions and consent management tools can block the Google tag)
  • Google for Developers, Measurement Protocol: verify implementation (debug_mode and a positive engagement_time_msec in params; check Realtime and DebugView)
  • Shopify Help Center, GTM in a custom pixel (Tag Assistant’s Troubleshoot tag isn’t compatible with custom pixels; test with Shopify Pixel Helper)
  • Analytics Mania, DebugView in Google Analytics 4 and MeasureSchool, how to fix GA4 DebugView (practitioner reports that an active internal traffic filter can remove your events from DebugView, cause unconfirmed; MeasureSchool checks for _dbg=1 in the Network tab)

← back to the reading room