Meta Pixel Not Tracking Conversions: 12 Causes and Fixes (2026)

Your Meta pixel fires on the page (Tag Assistant confirms it), but Events Manager shows nothing - or shows events that never make it into Ads Manager reporting. Welcome to the most common Meta Ads issue in 2026.

This guide is the diagnostic order we run when a pixel goes dark. 12 causes, 12 fixes, in the order to check them. Most operators find the issue in the first 4 checks.

Before you start: what 'not tracking' actually means

The diagnostic below is ordered to catch issue (1) first, then (2), then (3).

The 12-step diagnostic

Cause 1: Pixel base code not installed correctly

Symptom. No events at all in Events Manager, even after browsing the site logged out.

Fix. Open the page in an incognito browser. Open Tag Assistant. Verify the pixel base code is firing. If not, the base code is wrong, missing, or being blocked by a CSP header. Re-install via GTM or directly per Meta's docs.

Cause 2: Event code firing on wrong page

Symptom. PageView fires (Tag Assistant green), but Purchase or Lead events never fire.

Fix. Open the conversion page (thank-you page, order confirmation). Verify the event code is in the page source. Many GTM setups fire conversion tags only on URL match - if your thank-you page URL changed, the trigger does not match.

Cause 3: Aggregated Event Measurement priority not set

Symptom. Events fire and show in Events Manager > Test Events, but never appear in Events Manager > Overview or in Ads Manager.

Fix. Open Events Manager > pixel > Settings > Aggregated Event Measurement. Verify your top 8 events are configured AND prioritized. Events not in the priority list are filtered out for iOS users. This is the #1 cause we see in 2026 audits.

Cause 4: Conversion API event_id mismatch

Symptom. Events appear in Events Manager but conversions look inflated (double-counting) or deflated.

Fix. Open Events Manager > Test Events. Send a test event from pixel AND from CAPI with the same event_id. Verify dedup is working - the Deduplication Score should be 80%+. A common bug: pixel uses Date.now() for event_id but CAPI uses a different ID generator.

Cause 5: Browser ad blockers stripping the pixel

Symptom. Pixel works for you (developer browser), missing for a chunk of real users.

Fix. Test from a clean browser with uBlock Origin or Brave. If pixel does not fire, that traffic is invisible to client-side. The fix is Conversion API server-side - bypass the browser entirely. See /blog/what-is-conversion-api.

Cause 6: iOS opt-out + no CAPI

Symptom. Conversions appear in your CRM but not in Events Manager. Bigger gap on iOS users specifically.

Fix. Implement Conversion API for server-side conversions. Without CAPI, iOS opt-out users (50%+ of iOS traffic in 2026) are invisible. CAPI plus AEM priority is the minimum healthy setup.

Cause 7: Cross-domain attribution broken

Symptom. Pixel fires correctly on the storefront but conversions on a separate checkout domain (Recharge, Bold, custom checkout) are not tracked back.

Fix. Either install pixel on the checkout domain too, or use Conversion API server-side from the checkout system. Many third-party checkouts have CAPI integration but require manual configuration.

Cause 8: GTM container not loaded on conversion page

Symptom. Pixel fires on most pages but never on the thank-you page specifically.

Fix. Open the thank-you page source. Search for your GTM container ID. If missing, the conversion page lives outside GTM scope. Many e-commerce platforms (Shopify, WooCommerce) require pixel installation in checkout settings separate from GTM.

Cause 9: Custom event parameters formatted wrong

Symptom. Events fire and show in Events Manager but value, currency, or content_ids are missing or wrong.

Fix. Open Events Manager > Test Events > select event > Parameters. Verify value is a number (not "29.99 USD" string), currency is a 3-letter ISO code ("USD" not "$"), content_ids is an array. Smart Bidding cannot optimize toward malformed events even if the count is correct.

Cause 10: Account-level disapproval suppressing pixel signal

Symptom. Pixel works in Test Events but events never show in Ads Manager reporting; no error in Events Manager.

Fix. Check Business Settings > Pixels for any "Pixel disapproved" or "Restricted" flags. Some accounts hit this after policy violations - pixel keeps collecting data but ads cannot use it for optimization. Appeal via Business Help Center.

Cause 11: AEM priority list capped at 8

Symptom. Tracking 9+ events; some random events missing for iOS users.

Fix. Open AEM settings. The 9th, 10th, etc. events are silently dropped on iOS opt-out users. Reduce to your top 8 by priority order. The fix is choosing - not adding more.

Cause 12: Andromeda dedup regression (April 2026)

Symptom. Started after April 1; pixel and CAPI both reporting but Deduplication Score dropped to below 50%.

Fix. Verify event_id consistency across pixel and CAPI. Verify fbp and fbc cookies are being passed by CAPI calls. If both look correct, the issue is on Meta's side - file a support ticket referencing the April 2026 Andromeda dedup regression.

When to file a Meta support ticket

How Hyper helps

Hyper monitors pixel health continuously across all 12 of these causes. When AEM priorities drift, when CAPI dedup score drops, when account-level disapprovals hit - the agent flags it within hours, not weeks. The case study at /blog/ai-marketing-case-study shows the monitoring layer in action.

Frequently asked questions