How to Use Google Analytics 4 DebugView Documentation

Verifying that your new tags are firing correctly in Google Analytics 4 can feel like sending a message in a bottle and waiting for it to wash ashore. You set up an event, perform the action on your site, and then wait... and wait... for the data to eventually appear in your reports. GA4's DebugView solves this by giving you a real-time, second-by-second look at the data being sent from your browser or device directly to Google Analytics. This guide will walk you through what DebugView is, how to enable it, and how to use it to validate your tracking setup with confidence.

Graphed

Still Building Reports Manually?

Watch how growth teams are getting answers in seconds — not days.

Watch the Demo

What is GA4 DebugView?

DebugView is a special report inside your GA4 property that shows you a live stream of event data from testing and debugging devices. Unlike standard reports that can take 24-48 hours to process and display data, DebugView shows you events, parameters, and user properties the moment they are triggered. This instant feedback loop is essential for confirming your data collection is working as expected before you deploy changes live.

Think of it as looking over the shoulder of Google Analytics as it receives data from your website or app. You can see exactly what's arriving, in what order, and with all the associated details. It’s your primary tool for quality assurance, helping you catch implementation errors, verify custom event parameters, and ensure your e-commerce tracking is accurate from end to end.

How to Enable DebugView for a Website

To see data in DebugView, you first need to signal to GA4 that your device should be treated as a "debug" device. There are a few easy ways to do this for a website.

Graphed

Still Building Reports Manually?

Watch how growth teams are getting answers in seconds — not days.

Watch the Demo

Method 1: Use Google Tag Manager (GTM) Preview Mode (Recommended)

If you're using Google Tag Manager to deploy your GA4 tags, this is the simplest and most effective method. Activating Preview Mode automatically sets the necessary debug signal.

1. Open GTM Preview: In your Google Tag Manager container, click the Preview button in the top-right corner.
2. Connect to Your Site: A new tab will open for the Tag Assistant. Enter your website’s URL and click Connect. Your website will then open in another new tab with a "Tag Assistant Connected" badge in the corner.
3. Activate DebugView: That's it! As long as your website is connected to the GTM Preview mode, all events you trigger will automatically be sent to DebugView in your GA4 property.

This is the preferred method because it not only enables DebugView but also gives you a detailed look at what tags are firing (or not firing) and why from within the Tag Assistant window.

Method 2: Use the GA Debugger Chrome Extension

The "Google Analytics Debugger" is an official Chrome extension from Google that allows you to enable debug mode for any website you're visiting without needing access to its GTM container.

1. Install the Extension: Go to the Chrome Web Store and search for "Google Analytics Debugger." Add it to your browser.
2. Activate the Extension: Once installed, you'll see a new icon next to your address bar (it looks like a bug with "GA" on it). Navigate to your website, then click the icon. A small dropdown will show "ON" or "OFF." Click it so that it says ON.
3. Refresh the Page: You must reload the page after turning the extension on. Now, any actions you take on this site will be sent to DebugView. You can turn it off by clicking the icon again and refreshing the page.

Method 3: Manually Send the debug_mode Parameter

If you aren't using GTM and have GA4 installed directly on your site, you can manually enable debug mode by modifying the GA4 configuration code. This tells gtag.js to include the debug_mode parameter on all subsequent event hits.

Add the {'debug_mode': true} parameter to your gtag config command like this:

<!-- Google tag (gtag.js) -->
<script async src="https://www.googletagmanager.com/gtag/js?id=G-XXXXXXXXXX"></script>
<script>
  window.dataLayer = window.dataLayer || [],
  function gtag(){dataLayer.push(arguments),}
  gtag('js', new Date()),

  gtag('config', 'G-XXXXXXXXXX', {
    'debug_mode': true 
  }),
</script>

Remember to remove this line of code before publishing your changes to all users, as you typically only want your internal team's traffic appearing in DebugView.

Accessing and Navigating the DebugView Interface

Once you’ve enabled debug mode using one of the methods above, it's time to open DebugView itself. In your Google Analytics 4 property, navigate using the left-hand menu:

Admin > Property column > DebugView

The interface is split into a few key sections:

Graphed

Still Building Reports Manually?

Watch how growth teams are getting answers in seconds — not days.

Watch the Demo

The Middle Column: Timeline of Events

This is the main section, where you'll see a chronological stream of events coming in from your debug device. Each row represents a single event (like page_view, session_start, or a custom event like form_submission). You will see blue icons for events, green for conversions, and orange for user properties.

When you click on an event in this stream, the right side of the screen populates with a list of the parameters that were sent with that event. Click on a parameter to see its value. This is where you can confirm that your custom data, like a clicked button's text or a product's price, is being captured correctly.

The Left Column: Seconds Stream

This column provides a minute-by-minute visualization of the events arriving. Each circle represents one minute, and the numbers inside the circles tell you how many events were recorded during that minute. It’s useful for an at-a-glance view to see if events are actively coming through.

The Top Right Corner: Device Selector

If multiple people on your team are debugging a site at the same time, this dropdown lets you select which specific device to monitor. By default, it will show data from all active debug devices.

The Middle-Right Side Pane: Parameters, User Properties, Items

When you click an event, a right side pane will appear. The Parameters tab shows parameters specific to the selected event where you can find custom information you pass to an event from your custom code or with Data Layer. You will also see User properties in the section User Properties attached to the user who performed the event. If an event belongs to e-commerce, it will probably have an items list with product parameters in another section of this right-side menu.

Graphed

Still Building Reports Manually?

Watch how growth teams are getting answers in seconds — not days.

Watch the Demo

Using DebugView: Practical Troubleshooting Examples

Example 1: Verifying a "Contact Us" Form Submission

Let's say you just created a custom event called contact_form_submit that should fire when a user submits your contact form. You also want to capture the form's location (e.g., "footer" or "sidebar") as a parameter.

1. Enable GTM Preview Mode and connect to your site.
2. Navigate to the page with your contact form and fill it out. Click "Submit".
3. Watch the DebugView stream. You should see a blue event icon for contact_form_submit appear within seconds.
4. Click on the contact_form_submit event in the stream.
5. A pane will appear with the parameters sent with this hit. You should see a row for form_location with its value like "footer". If you see "(not set)" or the parameter is missing, you know your GTM variable or trigger configuration needs a second look.

Example 2: Troubleshooting an E-commerce Cart Funnel

Imagine your add_to_cart events are showing up, but they're missing pricing information, causing your revenue reports to be inaccurate.

1. Enable debug mode for your e-commerce site.
2. Navigate to a product page and click the "Add to Cart" button.
3. In DebugView, find the add_to_cart event.
4. Click the event. In the parameters list, you should see parameters like currency and value, along with an items array.
5. Click on the items parameter to expand it. Here, you should see all the information about the product you just added: item_id, item_name, price, quantity, etc.
6. If the price or value parameter is missing or registers as 0, you've pinpointed the problem. The data is not being correctly pulled from your store's data layer or your GTM setup needs adjustment.

Example 3: Confirming User Audiences

Let's say you've set up a user property called user_type to identify signed-in members and then want to be sure it sets for different audiences.

1. First, on your browser, you need to clear your GA4 cookie _ga_XXXXXXX (GTM debug will get a new Client ID on every reload).
2. Sign out of your account on your website. After the page reloads, you can go to DebugView and select any tag to be sure user_type = is not set.
3. Next, sign in on your site (in the same browser tab with debug enabled).
4. In DebugView, find the next page_view events.
5. Select it, go to the user_properties tab. You should now see that property user_type has some value, i.e., logged_user = true. This confirms your audience logic is working as intended, and users will be correctly segmented into your audiences in other reports in GA.

Final Thoughts

Getting comfortable with GA4's DebugView is one of the most powerful steps you can take to ensure your data is clean, accurate, and reliable. It removes the frustrating guesswork and lengthy delays from the debugging process, allowing you to validate tracking changes instantly and deploy with confidence. Learning it is essential for having 100% confidence when your reports are in the hands of management.

Verifying data collection is just the first step. The real challenge is turning all that data - from GA4, ads platforms, your CRM, and more - into actionable insights. At Graphed (target="_blank" rel="noopener"), we simplify this process by connecting users with an AI Analyst assistant. You can use natural language to build dashboards in real-time. Instead of manually wrangling data at every sales meeting, you can ask our tool "show me this Quarter Conversion Rate and Revenue vs previous quarter's on a line chart" and get an amazing visualization instantly.