DebugView is a tool built into Google Analytics 4 that lets you see in real time the events sent by an app or website to the measurement platform. Unlike standard reports, which show data after processing that can take several hours, DebugView displays information as soon as it is received, allowing you to immediately check whether a configuration works as expected.
This feature is designed especially for developers, analysts, and marketing specialists who need to validate tracking before releasing it to production. By enabling debug mode on a device or in a browser, collected events are marked and routed to a dedicated view, separate from real user data. This way you can inspect parameters, properties, and interaction sequences without polluting the final statistics.
The mechanism behind debug mode
The mechanism relies on sending events marked with a special debug mode. When this mode is active, the GA4 property recognizes the data as coming from a verification device and shows it in the DebugView section of the interface. Events appear in a tree structure: each event can be expanded to show the associated parameters and transmitted values.
The display is temporary and tied to the debug session. If the device stops sending events, the timeline stops. This makes the tool ideal for targeted, short-term tests, not for historical analysis.
Permissions and activation: what you need
To use DebugView you need the appropriate permissions on the GA4 property, typically the editor role or higher. You also need to enable debug mode on the device or environment you want to verify. The methods vary depending on the platform and the implementation tool used.
On a website
For a website, debug mode can be enabled via a dedicated browser extension or by setting a specific parameter in the tag configuration. Once active, requests sent to the platform are marked and appear in DebugView.
In mobile apps
In mobile apps, debug mode is enabled with a configuration option provided by the platform SDK. On Android and iOS there are different procedures, but the goal is the same: to have events marked as debug and displayed in the correct property.
Aggregated data and individual events in real time
DebugView and standard GA4 reports serve different purposes and should not be confused. Standard reports aggregate data from all users, apply thresholds and privacy treatments, and take time to process. DebugView, by contrast, shows individual events in real time, without aggregation and without the same thresholds.
| Feature | DebugView | Standard reports |
|---|---|---|
| Update | Real time | After hours of processing |
| Data shown | Individual debug events | Aggregated data from all users |
| Persistence | Temporary, tied to the session | Historical, according to data retention |
| Typical use | Configuration verification | Performance analysis |
| Impact on real data | None | Forms the basis of statistics |
What it offers and what it doesn’t show
The main advantage of DebugView is speed: it lets you identify implementation errors, missing parameters, or duplicate events before data enters official reports. This reduces the risk of making decisions based on incorrect measurements.
The most obvious limitation is that the tool does not provide an overview: it shows what happens on one device at a time and does not allow statistical analysis. Also, the time window is short and data is not retained for long. For this reason, DebugView should be understood as a technical control tool, complementary to and not a replacement for reports.
The step-by-step verification sequence
- Check that you have the necessary permissions on the GA4 property.
- Enable debug mode on the device or browser to be tested.
- Open the DebugView section in the admin interface or in the analysis section.
- Interact with the site or app to generate the events to check.
- Expand each event to read the transmitted parameters.
- Compare the observed values with those expected from the configuration.
- Fix any anomalies and repeat the test.
- Disable debug mode once verification is complete.
Frequently asked questions about DebugView GA4
What exactly does DebugView show?
It shows in real time the events sent by a device in debug mode, with their parameters and values. It does not show aggregated data from other users.
Do debug data affect official reports?
No, events marked as debug are routed to the dedicated view and do not alter the property’s final statistics.
How long do events remain visible?
Events remain visible only for the duration of the debug session and for a short period afterward. They cannot be viewed days later.
Do I need a browser extension to enable it?
It is not mandatory, but a dedicated extension simplifies activation on the web. Alternatively, you can act on the tag configuration.
Can I use DebugView on multiple devices at the same time?
Yes, it is possible, but reading becomes more complex. For accurate checks, it is better to test one device at a time.
What permissions are required to access it?
Typically, the editor role or higher on the GA4 property is required. Users with read-only permissions may not see the section.
Having this problem?DebugView GA4 not showing conversion events?Without accurate debugging, conversions are not recorded and Google Ads campaigns waste budget. I configure GA4, GTM, and advanced conversions for precise, verified tracking.Discover the Conversion Tracking service