How to See Events in Google Analytics 4 DebugView

You’ve carefully configured a new event in Google Analytics 4, hit publish in Google Tag Manager, and then... nothing. You check the Realtime report, wait a few minutes, and your new event is nowhere to be found. This frustrating guesswork is exactly why GA4’s DebugView exists. This article will show you exactly how to enable and use DebugView to see your events in real-time, troubleshoot your setup, and finally get your tracking right the first time.

Graphed

Still Building Reports Manually?

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

Watch the Demo

So, What Is Google Analytics 4 DebugView Anyway?

Think of DebugView as a live, unfiltered console for a single user's activity on your website or app. While the standard Realtime report gives you a high-level overview of all users, DebugView isolates one browser or device - yours - and shows you every single event, parameter, and user property you send to Google Analytics, exactly as it’s received.

It's designed specifically for testing and validation. When you enable debug mode, you're telling GA4, "Hey, for my current session, record everything immediately and show it to me in this special report so I can make sure it’s working."

Here’s why it’s so essential for anyone setting up GA4:

• Immediate Feedback: Events appear in DebugView instantly. No more waiting 30 minutes to an hour (or longer) for data to process and show up in standard reports. You know right away if your GTM tag fired correctly.
• Granular Detail: You can click on any event to see all the parameters that were sent with it. Did the value and currency parameters fire with your purchase event? DebugView will show you.
• Validate Complex Setups: Testing e-commerce funnels, custom conversions, or lead form submissions becomes simple. You can trigger the event on your site and watch it appear with all the correct data in DebugView moments later.

Four Ways to Enable DebugView

Before you can use DebugView, you need to enable debug mode on your own device. GA4 offers a few different ways to do this, depending on your setup. Here are the most common methods.

Graphed

Still Building Reports Manually?

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

Watch the Demo

Method 1: Google Tag Manager (GTM) Preview Mode

If you're using Google Tag Manager to deploy your GA4 tags (which you probably should be), this is the easiest method. The GTM Preview mode automatically enables debug mode for GA4.

1. Go to your Google Tag Manager workspace.
2. Click the Preview button in the top-right corner.
3. Enter your website’s URL in the popup window and click Connect. A new tab will open with your website, and you’ll see the "Tag Assistant" box in the bottom-right corner.
4. Now, go to your Google Analytics 4 property.
5. In the left-hand navigation, navigate to Admin, and then under Data display, click on DebugView.

That's it! As you navigate your site in the preview tab and interact with elements, you’ll see the events streaming into DebugView.

Method 2: Google Analytics Debugger Chrome Extension

If you aren’t actively in GTM or want a quick way to check a live site, the official Google Analytics Debugger Chrome extension is another great option.

1. Go to the Chrome Web Store and search for "Google Analytics Debugger" or get it here.
2. Click Add to Chrome to install it.
3. Once installed, you'll see a new icon next to your URL bar (it looks like a bug with "GA" on it).
4. Navigate to your website, and click the new debug icon. An "ON" next to the icon means debug mode has been enabled for this tab. Simply click it again to turn it off.
5. Just like the GTM method, head over to the DebugView report in GA4 to see a live stream of your activity. You may need to refresh your webpage once after turning the extension ON.

Method 3: Manually Send the debug_mode Parameter (Advanced Users)

If you are a developer or have GA4 installed directly on your site without GTM, you can modify the GA4 config tag to force debug mode.

All you need to do is add a debug_mode parameter and set it to true within your existing gtag configuration. Your code would look something 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 }), // This line enables debug mode
</script>

Remember to remove this or set it to false when you're done testing, as you don't want every site visitor's data to be sent for debugging purposes.

Graphed

Still Building Reports Manually?

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

Watch the Demo

Method 4: For Mobile Apps (via Firebase)

If you're working with a mobile app, the process is different but just as straightforward. You'll enable debug mode through developer tools for both iOS and Android.

For Android:

Execute the following commands using a terminal and the Android Debug Bridge (adb):

adb shell setprop debug.firebase.analytics.app <your_app_package_name>

For iOS (in Xcode):

You can enable debug mode by editing your scheme in Xcode and adding an argument. In Xcode, select Product > Scheme > Edit Scheme. Select Run from the left menu, go to the Arguments tab, and add the following launch argument:

-FIRDebugEnabled

Once enabled, you’ll be able to see your app's live events in the GA4 DebugView, just like with a website.

How to Read the DebugView Interface

Once you’ve successfully enabled debug mode, you’ll see events streaming into your DebugView report. At first, it might look like a flurry of activity, but it’s actually quite simple to understand.

The interface is mainly divided into two columns:

1. The Middle Column (Vertical Timeline): This is the live stream. Each circle on the timeline represents an event.

• 🔵 Blue Circles are standard, automatically collected events (like page_view, session_start, first_visit, and scroll).
• 🟢 Green Circles are custom events you've configured. These are the ones you’ll likely be testing most often, like generate_lead or add_to_cart.
• 🟠 Orange Circles represent conversion events. It’s a quick visual indicator to see if an action you defined as a conversion was a success.

2. The Right-hand Column (Event Details): When you click on any event in the timeline, this column populates with all the specific data sent with that event.

• Parameters: This is a list of all parameters captured for the selected event. This is the most crucial section for troubleshooting. Did you intend to capture the form_id or product_name? This is where you verify what was sent to GA4 correctly.
• User Properties: Here, you’ll see a snapshot of the current user properties associated with your device.

At the very top of the DebugView report, you'll see a "Debug device" selector. If multiple team members are testing in debug mode simultaneously, you can use this dropdown to isolate and view the data stream from a specific device.

Graphed

Still Building Reports Manually?

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

Watch the Demo

Practical Tips and Common Questions

Keep these things in mind to get the most out of your testing sessions:

"I’m in debug mode, but don't see my device." Double-check that you don't have an internal traffic filter set up in GA that could be excluding your IP address. Developer-level filters can block debug traffic from being processed.

"My event fired, but a parameter is missing!" This is exactly what DebugView is for! It usually means your Google Tag Manager variable is configured incorrectly. Go back to GTM, check your variable settings (e.g., is your CSS Selector or Data Layer Variable name correct?), re-enter Preview mode, and try again.

”Can I use this for real analysis?” No. DebugView data is only intended for real-time validation. It's not processed with the same rigor as standard report data and is automatically discarded. Stick to regular reports for any actual analysis.

Final Thoughts

Getting your tracking right is the first step to truly understanding your site performance, and Google Analytics 4 DebugView is the single most important tool for that job. By enabling it with GTM's Preview mode or the handy Chrome extension, you can stop guessing and start confirming that your new events are firing perfectly, complete with all the data you intended to capture.

Once your event tracking is solid, the next challenge is to bring all of your data together to get a clear picture of your marketing and sales performance. A lot of teams spend hours downloading CSVs and building manual reports. At Graphed, we've automated this entire process. We connect directly to data sources like Google Analytics, Shopify, Facebook Ads, and Salesforce so you can build live dashboards and reports in seconds using simple, natural language. It’s like having a data analyst on your team, minus the cost and complexity.