What is Debug View in Google Analytics 4?

Verifying that your Google Analytics 4 setup is working correctly can feel like shouting into the void. You add a new tracking tag, click around on your website, and then wait... and wait... for the data to eventually show up in your reports. This article explains how to use DebugView, a real-time monitor that shows you exactly what data GA4 is receiving from your browser as you send it.

Graphed

Still Building Reports Manually?

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

Watch the Demo

We'll walk through what DebugView is, how to turn it on, and how to use it to confirm your events, parameters, and user properties are being tracked perfectly. It's the best way to get instant feedback and fix tracking issues before they affect your data.

What is GA4 DebugView, Exactly?

DebugView is a special report inside your Google Analytics 4 property that shows you a granular, real-time stream of events from a single browser or device that has debugging enabled. Think of it as opening up a direct, live feed between your computer and Google's servers.

Unlike standard GA4 reports that can have a delay of several hours and show aggregated data from all users, DebugView is:

• Instant: Events appear within seconds of you performing an action on your website.
• Raw: It shows the unprocessed event data exactly as GA4 receives it.
• Isolated: It focuses only on data from your specific "debug" device, so you aren't seeing traffic from other real-time visitors.

This makes it an indispensable tool for anyone setting up or troubleshooting their analytics. You get immediate confirmation that your tags are firing correctly without having to wait a day to find out something was broken.

Key Use Cases: When to Use DebugView

So, when would you actually need to use this? Here are the most common scenarios where DebugView is your best friend.

Graphed

Still Building Reports Manually?

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

Watch the Demo

1. Validating Your Initial GA4 Setup

The moment after you've installed the GA4 configuration tag on your site is the perfect time to use DebugView. Just by enabling it and navigating to a few pages, you can instantly confirm that the foundational page_view and session_start events are firing. If they're showing up in the timeline, you know the core connection is working.

2. Testing New Custom Events

Let's say you want to track when users submit a "Request a Demo" form. You configure a custom event called generate_lead in Google Tag Manager. Instead of submitting the form and hoping it tracks, you can use DebugView.

Enable debug mode, open your site, fill out and submit the form. You can then watch the DebugView timeline. If the generate_lead event appears in real-time, you know your GTM trigger and tag are set up correctly. If it doesn't, you know immediately there's an issue to investigate.

3. Verifying Event Parameters

Events on their own are good, but events with additional context (parameters) are great. Imagine you have a custom event for downloads called file_download. You likely want to send along a parameter that specifies which file was downloaded, like file_name.

In DebugView, you can click on any event in the timeline to inspect the parameters that were sent with it. When you trigger your file_download event, click on it and verify that the file_name parameter is present and contains the correct document title.

Graphed

Still Building Reports Manually?

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

Watch the Demo

4. Troubleshooting Ecommerce Tracking

Ecommerce tracking in GA4 is event-based and notoriously tricky to get right. From view_item and add_to_cart to the all-important purchase event, each one needs to carry very specific parameters for items, value, and transaction IDs.

DebugView is essential for this. You can step through your entire purchase funnel and check each event individually. For example, when you test a purchase, you can click on the purchase event in DebugView to confirm that:

• The currency and value parameters are correct.
• An items array is present and populated with the products you just bought.
• The transaction_id is being recorded properly.

Catching a mistake here, like a missing item array, can save you from massively underreporting your revenue.

How to Enable and Use DebugView

There are a few ways to turn on debug mode for your browser. The two most common and user-friendly methods involve using Google Tag Manager's Preview mode or a simple Chrome extension.

Method 1: Using GTM Preview Mode

This is the preferred method if you're managing your GA4 tags via Google Tag Manager. Activating GTM's Preview automatically enables GA4 debug mode.

1. Navigate to your Google Tag Manager container and click the "Preview" button in the top-right corner.
2. In the new tab that opens, enter your website URL and click "Connect".
3. Your website will load in another new tab, with the GTM debug panel connected in the corner.
4. Now, go to your GA4 property. In the left-hand navigation, go to Admin, and under Data display, click on DebugView.

That's it! As you navigate around your site and trigger events, you'll see them appear in the DebugView report.

Method 2: Using the Google Analytics Debugger Chrome Extension

If you aren't using GTM or you just want a quick way to enable debugging without opening Preview mode, this is a great alternative.

1. Install the official Google Analytics Debugger extension from the Chrome Web Store.
2. Navigate to your website.
3. Click on the puzzle-piece icon for your Chrome extensions and find the Google Analytics Debugger. Clicking its icon will turn it ON.
4. Reload your webpage. The extension's icon will now show a small "ON" banner.
5. Go to the DebugView report in GA4. Your device's activity will now appear.

To stop sending debug data, just click the extension's icon again to turn it OFF.

Understanding the DebugView Interface

When you first open DebugView, it can look a bit busy, but it's organized logically. There are two main columns to pay attention to.

The Middle Column: Seconds and Events Timeline

This is the main activity stream. Events are logged chronologically as they happen. Each row represents an event, marked with an icon:

• Blue Icon: A standard event (e.g., page_view, scroll).
• Green Icon: A conversion event.
• Orange Icon: A user property being set or changed.

The vertical blue lines organize the events into minute-by-minute blocks.

Graphed

Still Building Reports Manually?

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

Watch the Demo

The Right Column: Parameter Details

When you click on an event in the middle column, this section comes to life. It shows you all the parameters that were sent along with that selected event.

For example, if you click a page_view event, you'll see parameters like page_location (the full URL) and page_title. If you click your custom generate_lead event, this is where you'd confirm if parameters like form_name and lead_type came through correctly.

Nearby, you'll also see tabs for looking at the User Properties currently set for your device and the most common events over the last 30 minutes.

A Few Tips and Common Gotchas

• Device Selector: At the top-left of DebugView, you'll see a "Debug device" selector. If multiple people are debugging simultaneously, make sure you've selected your own device to avoid confusion.
• "I can't see my data!": If nothing is appearing, give it a minute. Then, double-check that GTM Preview is connected or the Chrome Extension is turned on. Also, remember to reload the page on your site after enabling the extension. Ad-blockers can also sometimes interfere with GA4 tracking.
• Don't Confuse it with the Real-Time Report: The standard Real-Time report and DebugView are different. The Real-Time report shows a high-level overview of all your site visitors in the last 30 minutes and is subject to some processing rules. DebugView is a raw, deep-dive into one specific user's unprocessed data.

Final Thoughts

Getting comfortable with DebugView is a non-negotiable step for anyone serious about accurate data collection in Google Analytics. It takes the guesswork out of troubleshooting by giving you direct, immediate feedback on your setup, ensuring the event data you're collecting is reliable and complete before it ever hits your reports.

While DebugView is perfect for checking if your raw GA4 data is flowing correctly, the next step is connecting it with data from all your other platforms to get real answers about business performance. We built Graphed for this exact reason. Instead of wrangling multiple data sources or piecing together dashboards manually, we let you use plain language to build the reports you need in seconds—connecting tools like GA4, Shopify, and your ad platforms automatically to give you insights that drive growth.