Meta ads for Shopify: Conversions API without the jargon
The Conversions API sends purchases to Meta from Shopify's servers, so ad results don't depend on the browser. How to turn it on, what each data-sharing level sends, and the double-counting problem.
On this page
On Shopify, you turn on the Meta Conversions API by setting data sharing to Enhanced or Maximum in the Facebook & Instagram app. It sends purchase and other events to Meta from Shopify's servers as well as from the browser pixel, so Meta sees sales that ad blockers and browser privacy settings would hide. That gives Meta's ads more conversions to learn from. The two things to get right are choosing the data-sharing level knowingly and making sure purchases aren't counted twice.
This is for store owners running or starting Meta ads on Shopify. It doesn't cover campaign strategy; for that see our Meta ads service.
Disclosure: Cloudgramam sets up, migrates and markets Shopify stores, so we have an interest in this topic. You pay Shopify, app makers and payment providers directly; we don't resell plans, apps or hosting. Prices and features were checked on Shopify's own pages on 15 November 2026 and change often, so check them again before you decide.
What is the Conversions API, in plain words?
The Meta pixel is a piece of code in the shopper's browser that tells Meta "this person bought something". Browsers and ad blockers increasingly stop it. The Conversions API sends the same message from Shopify's servers instead, which browsers can't block. Meta matches the two and counts each sale once, if both carry the same event ID.
Better data means Meta can find more people like your buyers, and your reports show results closer to reality.
What does each data-sharing level send?
In the Facebook & Instagram app, go to Sales channels, then Facebook & Instagram, then Settings, then Data sharing settings. Shopify's Meta data sharing help page describes three levels (checked 15 November 2026):
| Level | How events are sent | What it means |
|---|---|---|
| Standard | The Meta pixel in the browser only | Ad blockers can stop it, and then Meta sees nothing |
| Enhanced | The pixel plus the Conversions API, which sends purchases server to server | Shares customer name, location, email and phone with Meta to match users |
| Maximum | The same methods as Enhanced | Same data as Enhanced; Shopify says the store also gets Meta's latest advertising technology |
Enhanced and Maximum give Meta far more to work with, and they share customers' personal details to do it. Your privacy policy should say you share data with Meta for advertising, and your cookie or consent set-up should match what you send. If you sell to people in India, consider what the Digital Personal Data Protection Act requires of you; ask your lawyer, not your ad agency.
How do you check it's working?
- Open Meta Events Manager and select your dataset (pixel).
- Look at the Purchase event. It should show both "Browser" and "Server" as connection methods.
- Check the deduplication information for Purchase. Most events should be deduplicated, meaning Meta matched browser and server copies.
- Check the event match quality score. Higher means Meta can match more purchases to its users.
- Place a real order and look for it in Test events.
What's the hard case with the Conversions API?
Purchases counted twice because an old pixel is still in the theme. It starts innocently: years ago someone pasted the Meta pixel code into the theme, and later the store installed the Facebook & Instagram app. Now two pixels report each purchase: the old one without an event ID, and the app's one with an ID that matches the server event. Meta can't match the old one, so it counts it as a second sale. Ads Manager shows a return on ad spend twice as good as reality, and the owner raises the budget based on sales that didn't happen.
How to spot and fix it:
- Compare Meta's purchase count for a week with Shopify's order count from Meta-attributed visits, allowing for Meta's attribution window. If Meta reports far more purchases than Shopify has orders in total, something's double counting.
- Use the Meta Pixel Helper browser extension on a product page. More than one pixel, or the same pixel firing twice, is the sign.
- Remove the old pixel code from the theme files and any custom pixel that duplicates it, leaving the app as the only source.
- Do the same check for other tools. A tag manager or another app sending Meta purchase events causes the same problem.
Our Shopify analytics and tracking setup guide explains why Shopify, GA4 and Meta never agree exactly, and how far apart is normal.
Frequently asked questions
Do I need a developer to set up the Conversions API on Shopify?
No. Setting data sharing to Enhanced or Maximum in the Facebook & Instagram app turns it on.
Is the Facebook & Instagram app free?
Yes, the app is free. You pay Meta for ads.
Will the Conversions API improve my ad results?
It usually gives Meta more purchases to learn from, which tends to help. It doesn't fix weak creative or offers.
Can I use the Conversions API without the pixel?
On Shopify's Enhanced and Maximum settings, both run together and Meta deduplicates them. That's the set-up Shopify's app uses.
Want your Meta tracking checked and your ads run properly? See our Meta ads for Shopify service.