Guide · Updated August 2026

Meta Pixel says “connected” — but isn't tracking purchases

This is one of the most-reported problems in the entire Shopify ecosystem, and the reviews of the official Facebook & Instagram app are full of it: “This is not giving us any pixel whatsoever.” “My pixel is suddenly not firing.” “Always having an issue with pixels value.” The badge says connected; Ads Manager says nobody's buying. One of them is lying, and it's the badge.

Why the "connected" badge lies

"Connected" means Shopify holds a valid link to your Meta business assets. It does not mean events are being generated on your storefront, accepted by Meta, or attributed to your ads. Every one of those stages can fail independently while the badge stays green:

• Event generation can stop after Shopify checkout or theme changes.
• Meta can silently discard events it considers malformed or duplicated.
• Data-quality throttles and account reviews pause processing without notice.
• Token/permission changes (password resets, Business Manager edits, personnel changes) can invalidate the pipeline behind the scenes.

Confirm it in five minutes

1. Meta Events Manager → Data Sources → your pixel. Look at the event graph for the last 7 days. A cliff or a flatline in Purchase events while your Shopify Orders page shows steady sales is your confirmation.
2. Test Events tab: enter your store URL and click around your own store. Watch whether PageView, ViewContent, AddToCart appear live.
3. Compare totals: Purchases Meta received in 48h vs. orders Shopify recorded in the same 48h. Expect a gap of 10–30% (ad blockers, iOS, consent). A gap of 80–100% means broken tracking, not privacy loss.

Fixes, matched to cause

• Started after a checkout/theme change? Old script-based tracking died with checkout.liquid. Remove legacy snippets and rely on the channel app's native pixel, or implement a Customer Events web pixel. Duplicate legacy + native tracking is itself a cause of discarded events.
• Events fire in Test Events but purchases are missing? Classic checkout-scope failure. Verify the pixel is set at the sales-channel level (not just theme), and that Conversions API is enabled in the channel app settings — server-side events survive what browser events don't.
• Zero events of any kind? Disconnect and reconnect the Facebook & Instagram channel with an admin account. Confirm in Business Manager that the pixel still lists your store's domain and the connection user still has permissions.
• Events arrive but "pixel value" errors / wrong amounts? Usually a second app also sending purchase events with different parameters. Audit installed apps for anything touching the pixel and remove the overlap.
• Everything looks right and it's still dead? Check Business Manager notifications for data-quality or policy flags — processing pauses often surface only there, days late.