# GA4 DebugView for WooCommerce: Verify Your Tracking in 10 Minutes

> DebugView is the only sane way to verify GA4 eCommerce tracking. How to flag debug traffic, walk the funnel, and read the three failure patterns that matter.

*Source: https://plugins.viglan.com/ga4-debugview-woocommerce/*

Every WooCommerce tracking guide ends with the same advice: verify in DebugView. This is the ten minute version of how to actually do that, from enabling debug traffic to reading the event stream like someone who has done it before.

## What DebugView is

DebugView (GA4 Admin → DebugView) shows events from debug-flagged devices in real time, one device at a time, with full parameter detail. Unlike the Realtime report it shows every parameter of every event within seconds — which makes it the only sane way to verify an eCommerce setup.

## Getting your traffic flagged as debug

- **GTM Preview mode** — connect your store in Tag Assistant; everything you do in that window is debug traffic. Zero code.
- **Chrome extension** — Google Analytics Debugger flags all your browsing until switched off.
- **debug_mode parameter** — a tagging plugin can send debug_mode on its events site-wide; useful for testing checkouts on phones where extensions do not exist.

## The ten minute funnel walk

1. Open DebugView, pick your debug device.
2. Visit a category page — expect `view_item_list` with items and item_list_name.
3. Click a product — expect `select_item`, then `view_item` with price and currency.
4. Add to cart from the category page too, not just the product page — AJAX adds are where tracking usually breaks first.
5. Run checkout to the thank-you page with a 100 percent coupon — expect `begin_checkout`, `add_shipping_info`, `add_payment_info`, then exactly one `purchase` with transaction_id, value and items.
6. Refresh the thank-you page — if a second purchase appears, your deduplication is broken and revenue is inflated.

## Reading what you see

Click any event to expand parameters. The three failure patterns worth memorizing: an **empty items array** (payload built before product data was ready), **value as a string** (currency symbols leaked into numbers), and **events missing only on mobile** (a consent banner or blocker difference between your devices).

## When DebugView shows nothing at all

Work backwards: is the device actually flagged (Tag Assistant connected)? Is the GA4 config tag firing (GTM Preview shows tag status)? Is consent granted in this browser session? Is an ad blocker active? Ninety percent of empty DebugView sessions are one of those four.

*TrackPilot ships a built-in event debugger that shows the dataLayer stream directly in wp-admin — so you can verify events before they even reach GA4, then confirm the last mile in DebugView. [See TrackPilot →](https://plugins.viglan.com/plugins/trackpilot-for-woocommerce-ga4-gtm-tracking-pro/)*