Conversions API
How to Set Up Facebook Conversions API for Shopify (2026)
Set up Facebook Conversions API on Shopify two ways: Shopify’s Facebook & Instagram app or a CAPI app. Test events in Events Manager and fix duplicate sales.
By PixlBridge Team
Updated 17 min read
On this page
There are two no-code ways to set up the Facebook Conversions API on Shopify: choose the Enhanced or Maximum data sharing level in Shopify’s own Facebook & Instagram app, or install a Conversions API app such as PixlBridge from the Shopify App Store. Either way, your store’s events, purchases above all, reach Meta from a server instead of depending only on the Meta Pixel in the shopper’s browser.
Switching it on is the easy part. The problems tend to come afterwards: two tools sending the same purchase, events landing in the wrong pixel, or server events that never arrive. This guide covers both methods step by step, when to choose which, how to avoid duplicate purchases, how to test in Meta Events Manager and how to fix the common problems.
Disclosure: PixlBridge publishes this guide, and its app is Method 2. Shopify’s app is described from Shopify’s public help pages. Shopify and Meta rename menus from time to time, so if a label below differs from your screen, follow what your admin shows.
Quick answer: how to set up the Facebook Conversions API on Shopify
- Check what already sends events to Meta: Shopify’s Facebook & Instagram app, Meta Pixel code in your theme and other tracking apps.
- Choose a method: Shopify’s Facebook & Instagram app, or a Conversions API app such as PixlBridge.
- Connect your Meta assets: the ad account and the Meta Pixel your ads already use.
- Turn on server events: Enhanced or Maximum data sharing in Shopify’s app, or connect Facebook in the Conversions API app and choose the events to send.
- Test in Meta Events Manager: send a test event, then check that a real order arrives as a Purchase from the server.
- Count each purchase once: let only one tool send purchases, and check that Meta’s Purchase count tracks your Shopify orders.
What the Conversions API adds to your Shopify tracking
The Conversions API (CAPI), also called the Facebook or Meta Conversions API, lets a server send events such as a purchase straight to Meta. The Meta Pixel reports the same events from the shopper’s browser, where ad blockers, browser privacy limits and tabs closed too early can stop it. Server events don’t rely on the browser reaching Meta, so they can get some of those missed events through.
Meta recommends running both, with the same event ID on the browser and server copy of each event so that Meta counts it once. In Events Manager your pixel may be labeled a dataset: same thing, same ID. For the full comparison, see how the Meta Pixel and the Conversions API work together; for what better data does for your ads, read the benefits of the Conversions API.
Two ways to connect Shopify to the Facebook Conversions API
Both methods work without code. They differ in how much control and visibility you get, and in cost.
| Shopify’s Facebook & Instagram app | A Conversions API app (PixlBridge) | |
|---|---|---|
| How you turn it on | Choose Enhanced or Maximum data sharing | Install, connect Facebook, choose your ad account and pixel |
| Sent server-side | The purchase event, as Shopify’s help center describes it | Seven standard events, from PageView to Purchase |
| Event control | One data sharing level for the store | Each event type on or off, per store |
| Checking delivery | Meta Events Manager | Events Manager, plus a status panel, Recent activity and a store health page in the app |
| Ad results | Meta Ads Manager | ROAS (return on ad spend) by campaign, ad set and ad, next to your Shopify sales |
| Also does | Syncs your products to a Meta catalog | “Why no sale?” for products with traffic but no sales, alerts and email reports |
| Cost | Free to use | Paid monthly plan |
Choose Shopify’s Facebook & Instagram app if…
- You want a free start and are happy to read your results in Ads Manager.
- You already use the app for your product catalog.
- You prefer to keep tracking inside Shopify’s and Meta’s own tools.
Choose a Conversions API app such as PixlBridge if…
- You want the whole funnel, from page views to purchases, sent server-side, with a switch for each event.
- You want to see whether each event reached Meta, and Meta’s message when one fails.
- You want Meta ad results and ROAS in the same place as your Shopify sales.
You can also combine them, for example keeping Shopify’s app for the catalog and PixlBridge for tracking. That works as long as only one of the two sends purchases, as explained further down.
Before you start
Have these ready:
- Shopify admin access that lets you install apps.
- Your Meta assets: a business portfolio (formerly Business Manager) with your ad account. Shopify’s app also needs a published Facebook Page connected to that portfolio, and your Facebook account needs full control of both.
- The Meta Pixel your ads already use. Reuse it instead of creating a new one, so your event history and the audiences built on it carry on.
- Admin access to the ad account. Connect PixlBridge with a Facebook account that is an admin of the ad account; otherwise Meta can refuse the events.
Check what already sends events to Meta
Tracking that was added long ago and forgotten is a common source of duplicate purchases. Before you add anything, look in these places:
- Settings → Customer events in the Shopify admin, which lists the app pixels and custom pixels on your store.
- Your theme code, usually
theme.liquid, for pasted Meta Pixel code. - Online Store → Preferences, where a Meta Pixel could be added in older setups.
- Other apps and tag managers that send events to Meta, including any an agency set up.
The free Meta Pixel checker for Shopify reads a store’s public page and shows its Pixel ID, how the pixel was added and whether it’s added twice.
Method 1: Shopify’s Facebook & Instagram app
Shopify’s Facebook & Instagram app is Meta’s own sales channel for Shopify (Shopify’s help center calls it Facebook and Instagram by Meta). It connects your store to Meta, and its customer data sharing setting decides whether it uses the Conversions API.
- Install the app. Add Meta’s Facebook & Instagram app from the Shopify App Store, or open it under Sales channels if it’s already installed. Make sure the developer is Meta, not a look-alike.
- Connect your Meta account. Sign in with Facebook and choose your business portfolio, Facebook Page, ad account and, if you sell there, your Instagram account. Check each one before you confirm: the wrong portfolio or ad account causes trouble later.
- Open the data sharing settings. Go to Sales channels → Facebook & Instagram → Settings and open the data sharing settings. Shopify’s own help pages call this screen both “Data sharing settings” and “Share data settings”.
- Turn on customer data sharing and choose a level. Enhanced or Maximum adds the Conversions API (see the table below).
- Select your Meta Pixel and confirm. Pick the pixel your ads already use.
- Remove old pixel code you found in your theme or in Online Store → Preferences. Shopify’s help center recommends it, so the pixel doesn’t run twice.
There’s no access token to create and no code to write.
Standard, Enhanced or Maximum?
| Level | What it uses | What it shares with Meta |
|---|---|---|
| Standard | The Meta Pixel only, in the browser, where ad blockers can stop it | Browsing behavior |
| Enhanced | Meta Pixel + Conversions API | Browsing behavior, plus customers’ name, location, email address and phone number |
| Maximum | Meta Pixel + Conversions API, kept up to date with Meta’s latest ad technology | The same as Enhanced |
Standard doesn’t use the Conversions API. At Enhanced and Maximum, Shopify’s help center says the Conversions API sends the purchase event from Shopify’s servers to Meta’s. Pick Maximum if you want the app’s most complete setup. Both levels share more customer information, so make sure your privacy policy covers it.
Method 2: Shopify CAPI integration with PixlBridge
PixlBridge is a Shopify app that sends your store’s events to Meta from its server through the Conversions API, and reports your Meta ad results and ROAS next to your Shopify sales. There’s no code to add and no theme to edit.
- Install PixlBridge from the Shopify App Store and approve the permissions Shopify shows. Your PixlBridge account is created automatically. The app collects events through Shopify’s own systems: a web pixel that listens to Shopify’s customer events, and order webhooks that add each order’s details.
- Connect Facebook & Instagram with Facebook Login for Business, signed in as an admin of the ad account.
- Choose your ad account and your Meta Pixel: the pixel your ads already use.
- Choose your events. All seven standard events are sent unless you switch one off (My store → Advanced settings → What to report). If Shopify’s Facebook & Instagram app also sends purchases, decide now which tool sends Purchase (see the next section).
- Send a test event from the setup steps on Home, or from My store → More → Send a test event. PixlBridge sends one test event to your pixel through the Conversions API and tells you whether Meta received it. It’s a custom event with no value, never a Purchase, so your sales numbers don’t change. To watch it arrive in Events Manager, add the test code Meta shows under Test events.
Which events PixlBridge sends
| What the shopper does (Shopify event) | Meta standard event |
|---|---|
Views a page (page_viewed) | PageView |
Views a product or collection (product_viewed, collection_viewed) | ViewContent |
Searches the store (search_submitted) | Search |
Adds to cart (product_added_to_cart) | AddToCart |
Starts checkout (checkout_started) | InitiateCheckout |
Submits payment details (payment_info_submitted) | AddPaymentInfo |
Completes the order (checkout_completed plus the orders/paid webhook) | Purchase, one per order |
What happens after you connect
- Customer details become hashed match keys. Email, phone, name, city, state, zip and country, the details Meta uses to match an event to a person, are normalized and SHA-256 hashed before sending, and the raw values aren’t stored. Click and browser IDs (
fbc,fbp), IP address and user agent go to Meta the way it expects. - One Purchase per order. The completed checkout from the web pixel and the paid order from Shopify’s webhook are merged into a single Purchase with the full set of match keys.
- Event IDs come from Shopify. Each event ID is built from Shopify’s own identifiers, so a browser pixel that uses Shopify’s event IDs isn’t counted twice.
- Delivery is quick and retried. Events reach Meta within seconds and purchases within about a minute, in batches of up to 1,000. If a send fails for a temporary reason, retries start at one minute and double each time; after five attempts the event is marked failed with Meta’s message.
- The web pixel follows your privacy settings. Shopify’s customer privacy settings control when the web pixel runs in the shopper’s browser. Purchases built from Shopify’s order webhooks are sent from the server, so your privacy policy should cover them. PixlBridge acts as your store’s processor.
Once events flow, Home shows your Shopify sales and blended ROAS (store sales ÷ Meta ad spend), and the Ads overview shows ad spend, purchases, purchase value and ROAS for each campaign, ad set and ad, with its creative. For the mechanics in depth, read how server-side tracking works on Shopify, or see how PixlBridge sends your Shopify sales to Meta.
Running both? How to avoid duplicate purchases
Deduplication is how Meta keeps one copy of an event that reaches it twice. Meta merges a browser event and a server event when they have the same event name and the same event ID and arrive within 48 hours of each other. When two tools each make their own IDs, Meta may not recognize their copies as the same order, and when both send the purchase from a server, Meta counts it twice.
That’s the overlap to settle when you use Shopify’s Facebook & Instagram app and PixlBridge together. At Enhanced or Maximum, Shopify’s app sends purchases server-side with its own event IDs, while PixlBridge sends its own Purchase for the same order. Let one tool own Purchase:
| Your setup | What to do |
|---|---|
| Shopify’s app only, at Enhanced or Maximum | Remove any old pixel code; nothing else should send purchases. |
| PixlBridge only | Leave Purchase on in PixlBridge. |
| Both, keeping Shopify’s app at Enhanced or Maximum | Switch off Purchase in PixlBridge. It keeps sending the other events, and its reports still use your Shopify orders and Meta’s ad results. |
| Both, with PixlBridge sending purchases | Lower Shopify’s app to Standard, so it no longer sends purchases through the Conversions API. |
| Old theme code or another tracking app as well | Remove the extra code, or switch off that tool’s purchase event. |
PixlBridge shows a reminder about this overlap next to its Purchase switch and in the store health notes. Whichever row fits, check the result: over a few days, the Purchase count in Events Manager should sit close to your number of Shopify orders, not near double.
How to test your Shopify Facebook Conversions API setup
A connected app isn’t proof that events arrive, so test right after setup. These checks happen in Meta Events Manager, on the pixel your store sends to.
- Open Test events. In Events Manager, select your pixel (or dataset) and open the Test events tab.
- Click through your store. Open it from Test events or in another tab, then view a product, search, add to cart and start checkout. Events from a browser pixel, such as the one Shopify’s app adds, show up as you go.
- Send a server test event. Server events only show in Test events when they carry the test code Meta displays there. In PixlBridge, use Send a test event with that code; it should appear within a minute. To see the store’s live server events here as well, save the code under My store → Advanced settings → Test & tools while you test, then remove it: while it’s set, every event from the store is tagged as a test.
- Check a real Purchase. This is the main server check for Shopify’s app too. Place a real order (a small one you refund is fine), then open Purchase in the Overview tab. Its connection methods should include Server, plus Browser if a browser pixel runs. A new purchase can take a few minutes to show.
- Check deduplication. When an event arrives from both the browser and the server, its details in the Overview show how many events Meta deduplicated, and the Diagnostics tab lists any problems Meta finds.
- Compare with your Shopify orders. Over a few days, compare Meta’s Purchase count and values with your orders for the same dates. Events Manager counts every Purchase it receives, from an ad or not, so compare it with your orders rather than with Ads Manager results, which follow attribution settings. Small gaps are normal; near double means two senders, and far fewer means events are going missing.
- Check Event Match Quality (EMQ), Meta’s 0–10 score for how well your events can be matched to people on Facebook and Instagram. Look at it for Purchase once some orders have come in.
Checks inside PixlBridge
PixlBridge shows the same picture from its side. On My store, the “Meta Pixel + Conversions API” panel says whether tracking is working, and Recent activity lists each event with “Sent to Meta (CAPI)” once Meta has it. The store health page adds event counts and the share of purchases carrying each match key, such as email or phone.
Common problems and how to fix them
Meta shows more purchases than you have orders
The usual cause is two tools sending the same order with different event IDs: old theme code plus an app, two tracking apps, or Shopify’s app at Enhanced or Maximum plus PixlBridge with Purchase on. Find the extra sender with the checklist in “Before you start”, then follow the table in the section on running both.
No server events, or events in the wrong pixel
With Shopify’s app, check that customer data sharing is on and set to Enhanced or Maximum, and that the right pixel is selected. With PixlBridge, check that Facebook & Instagram is connected with an ad account and pixel chosen, and that the event isn’t switched off. If your tool says it’s sending but Events Manager stays empty, compare the pixel it uses with the pixel your ad sets optimize for, then send a test event again.
Meta refuses the events
Meta can refuse server events when the connected Facebook account lacks permission, for example error #270 when the person who connected isn’t an admin of the ad account. The fix is to give that person admin access to the ad account in Meta Business Settings, or to have an ad account admin reconnect. PixlBridge explains this on its dashboard, holds the refused events and retries daily, but Meta only takes events up to 7 days old, so fix it soon.
Purchase values or currency don’t match Shopify
Open a Purchase in Events Manager and compare its value and currency with the order. Shopify’s app uses the order’s total price, which Shopify says includes duties, taxes and discounts, so it won’t match a net sales report. If you sell in several currencies, Ads Manager converts purchase values into your ad account’s currency, so totals won’t match Shopify to the cent. A large gap or a wrong currency can mean another tool is sending its own purchase.
Low Event Match Quality
A low EMQ means Meta can match fewer of your events to people. Check which customer details your events carry: with Shopify’s app, only Enhanced and Maximum share details such as email and phone; with PixlBridge, the store health page shows the share of purchases carrying each match key. Browsing events naturally score lower than purchases, because shoppers haven’t typed in any details yet. The Event Match Quality guide covers which details count most and how to raise the score.
Fewer events than store visits
Some gap is expected. Where your store asks visitors for consent, Shopify’s customer privacy settings decide when web pixels run, so visitors who decline aren’t tracked in the browser. That’s your consent setup working as intended, not something to work around.
Best practices once it’s running
- Re-test after changes. A new theme, a checkout change or a new tracking app can add a second sender or break the first.
- Check Events Manager regularly. A weekly look at connection methods, Diagnostics and EMQ for Purchase catches a problem before it runs for long.
- Set your privacy settings for where you sell. Shopify’s customer privacy settings control when web pixels run in shoppers’ browsers, so set them up for the consent rules that apply to your customers.
- Cover server-side sharing in your privacy policy. Purchases sent to Meta from a server need disclosing too: say that you share customer data with Meta for advertising and measurement.
- Judge ads on your Shopify numbers too. Meta’s attributed purchases and your orders measure different things, and ROAS only means something next to your margins.
Summary
You can set up the Facebook Conversions API on Shopify without code in two ways. Shopify’s Facebook & Instagram app turns it on when you choose Enhanced or Maximum data sharing, a free way to send purchases to Meta from a server. PixlBridge, a Conversions API app, sends the whole funnel server-side, with a switch for each event, delivery checks and ROAS next to your Shopify sales.
Whichever you pick, use the pixel your ads already use, let only one tool send purchases, and test in Events Manager: a test event first, then a real order arriving as a Purchase from the server, then a few days of Purchase counts that track your Shopify orders.
To try Method 2, install PixlBridge from the Shopify App Store. It’s free for 14 days with no card, and after that plans start at $29 a month.
Frequently asked questions
Is the Facebook Conversions API free on Shopify?
Meta doesn’t charge for the Conversions API, and Shopify’s Facebook & Instagram app is free to use on all Shopify plans, subject to store eligibility. Conversions API apps such as PixlBridge charge a monthly subscription for their extra features.
Do I need coding skills to set up the Conversions API on Shopify?
No. Shopify’s Facebook & Instagram app turns it on with a data sharing setting, and a Conversions API app such as PixlBridge installs from the Shopify App Store and connects with a Facebook login. Neither needs theme edits or a Meta developer app of your own.
Which Shopify data sharing level uses the Conversions API?
Enhanced and Maximum. Standard uses only the Meta Pixel in the shopper’s browser. Shopify says Maximum also keeps the connection up to date with Meta’s latest advertising technology.
Do I still need the Meta Pixel if I use the Conversions API?
Meta recommends running both: the pixel reports from the browser, the Conversions API from a server, and a shared event ID lets Meta keep one copy of each event. A server-only setup still works, and Meta can still use those events to optimize your ads.
Can I use Shopify’s Facebook & Instagram app and PixlBridge together?
Yes, as long as only one of them sends purchases. Switch off Purchase in PixlBridge, or lower the app’s data sharing to Standard so it stops sending purchases through the Conversions API, then check that each order reaches Meta once.
How do I know the Conversions API is working on my Shopify store?
In Meta Events Manager, open your pixel and check that events such as Purchase show Server as a connection method. Use the Test events tab to watch a test event arrive, then compare Meta’s Purchase count with your Shopify orders for the same days.
Why does Meta show more purchases than my Shopify orders?
If Events Manager receives clearly more purchases than you have orders, two tools are probably sending the same purchase with different event IDs, such as old theme code plus an app, or Shopify’s Facebook & Instagram app plus a Conversions API app. Ads Manager follows its own attribution settings, so its purchase count won’t match your orders exactly either way.
Does the Conversions API improve ROAS?
It can help Meta receive purchases that browser tracking misses, which gives its delivery system more complete data to learn from. It doesn’t guarantee a higher ROAS: results still depend on your creative, offer, pricing and audience.






