How to Tell If Your Meta Pixel Is Broken (and How to Fix It)

A broken Meta pixel almost never announces itself. Campaigns keep spending, the dashboard keeps loading, and everything looksfine — right up until you realize conversions stopped reporting days ago and your optimization has been flying blind the whole time. Here's how to catch it, what usually causes it, and how to make sure you never find out from an angry client.

Why a broken pixel is so dangerous

When your Meta pixel or Conversions API (CAPI) stops sending events correctly, Meta's algorithm loses the signal it uses to optimize. Wasted spend is only the first problem. You also get inflated or missing conversion counts, broken attribution, and audiences that quietly stop growing. Because none of this throws an obvious error, it can run for days or weeks before anyone notices.

Signs your Meta pixel is broken

Watch for any of these red flags:

• A sudden drop in reported conversionsthat doesn't match a change in spend or performance.
• Events not appearing in Events Manager— or the “last received” timestamp is hours or days old.
• A falling Event Match Quality (EMQ) score on your CAPI events, which means Meta can no longer match events to real people.
• A spike in duplicate events — usually a sign your browser pixel and server events stopped deduplicating.
• “Pixel inactive” or error warnings in the Events Manager data-source diagnostics.

How to check your pixel manually

1. Open Meta Events Manager→ select your data source. Look at “Events received” and the last-received time. If it's stale, events aren't arriving.
2. Use the Meta Pixel Helper Chrome extension on the site. Load a key page and a conversion page and confirm the expected events fire (PageView, Purchase, Lead, etc.).
3. Check the Diagnostics tab in Events Manager for warnings like missing parameters, low EMQ, or deduplication issues.
4. Run a test event via the Test Events tool and complete the action yourself to see it arrive in real time.

Not sure what a healthy EMQ score looks like or why it matters? We break it down in the Taglert FAQ.

The most common causes

1. A site change dropped the tag

The single most common culprit. A developer ships a redesign, migrates platforms, or edits the theme, and the pixel base code or CAPI integration gets removed or moved. The site works perfectly — the tracking just silently disappears.

2. Consent or cookie changes

A new consent-management platform, a stricter cookie banner, or an ad-blocker update can block the pixel from firing for a large share of users.

3. Broken deduplication

If you run both the browser pixel and CAPI (you should), they need to share the same event_id so Meta counts each event once. When a code change breaks that, duplicate events spike and your numbers inflate.

4. Missing customer parameters

CAPI events rely on hashed customer data (email, phone, external_id, fbc/fbp) to match to people. If a change strips those parameters, your EMQ score drops and attribution suffers — even though events are still “firing.”

How to fix it

• Reinstall or restore the base code / CAPI integration if a site change removed it. Verify with the Pixel Helper afterward.
• Send a shared event_id on both the Pixel and CAPI for every event to fix duplicates.
• Restore missing match keys — make sure your server events include as many hashed customer parameters as possible to lift EMQ.
• Check your consent setup so the pixel fires for users who have consented.

The real fix: don't rely on noticing

Every method above requires youto remember to check — and to check every client account, regularly. That's exactly why broken pixels go unnoticed: nobody manually audits Events Manager for ten accounts every morning.

This is the problem Taglert solves. It monitors your pixel activity, CAPI event match quality, and duplicate-event rate across every connected account every 30 minutes, and alerts you by email and Slack the moment something breaks — with the likely cause and fix. You find out in minutes, not when your client asks why their sales report looks off.