Meta Pixel vs Conversions API: Why Your Purchase Data Is Wrong
Meta reports fewer or double purchases compared with your store? Learn how the Meta Pixel and Conversions API work together, how deduplication works and how to check your setup.

In short
- The Meta Pixel tracks events in the browser. The Conversions API (CAPI) sends events from your server. The best setup uses both.
- When you send the same event both ways, Meta needs a matching event name and event ID to count it once.
- Event Match Quality shows how well Meta can match your events to people. Meta suggests aiming for 6.0 or higher where possible.
- Wrong data does not only spoil reports. It teaches Meta's delivery system to find the wrong people.
"Shopify shows 120 orders this week. Meta shows 70." Or the opposite: "Meta shows more purchases than we actually had." If your numbers do not match, you are not alone. Tracking problems are behind a large share of the Meta Ads issues we see.
And this is not just a reporting issue. Meta uses your conversion events to decide who to show ads to. If it receives incomplete or duplicated purchases, it optimizes on bad information, and performance suffers.
Pixel and Conversions API in plain words
The Meta Pixel is a small piece of code on your website. When a visitor views a product, adds to cart or buys, the pixel sends that event from the visitor's browser to Meta.
The problem: browsers and devices increasingly block or limit this. Ad blockers, privacy settings, slow connections and people leaving before the page finishes loading all mean some events never arrive.
The Conversions API sends the same events from your server (or your platform's server, such as Shopify's) directly to Meta. It does not depend on the visitor's browser, so it is more reliable.
The recommended approach is to use both. The pixel catches what happens in the browser; the Conversions API fills the gaps.
Why you see double purchases
If both the pixel and the Conversions API send the same purchase, Meta has to know they are the same event. Meta's documentation explains that for deduplication, the pixel's event ID must match the Conversions API's event_id, and the event names must match too.
When this is missing or broken, Meta may count one purchase twice. You will see:
- More purchases in Meta than in your store
- A ROAS that looks too good to be true
- A "missing deduplication parameter" warning in Events Manager
Why you see too few purchases
The opposite problem usually means:
- The pixel stopped firing after a theme or checkout change
- The Conversions API is not connected, or only sends some events
- Events arrive without enough customer information to be matched to a person
- An app or custom code is sending events with the wrong names
How to check your setup in 15 minutes
- Compare numbers. Pick the last 7 days. Compare purchases and revenue in your store with Purchase events in Events Manager (not just attributed purchases in Ads Manager).
- Open Events Manager → your dataset. Check that Purchase, InitiateCheckout, AddToCart and ViewContent are all receiving events from both browser and server.
- Check deduplication. Look for warnings about missing event IDs or low deduplication coverage.
- Check Event Match Quality. Click the Purchase event to see the score and Meta's recommendations.
- Place a test order using the Test Events tool and confirm a single Purchase is recorded with the correct value and currency.
How to improve Event Match Quality
Event Match Quality (EMQ) is a score from 1 to 10 that shows how well the customer information you send helps Meta match events to accounts. Meta's documentation says a higher score can help decrease your cost per action, and suggests aiming for 6.0 or higher where possible.
To improve it, send more of the customer information parameters Meta supports, correctly formatted and hashed, for example email, phone number, external ID and the fbp and fbc browser values. Most Shopify setups do this through Meta's official sales channel. Make sure your privacy policy and consent handling cover this data.
Shopify, WooCommerce and custom sites
- Shopify: the official Facebook & Instagram sales channel can send both pixel and Conversions API events. Set data sharing to the highest level your privacy policy allows, and avoid running extra pixel apps that send the same events again.
- WooCommerce/WordPress: use a well-maintained plugin or a server-side tagging setup, and confirm event IDs match.
- Custom sites and lead forms: send server events for leads and purchases from your backend, with a consistent event_id shared between browser and server.
What about Google Ads?
The same principle applies. Google's Smart Bidding needs conversion tracking to work, and it optimizes on whatever conversions you record. Duplicate or missing conversions mislead it in the same way. Our Google Ads management setup always starts with a tracking check.
Our take
Before we change a single campaign in a new account, we check tracking. It is the least exciting part of advertising and often the most valuable. Clean data makes reports trustworthy and lets the platforms find real buyers. If your numbers do not add up, our Meta Ads management audit includes a full tracking review.
FAQ
Do I still need the Meta Pixel if I use the Conversions API?
Meta recommends using both together. The pixel captures browser events and the Conversions API adds reliable server events, with deduplication so nothing is counted twice.
Why does Meta show different numbers from Shopify?
Meta reports attributed conversions within its attribution window, while Shopify reports all orders. Some difference is normal. Large or sudden gaps usually mean a tracking problem.
Is the Conversions API hard to set up?
On Shopify it is usually a matter of connecting the official sales channel correctly. Custom sites need developer work to send server events with the right parameters.
Sources
Meta Ads growth strategist and founder of Escalehub. Works with e-commerce brands and lead generation businesses on paid ads, tracking and conversion.
Need help with this? Get a free audit →

