Is Your Meta Pixel Tracking Sales? 5 Checks to Run
By Barrie Le Gall, Meta Business Partner · Updated October 2026
Make a test purchase or enquiry, then check it appears once in Meta's Events Manager under the right event name. Then compare a week of Meta's reported sales with your real orders. If Meta shows far fewer, events are being missed. If it shows nearly double, they're being counted twice.
In short
The Meta pixel reports actions on your website back to Meta from the visitor's browser.
The Conversions API sends the same actions from your server, so fewer are lost to ad blockers and cookie choices.
Running both is the standard set-up, but each event needs a matching event ID so Meta counts it once.
Reported sales close to double your real orders usually means events are being counted twice.
If tracking is wrong, Meta learns from the wrong people and your ads get worse.
What does the Meta pixel do?
The Meta pixel is a piece of code on your website that tells Meta when someone does something that matters, such as buying or enquiring.
Each of these actions is called an event. Common ones are PageView, Lead and Purchase. Meta uses them in two ways. It reports them in Ads Manager as results. And it learns from them, so it can show your ads to more people like the ones who bought.
What is the Conversions API, and do I need it?
The Conversions API sends the same events to Meta from your server instead of the visitor's browser. If you run ads to sell or get enquiries, you need it.
The pixel runs in the browser, so ad blockers, cookie choices and some phone settings stop it seeing everything. The Conversions API, often shortened to CAPI, doesn't rely on the browser. It fills those gaps.
You don't always need a developer. Meta's Conversions API Gateway runs the server side for you, and platforms such as Shopify have their own built-in connections.
How can I check my pixel is working?
Run these five checks. They take about 20 minutes.
Open Test Events. In Meta Events Manager, select your pixel and open the Test Events tool.
Make a test action. Buy something cheap or send an enquiry on your own site, ideally on your phone. Watch it arrive in Test Events. If you run the pixel and the Conversions API, you should see both versions carrying the same event ID.
Check the event name. A purchase should arrive as Purchase and an enquiry as Lead. The browser and server versions must use the same name.
Compare a week. Put Meta's reported purchases or leads for the last 7 days next to your real orders or enquiries.
Check your campaign. Make sure the ad set optimises for that same event, not for clicks or page views.
While you're in Events Manager, look at Event Match Quality. It's Meta's score for how well it can link your events to real people. A low score means Meta is learning from less than it could.
Why don't Ads Manager numbers match my sales?
Some gap is normal. A big gap in either direction means something is wrong.
Meta credits a sale to an ad if the buyer clicked or viewed it within a set window. Some of your sales come from people who never saw an ad. Some sales are hidden by ad blockers. And some events get counted twice.
What you see | What it usually means | What to do |
|---|---|---|
Meta shows far fewer sales than your orders | Events are being missed | Add or fix the Conversions API |
Meta shows close to double your orders | Events are counted twice | Fix the event ID so browser and server events match |
Meta roughly tracks your orders | Tracking is broadly working | Keep comparing weekly |
Meta treats a browser event and a server event as one only if the event ID and event name match, within 48 hours of the first one arriving.
What happens to my ads if tracking is wrong?
Meta learns from the wrong signal, so it finds the wrong people.
Here's how it should work. The ad finds the right person. The landing page turns their click into a customer. Tracking reports that sale back to Meta, which teaches it who to find next. Break the tracking and the loop breaks. Meta goes back to finding people who click, because clicks are all it can see.
Missed events also slow learning. Meta says an ad set needs about 50 results within 7 days to finish its learning phase. Every missed sale pushes that further away.
From the accounts I run, tracking is the first thing I check in a new account, before the ads or the page.
Frequently asked questions
Do I need both the Meta pixel and the Conversions API?
For most businesses running ads to sell or get enquiries, yes. The pixel sees actions in the browser. The Conversions API sends them from your server, which catches the ones the browser misses. Run both, with matching event IDs, so Meta counts each sale once.
How do I know if my events are being counted twice?
Compare Meta's reported sales with your real orders over a week. If Meta's number is close to double, events are almost certainly being counted twice. In the Test Events tool, check that the browser and server versions of each event carry the same event ID and event name.
What is Event Match Quality?
Event Match Quality is a score in Meta Events Manager showing how well Meta can link your events to the people who did them. A higher score means Meta can learn from more of your sales. It usually improves when your set-up sends more customer details, such as email address, securely through the Conversions API.
Can I set up the Conversions API without a developer?
Often, yes. Meta's Conversions API Gateway handles the server side without code. Shopify and many other platforms have built-in connections to Meta. If your site is custom-built, you may need a developer, or someone who has set it up many times before.
Not sure your tracking is right?
Send me your website and access to Events Manager. On a free 30-minute call I'll tell you whether your tracking is counting sales properly and what I'd fix first. Book your free review. Pixel and Conversions API set-up is part of how I run Meta ads.
Sources: Relevant Audience on the pixel and Conversions API · PixelFlow on deduplication · PPC Land on the learning phase
