Meta Pixel Not Firing — Troubleshooting Guide

bolt

Quick Answer

Use Meta's event-testing tools to confirm whether the expected browser and server events arrive with the correct Pixel ID and parameters. Check tag-manager configuration, consent behavior, deduplication, and browser/server mismatches. Diagnosis and repair time depends on the implementation.

Why This Happens

Wrong Pixel ID or Pixel installed on wrong domain

An ID mismatch can cause pixel issues when the Pixel ID in your website code doesn't match the Pixel ID in Meta Events Manager. This can happen when accounts have multiple pixels, after migrating Business Managers, or when a developer copies code from another implementation. The Meta Pixel Helper extension shows the Pixel ID that's firing, which you can compare against the ID in Events Manager.

iOS 14+ App Tracking Transparency changes

Apple's ATT framework, introduced in iOS 14.5, lets users opt out of cross-app tracking, so Meta can only receive events from iOS users who have consented. This creates a data gap that varies by audience and consent rate — the exact share of missing events depends on your users. If you're seeing lower event counts than expected, part of the gap may be the iOS consent opt-out rather than a broken pixel. The Conversions API sends events from your server, which is a different path than the browser Pixel and does not depend on the same browser consent.

Browser extensions blocking the Pixel

Ad blockers, privacy extensions (uBlock Origin, Privacy Badger, Ghostery), and Firefox Enhanced Tracking Protection can block the Meta Pixel. The share of visitors affected varies widely by audience and is hard to measure precisely. This isn't a 'broken' pixel — it's expected behavior for those visitors. The Conversions API (server-side events) sends events from your server directly to Meta rather than the visitor's browser, which is a different path that browser-level blocking does not affect the same way.

Tag Manager configuration errors or conflicts

When implementing the Pixel through Google Tag Manager or another TMS, errors in trigger rules, variable configuration, or firing order can cause events to not fire, fire multiple times, or fire on the wrong pages. Check whether the base Pixel code fires while custom events fail to trigger because of incorrect DOM variables, or whether a new tag overrides the existing implementation. Use GTM debug mode to see exactly which tags fire on which pages.

Server-side Conversions API events not matching browser events

If you're running both the browser Pixel and the server-side Conversions API, duplicate events or event name mismatches can make Events Manager show confusing data — either inflated event counts or missing events. Both implementations should use the same event names and include the `event_id` parameter for deduplication. Without it, Meta may count some events more than once, which can distort your attribution and optimization data.

Step-by-Step Recovery

Install and run Meta Pixel Helper on your site

Install the Meta Pixel Helper Chrome extension from the Chrome Web Store, then visit each page of your funnel. The extension shows whether the Pixel is firing, which Pixel ID is active, and what events are being sent. A red icon means the Pixel is not found or has errors. A green icon with event names confirms it's working. Screenshot any errors shown — they'll help you identify the exact problem.

Verify the Pixel ID matches Events Manager

In Meta Events Manager (business.facebook.com/events_manager), find your Pixel and note the exact Pixel ID (a 15–16 digit number). Compare this against the Pixel ID in your website code or tag manager. If they don't match, update the code with the correct ID. After updating, clear your browser cache and retest with Pixel Helper.

Check your tag manager for configuration errors

If using Google Tag Manager, open GTM in debug/preview mode, then browse your site. Watch for whether the Meta Pixel tag fires and whether the correct variables are being passed. Check whether PageView fires while custom events do not, whether purchase events are missing required parameters such as value or currency, and whether events fire on every page instead of specific pages. Fix trigger rules and variable configuration, then test again.

Implement or audit your Conversions API setup

The Conversions API (CAPI) sends events from your server to Meta. If you use CAPI, configure it through Meta's documented partner integration or direct API, then verify in Events Manager that event names match browser events and that the `event_id` deduplication parameter is sent.

Configure your Aggregated Event Measurement settings

For iOS optimization, Meta requires you to configure Aggregated Event Measurement (AEM) in Events Manager. Verify your domain, then configure the conversion events per domain as shown in the tool (AEM allows up to 8 events per domain, set in priority order). Without this setup, iOS optimization may be limited even when events fire correctly. Go to Events Manager → Data Sources → select your Pixel → Configure Web Events.

Test events using Events Manager's Test Events tool

Events Manager has a built-in Test Events tool that shows real-time event firing. Go to Events Manager → your Pixel → Test Events. Open your website in another tab and complete the actions you're testing (add to cart, purchase, etc.). Events should appear in the test panel within a few seconds. This is useful for diagnosing CAPI issues because it shows both browser and server-side events, whereas Pixel Helper shows browser events.

Audit your audience data and regenerate retargeting pools

If tracking was broken for a significant period, your custom audiences may have shrunk. After fixing the Pixel, check your Custom Audiences in Ads Manager — you may see a 'refreshing' status as Meta rebuilds the audience from recent events. For audiences that have become too small to deliver, you can try expanding your lookback window or broadening your event criteria to rebuild audience size.

Prevention Checklist

check_box_outline_blankSet up weekly Pixel health monitoring alerts in Meta Events Manager
check_box_outline_blankImplement Conversions API alongside browser Pixel for redundant tracking
check_box_outline_blankUse event_id parameter in all events to enable proper deduplication
check_box_outline_blankComplete domain verification and configure Aggregated Event Measurement
check_box_outline_blankTest all funnel events after any website update, CMS migration, or tag manager change
check_box_outline_blankDocument your Pixel ID, GTM container ID, and CAPI access token in a secure internal reference

Expected Timeline

scheduleResolution Timeline

Diagnosis and repair timing depends on the site's tag setup, consent flow, browser/server event paths, and access to deployment tools

Next Steps

Fixing this resolves the immediate problem. It does not change the setup that produced it. These cover the Meta account structure, permissions, and review exposure underneath.

Advertising Measurement Incident Response: Reconcile the Signal Before You Change the Systemarrow_forward How to Diagnose an Ad Spend Outage: A 4-Step Recovery Checklistarrow_forward Meta Agency Ad Accounts: Ownership, Partner Access, and Billingarrow_forward What AdsInfra charges to run this as managed infrastructurearrow_forward

shield_with_heartAdsInfra

Scaling past $50k/mo?

AdsInfra coordinates agency ad-account access, billing, permissions, and restriction-response workflows for high-spend teams across Meta, TikTok, and Google.

check_circleCoordinated account access and billing workflows
check_circleHuman-led restriction review and escalation
check_circlePlatform-specific onboarding and compliance checks

Check Eligibility Talk to a Specialist

Frequently Asked Questions

Why is my Meta Pixel showing fewer conversions than my actual sales?expand_more

Several factors can cause underreporting: iOS 14+ ATT opt-outs, ad blockers, cross-device journeys that Meta can't stitch together, and browser cookie restrictions from Safari's ITP. The size of the gap varies by audience and isn't precisely measurable. Implementing the Conversions API can improve signal, but some underreporting may remain. Compare Meta's reported conversions against your backend order data to gauge the gap for your account.

Can I have multiple Meta Pixels on one website?expand_more

Multiple Pixels can fire on the same site. Verify in Events Manager and your tag manager which Pixel receives each event; duplicate installations can produce duplicate events or conflicting attribution data. Use Meta's pixel/data-source sharing controls in Business Manager when multiple authorized accounts need the same data source.

How do I know if the iOS 14 changes are affecting my results?expand_more

Check your event match quality score in Events Manager — Meta displays this per event, and lower scores suggest weaker matching. Also compare your 7-day click attribution data against your backend conversions for the same period. A large gap between the two suggests tracking loss from iOS and browser restrictions. Implementing CAPI with hashed customer data (email, phone) can improve match quality.

What's the difference between the Meta Pixel and the Conversions API?expand_more

The Meta Pixel is JavaScript that sends browser events to Meta. The Conversions API sends server events instead. Browser events can be blocked by browser or device controls; server events follow a separate path. If you use both, configure matching event names and `event_id` values, then verify deduplication in Events Manager.

My Pixel was working fine and then suddenly stopped — what changed?expand_more

Check the site's source or tag manager to confirm that the Pixel code and triggers remain present after any website, CMS, theme, plugin, or developer change. Then inspect Events Manager diagnostics and the site's Content Security Policy for the specific error or blocked request.