Meta Conversions API for Shopify Stores: What It Fixes and How to Turn It On
The Meta Conversions API sends your store's event data to Meta from a server instead of the shopper's browser.
On Shopify you turn it on by raising your Meta data sharing level to Enhanced or Maximum. It runs alongside the Meta Pixel and does not replace it.
What Is Conversions API in Plain Terms?
It is a server-to-server connection to Meta, which makes it a form of server side tracking. The data can come from your server, website platform, mobile app or CRM.
Other ad platforms, such as TikTok and Google Ads, offer the same kind of direct integration. You may also see Meta's version called Meta CAPI or the Facebook Conversions API.
Server events end up in the same place as browser events. Meta links them to a dataset ID and processes them just like events sent by the Meta Pixel.
Conversions API vs Meta Pixel: What Is the Difference?
The Pixel is JavaScript that runs in the shopper's browser. The Conversions API is a call from your server to Meta's server.
You do not have to choose between them. Meta's best practice is to use the Conversions API in addition to the Meta Pixel and send the same events through both.
You need a Pixel ID before you can use the Conversions API at all. Meta also asks you to reuse that same Pixel ID for browser and server events.
Why the Meta Pixel Under-Reports Conversions on Its Own
Browser events get lost for ordinary reasons. Network connectivity issues and page loading errors can stop the Pixel from sending an event. The Conversions API can share those events instead.
Ad blockers cause the next gap. At Shopify's Standard level, your store uses only the Meta pixel, and a browser ad blocker can stop it from sharing data.
Worldwide, 29.5% of internet users use ad blockers at least some of the time. Among Americans, the figure is 32.5%. Both numbers come from GWI data for Q2 2025, reported by Backlinko.
Safari limits tracking on its own. Apple's WebKit team announced full third-party cookie blocking in Safari on March 24, 2020. Safari also deletes a site's script-writable storage after seven days of Safari use without interaction with that site.
We know of no reliable figure for how many purchases the Pixel misses on its own. The dataset checks covered below show how your own setup performs.
Under-reporting and over-attribution are different problems. The Pixel misses some events, while platform attribution claims too much credit for the events it does catch. Our marketing efficiency ratio explainer covers a blended metric that holds up despite attribution gaps.
How to Set Up the Conversions API on Shopify
Shopify has three Meta data sharing levels: Standard, Enhanced and Maximum. Only Enhanced and Maximum turn on the Conversions API alongside the pixel. To change your level:
- From your Shopify admin, go to Sales channels > Facebook & Instagram.
- Click Settings.
- Click Data sharing settings.
- Choose Enhanced or Maximum.
If the Facebook & Instagram channel is not connected yet, start with our Facebook and Instagram Shopify setup guide.
| Level | What Runs | What Shopify Shares |
|---|---|---|
| Standard | Meta pixel only | Browsing behavior, blockable by browser ad blockers |
| Enhanced | Pixel plus Conversions API | Customer name, location, email, phone, browsing behavior |
| Maximum | Pixel plus Conversions API, updated with Meta's latest advertising technology | Same as Enhanced |
Enhanced and Maximum share the same data: your customers' names, locations, email addresses and phone numbers, plus their browsing behavior in your store.
Shopify's Conversions API sends the purchase event from Shopify's servers to Meta's. Browser ad blockers cannot block data sent from server to server. This covers only the purchase event, so your other events may still be blocked.
Shopify's Meta pixel tracks seven events automatically:
- PageView
- ViewContent
- Search
- AddToCart
- InitiateCheckout
- AddPaymentInfo
- Purchase
For most stores, choosing Enhanced or Maximum is the whole Conversions API setup on Shopify. Shopify points merchants to a partner integration for this, rather than custom code.
Two Other Ways to Set Up the Meta Conversions API
On April 15, 2026, Meta announced a one-click Conversions API setup. It needs no technical expertise, no costs and no ongoing maintenance.
The update can also use AI to add page and product details, such as product names and availability, to your events.
The second route is the Conversions API Gateway in Events Manager. It needs no coding, and Meta says it cuts integration time from weeks to hours or even minutes.
The Gateway is not free in practice. Its only cost is the cloud resources it runs on, or a partner's fees, which you pay. It runs on AWS EKS, AWS ECS Express or GCP.
How Conversions API Event Deduplication Works
If the same purchase arrives from both the browser and the server, it could be counted twice. Meta prevents that with deduplication.
Because each event goes through both tools, deduplication depends on matching keys. The main rule is that the Pixel's eventID must match the Conversions API's event_id. The event_name must match as well.
The alternative is to keep the same event_name and match on a combination of external_id and fbp instead of event_id.
Four details decide whether it works:
- The window is 48 hours from when Meta receives the first event carrying that event_id.
- When Meta finds duplicates, it generally keeps the event it received first.
- On the fbp route, server events are not discarded if no browser event arrived in the past 48 hours. This holds even if an identical browser event arrives after the server event.
- On that same fbp route, Meta does not deduplicate events when you use only one event source, browser-only or server-only.
Your event_id can be any unique string you choose. An order number works.
Conversions API Event Timing Rules and Limits
Late events cost you performance. These are Meta's timing rules:
- Sending events in real time, or within 1 hour, helps make sure they can be used for attribution and optimized ad delivery.
- Events sent more than 2 hours late can cause a significant drop in performance for ads optimized for them.
- A delay of 24 hours or more may cause significant issues with attribution and optimized ad delivery.
- The event_time can be at most 7 days before you send it.
- If any event_time is older than 7 days, Meta returns an error for the entire request.
- Offline and physical store transactions get longer. Upload them within 62 days.
Two batch rules save debugging time. One batch can carry up to 1,000 events. If any single event is invalid, Meta rejects the whole batch.
Also include event_source_url. It is required for website events sent through the Conversions API, and it is easy to miss.
How to Check If Your Conversions API Is Working
Skip generic uplift stats and look at your own dataset. Three Meta metrics show how well your setup works.
Event Match Quality is a score out of 10. It estimates how well the customer details on your server events can match those events to a Meta account. Meta sets no target score, so track whether yours rises as you send more customer details.
Event Coverage is the 7-day average share of your Meta Pixel events that the Conversions API also covers. Below 75% coverage, Meta suggests watching the uplift in additional conversions as you cover more events.
Additional Conversions Reported estimates how many conversions are measured because of your Conversions API setup.
Sending more customer information parameters may help raise Event Match Quality. Every request needs at least one user_data parameter.
Hash email, phone, name, city, state, zip and country with SHA-256 before you send them. IP address, user agent, FBC and FBP are sent without hashing.
What the Meta Conversions API Does Not Fix
Meta reports that advertisers with a Conversions API setup for web events saw an average 17.8% lower cost per result than those without it. The figure comes with no published sample size or method, so measure the change in your own account.
A clean setup still has three limits.
It does not bypass consent. If you control consent for Pixel data, use the same logic for data sent through the Conversions API. A shopper's opt-out still applies on the server side.
It does not remove your privacy obligations. Data sharing is your choice as the merchant, and not everyone wants their data shared. Keep your store's privacy policy up to date.
It does not fix weak unit economics. Cleaner event data gives Meta better inputs to optimize against, but your margin, creative and landing page stay the same. Run the numbers with our CAC calculator before blaming tracking.
Once your events are clean, our guide to Meta Advantage Plus covers what Meta automates next.
How Agency AI Uses Your Meta Conversions API Data
We do not set up or manage your Conversions API. You switch it on in Shopify, as shown above. We build and run your Meta and Google ad campaigns.
Our recommendations are based on the last 7 days of your account data. We read the Meta account data that a healthy setup feeds, so a working Conversions API gives our recommendations more complete purchase numbers.
We push optimization changes into Meta on your behalf, but only the ones you approve. Google follows the same rule. Each recommendation there has an Apply button, and clicking it makes the change directly in your Google Ads account.
Agency AI costs $59 per month or $492 per year on the Shopify App Store, with a 30-day free trial. The listing shows a 5.0 star rating and a launch date of October 27, 2025.
Frequently Asked Questions
Sources
Meta's developer documentation covers the Conversions API definition, dataset ID behavior, best practices and deduplication rules. It also covers event timing, batch limits, parameter requirements, the three dataset quality metrics and the Conversions API Gateway. The 17.8% figure and the April 15, 2026 one-click setup come from Meta's business news page.
Shopify's Help Center covers the three data sharing levels, the admin path, the seven tracked pixel events, ad blockers and privacy policy guidance. The note that TikTok and Google Ads offer the same kind of integration comes from Shopify's blog.
Apple's WebKit blog covers Safari's third-party cookie blocking, announced March 24, 2020, and the seven-day storage rule. Backlinko, citing GWI data for Q2 2025, supplies the 29.5% worldwide and 32.5% United States ad blocker figures.
Agency AI product details come from our knowledge base at support.agencyai.app. Pricing, rating and launch date come from our Shopify App Store listing.
Free to install. Launch campaigns and pay nothing for your first 30 days.
