GA4 Debug View: How to Test Events Before They Go Live

You just set up a new GA4 event. How do you know it actually works before pushing it live and waiting 24 hours to see data in reports?

GA4’s DebugView shows events in real-time — within seconds of firing. Here’s how to set it up and use it effectively.

Three Ways to Enable Debug Mode

Method 1: GA4 DebugView Chrome Extension (Easiest)

1. Install the GA4 DebugView extension from the Chrome Web Store
2. Click the extension icon to enable debug mode (icon turns orange)
3. Navigate to your site
4. Open GA4 → Admin → DebugView

Events from your session now appear in real-time. The extension adds debug_mode=true to every GA4 hit.

Pros: No code changes. Works immediately. Toggle on/off. Cons: Only works in YOUR browser. Can’t debug other users’ sessions.

Method 2: GTM Preview Mode + GA4 Debug

If you’re using Google Tag Manager:

1. Open GTM → Preview → enter your site URL
2. The preview window opens with GTM debug panel
3. GA4 automatically receives events with debug mode enabled
4. Open GA4 → DebugView to see events alongside the GTM tag firing sequence

This is the best approach because you see BOTH the GTM tag fires AND the GA4 event receipt simultaneously. If a GTM tag isn’t firing, you’ll see it here.

Method 3: Code-Based Debug Mode

Add debug_mode: true to your GA4 configuration:

gtag('config', 'G-XXXXXXX', { debug_mode: true });

Or in GTM: edit your GA4 Configuration tag → Fields to Set → add debug_mode = true.

Important: Remove this before deploying to production — you don’t want every visitor’s events showing in DebugView.

Reading DebugView

The Timeline

DebugView shows a timeline of events from the last 30 minutes. Each event appears as a colored dot:

Color	Meaning
Blue	Standard event (page_view, scroll, etc.)
Green	Conversion event
Orange	Automatically collected event

Click any event to see its parameters.

What to Check Per Event

For each event, verify:

1. Event name — Does it match what you configured? GA4 event names are case-sensitive. Purchase and purchase are different events.

2. Parameters — Click the event to expand. Check:

   • currency and value for ecommerce events
   • transaction_id for purchase events (must be unique per order)
   • items[] array with item_id, item_name, price, quantity
   • Any custom parameters you added

3. User properties — Scroll down to see user-scoped properties (user_id, etc.)

4. Timing — Events should appear within 1-2 seconds of the action. If they’re delayed or missing, the tag isn’t firing correctly.

Check our GA4 event reference for the correct parameter names for each event type.

Common Issues in DebugView

Event appears in GTM Preview but NOT in DebugView:

• GA4 Measurement ID is wrong (typo in G-XXXXXXX)
• Tag is firing but with incorrect configuration
• Consent Mode is blocking the hit (check if analytics_storage is denied)

Event has wrong parameters:

• Data layer variable names don’t match GTM variable configuration
• Variable returns undefined — check the data layer
• Value is a string instead of number ("29.99" instead of 29.99)

Purchase event fires but no value:

• value parameter is missing or undefined
• Currency not set (GA4 requires both value and currency)
• Transaction ID missing — GA4 won’t log revenue without it

Events fire twice:

• Duplicate GA4 tags (one from GTM, one hardcoded in HTML)
• Page loads twice (SPA routing issue)
• Check for duplicate tags using our GTM audit checklist

Testing a Complete Ecommerce Flow

Walk through your entire conversion funnel in debug mode:

1. Homepage → Verify page_view fires
2. Product page → Verify view_item with correct product data
3. Add to cart → Verify add_to_cart with item details
4. Checkout → Verify begin_checkout with cart value
5. Purchase → Verify purchase with transaction_id, value, currency, and items[]

If any event is missing or has wrong data, fix it in GTM before publishing.

For ecommerce-specific setup details, see our GA4 ecommerce tracking guide.

DebugView vs. Realtime Report

Feature	DebugView	Realtime Report
Delay	1-2 seconds	30-60 seconds
Filtering	Single debug user only	All users
Parameters	Full parameter detail	Limited
Duration	30 minutes	30 minutes
Requires debug mode	Yes	No

Use DebugView for: Testing new events, verifying parameters, debugging issues. Use Realtime for: Checking overall traffic, verifying that events fire for all users (not just you).

Automated Testing

For ongoing verification (not just one-time debugging):

1. Set up a GA4 custom alert for zero conversions in 24 hours
2. Use our free tracking scan to periodically check that all tags fire
3. After every GTM publish or site update, walk through the debug flow above

Tracking breaks silently. A monthly debug check prevents the “we’ve been losing data for 3 months and nobody noticed” problem.