How to Set Up and Verify the Meta Conversions API on Shopify

Last updated: 2 November 2026

The Meta Conversions API (CAPI) sends purchases and other events from Shopify’s servers straight to Meta, alongside the Meta pixel in the browser. On Shopify, you switch it on in the Facebook & Instagram sales channel with the Enhanced or Maximum data-sharing level. Then record a test order’s browser traffic from checkout and check event ID and value. Without access to the server event, the ID match stays unproven; deduplication data is only a plausibility check.

Key takeaways

What the Meta Conversions API does

The Conversions API sends events such as Purchase from server to server. Meta recommends it alongside the pixel.

Meta pixel Conversions API
Runs in the visitor’s browser between Shopify’s and Meta’s servers
Can lose events through ad blockers, connection problems, page errors configuration mistakes
Active on Shopify from level Standard Enhanced or Maximum

Meta uses purchase events to decide who sees your ads. Missing or duplicated purchases mean bad signals and a drifting ROAS.

What you need before you start

Setting up the Conversions API on Shopify

Step 1: Connect the Facebook & Instagram sales channel

The official integration, “Facebook and Instagram by Meta”, is a sales channel, not an app. Start the setup, connect your Facebook account, business portfolio and Facebook page, accept the terms and finish. Then connect your pixel in the data sharing settings.

Step 2: Set data sharing to Enhanced or Maximum

Go to Sales channels > Facebook & Instagram > Settings > Data sharing settings and open the Customer data sharing section.

Level What Shopify sends
Standard Meta pixel in the browser only
Enhanced Meta pixel plus Conversions API; shares customer details such as name, location, email and phone number
Maximum as Enhanced, plus what Shopify calls Facebook’s latest advertising technology

Per Shopify, privacy settings differ by installation date; check the description in your admin.

Step 3: Remove duplicate pixel sources

Once the channel runs, remove any other Meta pixel code for the same events; Shopify warns it can cause duplicate or incorrect data. Look in:

Step 4: Check for old thank-you page scripts

Many stores used to fire the purchase event from a thank-you page script via Additional scripts or checkout.liquid. Shopify has switched this off on the Thank you and Order status pages: for Plus stores from 28 August 2025, for all others the deadline was 26 August 2026. If you relied on such a script, check that the channel or a pixel under Customer events now captures purchases.

Step 5: Check consent

In markets that require consent, including the EEA, Shopify runs web pixels only once visitors grant permission. Shopify doesn’t say explicitly how the Meta channel handles server events without consent, so agree banner settings and privacy policy with your privacy advisor.

How to check that the Conversions API works

Meta shows three different numbers, and none automatically equals your Shopify order count:

Number Where What it counts
Events received Events Manager, Overview every event before deduplication, consent filtering and processing, so browser and server events of one purchase count separately
Deduplication Event Details, Event Deduplication tab the share of events Meta merged as the same purchase
Attributed purchases Ads Manager only purchases Meta credits to your ads, per attribution setting

Preparation: network recording

Before completing the test order, open Chrome DevTools, Network tab, keep recording on and enable “Preserve log”. DevTools only records while open, and “Preserve log” keeps requests across page loads.

Check 1: Test order and connection method

Place a real test order, for example of a cheap product you refund later, and note order number, time and amount. After about 20 minutes, open your pixel’s Overview in Events Manager. Connection Method shows per event type, not per order, how events arrived; for Purchase you should see browser and server.

The free Meta Ads Data Advisor extension for Chrome and Edge (formerly Meta Pixel Helper) shows which pixel events fire on a page.

Check 2: Event ID and deduplication

When pixel and Conversions API send the same purchase, Meta merges them if event name and event ID match, both go to the same pixel ID and arrive within 48 hours. Verify this on your test order:

  1. Browser: filter the recording for “facebook.com/tr” and open the Purchase request. Note pixel ID (“id”), event ID (“eid”), value and currency. Reloading the thank-you page is no substitute.
  2. Server: compare the noted event ID with this order’s server “event_id”, plus event name “Purchase” and pixel ID. With your own server setup, check your server log or use the Test Events tool with a temporary test code. Shopify describes no such access for its native channel; without it, this order’s ID match remains unverified.
  3. Plausibility: open Event Details for Purchase, Event Deduplication tab. Meta shows the share of events deduplicated per source and warns when it is too low, how often each source sends a key such as the event ID, and the “Overlap”. Low overlap, says Meta, means the IDs aren’t unique or only one source sends them. These aggregates don’t prove your test order.

Check 3: Compare volumes only with a defined counting method

For example, compare Shopify orders in the Online Store channel, excluding POS and test orders, against Purchase events received in the Events Manager overview, same date range and time zone. A higher Meta number alone is no error, since the overview counts browser and server events separately. Meaningful signals:

Ads Manager purchases don’t fit this comparison; they only include attributed purchases.

Check 4: Value and currency

Meta requires a value and currency for Purchase events. Shopify sends the total price including duties, taxes and discounts, and your ad account ROAS is based on it. If you measure profitability on net revenue, adjust for this when setting your break-even ROAS.

Check 5: Event Match Quality

Event Match Quality is Meta’s 1 to 10 score for how well server events match Meta accounts. It uses customer information such as email and phone number, hashed with SHA-256 before sending, plus browser identifiers like fbp and fbc. Hashed does not mean anonymous: Meta matches exactly these hashes against its account data. A low score is a reason to review data sharing and checkout.

Common problems

Symptom Likely cause What to check
Overview shows more Purchase events than orders often normal: counted before deduplication Event Deduplication, not the raw number
Warning or low overlap under Event Deduplication event ID missing in one source or not matching “eid” vs. server “event_id”, where accessible
Purchase fires twice or with two pixel IDs pixel code in a second place Data Advisor, Customer events, theme code, apps
Purchase arrives only via browser data sharing set to Standard data sharing settings in the channel
No Purchase request in Network tab late recording or no consent retest: “Preserve log” on, consent given
Far fewer Purchase events than orders blocked events, missing consent, old thank-you script connection method, consent banner, Customer events
Purchase values don’t match taxes, discounts or currency handled differently compare a test order in both systems
Many “conversions”, little revenue campaign optimizes for a soft event like Add to cart ad set performance goal

Shopify channel, server-side tagging or a tracking app?

Option Strengths Watch out for
Facebook & Instagram channel Meta’s official channel, built into Shopify, no own server less control over individual parameters
Server-side tagging (e.g. GTM server container) full control, several platforms from one source hosting costs, technical skills, ongoing maintenance
Tracking app several channels bundled, no code ongoing fees, risk of duplicates next to the channel

Our advice: start with the Shopify channel, switch only for a concrete reason, and keep a single setup sending Meta events via browser and server.

Free tracking check

Not sure about your setup? Send your store link via our contact form with the keyword “Tracking Check”. We check from the outside which Meta events fire in the browser and whether pixel code runs twice, and send you a short free assessment. At EXRE we run ads on Meta, TikTok and Google and build the Shopify stores and landing pages those clicks land on.

FAQ

Do I need the Conversions API if my Meta pixel already works?

Yes. Meta recommends sending the same events through pixel and Conversions API, because the pixel can lose events to ad blockers, connection problems or page errors.

Which data-sharing level should I choose on Shopify?

Standard uses only the pixel. Enhanced adds the Conversions API and shares customer data such as email and phone number for matching. Maximum adds what Shopify calls Facebook’s latest advertising technology. For reliable measurement, choose Enhanced or Maximum and align consent with your privacy advisor.

Why does Meta show more purchases than I have Shopify orders?

The Events Manager overview counts events before deduplication and consent filtering, so a purchase reported by browser and server appears twice, which is fine. Real signs of double counting are a warning or low overlap under Event Deduplication and pixels firing twice in Meta Ads Data Advisor.

How do I check that deduplication works?

Start recording before a test order, with “Preserve log” on, and note the Purchase request’s event ID (“eid”). Meta merges pixel and server events if event name, event ID and pixel ID match and both arrive within 48 hours. Only your order’s server event can confirm the match; Shopify describes no access to it for the native channel, where Event Deduplication is only a plausibility check.

Does old pixel code on the Shopify thank-you page still work?

No. Shopify has switched off Additional scripts and checkout.liquid on the Thank you and Order status pages, for Plus stores from 28 August 2025, for all others with a deadline of 26 August 2026. Capture purchases through the channel or a pixel under Customer events.

Sources

Read on 25 October 2026; the passages on the Events Manager overview, deduplication, event ID and hashing, and Shopify’s English labels re-checked on 29 October 2026; event ID matching, Test Events, pixel parameters, Shopify data sharing and Chrome network recording on 2 November 2026.

Leave a Reply

Your email address will not be published. Required fields are marked *