Why Meta doesn't track all your sales (and what it's costing you)

The pixel lives somewhere fragile

Meta's classic pixel is a small piece of code that runs inside your customer's browser. When someone buys, the browser has to run that code and tell Meta. If the browser doesn't run it, the event doesn't exist.

And there are a lot of reasons a browser won't run it.

The four biggest leaks

1. Ad blockers

Between 25% and 40% of users in LATAM have some kind of blocker turned on, especially on desktop. A blocker doesn't block "ads": it blocks tracking scripts. Meta's is first on the list.

2. iOS and cross-app tracking

Since iOS 14.5, if your customer buys from Instagram's in-app browser on an iPhone and didn't grant tracking permission, most of the signal gets cut. If you sell clothing, beauty or accessories, this is probably your biggest hole: it's where your audience is.

3. Cookies that delete themselves

Safari deletes tracking cookies after 7 days. Chrome is heading the same way. If someone sees your ad today and buys three weeks from now — normal for a high-ticket item — to Meta that sale came out of nowhere.

4. Accelerated checkouts

One-click payments skip the traditional checkout flow. Fewer steps for the customer, fewer events for your pixel.

What losing events really does to you

The real problem isn't the report. It's that the algorithm learns from those events. Every purchase that reaches Meta teaches it what your buyer looks like. If only half of them get there:

• Your lookalike audiences are built from an incomplete sample and perform worse
• The algorithm takes longer to exit the learning phase
• Retargeting reaches fewer people than it should
• Your CPA rises without you touching a single campaign
• You turn off ads that were actually working

That last one is the most expensive. If an ad drove 12 sales and Meta only recorded 5, you're going to pause it as "unprofitable." You're shutting down what works.

How to fix it: send the event from the server

The fix isn't to fight browsers. It's to stop depending on them.

With server-side tracking, the purchase notification doesn't leave from your customer's browser: it leaves from the server. A blocker can kill a script in the browser. It can't kill a conversation between two servers. That's why the events that used to get lost now arrive.

On top of that, the event travels more complete — with identity data that raises your EMQ, Meta's match quality score. Better EMQ means better optimization and a lower cost per result.

The bottom line

If the gap between what your store shows and what Meta shows is bigger than 15%, you don't have a reporting problem. You have an optimization problem that's making you overpay for every sale, every day.