Why does the GTM debugger show a tag as fired, but GA4 is not receiving any data?

“Fired” in the Tag Manager preview only means that the tag ran in the browser, not that GA4 received and kept the data. Between the tag and your reports, the request can go to the wrong measurement ID, be blocked by the browser, be reduced by consent mode or be removed by a data filter in GA4. In most cases one of these four points is the cause.

Also check where you are looking: standard reports take time to process, so for testing use DebugView or the Realtime report. And remember that preview mode only affects your own browser. Until you publish the container, real visitors do not run the new tag at all.

Why does a fired tag not send data to GA4?

• Wrong measurement ID. The Google tag or GA4 event tag uses a measurement ID from a different property or data stream, or a variable that is empty at the moment the tag fires. The data arrives, just not where you are looking.
• Request blocked. Ad blockers, browser privacy features or a strict Content Security Policy on the website can block the request to Google after the tag has fired.
• Consent not granted. With consent mode and analytics_storage denied, tags send cookieless pings instead of normal hits. According to Google, events are then not visible in DebugView.
• Data filter active. An active internal traffic filter excludes visits from IP addresses defined as internal, often your own office, and a developer traffic filter excludes debug-mode events. Filtered data is never processed and cannot be recovered.
• Server-side tagging. If the Google tag sends to a server container via server_container_url, the data only reaches GA4 if a client claims the request and a GA4 tag fires in the server container.

How do I find the cause step by step?

1. Check the measurement ID. Compare the ID in the tag with the ID under Admin → Data streams in the GA4 property you are looking at.
2. Watch the network. Open the browser’s developer tools, tab Network, and filter for collect. You should see a request with your measurement ID for every event. If there is none or it shows as blocked, the problem is in the browser or on the website.
3. Test without blockers. Repeat the test in a private window without extensions and accept all cookies in the consent banner.
4. Use DebugView. Start preview mode via Tag Assistant, which enables debug mode for your device, and open Admin → Data display → DebugView in GA4. Events should appear within seconds.
5. Check data filters. In the GA4 admin area, open Data filters and see which filters are active and whether your own traffic is excluded.
6. Publish the container. When the tag works in preview, publish the version so that real visitors run it too.

When is a delay normal?

DebugView and the Realtime report show events within seconds to minutes. Standard reports need longer, because GA4 processes data before it appears there. If events are visible in DebugView, the setup works and you only need to wait for the reports.

Test in this order: measurement ID, network request, consent, DebugView, data filters. If the request with the right ID leaves the browser and appears in DebugView, the tag is fine.

For events that do not fire at all, see our article on GTM events that are not tracking.

Sources

• Tag Manager Help: Preview and debug containers
• Analytics Help: Monitor events in DebugView
• Analytics Help: Data filters
• Analytics Help: Consent mode on websites and mobile apps

Your tags fire, but the numbers in GA4 do not add up? We check tagging, consent and data flow end to end and show you where data gets lost. Book a free intro call or read more about our tracking.