Tracking guides
What the common tracking faults mean, how to confirm them yourself, and how to fix them.
Guides
- Meta Pixel not firing? How to find the cause
Meta Pixel installed but not firing? Confirm it in the network panel, then work through the usual causes: trigger, JavaScript error, deleted Pixel ID, CSP, consent.
- Duplicate purchase events: why one order is counted twice
One order, two purchase events. The usual causes (a tag installed twice, GA4 configured twice, no order ID for deduplication) and how to find the second install.
- GTM container returns 404: what it means and how to fix it
gtm.js returning 404 means Google has no published container under that ID: deleted, mistyped or never published. Every tag inside stops. How to find and fix it.
- Tracking pixel blocked by your own Content-Security-Policy
Your pixel runs, tries to send, and your own site blocks it. How a Content-Security-Policy stops tracking requests, how to spot it in the console, and how to fix it.
- Why your platforms report different purchase values
Why GA4, Meta and Google Ads report different revenue for the same orders: different value definitions, missing or invalid currency, formatted amounts, zero values.
Free checkers
- Is my Meta Pixel actually firing?
Free Meta Pixel checker. A real browser opens your page and shows whether the pixel sent PageView and other events, with the Pixel ID and payload. No signup.
- Is GA4 actually tracking this page?
Free GA4 checker. See whether your GA4 tag sends page_view and other events from a real browser, with the Measurement ID, duplicates and consent state.
- Does your Google Tag Manager container actually load?
Free Google Tag Manager checker. See whether gtm.js loads and the container actually runs, or returns 404 because it was deleted or mistyped. Real browser, no signup.
- Do your tags wait for the cookie banner?
Free consent timing check. See which tags send data before the cookie banner is answered, and whether Google Consent Mode v2 sets ad_user_data and ad_personalization.