GA4 DebugView Not Showing Events: Why It Is Empty and What to Do
Quick fix
GA4 debugview not showing events usually means debug mode isn't on for your device, or events are being held back. Start debug mode through Tag Assistant or preview mode, then open DebugView under Data display in Admin. Consent mode and client-side privacy controls can hide events, and setting debug_mode to false does not turn it off.
- Start debug mode with Tag Assistant or preview mode.
- Open Admin, then DebugView under Data display.
- Pick your device in the Debug Device selector.
- Check consent mode and privacy controls are not blocking events.
Can't fix it yourself? Send me the details
What this error means
DebugView shows events from devices that have debug mode switched on, as they happen. If no device is in debug mode, or consent or privacy controls stop events, the view stays empty even when the site is tracked normally.
Why it happens
1Debug mode is not on
Debug mode must be enabled for your device or for all devices.
How to tell if this is you: The Debug Device selector lists nothing.
2The debug parameter is set wrongly
Setting it to false does not disable debug mode, so leave the parameter out to turn it off.
How to tell if this is you: debug_mode appears with a false value.
3Consent or privacy controls
Events are not visible if client-side privacy controls apply or consent was not given.
How to tell if this is you: Events appear for users who consented only.
4Looking at the wrong device
Several devices can be in debug mode at once.
How to tell if this is you: The Debug Device selector shows others.
How to fix it
Turn debug mode on
For: Debug mode is not on, The debug parameter is set wrongly
- Use Tag Assistant or preview mode for your own device.
- For everyone, add debug_mode true to the config command or Google tag.
- For certain events only, add it to those events.
Open the right view
For: Looking at the wrong device
- Go to Admin, then Data display, then DebugView.
- Choose your device in the Debug Device selector.
Check consent
For: Consent or privacy controls
- Check that consent mode and privacy controls allow Analytics cookies for your test.
How long it takes
Google doesn't publish a timeline for this.
How to stop it happening again
- Filter out debug traffic so it does not affect your reports.
- Remove the debug parameter rather than setting it to false.
- Use the Acquisition reports, not DebugView, to judge attribution.
From my desk
I confirm debug mode is actually on for my device, usually through Tag Assistant or preview mode, then pick my device in the selector. If events still don't appear, I look at consent mode and privacy settings, because events can be hidden when analytics cookies aren't accepted. Only then do I touch the tags.
Muhammed Abdul Kalam
When to get help
- You've worked through the checks and the status still isn't changing.
- The account has many campaigns and ad groups and you cannot tell which change caused the problem.
- Results are suffering during a launch or sale and every day costs real money.
Stuck on this? Send me the details.Tell me what the platform shows and what you've tried so far.
Send me the detailsFAQs
How do I enable debug mode for myself?
Use Tag Assistant or preview mode.
How do I turn debug mode off?
Leave out the debug_mode parameter. Setting it to false does not disable it.
Why are consented users the only ones I see?
Events are not visible if consent mode is used and users have not consented to Analytics cookies.
What are the Seconds and Minutes streams?
Seconds shows the last 60 seconds of events and Minutes archives the last 30 minutes.
Can I trust attribution in DebugView?
No. It does limited attribution analysis, so use the Acquisition reports.