Why Your Meta Ads Numbers Don't Match Your Sales (and How the Meta Conversions API Fixes It)
Ads Manager says 42 sales, Shopify says 61. Here's where the missing customers went, and how to get them back into your data.
The Meta Conversions API matters for one very ordinary reason. You open Ads Manager and it says 42 purchases, Shopify says 61, and your bank balance, annoyingly, agrees with Shopify. So who's lying?
Nobody, really. The browser pixel you installed a couple of years ago is just missing a chunk of what happens on your store. The fix is the Meta Conversions API (CAPI for short), and if you sell to customers in the UK, USA, Canada or Australia, it's probably the most useful tracking upgrade you can make this year. Let me walk through it the way I'd explain it to a client on a call.
What's actually going wrong with your pixel
Picture a UK store doing around 60 orders a week. If Meta only hears about 42 of them, the algorithm treats the other 18 customers as if they never existed. It stops looking for people like them, and some of your best buyers quietly vanish from the data your ads learn from. Repeat that for a few months of ad spend and you can see why the gap matters.
The classic Meta Pixel is a small piece of JavaScript that runs inside your customer's browser. When someone buys, the browser is supposed to tell Meta. The word to notice there is "supposed."
Ad blockers can stop that message from ever leaving. Safari and Firefox limit how long tracking cookies live. iPhone users can opt out of tracking with one tap. Some people close the tab before the thank-you page finishes loading, and a slow theme or a stack of apps can break the event entirely. Each one is a small leak. Together they can add up to a big gap.
And here's the part that hurts: Meta's algorithm learns from the data you send it. If it only sees part of your sales, it optimises for part of your customers. You're paying to teach it with half the lesson.
The Meta Conversions API in plain English
Think of the pixel as a customer telling Meta, "I bought something." The Meta Conversions API is your store's server telling Meta the same thing directly. No browser involved, so nothing to block.
Your server already knows about every order, because it has to. The Meta Conversions API just forwards that information to Meta, along with customer details such as email and phone number, which are hashed (scrambled with SHA-256) before they leave. Meta uses those details to match the sale to a real person on Facebook or Instagram.
It's worth saying clearly: CAPI doesn't replace the pixel. Meta recommends running both, and that's what I set up for clients. The browser catches what it can, the server fills the gaps, and a deduplication step makes sure nothing is counted twice.
Pixel only vs pixel plus CAPI
| Pixel only | Pixel + Meta Conversions API | |
|---|---|---|
| Where the event is sent from | Customer's browser | Browser and your server |
| Affected by ad blockers | Yes | Much less |
| Survives short cookie lifetimes | Poorly | Better, thanks to customer data matching |
| Can send offline or CRM events | No | Yes |
| Setup effort | Low | Medium |
Five signs you need the Meta Conversions API
- Ads Manager purchases are consistently lower than your store's orders.
- Your Event Match Quality score in Events Manager sits at "Poor" or "OK."
- Cost per purchase in Meta looks worse than your real profit says it should be.
- Campaign performance jumps around without any change on your side.
- A large share of your traffic comes from iPhones or privacy-focused browsers.
One honest caveat. Not every gap is a tracking fault. Ads Manager uses its own attribution window, while Shopify credits the last click. A difference of 10 to 20 percent can be perfectly normal. If your gap is far bigger than that, tracking is the likely culprit.
How a proper Meta Conversions API setup works
Audit what you have now
Before touching anything, I check what the pixel is really firing. Duplicate pixels, missing purchase values and broken currency codes show up more often than you'd think.
Choose the right method
For most Shopify stores, the native Facebook and Instagram integration with data sharing set to maximum is the quickest route. WooCommerce has plugins that do a decent job. If you need full control, or you also want to send data to Google and TikTok, a server-side Google Tag Manager container is the better long-term choice.
Match customer data and deduplicate
Every event needs the same event name and event ID from both the browser and the server. That's how Meta knows they're one purchase, not two. Get this wrong and your numbers will double, which is somehow worse than missing data.
Test before you trust it
Events Manager has a Test Events tool. Place a real test order and watch it arrive from both sources. Check the value, the currency and the deduplication status.
Monitor for a couple of weeks
Give it time, then compare Meta's purchase count against your store. The gap should shrink and your match quality should climb.
Which Meta Conversions API setup method fits your store?
There's no single right answer, and the simplest option is often perfectly fine. Here's how I think about the four common routes.
Native Shopify or WooCommerce integration
The quickest route, and often free. It suits a simple store that only advertises on Meta. You get less control over what's sent and how it's matched, but for many shops it's a big step up from the pixel alone.
Conversions API Gateway
Meta's own hosted option. It needs less code than a custom build, though you give up some flexibility and stay tied to Meta's way of doing things.
Server-side Google Tag Manager
More work up front, but you end up with one clean data stream you control. You can send it to Meta, Google and TikTok from the same place, which is usually the better long-term choice once several platforms are in play.
A custom API build
Only worth it for unusual setups, such as headless stores, custom checkouts or sales that close inside a CRM.
Mistakes I keep seeing
Turning it on and walking away. A setup that was fine in March can quietly break after a theme update. Someone needs to look at it.
Sending too little customer data. An event with only an IP address is hard for Meta to match. Email and phone, when the customer has given consent, make a real difference.
Ignoring deduplication. I'll say it again because it matters. Double-counted purchases make your ROAS look brilliant right up until you check the bank.
Trusting one platform. Compare Meta against your store data and, if you can, a neutral analytics tool. No single dashboard tells the whole story.
Forgetting the events before the sale. Purchase gets all the attention, but Add to Cart and Initiate Checkout teach the algorithm what a serious buyer looks like. Send those through the server too.
Will this improve my ad results?
Not by magic. Nobody can promise you that and I won't either. What the Meta Conversions API gives you is better data going into Meta's system and more trustworthy numbers coming out. Better inputs usually lead to smarter optimisation, and clearer reports mean you stop killing good campaigns by mistake. Your creative, offer and budget still do the heavy lifting.
Where AI automation fits in
Once tracking is clean, you can start doing useful things with it: sending new customers to a WhatsApp sequence, flagging high-value orders to your team, or feeding purchase data back into your ads. I wrote about how that works for online shops in my guide to AI automation for UK e-commerce. Reliable tracking is the foundation, and the automation sits on top of it.
A ten-minute checklist before you change anything
Whether you fix this yourself or hand it to someone like me, spend ten minutes on these first. It saves hours later.
- Install the Meta Pixel Helper browser extension and check that Purchase fires once, with a value and a currency.
- Open Events Manager and note the Event Match Quality score for Purchase.
- Compare the last seven days of Ads Manager purchases with your store's orders.
- Check your cookie banner. Does it really hold back the pixel until someone accepts?
- Write down how tracking is set up today (native app, plugin or GTM), so nobody adds a second layer on top of the first.
Frequently asked questions
Is the Meta Conversions API replacing the Meta Pixel?
No. Run both, with deduplication, so each covers the other's blind spots.
Does the Meta Conversions API work without cookie consent?
No. You still need to respect consent rules in your market. It changes the route the data takes, not the permission you need.
How long does setup take?
A Shopify store using the native integration can be done in an afternoon. A custom or server-side GTM build with proper testing usually takes a few days.
Will my ROAS jump overnight?
Probably not. Expect more accurate reporting first, and better optimisation over the following weeks.
Do I need the Meta Conversions API if I only spend a little on ads?
Small budgets feel missing data the most, because every sale is a bigger slice of what Meta learns from. You probably don’t need anything fancy at that stage, though. The native store integration is usually enough.
Want it done properly?
If your Meta numbers and your sales don't line up, I'm happy to take a look. Send me a few lines below, or see my work and reviews on my Upwork profile.
Hasan Abrar helps e-commerce brands in the USA, UK, Canada and Australia fix their tracking, build their websites and automate the boring parts of their business.
Tell me what's not adding up
A few lines about your store and your tracking problem is enough. I reply personally within 24 to 48 hours.