Why it happens
Debug mode is not on for your visit. DebugView shows events from devices in debug mode. Google names two ways to turn it on: Tag Assistant, which adds a parameter to your website address, or a debug_mode parameter in the Google tag. Opening your store in a normal tab does neither.
You declined analytics on your own banner. Google's DebugView help says events are not visible in debug mode when users have not given consent for Analytics cookies, or when privacy controls run on the client side. On Shopify, pixels also wait for consent: in markets where consent is required, web pixels run only when visitors have given the permissions the pixel asks for. If you clicked Decline while testing, DebugView stays empty.
Shopify runs the tag in a sandbox. On Shopify, the Google tag often comes from the Google & YouTube sales channel. Shopify runs pixels from apps and sales channels in a strict sandbox that uses web workers. Custom pixels run in a lax sandbox, an iframe. Tag Assistant switches on debug mode through a parameter in the page address. Shopify's pages do not say whether a pixel in the sandbox picks it up. So an empty DebugView on a Shopify store does not prove the tag is off.
The wrong device or property is selected. DebugView has a Device selector. If several devices are in debug mode, the report may focus on another one. It also shows only the property you have open. A Tag Assistant session on a different measurement ID sends its events somewhere else.
The event was a test sent to Google's validation server. Google says events sent to the validation server do not show up in reports. That server checks the event format. Google adds that it does not check the API secret, so a valid test can still go nowhere.
Debug mode is still on from earlier. The opposite case. Google says setting debug_mode to false does not turn debug mode off. Only removing the parameter does. Old test traffic can then sit in DebugView and confuse you.
Check it yourself
- 1Open your store in a new window and accept analytics on your cookie banner.
- 2Open Google Tag Assistant, connect it to your store's address and keep the store tab it opens.
- 3In GA4, go to Admin, then under Data display click DebugView. Check that the property is the one your store's measurement ID belongs to.
- 4Use the Device selector at the top. Pick the newest device.
- 5Browse a product and add it to the cart. Look for page_view, view_item and add_to_cart in the Seconds stream, which shows the last 60 seconds.
- 6If DebugView stays empty, open the Realtime report in another tab. Read Event count by event name. Events there mean the tag works and only debug mode did not reach it.
- 7If Realtime is empty too, go to Shopify admin > Settings > Customer events. Click More options next to your Google pixel, then Test, and watch Events received in Shopify's Pixel Helper.
- 8If the Pixel Helper says "Pixel is awaiting consent", accept tracking or click Give consent to continue test. Then repeat step 5.
For every way a purchase can reach GA4, see how a paid order reaches Meta, GA4 and Google Ads.
FAQ
Do I need DebugView to test GA4 on Shopify?
No. DebugView is one tool. Realtime shows recent events by name, and Shopify's Pixel Helper shows what each pixel received on your store.
Why do I see page_view in Realtime but nothing in DebugView?
Your visit is not in debug mode as GA4 sees it. The tag works. Use Realtime for the test, or set debug mode in the tag itself if you control it.
Why does my test purchase not show anywhere?
Check whether the test went to Google's validation server. Those events never reach reports. For a real purchase that never arrives, see GA4 purchase event not firing on Shopify.
Will debug traffic spoil my reports?
Google says you can filter out developer traffic so data from debug mode does not affect your reports.
My purchases are lower than Shopify's orders. Is that a DebugView problem?
No. That has its own page: GA4 shows fewer purchases than Shopify.