You flipped on debug mode, opened GA4 DebugView, clicked around your store — and the panel just sits there empty. Frustrating, because you can’t tell whether tracking is broken or debug mode never turned on.
Almost always it’s the second one. DebugView is a fussy tool with a narrow definition of “debug traffic,” and most empty panels come down to a handful of causes. Here’s the ordered checklist — start at the top and stop when events appear.
First, understand what DebugView actually shows
DebugView is not a report of your store’s traffic. It shows only the sessions that are currently in debug mode — normally just the one browser you’re testing from. If debug mode isn’t active on your device, the panel is empty even though tracking is working perfectly for real shoppers.
So an empty DebugView usually means “I haven’t marked my own traffic as debug yet,” not “tracking is broken.”
The ordered diagnosis
1. Is debug mode actually on?
There are three legitimate ways to flag your traffic as debug:
- GTM Preview / Tag Assistant — if you deploy GA4 through Google Tag Manager, opening Preview mode automatically sends
debug_mode: true. This is the most reliable method. - Google Analytics Debugger Chrome extension — toggle it on, then reload the store.
- A
debug_mode: trueparameter on the GA4 config/event (hard-coded).
If none of these is active, DebugView will be empty. Turn one on and reload the page — events should appear within a few seconds.
2. Are you looking at the right property — and the right device?
- Wrong property/data stream. Confirm the Measurement ID (
G-XXXXXXX) firing on your store matches the property whose DebugView you’re staring at. On Shopify it’s easy to have a stale ID in a theme snippet and a newer one in GTM. - Device selector. DebugView has a device picker in the top-left. If several testers are in debug mode, you may be looking at someone else’s device. Select yours.
3. Is your own consent banner blocking you?
If you run Consent Mode v2 (mandatory for EU/UK traffic) and you haven’t accepted your own banner, analytics may be denied — and if your setup blocks instead of adjusts collection, no event is sent at all. Accept consent, reload, and re-check. (If events are still blocked after consent, that’s a real misconfiguration — see Consent Mode blocking all GA4 events.)
4. Is an ad blocker eating the request?
Ad blockers, Brave’s shields, and strict tracking-protection settings block the request to google-analytics.com / the Measurement Protocol endpoint before it ever leaves the browser. Test in a clean profile — an incognito/private window with no extensions — to rule this out. This is also a reminder of why you eventually want server-side tracking: it can’t be blocked at the browser.
5. Is the config/GA4 tag even firing?
If debug mode is on, consent is granted, and there’s no blocker but DebugView is still empty, the tag itself isn’t firing:
- In GTM Preview, confirm the GA4 Configuration tag and your event tag show as fired, not “not fired.”
- Check the tag’s trigger — a common Shopify mistake is a trigger that never matches on the checkout or thank-you page (especially after the
checkout.liquidmigration). - If the
purchaseevent specifically is missing, walk the purchase event not firing checklist.
6. Server-side setups: is debug routed through?
If GA4 is fed from a server container (sGTM), debug_mode has to survive the hop to the server and be forwarded to GA4. If it isn’t passed through, browser QA looks fine but DebugView stays empty. Verify the server path end-to-end with these five checks, and if the server preview is empty too, troubleshoot the server GTM.
Quick reference
| Symptom | Most likely cause | Fix |
|---|---|---|
| Panel totally empty | Debug mode not on | Open GTM Preview or the GA Debugger extension |
| Empty for you, others see events | Wrong device selected | Pick your device in the DebugView device selector |
| Empty after consent banner shown | Consent denied/over-blocking | Accept consent; check Consent Mode config |
| Empty only in your normal browser | Ad blocker/extension | Test in a clean incognito profile |
| Tag shows “not fired” in Preview | Trigger doesn’t match | Fix the trigger / event configuration |
| Browser fine, server path empty | debug_mode not forwarded | Pass debug through the server container |
Not sure which of these is silently costing you conversions? The free Tracking-Health Mini-Audit checks your GA4, consent and server-side setup and returns a red/yellow/green score in ~10 minutes.
FAQ
Why is my GA4 DebugView empty?
Usually debug mode isn’t actually on — DebugView only shows devices flagged as debug traffic via GTM Preview, the GA Debugger extension, or a debug_mode:true parameter.
How do I enable debug mode on Shopify? Open your store in GTM Preview, or install the Google Analytics Debugger Chrome extension and toggle it on, then reload.
Does DebugView show all traffic? No — only sessions currently in debug mode. Use Realtime or standard reports for everyone else.
Can consent mode block DebugView? Yes — if analytics is denied and your setup blocks collection, nothing is sent. Accept your own banner before testing.
Sources
- Google — GA4 DebugView (Analytics Help)
- Google — Monitor events with DebugView (developer guide)
- Google — Verify your GA4 implementation