All posts

Tracking Meta Ads Shopify Conversions API

Meta Conversions API for Shopify Stores: What It Fixes and How to Turn It On

August 23, 2026 Agency AI Team 9 min read

META TITLE: Meta Conversions API for Shopify Stores: Setup Guide

META DESCRIPTION: Meta Conversions API on Shopify: what it fixes, how to turn it on, how event deduplication works, and the three things it does not fix.

SLUG: meta-conversions-api

TAGS: Meta Conversions API, CAPI, Meta Pixel, Shopify data sharing, server side tracking, event deduplication

*Hero image to be added. Alt text: Shopify admin data sharing settings screen showing Standard, Enhanced and Maximum levels*

The Meta Conversions API sends your store's event data to Meta from a server instead of a browser. Meta calls it a connection between an advertiser's marketing data and Meta's systems.

On Shopify you turn it on by raising your Meta data sharing level to Enhanced or Maximum. It runs alongside the Meta Pixel. It does not replace it.

What Is Conversions API in Plain Terms?

Meta's developer documentation defines it as a server-to-server connection. The data can come from an advertiser's server, website platform, mobile app or CRM.

Shopify's blog is plainer. It calls a conversion API a direct integration to an ad platform like Facebook, TikTok or Google Ads. The method, in Shopify's words, is "a server-to-server connection".

Merchants search for this under several names. You will see meta capi, facebook conversions api and conversions api facebook. All three point at the same product.

The destination does not change. Meta states that server events "are linked to a dataset ID and are processed like events sent using the Meta Pixel".

This is server side tracking. The event leaves your server, not the shopper's browser.

Conversions API vs Meta Pixel: What Is the Difference?

The Pixel is browser-side JavaScript. The Conversions API is a server-to-server call.

Meta does not frame this as a choice. Its best practices page says to "Use the Conversions API in addition to the Meta Pixel, and share the same events using both tools."

The get-started page is blunter. It says "You must obtain a Pixel ID to use the Conversions API." Meta also tells advertisers to reuse the same Pixel ID for browser and server events.

Why the Meta Pixel Under-Reports Conversions on Its Own

Meta names a mechanism, not a percentage. Its docs say the Conversions API shares events "that the Pixel may lose due to network connectivity issues or page loading errors".

Shopify adds the ad blocker angle. At the Standard level a store uses only the Meta pixel. Shopify states that "A browser-based ad blocker can prevent the Meta pixel from sharing data."

Backlinko, citing GWI data for Q2 2025, reports that "29.5% of internet users use ad blockers at least sometimes when online". The same page puts the figure for Americans at 32.5%.

Browsers erode the other side. Apple's WebKit team announced full third-party cookie blocking in Safari on March 24, 2020. Its wording: "Cookies for cross-site resources are now blocked by default across the board."

Safari also deletes a site's script-writable storage after seven days of Safari use without interaction.

Neither of those sources is Meta or Shopify.

We will not give you a percentage of lost purchases. No source we opened publishes one.

Under-reporting and over-attribution are different problems. The Pixel under-captures events, while platform attribution over-claims credit for the events it does capture. Our marketing efficiency ratio explainer covers the blended metric that survives attribution gaps.

How to Set Up the Conversions API on Shopify

Shopify offers three Meta data sharing levels: Standard, Enhanced and Maximum. Only Enhanced and Maximum switch on the Conversions API alongside the pixel.

Shopify's path, in its own words: "From your Shopify admin, go to Sales channels > Facebook & Instagram. Click Settings. Click Data sharing settings."

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 behaviour, blockable by browser ad blockers
Enhanced	Pixel plus Conversions API	Customer name, location, email, phone, browsing behaviour
Maximum	Pixel plus Conversions API, updated with Facebook’s latest advertising technology	Same as Enhanced

Know what you are switching on. At Enhanced and Maximum, Shopify shares "your customer's name, location, email address, and phone number, as well as their browsing behavior in your online store".

Shopify says the Conversions API "sends the purchase event between Shopify and Facebook servers". It adds that "Data sent from server to server can't be blocked by browser-based ad blockers."

Read that scope narrowly. Shopify names the purchase event, not every event.

Shopify's Meta pixel automatically tracks seven events. They are PageView, ViewContent, Search, AddToCart, InitiateCheckout, AddPaymentInfo and Purchase.

For most stores that is the whole facebook conversions API shopify setup. Shopify itself points merchants to "partner integration for setting up the Facebook conversions API" rather than custom code.

Two Other Ways to Set Up the Meta Conversions API

Meta announced a one-click Conversions API setup on April 15, 2026. Meta calls it "a one-click option that requires no technical expertise, no costs, no ongoing maintenance".

Meta also says the update lets businesses "use AI to automatically include additional page and product information". That covers product names and availability in the events they share. It is a vendor claim.

The second route is the Conversions API Gateway in Events Manager. Meta says "No coding is necessary" and that it cuts integration time "from weeks to hours or even minutes".

The Gateway is not free in practice. Meta states its "only cost... is the associated cloud resource or partner fees". It runs on AWS EKS, AWS ECS Express or GCP.

How Conversions API Event Deduplication Works

Sending the same purchase from browser and server would double count it. Meta's answer is deduplication.

Meta's recommended setup is to "Send all events via both Pixel and Conversions API." Deduplication then depends on matching keys.

The core rule: "a Meta Pixel's `eventID` must match the Conversion API's `event_id`". The event_name must match as well.

Meta's best practices page allows one alternative. Use an identical event_name plus "either `event_id` or a combination of `external_id` and `fbp`".

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, "we generally prefer the event that is received first".
On the fbp route, "Server events will not be discarded if a browser event has not been received in the past 48 hours". Meta adds that this holds "even if an identical browser event arrives after the server event."
On that same fbp route, Meta "Does not deduplicate events when only using one event source, that is browser-only or server-only."

Your event_id can be anything unique. Meta says "This ID can be any unique string chosen by the advertiser." An order number works.

Conversions API Event Timing Rules and Limits

Late events cost you performance. Meta publishes the thresholds.

Real time, or within 1 hour, "helps ensure that they can be used for attribution and optimized for ad delivery".
More than 2 hours late "can cause a significant decrease in performance for ads optimized for those events".
A delay of 24 hours or more "may experience 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. Meta says to 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.

One field is easy to miss. The event_source_url is "required for website events shared using the Conversions API".

How to Check If Your Conversions API Is Working

Ignore generic uplift stats and read your own dataset. Meta publishes three metrics for exactly this.

Event Match Quality is a score out of 10. Meta says it shows how effective your server-sent customer information "may be at matching event instances to a Meta account". Meta publishes no pass mark. Any blog handing you a target score invented it.

Event Coverage is "the 7-day average percentage of Meta Pixel events that are covered by the Conversions API". Meta names one threshold here. Below 75% coverage, it tells advertisers to "monitor the uplift in additional conversions" from covering more events.

Additional Conversions Reported estimates "how many conversions... are measured as a result of an advertiser's Conversions API setup". Trust that number over any vendor average.

To raise match quality, send more customer fields. Meta hedges the promise: "Sending additional customer information parameters may help increase Event Match Quality."

At least one user_data parameter is required on every request. Email, phone, name, city, state, zip and country must be SHA-256 hashed first. IP address, user agent, FBC and FBP are not hashed.

What the Meta Conversions API Does Not Fix

Meta's headline number is a vendor claim about its own product. Meta says advertisers with a Conversions API setup for web events "saw an average 17.8% lower cost per result compared to those without Conversions API."

Meta publishes no sample size and no methodology for that figure. Treat it as marketing, then measure your own account.

Three limits are worth stating plainly.

It does not bypass consent. Meta is explicit. "If you have logic for controlling consent with respect to sharing Pixel data, use the same logic with respect to sharing data via Conversions API." An opt-out still applies on the server side.

It does not remove your privacy obligations. Shopify frames data sharing as the merchant's choice. Its wording: "not everyone wants their data shared." Shopify tells merchants to keep the store privacy policy up to date.

It does not fix weak unit economics. Cleaner event data improves the inputs Meta optimizes against. It does not change your margin, creative or landing page. Run the numbers with our CAC calculator before blaming tracking.

Our guide to Meta Advantage Plus covers what Meta automates once events are clean.

How Agency AI Uses Your Meta Conversions API Data

Agency AI does not set up or manage your Conversions API. Its Shopify App Store listing describes Meta and Google Ads management, and we found no Agency AI documentation covering tracking setup.

What it does is read the Meta and Google account data that a healthy setup feeds.

Agency AI's own knowledge base is explicit about the limits. It states that "Agency AI does not push optimization changes into Meta on your behalf." It adds that "Every optimization change requires you to act first."

Google works differently. There a recommendation carries an Apply button, and Agency AI "makes the change directly in your Google Ads account." Agency AI "analyzes the last 7 days of your account data" to generate recommendations.

Pricing, verified on the Shopify App Store on August 25, 2026: $59 per month or $492 per year, with a 30-day free trial. The listing shows a 5.0 rating from 5 reviews and a launch date of October 27, 2025.

Frequently Asked Questions

What is the Meta Conversions API?

It is a server-to-server connection that sends marketing data to Meta. Meta's documentation covers website events, app events, messaging events and offline conversions. On Shopify it mainly carries the purchase event.

Does the Conversions API replace the Meta Pixel?

No. Meta's get-started page says "You must obtain a Pixel ID to use the Conversions API." Meta recommends running both and sending the same events through each.

How do I turn on the Conversions API on Shopify?

Go to Sales channels, then Facebook & Instagram, then Settings, then Data sharing settings. Choose Enhanced or Maximum. Standard runs the pixel alone.

Will sending events twice double count my purchases?

Not if the keys match. Meta deduplicates when event_name and event_id both match, within 48 hours of the first event.

Does the Conversions API get around ad blockers?

Only partly. Shopify says server-to-server data "can't be blocked by browser-based ad blockers", and its Conversions API sends the purchase event.

Is the Meta Conversions API free?

On Shopify it is part of the sales channel data sharing settings. The Conversions API Gateway is different. Meta says its only cost is "the associated cloud resource or partner fees", which you pay.

Sources

Every quotation was taken from primary documentation. Meta's developer documentation at developers.facebook.com supplied most of this article. That covers the Conversions API definition, dataset ID behaviour, best practices and deduplication rules. It also covers event timing thresholds, batch limits, parameter requirements and the three dataset quality metrics. All pages read on August 25, 2026. The 17.8% lower cost per result figure and the April 15, 2026 one-click setup announcement come from Meta's own business news page. Both are vendor claims about Meta's product, published without a sample size or methodology. The Conversions API Gateway details, including its cost model and cloud options, come from Meta's developer documentation. Shopify's Help Center supplied the three data sharing levels, the admin path, the seven tracked pixel events, ad blocker wording and privacy policy guidance. The plain-English conversion API definition comes from Shopify's blog. Both Meta and Shopify statements are vendor claims about their own products. Two sources are independent of Meta and Shopify. Apple's WebKit engineering blog covers full third-party cookie blocking, announced March 24, 2020, and the seven-day storage deletion rule. Backlinko, citing GWI data for Q2 2025, supplies the 29.5% worldwide and 32.5% United States ad blocker figures. Agency AI product statements come from its own public knowledge base at support.agencyai.app. The pricing, rating and launch date were verified live on the Shopify App Store listing on August 25, 2026.

INTERNAL LINKS: marketing efficiency ratio -> what-is-mer; Facebook and Instagram Shopify setup guide -> 2026-01-01-facebook-instagram-shopify-setup; CAC calculator -> cac-calculator; Meta Advantage Plus -> meta-advantage-plus

Free to install. Launch campaigns and pay nothing for your first 30 days.