Meta Pixel Not Tracking Purchases: Causes and How to Check
Meta and CAPI · 4 min read · by Anna Viggeborn
Your store records orders. Meta Events Manager records nothing, or far fewer purchases than you know happened. That gap is almost always a firing problem, a loading problem or a consent problem.
The most common causes
- The Purchase event never fires on the confirmation page, often because the page is rendered client side and the trigger never matches.
- The pixel loads after the user leaves the confirmation page, so the event is cut off.
- A consent banner blocks the pixel until acceptance, and most users never accept on the thank you page.
- A theme, checkout or app update removed the snippet.
- A redirect sends the buyer to an external payment confirmation that has no pixel on it.
- An ad blocker or browser protection blocks the browser request.
How to check in order
1. Events Manager → Test Events → complete a real test order
2. Does Purchase appear at all?
3. If yes: compare event count to orders for the same day
4. If no: check the confirmation page source for the pixel
5. Check consent state and whether the event is gated
6. Check whether server events exist in parallel
What it means for decisions
Missing purchases understate conversions and ROAS, and they also starve the optimisation system of the outcome it is supposed to learn from. Do not cut budget on a campaign until you know the event is landing.
If the browser path is fragile, the durable fix is usually the Conversions API alongside the pixel, with correct deduplication.
Not sure whether you have a performance problem or a signal problem?
Your performance may be fine. Your signals aren't.
Run a free Milestic Signal AuditContinue the diagnostic path