How to quickly check your Meta pixel fail rate
In Meta Events Manager, filter the Purchase event and look at the event match quality and signal loss percentage. Or use GTM Preview mode to manually trigger a purchase event and verify the pixel fires. For continuous monitoring, TagSense shows per-session pixel fail rates automatically.
1. Consent mode blocking the pixel pre-consent
The most common cause of Meta pixel failures in GDPR-compliant markets. If your GTM consent mode integration is configured to block the Meta pixel until the user accepts the ads consent category - and your consent banner is firing late, not firing, or firing incorrectly - the pixel never loads for a significant portion of users.
Check your GTM consent mode setup. The Meta Pixel tag should have "Requires additional consent for: ad_storage" configured. Verify in GTM Preview that consent events are firing before the pixel fires. Use the TagSense consent dashboard to see your ad consent grant rate and violation log.
2. Ad blockers and tracking prevention (iOS ITP)
iOS Intelligent Tracking Prevention (ITP) and ad blockers are systematically blocking third-party JavaScript including the Meta pixel. On some audiences (tech-savvy users, iOS-heavy demographics), ad blocker rates can exceed 40%.
Implement Meta Conversions API (server-side) to send events directly from your server, bypassing browser restrictions. Server-side events are not affected by ad blockers or ITP. TagSense monitors your browser pixel separately from Conversions API - so you can see the gap and quantify the signal loss.
3. Pixel fires on page load but not on purchase
The pixel base code fires on every page (page_view event) but the Purchase event fails on the order confirmation page. Common cause: the checkout or order confirmation page is on a different subdomain, a different technology stack (headless checkout), or a third-party payment processor with a different GTM container.
Verify the GTM container is installed on the order confirmation page. Use GTM Preview mode specifically on the /order-confirmation URL. Check if the page is served by a different domain or iframe that lacks the GTM container. For cross-domain or headless setups, consider server-side events via Conversions API.
4. Content Security Policy (CSP) blocking the pixel
A strict CSP header on your checkout or order confirmation page may block connect.facebook.net from loading. This is especially common on checkout pages where developers tighten security headers after PCI DSS reviews.
Check your CSP header (in browser DevTools → Network → Response Headers for any page request). If script-src or connect-src does not include connect.facebook.net and graph.facebook.com, the pixel will be blocked. Add the required Facebook domains to your CSP allowlist. TagSense Security dashboard shows CSP violations automatically.
5. Duplicate pixel installations conflicting
If the Meta pixel is installed both via GTM and hardcoded in the page source, the two installations can conflict and cause double-firing or mutual suppression depending on load order.
Search your theme or template files for fbq() or the fbevents.js script. If found, remove the hardcoded version and rely solely on GTM. TagSense Tag Inventory shows duplicate tag detection automatically.
How to monitor Meta pixel health continuously
Manual diagnosis works once. But Meta pixel failures often re-emerge after site updates, A/B test deployments, or CMS changes. Continuous monitoring catches failures within 24 hours - before they cost weeks of ad spend.
TagSense monitors Meta pixel fire rate in real user sessions and shows the estimated GBP revenue at risk when the fail rate spikes. You get alerted before you have to notice a revenue drop in your ads dashboard.
Related articles and resources
Monitor your Meta pixel continuously
TagSense shows Meta pixel fail rate, estimated GBP impact, and alerts within 24 hours of any spike. Free plan available.