How to Debug Google Analytics 4

Nothing is more frustrating than looking at your Google Analytics 4 reports and realizing the data doesn't make sense. Whether it's missing conversions or strange traffic numbers, incorrect tracking can lead you to make bad decisions about your marketing and website. We'll walk you through how to use Google's own tools to find and fix the most common GA4 setup issues so you can trust your data again.

Graphed

Still Building Reports Manually?

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

Watch the Demo

Why Debugging GA4 is Essential (And When to Do It)

Setting up Google Analytics 4 isn't a "set it and forget it" task. Tagging issues, website updates, or plugin conflicts can break your tracking without you realizing it for weeks. Regularly debugging your setup is crucial for data accuracy. Without it, you're flying blind.

You should make a habit of debugging your GA4 implementation any time you:

• Complete a new GA4 setup.
• Add a new custom event (like a form submission or button click).
• Set up a new conversion action.
• Change how your website's data layer is structured.
• Launch new landing pages or marketing campaigns.
• Notice that your reports look "off" or numbers suddenly drop.

Getting comfortable with debugging ensures your investment in analytics pays off with reliable insights into user behavior and campaign performance.

Your Core GA4 Debugging Tool: Hello, DebugView!

Google Analytics 4 has a powerful, built-in feature specifically for troubleshooting: DebugView. This tool gives you a real-time stream of all the events, parameters, and user properties being sent from your browser to GA4 as you interact with your site. It’s the single most important tool for confirming your tags fire correctly.

Graphed

Still Building Reports Manually?

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

Watch the Demo

How to Enable Debug Mode to Use DebugView

To see data in DebugView, you first need to tell Google Analytics you're in "debug mode." There are two primary ways to do this, but the first method using Google Tag Assistant is the most reliable.

Method 1: Using Google Tag Assistant (Recommended)

Google Tag Assistant lets you open a special debug version of your website that communicates directly with GA4's DebugView. It works whether you've installed GA4 via Google Tag Manager or directly on your site with a gtag.js snippet.

Here’s how to use it:

1. Navigate to tagassistant.google.com.
2. Click the Add domain button.
3. Enter your website's full URL (e.g., https://www.yourwebsite.com) and click Connect.
4. A new browser tab or window will open with your website. You'll see a small "Tag Assistant Connected" badge in the bottom-right corner. This confirms you're in debug mode.
5. Keep both the Tag Assistant tab and your website tab open. In your GA4 account, navigate to Admin > Data display > DebugView.

You should now start to see events from your website populate in DebugView as you click around and interact with your site in the new tab.

Method 2: Using the GA Debugger Chrome Extension

If you need a quicker, simpler way to enable debug mode just for yourself, the GA Debugger Chrome extension is a great option. It’s slightly less comprehensive than Tag Assistant but perfect for fast checks.

1. Install the official Google Analytics Debugger extension from the Chrome Web Store.
2. Once installed, click the puzzle icon in your Chrome toolbar to find the extension’s icon (it looks like a bug with "GA" on it). Click on it.
3. A small dropdown will appear. Click ON. The icon will now have a small "ON" badge.
4. Open your website in a new tab and start browsing. Just like with Tag Assistant, this should trigger debug mode.
5. Navigate to DebugView in your GA4 account to see the real-time event stream.

Remember to turn the extension OFF when you're done troubleshooting, as leaving it on can affect your browsing experience on other sites.

Using DebugView to Solve Common GA4 Problems

Once you see your events flow into DebugView, you can start testing for common issues. The interface shows events in a chronological stream. Clicking on any event in the main stream reveals the specific parameters sent with it.

Step 1: Verifying Basic Pageviews

The first thing to check is that basic page tracking is working. Every time you navigate to a new page on your site, you should see a page_view event pop up in DebugView.

1. While in debug mode, visit a few different pages on your website.
2. Watch the DebugView stream. A page_view event (in blue) should appear for each new page loaded.
3. Click on one of the page_view events in the timeline.
4. In the Parameters tab on the right, look for critical information like:

What to look for: If page_view events aren't firing, or if the parameters are incorrect (e.g., the URL is wrong), it's a sign your base GA4 tag is not installed correctly on all pages of your site.

Graphed

Still Building Reports Manually?

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

Watch the Demo

Step 2: Testing Custom Events and Conversions

This is where DebugView really shines. Let's say you've set up a custom event to track when someone submits your "Contact Us" form, and you've named the event generate_lead.

1. Go to your contact page and fill out the form yourself.
2. Immediately switch back to the DebugView window.
3. Look for your custom event name - in this case, generate_lead - in the event stream. Keep in mind that conversion events show up in green, while regular custom events are blue.
4. Click on the generate_lead event.
5. Inspect its parameters. Did you send along extra info, like the form_id or form_destination? Verify that those custom parameters are present and have the correct values.

What to look for: If the event doesn't appear at all, the tag trigger you configured (e.g., "on form submission") is likely faulty. If the event appears but its parameters are missing or incorrect, the issue is with how you're capturing and sending that data in your tag variables.

A note on conversions: For an event to count as a conversion, you must first mark it as such in GA4 by going to Admin > Data display > Conversions and making sure the toggle is switched on for your event name. Conversions will appear in DebugView instantly, but it can take 24-48 hours before they show up in standard GA4 reports.

Step 3: Checking Ecommerce Tracking

For ecommerce sites, debugging events like add_to_cart, view_item_list, and purchase is vital. One misplaced parameter can throw off your entire revenue reporting.

Let’s test an add_to_cart event:

1. On your site, find a product and click the "Add to Cart" button.
2. Go to DebugView and find the add_to_cart event.
3. Click on it. The most important parameter here is the items array.
4. Click on the dropdown for the items parameter to expand it. You should see all the details of the product you just added, including:

What to look for: An improperly formatted items array is the most common ecommerce tracking bug. Every ecommerce event that involves a product (or products) requires this exact parameter structure. If the product data inside the items array is missing, has the wrong names (e.g., product_id instead of item_id), or passes the wrong values (e.g., price is formatted with a currency symbol), your ecommerce reports will be incomplete or inaccurate.

Graphed

Still Building Reports Manually?

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

Watch the Demo

Beyond DebugView: Other Troubleshooting Spots

While DebugView is for event-level validation, a few other areas in GA4 can help diagnose broader data issues.

Using Realtime Reports

The Realtime report in GA4 (found under Reports > Realtime) offers a 30,000-foot view of what's happening on your site in the last 30 minutes. It's less granular than DebugView but great for checking things like:

• Overall user counts and regional traffic.
• Events that are firing most frequently.
• Traffic sources for new users (e.g., are visitors from your new ad campaign showing up?).

If you see plenty of traffic from your country in Realtime but nothing in DebugView (while in debug mode), it could indicate a filter is blocking your debug traffic.

Checking Data Latency and Filters

Before you panic about missing data, remember two things:

1. Data Latency: Standard GA4 reports (like acquisition and engagement reports) are not instant. It can take up to 48 hours for data to be fully processed and appear. If you just launched a campaign, give it time.
2. Traffic Filters: Check your filters at Admin > Data settings > Data filters. Many users create filters to exclude internal IP addresses from office locations or developer traffic. If you've recently changed locations, your traffic might be getting filtered out of the standard reports, which is why it's essential to use DebugView for testing since it bypasses these filters.

Final Thoughts

Getting your GA4 tracking right is the foundation of data-driven marketing. Using tools like DebugView and Google Tag Assistant transforms debugging from a confusing guesswork game into a clear, methodical process. By regularly verifying that your pageviews, events, and conversions are firing as expected, you can build a reliable analytics system that helps you grow your business.

While fixing your tracking setup is critical, the next step is connecting that clean data to the rest of your marketing and sales stack to get the full picture. With so much data scattered across Google Analytics, Shopify, Facebook Ads, and Salesforce, it’s easy to spend all your time pulling reports instead of acting on insights. This is why we built Graphed to help. We make it easy to connect all your data sources and create real-time dashboards using simple natural language, so you can stop manually exporting CSVs and get immediate, cross-platform answers.