When Google Tag Manager shows the GTM Debugger tag as fired but GA4 receives no data, there is a configuration issue between GTM and GA4. A fired status in the Debugger only means the trigger activated the tag — not that data was delivered correctly. Additionally, incorrect Measurement IDs or network errors may be the cause. Learn why GA4 shows no data despite a fired tag.

Why Does the GTM Debugger Show Tag as Fired but GA4 Receives No Data?

The Google Tag Manager Debugger shows the tag as fired but GA4 shows no data when the Measurement ID is incorrect or the GA4 configuration tag is missing. The Debugger only checks whether the trigger activated the tag — it does not verify delivery. However, ad blockers or browser settings can also block the network request. Therefore, check the Network tab in developer tools for collect requests. Additionally, the event diagnosis for GA4 helps.

Verifying Network Requests and GA4 Configuration

Open developer tools and filter the Network tab for collect. This shows whether GTM sends a request to google-analytics.com. Moreover, the response code should be 204, confirming successful delivery. If the request is missing, something blocks execution. The GA4 diagnostics help describes additional verification steps.

Our Recommendation

Always check the Network tab for collect requests when the Debugger shows a tag as fired. The response code should be 204. Furthermore, we recommend using GA4 DebugView in parallel to verify events in real time. Additionally, double-check the Measurement ID in every GA4 tag and ensure a GA4 configuration tag fires first on every page.

Conclusion

A tag shown as fired in the Debugger does not guarantee data delivery to GA4. Therefore, verification via network requests and DebugView is essential. Our Google Ads agency ensures your data reaches GA4 correctly.