How to Use Google Analytics Debugger

Ensuring your Google Analytics data is accurate is critical, but troubleshooting tracking issues can often feel like searching for a needle in a haystack. If you've ever found yourself wondering if your events are firing correctly or why conversions aren't showing up, there's a simple tool that gives you a direct, real-time look at the data being sent from your site. This article will show you how to use the Google Analytics Debugger to verify your setup and troubleshoot problems with confidence.

Graphed

Still Building Reports Manually?

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

Watch the Demo

What is the Google Analytics Debugger?

The Google Analytics Debugger is a free Chrome browser extension created by Google. When activated on your website, it logs detailed information about every tag, event, and data point being sent to Google Analytics directly into your browser's Developer Console. Think of it as a live feed of your analytics tracking in a human-readable format. Instead of waiting hours for data to appear in your reports and wondering if it's correct, the debugger shows you exactly what GA receives the moment it happens.

This behind-the-scenes look is incredibly useful for marketers, developers, and analysts who need to validate their tracking implementation on the fly.

Why You Need the GA Debugger in Your Toolkit

You might be comfortable looking at reports within the GA4 interface, but that data is processed and aggregated. The debugger shows you the raw, individual "hits" as they are sent. Here’s why that's so important:

• Immediate Verification: Confirm that your base GA4 tracking code is installed and firing correctly on every page load without having to wait for the data to process.
• Event Tracking Troubleshooting: See if custom events - like button clicks, form submissions, or video plays - are being triggered as expected. You can inspect the event names and any parameters you’re sending with them.
• E-commerce Validation: For online stores, this is a must-have. You can use it to verify that e-commerce events like add_to_cart, begin_checkout, and purchase are sending the correct product details, prices, and transaction IDs.
• Checking Custom Dimensions and Metrics: See in real-time if custom user properties (like 'account_type' or 'logged_in_status') or event parameters are being captured and sent to GA properly.
• Save Time and Frustration: It dramatically cuts down on the troubleshooting lifecycle. You no longer have to make a change, wait a day, and then check reports. You can make a change and see the result instantly.

How to Install and Enable the GA Debugger

Getting started is quick and easy. Since it's an official Google extension, you just need to add it to your Chrome browser.

Step 1: Install the Extension Head over to the Google Analytics Debugger page on the Chrome Web Store. Click "Add to Chrome" and confirm the installation.

Step 2: Enable the Debugger Once installed, you’ll see a small Google Analytics icon next to your address bar, typically with an "OFF" label on it. Simply click this icon to turn it on for your current tab. The icon's label will change to "ON."

Important: To start debugging, you need to turn the extension on and then reload the web page you want to inspect. The debugger only starts working on page loads that happen after it has been enabled. To turn it off, just click the icon again.

Graphed

Still Building Reports Manually?

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

Watch the Demo

Putting the Debugger to Work: Reading the Console Output

With the extension installed and enabled, you're ready to start inspecting your traffic. This is where you’ll find all the rich diagnostic information.

Step 1: Open the Developer Console

On the webpage you want to debug, open your browser's Developer Console. You can do this by right-clicking anywhere on the page and selecting "Inspect," then clicking the "Console" tab. Alternatively, you can use a keyboard shortcut:

• Windows/Linux: Ctrl + Shift + J
• Mac: Cmd + Option + J

Step 2: Filter the Console (Optional but Recommended)

The console can get noisy with messages from other scripts on your site. To make your life easier, type GTM_TRACER into the filter box at the top of the console. This will hide most other messages and only show output from the Google Analytics Debugger.

Step 3: Understanding the Hit Data

As you navigate your site and interact with different elements, you’ll see new blocks of information appearing in the console. Each block represents a single "hit" sent to Google Analytics. This could be a page view, an event, a conversion, or another type of interaction.

The output looks a bit technical at first, but it's organized logically. Let's break down what you're seeing in a typical GA4 event hit:

>> GTM_TRACER: Published event: "page_view"
Hit sent to G-XXXXXXXXXX:
  en: "page_view"
  _fv: 1
  _ss: 1   
  dl: "https://www.yourwebsite.com/homepage"
  dt: "Your Awesome Homepage Title"
  tid: "G-XXXXXXXXXX"
  cid: "123456789.1234567890"  
  ep.page_title: "Your Awesome Homepage Title" 
  ep.ga_session_id: "987654321" 

While there are many parameters, a few are particularly important for troubleshooting:

• tid: This is your Measurement ID. The first thing you should check is that this matches your GA4 property's ID.
• en: This is the event name. For a page load, it will be page_view. For a custom event, it will be whatever you named it, like generate_lead.
• dl: Document Location. This is the full URL of the page where the event occurred.
• dt: Document Title. This is the title of the page.
• ep. and epn.: Event Parameters. These prefixes indicate any custom parameters you are sending along with your event, both text (ep.) and numeric (epn.). For example, ep.button_text: "Learn More" would show the text of a clicked button.
• up.: User Properties. If you set custom user properties, you’ll see them with this prefix.

Graphed

Still Building Reports Manually?

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

Watch the Demo

Common Scenarios for Using the GA Debugger

Now that you know what to look for, let's apply it to a few practical, everyday situations.

1. Verifying Your Base GA4 Installation

The simplest check is to ensure your tracking is working at all. After enabling the debugger and loading any page on your site, you should see hits for at least two events in the console: page_view and user_engagement. If you see those, along with your correct Measurement ID (tid), you can be confident your foundational tracking is in place.

2. Troubleshooting a Custom "Contact Form Submission" Event

Imagine you've set up an event to fire whenever someone submits your main contact form. You expect to see this populate in GA4 but it isn't. The debugger is your first stop.

Here's how you'd use it:

1. Enable the debugger and open the console.
2. Navigate to your contact page.
3. Fill out the form and click submit.
4. Watch the console immediately after you click submit.

You should see a new hit appear. Look for an event name (en) that matches what you configured, e.g., en: contact_form_submit. You can also inspect the event parameters to confirm you're capturing the correct information, such as ep.form_id: 'side_widget_contact'.

If you don't see the hit, you know the problem is with the trigger - it's not firing the event at all. If you do see the hit but the parameters are wrong, you know the issue is with how data is being collected and passed to the tag.

3. Checking an "Add to Cart" E-commerce Event

E-commerce tracking must be precise. To check if an add_to_cart event is working, navigate to a product page and click the add to cart button. You should see a hit with en: "add_to_cart". More importantly, you should inspect the parameters to ensure all the required item-level data is being passed, such as:

• currency: The currency code (e.g., "USD").
• item_name: The name of the product added.
• item_id: The SKU or ID of the product.
• price: The price of a single unit.
• quantity: The number of units added to the cart.

Without the debugger, identifying a missing price or incorrect item name could take days of missed or inaccurate sales data to notice.

Graphed

Still Building Reports Manually?

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

Watch the Demo

Connecting the Dots: From the Console to GA4's DebugView

The GA Debugger has a twin feature inside the GA4 platform called DebugView. When the extension is active, it adds a special parameter (_dbg=1) to all the hits it sends to Google. This parameter tells GA4, "Hey, this is a debug session. Don't process this with the rest of the 'live' data, but instead, send it over to the DebugView report."

To access it, go to your GA4 property and navigate to Admin > Data display > DebugView.

Here, you'll see a real-time stream of events coming from your browser (and any other devices in debug mode). It organizes the events into a chronological timeline, allowing you to click on any specific event (like contact_form_submit) to see all the parameters that were sent with it - just as you saw in the console, but this time from GA's perspective. This is the ultimate confirmation that Google isn't just receiving your data, but is interpreting it correctly.

Final Thoughts

While it might seem technical at first, the Google Analytics Debugger is an accessible and incredibly powerful tool for anyone who relies on data to make decisions. It demystifies tracking by giving you a clear, instant look into your data flow, empowering you to validate new implementations, diagnose problems quickly, and maintain a high level of data quality with confidence.

Making sure your data is tracked correctly is the essential first step, but the ultimate goal is turning that data into clear, actionable insights without spending all day in platform-specific reports. It's why we built Graphed. After you've ensured your events are firing, our tool makes it easy to visualize performance by letting you create real-time dashboards using simple, natural language. You can ask Graphed to "Show me a comparison of revenue from Google Ads vs. Facebook Ads for all 'purchase' events this month," and it builds the report for you instantly, unifying data from all your connected sources and saving you hours of manual reporting work.