Running Facebook or Instagram ads?

Meta Pixel dropping conversions? We fix it.

Meta ads look great in Ads Manager and terrible against Shopify. Usually the pixel fires twice, the Conversions API was never wired up, and iOS opt-outs ate the rest. We untangle what is really being reported and rebuild it so the numbers reconcile.

  • Since 2015Fixing technology
  • FreeEstimates
  • US teamReal engineers

pixel-events.log

still failing

What it is

Meta Pixel at a glance

The Meta Pixel (formerly Facebook Pixel) is the tracking code for Facebook and Instagram ad conversions. It is the companion to the Conversions API (CAPI), which is the server-side event channel that partially restored tracking lost to iOS 14 ATT (Apple, 2021) and Enhanced Tracking Protection on Firefox.

Events include Purchase, Lead, CompleteRegistration, AddToCart, and custom events you define yourself. Event Manager, Aggregated Event Measurement and Advanced Matching are the current measurement stack. Business Manager and Ads Manager tie all of it back to an ad account.

Type
Ad conversion measurement for Meta ads
First released
2015 as Facebook Pixel
License
Free with a Meta Business account
Maintained by
Meta Platforms, Inc.
Typically used for
Facebook / Instagram ad attribution, lookalike audiences, conversion optimisation, retargeting

The honest version

Meta Pixel pros and cons

No technology is all upside. This is where Meta Pixel earns its place and where it tends to cause trouble.

Where Meta Pixel is strong

  • Still the signal source for Meta adsIf you advertise on Facebook or Instagram, the Pixel is what credits a sale back to the ad that earned it. There is no alternative attribution route inside Ads Manager.
  • Conversions API catches what browsers missCAPI sends events straight from your server, so sales still land in Event Manager when iOS App Tracking Transparency or a blocker kills the browser pixel.
  • Aggregated Event Measurement keeps iOS reporting aliveApple's post-opt-out model receives up to eight ranked events per domain, which is enough for most stores to keep Purchase and a few steps before it.
  • Advanced Matching lifts the match rateHashed email, phone and name sent with each event help Meta reconcile a conversion to a user, which pushes Event Match Quality up and lets more sales attribute.
  • Server-side CAPI through the tools you already useShopify, WooCommerce, GTM server containers and Zapier each have a CAPI path, so you rarely need to write the integration from the ground up.
  • Browser plus server deduplicationShared event_id and event_name across both channels lets Meta discard duplicates, so you can run belt-and-braces without inflating your Purchase count.

Where Meta Pixel bites

  • iOS 14 ATT quietly broke client-side measurementSince Apple's 2021 prompt, a large share of iPhone traffic sends no browser events at all. A pixel-only setup now under-reports iOS conversions badly.
  • Duplicate pixels are the normA theme snippet, a GTM tag and a Shopify app all install their own copy, so Purchase fires two or three times until somebody audits what is actually on the page.
  • CAPI is not a checkbox installServer-side via CAPI Gateway or a sGTM container needs event_id alignment, hashed PII, a working test_event_code and a real deployment to prove it is deduping.
  • Aggregated Event Measurement caps you at eightPer verified domain, only eight prioritised events report for opted-out iOS users. Nine configured means one silently stops counting.
  • Ad account restrictions land hardA policy strike can disable the ad account overnight. Appeals go through Business Support and often take days, with no guarantee of reinstatement.
  • Event Match Quality obscures the real rateThe 0 to 10 score tells you matching is 'poor' or 'great' without ever revealing the percentage of events actually attributed, so tuning is partly guesswork.
  • Advanced Matching needs PII, hashed and consentedSending email or phone through the pixel only works when your consent banner captured it, which is a GDPR and CCPA question before it is a tracking one.

Sound familiar?

Common Meta Pixel problems we fix

The Meta Pixel problems that bring people to us, and what you have once each one is fixed.

Pixel: 142 Purchases · Shopify: 198 orders

Meta ads conversions don't match the store

iOS opt-outs, ad blockers and a missing CAPI leave a chunk of real sales uncounted, while duplicate pixels count a few of them twice.

Pixel and CAPI reconciled against orders

no CAPI events in Event Manager

Conversions API was never set up

Browser pixel only, no server events, no event_id, and nothing to catch iOS users or anyone running a content blocker.

CAPI live, deduped, match quality measured

Pixel Helper: 2 pixels found

The pixel fires twice on every page

A theme install plus a GTM tag plus a Shopify app, each loading its own fbq. Purchase gets reported more than once per sale.

One pixel, one source of truth

ad account restricted

The Meta ad account was shut off

A policy violation flag, often triggered by landing page content or billing, with campaigns paused and appeal buttons greyed out.

Appeal filed and account reinstated

Event Match Quality: 4.1

Match quality is stuck in the red

No Advanced Matching, hashing disabled, or PII blocked at the consent banner, so Meta cannot connect events to users reliably.

Match quality in the good band

AEM: 9 of 8 events attempted

iOS reporting is dropping an event

More than eight events configured in Aggregated Event Measurement, so one of the lower-ranked events silently reports nothing for opted-out iOS.

Eight prioritised events, counted

What we do

Meta Pixel help, from audit to CAPI rebuild

Call us for one dropped Purchase event, or hand us the whole ad tracking stack.

Audit
What is firing, how many times, from where, and what Meta is actually receiving in Event Manager.
CAPI rollout
Server-side events through CAPI Gateway, sGTM, Shopify or WooCommerce, with event_id deduplication proven.
Consent alignment
Pixel and CAPI gated on a consent banner that GDPR, CCPA and your lawyers will accept.
Ad account recovery
Appeals on restricted accounts, Business Manager clean-up, and getting campaigns running again.
Attribution reconciliation
Meta numbers checked against Shopify, GA4 and your accounting, with the gap explained in plain terms.
Managed Tech
Ongoing pixel and CAPI health checks, with a team to call when Event Manager goes quiet.

How it works

From first message to fixed

  1. Look Free estimate

    Tell us what's going wrong. We look at it, then tell you plainly what's wrong and what it will cost.

  2. Fix

    We fix the cause, not the symptom. If something is down, getting it back up comes first.

  3. Harden

    Backups, monitoring, updates and access, so the same problem can't quietly come back.

  4. Hand back or stay on

    You get a plain-language write-up. Or we stay on for hosting, upkeep and new work.

Often found together

Running Meta Pixel alongside something else?

We work on the whole stack, so the problem can be wherever it actually is.

Questions

Meta Pixel questions

Something else? Call+1 737 727 7327

Why are our Meta ads conversions lower than Shopify sales?

Three things stack up. iOS App Tracking Transparency means a big slice of iPhone buyers never send a browser event. Ad blockers and Enhanced Tracking Protection remove more. And without the Conversions API running server-side, there is no second channel to recover any of it. Add Advanced Matching and CAPI and the gap usually closes to something sensible.

How do we set up Meta Conversions API (CAPI) properly?

Pick a path first: Shopify's native CAPI, a WooCommerce plugin, CAPI Gateway on your own box, or a server-side GTM container. Then make sure every event has a shared event_id and event_name on both the browser and server side so Meta can deduplicate. Hash email and phone for Advanced Matching. Verify with test_event_code in Event Manager, and watch Event Match Quality climb once real traffic flows.

Why does our pixel fire twice on every page?

Almost always because the pixel got installed more than once. A theme snippet, a GTM container, and a Shopify or WordPress app each load their own copy. We open the Meta Pixel Helper, find each source, and leave exactly one in place.

Can you help us appeal a restricted Meta Ads account?

Yes. We review the policy flag, clean up whatever triggered it on the landing page or in Business Manager, and file the appeal through the right channel. Timelines are set by Meta, not us, but a well-prepared appeal gets a real answer faster than a generic one.

How do we align Meta Pixel with iOS 14 ATT and GDPR consent?

Consent first: the banner has to capture a real choice before any pixel or CAPI event fires for EU visitors. For iOS, prioritise your eight Aggregated Event Measurement slots around Purchase and the steps that lead to it. Send Advanced Matching only on consented sessions. That setup is defensible under GDPR and gets the most out of what Apple still allows.

Free estimate

Meta Pixel numbers not adding up?

Tell us what you're running and what's going wrong. A person reads it and comes back with an estimate.

  • No charge to find out what it will take
  • If it's urgent, say so

Replies come from a person. By sending, you authorize us to email you back. No marketing.