If Ads Manager says 120 purchases and your order sheet says 85, every optimisation decision you make is built on the wrong number. Here is how to close the gap first.
Ask most Bangladeshi online sellers how their Facebook ads are doing and they will read you a number from Ads Manager. Ask them how many orders were actually delivered last week and the number is usually different — sometimes very different. That gap is the single most expensive problem in paid media, because every budget decision is made on the platform number.
Why the two numbers disagree
- Duplicate events. A thank-you page that fires the purchase event twice, or a pixel and a Conversions API sending the same purchase without a shared event ID.
- The wrong action. A “purchase” that actually fires on add-to-cart or on the checkout page load.
- Cash on delivery. The platform counts an order the moment it is placed; you only count it when it is delivered and paid. Cancellations and returns never reach Ads Manager.
- Attribution windows. Meta can credit a purchase to an ad seen days earlier. Your order sheet has no idea which ad started the journey.
How to reconcile
- Export a week of platform-reported purchases and a week of real orders.
- Match them by date and value. Note duplicates, missing orders and cancelled COD orders.
- Fix the tracking: one purchase event, fired once, on the confirmed order, with deduplication between pixel and Conversions API.
- Record the ratio between the two numbers. Once it is stable, the platform number becomes useful again.
Why this comes before optimisation
Optimising against a broken number teaches the algorithm to find people who trigger the broken event — not people who buy. Fixing tracking first is unglamorous, but it is where most of the improvement in a first quarter comes from.
If you want a second pair of eyes on your account, send us read access and we will tell you what the data already says.
