Entry 002 · 06 Nov 2026 · 4 min
Meta Conversions API on Shopify: setup and checks
Set up Meta's Conversions API on a Shopify store, avoid double counting, and check it with one daily ratio: Meta purchases against Shopify orders.
Most Indian Shopify stores running Meta ads have the pixel installed and stop there. The pixel lives in the shopper's browser. When an ad blocker, a privacy setting or a slow payment redirect gets in the way, the purchase never reaches Meta. Meta then thinks your ads sold less than they did, and it optimises towards the wrong people.
The Conversions API fixes most of that. It sends each purchase from Shopify's server to Meta, alongside the pixel. Here is how to set it up on Shopify, and the one ratio we use to check it is working.
What the Conversions API does
Two copies of every event reach Meta: one from the browser (the pixel) and one from the server (the Conversions API). Each carries the same event ID, so Meta keeps one and drops the duplicate. If the browser copy goes missing, the server copy still lands.
The server event can also carry the customer's email and phone number, hashed before they leave your store. Meta uses them to match the order to a Facebook or Instagram account. Better matching means more of your sales get credited to the right ad, and the algorithm learns faster.
Setting it up on Shopify
On Shopify you do not need a developer or a third-party app.
- Install Meta's Facebook and Instagram app from the Shopify App Store and connect your Business Manager, ad account and pixel.
- Open the app's settings and find data sharing. Choose Maximum. Standard sends browser events only. Maximum adds the Conversions API and sends customer information with each event.
- Confirm the pixel is the one your campaigns use. Stores that changed agencies often have two pixels. Events going to a pixel your campaigns do not optimise for are wasted.
- Remove any old pixel code pasted into the theme or added by another app. Two installs of the browser pixel cause double counting that the event ID cannot fix.
Then check it in Meta's Events Manager. Open your pixel, go to the overview, and click into the Purchase event. You should see it received from both "Browser" and "Server". The event's Event Match Quality score should reach 6 or more out of 10 within a few days.
The check that matters: Meta purchases against Shopify orders
Events Manager tells you events are arriving. It does not tell you whether Meta is seeing the right number of them. For that we use one ratio, worked out daily or weekly:
Meta-reported purchases ÷ Shopify orders on the same days
If Meta ads are your only paid channel, a healthy store sits a little under 1. Some orders come from people who never saw an ad: repeat customers, word of mouth, search. Meta should not claim those.
Here is what the ratio looked like in three stores we checked between August and November 2026:
| Store | Days | Meta purchases | Shopify orders | Ratio |
|---|---|---|---|---|
| Fashion brand, Meta only | 91 | 194 | 220 | 0.88 |
| Second brand, Meta only | 55 | 96 | 101 | 0.95 |
| Third brand, 1 to 16 Oct | 16 | 0.01 | ||
| Third brand, 24 Oct to 4 Nov | 12 | 0.38 |
These are three stores, not a benchmark. They show the pattern well. The first two are healthy: Meta sees most orders and leaves some for other channels. The third was broken. For two weeks Meta reported about 1 purchase for every 100 Shopify orders, so its campaigns were optimising almost blind. After the tracking was fixed, the ratio rose to 0.38. That is better and still too low for a store where Meta drives most of the traffic.
Reading your own ratio
- Close to 1, or above it, with other paid channels running: Meta may be claiming orders that Google or email drove. Meta counts a sale up to 7 days after a click and 1 day after a view. Compare with Shopify's own referral data before scaling on Meta's ROAS.
- Between 0.7 and 0.95 with Meta as the main channel: normal.
- Below 0.5 with Meta as the main channel: Meta is missing orders. Check data sharing is on Maximum, that the right pixel is connected, and that checkout events fire on your payment provider's return page.
- A sudden drop: something changed. A theme update, a new checkout app or a payment gateway switch often breaks events. Compare the date of the drop with your change log.
Also check that the order counts in your reports are real. In one store the ratio looked odd because the order data itself had stopped updating, not because Meta had changed. If Shopify shows suspiciously flat orders day after day, look at the export before you look at Meta.
How often to look
Weekly is enough once it is set up. Put the two numbers side by side every Monday. If the ratio moves by more than about 20% from its usual level, look at what changed that week before you change the campaigns.
Questions
Do I need the Conversions API if I have the Meta pixel?
Yes. The pixel runs in the shopper's browser and misses orders when ad blockers, privacy settings or slow pages stop it. The Conversions API sends the same events from Shopify's server, so Meta sees more of your real orders.
Will the Conversions API double count my purchases?
Not if both the pixel and the server send the same event ID for each order. Shopify's Facebook and Instagram app does this for you. Custom setups need it added by hand.
What is a good Event Match Quality score?
Meta scores purchase events out of 10. Aim for 6 or above. Sending email and phone number with each order, which Shopify's app does at the Maximum setting, raises it.
Source: Setup steps from Shopify's Facebook and Instagram app and Meta Events Manager. Example ratios from three Indian D2C Shopify stores run or audited by Boring Commerce, Aug to Nov 2026. Brands are not named.