Short answer: DebugView in Google Analytics 4 shows the events and user properties that Analytics collects from a device in real time, so you can check your tags while you install them. It only shows devices in debug mode, which you turn on with Google Tag Assistant or a debug_mode parameter.
What DebugView shows
Google says DebugView displays the events and user properties Analytics collects from a user in real time, so you can troubleshoot as you install your tags. You find it in Admin, under Data display. The report has three columns.
| Column | What it shows | Use it to |
|---|---|---|
| Seconds stream (middle) | Events logged in the last 60 seconds; click one to see its parameters | Check that a form or button sends the event you expect |
| Minutes stream (left) | One circle per minute for the last 30 minutes, with the event count | Go back to a minute and load its events |
| Top Events (right) | The events logged most in those 30 minutes, with the current user properties | See what fired during your whole test |
Our summary of Analytics Help, read November 6, 2026.
If several devices are in debug mode, the Device selector picks the one the report follows. Like the Realtime report, DebugView does limited attribution, so Google points you to the Acquisition reports for where visits came from.
How to turn on debug mode
For your own device, Google suggests Google Tag Assistant at tagassistant.google.com or the Tag Manager preview mode. Tag Assistant adds a parameter to your website address that turns on debug mode. When you troubleshoot an installation, Google says it’s best to do it for your personal device, so you can find it easily in the Device selector.
To turn it on for every visitor, you add a debug_mode parameter set to true in your Google tag setup, or in the Google tag in Tag Manager. To turn it off, remove the parameter: setting it to false doesn’t disable debug mode. Our Google Tag Manager guide explains where those tags live.
How to check your events in DebugView
- Open Google Tag Assistant at tagassistant.google.com to turn on debug mode for your visit.
- Accept Analytics cookies on your site if your banner asks.
- In Google Analytics, go to Admin, then under Data display, click DebugView.
- Pick your device in the Device selector if more than one appears.
- Do the action you want to test, such as sending a form.
- Find the event in the Seconds stream and click it to see its parameters.
- Remove any debug_mode parameter you added when you finish.
When events don’t show up
Google says events aren’t visible in debug mode if you have client-side privacy controls, or if you use consent mode and the visitor hasn’t accepted Analytics cookies. So on a site with a consent banner, accept Analytics cookies on your test device before you look. Our guide to Google consent mode explains how that setting works.
If your device still doesn’t appear, check that the tag is on the page first. Our guide to setting up Google Analytics 4 shows how to confirm the tag with the Realtime report.
Keep test traffic out of your reports
Google says to filter out traffic while debug mode is on, so your tests don’t affect your report data. A data filter of the Developer traffic type filters out activity from developers who use debug mode.
Data filters only work from the moment you create them and don’t affect historical data. Once applied, the effect is permanent: excluded data is never processed.
Before you trust a test in DebugView
- Debug mode is on for your own device.
- Your device shows in the Device selector.
- Your test device accepted Analytics cookies.
- Each action you test shows its event in the Seconds stream.
- The event carries the parameters you expect.
- A developer traffic filter keeps your tests out of the reports.
RememberDebugView shows what GA4 receives from a device in debug mode. Test on your own device, check each event and its parameters, then keep that traffic out of your reports.
Measurement setup is part of our automation service, along with lead follow-up, and the accounts are yours. You can reach us on WhatsApp or through the form.
Quick answers about GA4 DebugView
Why don’t I see my events in DebugView?
Your device has to be in debug mode first. Google also says events don’t show in debug mode if client-side privacy controls block them, or if consent mode is on and the visitor hasn’t accepted Analytics cookies.
How do I turn on debug mode for my own device?
Use Google Tag Assistant at tagassistant.google.com or the Tag Manager preview mode. Tag Assistant adds a parameter to your website address that turns on debug mode for your visit.
Does setting debug_mode to false turn it off?
No. Google says setting the parameter to false doesn’t disable debug mode. To turn it off, remove the debug_mode parameter or field from your Google tag setup.
How far back does DebugView go?
The Seconds stream shows events from the last 60 seconds, and the Minutes stream shows one circle for each of the last 30 minutes. Click a minute to load its events into the Seconds stream.
Will my test visits show up in my GA4 reports?
They can. Google recommends filtering out traffic while debug mode is on, and a developer traffic data filter excludes activity from developers who use debug mode. Data filters don’t change data you already collected.
Sources
All read on November 6, 2026. Analytics Help: Monitor events in DebugView. Data filters.