The DebugView report shows you data (from events, event parameters, and user properties) as Analytics collects the data. The report can help you set up data collection, troubleshoot issues as issues arise, and understand a user's behavior as the user explores your website or app.
To use the DebugView report, enable debug mode and then go to Configure > DebugView on the left.
Step 1: Enable debug mode
Google tag (Websites)
To enable Analytics debug mode in your browser, install the Google Analytics Debugger Chrome extension. Once installed, enable the extension and refresh the page. From that point on, the extension will log 'debug_mode':true events, until you disable the extension.
To monitor all the events on a page, add a 'debug_mode':true parameter to your gtag('config'), as shown here:
gtag('config', 'G-12345ABCDE',{ 'debug_mode':true });
Or, if you only want to monitor certain events, add a 'debug_mode':true parameter to just those events, for example:
gtag('event', 'xyz', { 'debug_mode':true });
To disable debug mode, exclude the 'debug_mode' parameter; setting the parameter to false doesn't disable debug mode.
Google Tag Manager (Websites)
To monitor all events, use the tag type Google Analytics: GA4 Configuration and include the field 'debug_mode' = true:
Or, if you only want to monitor certain events, use the tag type Google Analytics: GA4 Event and set the debug_mode field to true for the event:
To disable debug mode, exclude the 'debug_mode' field; setting the field to false doesn't disable debug mode.
Google Analytics for Firebase (Mobile apps)
To learn how to enable and disable debug mode in your Android or iOS project, see Debug events.
Once you enable debug mode, you can see your events in the DebugView report in both Google Analytics and the Firebase console.
Step 2: Monitor the events
Once you enable debug mode on your devices, go to Configure > DebugView in the left navigation. Start using your website or app and monitor the events as they're triggered.
The Seconds stream (the middle column) shows the events that have been logged during the last 60 seconds. The Minutes stream (the left column) shows a series of archives of events over the last 30 minutes. The right column shows the Top Events logged during the 30-minute period, as well as the Current User Properties for the currently selected development device.
Seconds stream
By default, you see a list of events logged in the last 60 seconds. Each event displays a timestamp that corresponds to the time of its logging on the development device. Click an event to see a list of associated parameters. As user property values change during the course of app usage, you see events appear in the stream, the newest ones appearing at the top.
Minutes stream
This stream shows a series of circles, one circle for each of the most recent 30 minutes. The number in the circle indicates the count of events received in that minute. Clicking on one of these circles populates the Seconds stream with events that were logged during that minute of time.
Top Events and Current User Properties
The Top Events table shows the top events that were logged during the 30-minute period. The Current User Properties table shows the latest state of the set of User Properties for the currently selected development device.
Device selector
If you've enabled debug mode on multiple devices, use the Device selector to choose the specific device on which the DebugView report will focus. This lets multiple developers focus on their own instrumentation and validation efforts without impacting one another. The device-selector menu is in the upper left of the report, labeled DEBUG DEVICE.
Attribution data
Like the Realtime report, the DebugView report performs limited attribution analysis to ensure responsive reporting. We recommend that you refer to the Acquisition reports for the most accurate attribution information.