Home / Fixes / Meta pixel not firing
Pixel and ad tracking

Your Meta pixel isn't tracking purchases

When the pixel misses purchases, Meta optimizes toward the wrong people and your ROAS looks worse than it is. Most pixel gaps come down to a handful of fixable causes.

Signs this is happening to you

  • Meta Events Manager shows few or no Purchase events despite real orders
  • Test Events works, but live purchases never show up
  • Event Match Quality is low, so Meta can't attribute conversions
  • ROAS in Ads Manager looks far worse than your real Shopify revenue suggests

What's usually causing it

  • The pixel never runs on the new checkoutAfter Shopify's checkout extensibility change, pixels added the old way no longer fire on checkout or the thank-you page. The purchase event simply never happens.
  • No server-side backup via Conversions APIBrowser pixels are blocked by iOS, ad blockers, and consent tools. Without the Conversions API as a server-side backstop, a large share of purchases never reach Meta.
  • Duplicate pixels or duplicate eventsTwo pixels, or a pixel plus an app sending the same event, inflate or confuse Meta's data and tank Event Match Quality.
  • Missing or mismatched event parametersWhen value, currency, or the customer match keys are absent, Meta can't value or attribute the conversion even when the event fires.

How Mimetic finds it and ships the fix

Mimetic completes a real purchase on your store and verifies whether Meta actually receives a well-formed Purchase event, browser and server side.

  • We run a live purchase and watch whether the Meta Purchase event fires and what parameters it carries
  • We check for duplicates, missing values, and whether the Conversions API is backing up the browser pixel
  • We show you exactly where the event breaks and what it's costing in lost attribution
  • We open the fix as a pull request, including server-side coverage if you're relying on the browser pixel alone
Browser-only pixels miss a large share of purchases

Between iOS limits, ad blockers, and consent denials, a browser-only pixel commonly fails to report a meaningful share of real orders. Server-side coverage closes most of that gap.

Questions

How do I know if my pixel is firing without testing a purchase myself?

Mimetic completes a real purchase path on your store and reports whether the Meta Purchase event fired, what value it carried, and whether the Conversions API backed it up, so you don't have to place a test order yourself.

Is the Conversions API really necessary if the browser pixel works?

Yes, in practice. The browser pixel is blocked for a large share of users by iOS, ad blockers, and denied consent. The Conversions API sends the event server side as a backstop, which recovers conversions Meta would otherwise never see and improves optimization.

Will fixing the pixel change my reported ROAS?

Usually for the better. When Meta starts seeing purchases it was missing, attributed revenue rises and your real ROAS becomes visible, which also lets Meta's optimization target buyers more accurately.