Analytics & Tracking

Meta Conversions API on Shopify: Setup, Deduplication and Match Quality

How to set up the Meta Conversions API on Shopify, stop pixel and server events from double counting, and raise Event Match Quality without breaking consent.

TL;DR
  • The Conversions API sends purchase and browsing events from a server to Meta, so ad blockers and browser limits don't erase them. On Shopify, the native Facebook & Instagram app can switch it on in a few minutes.
  • Running the pixel and the Conversions API together is the recommended setup, but only if each event carries the same event name and event ID. Without that, Meta counts some purchases twice.
  • Event Match Quality depends on the customer details you send with each event. More consented, correctly formatted identifiers mean more conversions matched to ads, and better optimization.

What does the Conversions API do that the Meta pixel can’t?

The Meta pixel runs in the shopper’s browser. Ad blockers, browser privacy features, slow pages or a closed tab can stop it from firing.

The Conversions API (CAPI) sends the same events from a server, either Shopify’s or your own server-side container. Because it doesn’t depend on the browser, it catches conversions the pixel misses. Two things follow:

  • Meta sees more of your real sales, so delivery has more conversion data to learn from.
  • Events carry richer customer information. Hashed email, phone and address from the order help Meta match the purchase to a person who saw an ad.

CAPI doesn’t replace the pixel. Meta recommends sending both and letting it deduplicate.

What are your setup options on Shopify?

Option How it works Good for Watch out for
Native Facebook & Instagram app, data sharing set to Maximum Shopify sends pixel and server events for you Most stores; fastest setup Less control over which parameters and custom events are sent
Server-side Google Tag Manager A server container forwards events to Meta Stores needing custom values such as profit Hosting cost, more setup and maintenance
Meta’s Conversions API Gateway A Meta-provided server setup in your cloud account Teams that want a managed Meta-only route Covers Meta only; still needs maintenance
Third-party tracking app An app sends events to several platforms Stores on many ad platforms Another vendor holding customer data; check consent handling

Use one route for server events and one for browser events. Most double counting on Shopify comes from two tools both sending purchases. If you need custom values, such as profit instead of revenue, a server-side container is usually the right route; see our guide to server-side tagging for Shopify.

How do you turn on the Conversions API with Shopify’s native app?

  1. Install or open the Facebook & Instagram app. In the Shopify admin, go to Sales channels and open Facebook & Instagram.
  2. Connect the right assets. Check that the Business portfolio, ad account and pixel (dataset) are the ones your ads use.
  3. Open the data sharing settings. In the app’s settings, turn on customer data sharing.
  4. Choose a level. Shopify offers Standard (pixel only), Enhanced (pixel plus Conversions API, sharing customer details such as name, email, phone and location) and Maximum (the same as Enhanced, kept up to date with Meta’s latest advertising technology). Maximum is the usual choice.
  5. Remove other Meta pixels. Delete any pixel code hard-coded in the theme, custom pixels in Customer events, and any Meta tag in Google Tag Manager that also sends purchases.
  6. Update your privacy policy. Shopify’s help pages note that you should tell customers how you share their data.

How does deduplication work, and why do purchases get counted twice?

When the same purchase arrives from browser and server, Meta needs to see they are one event. It has two methods.

Event ID and event name (recommended). The browser event’s eventID must match the server event’s event_id, and the event names must match exactly (for example, “Purchase” on both). Meta deduplicates events that arrive within 48 hours of the first event with that ID. When the two events don’t differ meaningfully, Meta generally keeps the one received first.

Browser ID or external ID (fallback). Meta can also match events using the event name plus the fbp cookie value or an external_id, if they are set the same way on both sides. Meta notes this generally works only when the browser event arrives first.

Common causes of duplicates:

  • A pixel hard-coded in an old theme still fires alongside the app.
  • A tracking app and the native app both send server purchases.
  • Server events use the order number as the event ID, while browser events use a random ID.
  • Event names differ in case or wording, such as “purchase” and “Purchase”.

Common causes of under-counting: no server route at all, a server route that sends purchases but not earlier funnel events (view content, add to cart, initiate checkout), or consent settings that block events more widely than required.

What is Event Match Quality and how do you raise it?

Event Match Quality (EMQ) is a score from 0 to 10 that Meta shows in Events Manager for each event type sent through the Conversions API. It estimates how well the customer information on those events matches Meta accounts. Better matching means more conversions credited to the right ads and better delivery signals.

The parameters that drive it:

Parameter Source on Shopify Notes
Email (em) Checkout, account, newsletter form Normalize to lowercase and hash with SHA-256
Phone (ph) Checkout Digits only with country code, then hash
First and last name, city, state, ZIP, country Shipping or billing address Normalize and hash
External ID Shopify customer ID Stable across sessions; hashing recommended
Click ID (fbc) The fbclid in the landing page URL Must be captured on landing and kept
Browser ID (fbp) The _fbp first-party cookie Lost if cookies are blocked
IP address and user agent The shopper’s browser request Must be the shopper’s, not your server’s

Purchase events usually score best, since orders contain email, phone and address; view content scores lower, since most visitors are anonymous. To raise it:

  • Send identifiers on every event where you have them. A logged-in customer or known subscriber can be identified on product views, not just on purchase.
  • Capture the click ID early. If a redirect drops fbclid before it is stored, fbc is lost for that visit.
  • Pass the shopper’s IP and user agent. A common server-side mistake sends the container’s own IP with every event.
  • Collect more first-party data. Email capture, accounts and post-purchase surveys add identifiers you can use with consent.

Server-side tracking does not exempt you from privacy rules. If a shopper opts out of the sale or sharing of personal data, your server events must respect that just like the pixel. – Connect your consent management platform to Shopify’s customer privacy settings so both browser and server events read the same choice.
– Check how your setup handles shoppers in states with opt-out rights and in other countries if you sell abroad.
– Don’t send sensitive categories of data. Health-related products need extra care in what event names and product details reveal.

Rules vary by state and change often, so confirm your setup with counsel.

How do you check that your setup is working?

  1. Test events. In Meta Events Manager, use the test events tool while placing a test order. The purchase should arrive from browser and server, marked as deduplicated.
  2. Compare counts with Shopify. Over a full week, compare online store orders with Meta’s purchase events. They should be close.
  3. Check diagnostics. Events Manager flags missing parameters and deduplication problems.
  4. Check EMQ per event. Purchase, add to cart and view content separately.
  5. Recheck after changes. New themes, checkout apps and consent banners often break tracking quietly.

Worked example: reading a tracking audit

The numbers below are illustrative.

A store records 1,000 online orders in a week in Shopify. Meta Events Manager shows 1,380 purchase events received.

  • Step 1: spot the gap. 380 extra purchases point to double counting.
  • Step 2: find the sources. Events Manager shows purchases arriving from the browser, the server and a second browser integration. An old pixel snippet in the theme’s layout file is still firing alongside the app.
  • Step 3: fix and compare. After removing the snippet, the next week shows 1,000 Shopify orders and 960 Meta purchases. A small shortfall is normal, since some shoppers block tracking or decline consent.
  • Step 4: check the impact. Meta’s reported ROAS falls, because it was counting phantom sales, while store revenue is unchanged. Targets set on the inflated numbers need resetting.

A gap the other way, say 1,000 orders and 650 Meta purchases, usually means the server route is missing or broken. For Shopify and GA4 gaps, see our guide to the GA4 and Shopify revenue discrepancy.

Checklist: Conversions API on Shopify

  • [ ] One route sends browser events and one route sends server events, with no extra pixels in the theme, Customer events or GTM.
  • [ ] Data sharing is set to Maximum (or Enhanced) in the Facebook & Instagram app, connected to the correct pixel.
  • [ ] Browser and server events share the same event name and event ID.
  • [ ] View content, add to cart, initiate checkout and purchase are all sent from the server.
  • [ ] Email, phone, name, address and external ID are normalized and hashed before sending.
  • [ ] The fbc click ID and fbp cookie are captured and passed on.
  • [ ] The shopper’s IP and user agent are sent, not the server’s.
  • [ ] Consent choices apply to server events as well as the pixel.
  • [ ] Weekly Meta purchase counts are compared with Shopify orders.
  • [ ] Tracking is retested after every theme, checkout or consent change.

FAQ

Do I still need the Meta pixel if I use the Conversions API?

Yes, in most setups. Meta recommends sending both. The browser event carries cookies and click information the server may lack, and the server event covers what the browser misses. Deduplication with a shared event ID keeps the purchase from being counted twice.

What is a good Event Match Quality score?

Higher is better, and purchase events should score higher than early-funnel events because they include order details. Rather than chasing a fixed number, check which identifiers Events Manager says are missing and add the ones you can send with consent.

Why does Meta report more purchases than Shopify?

Usually because the same purchase arrives from two sources without a matching event ID, or because two tools both send purchases. Remove the extra source, confirm matching event IDs and compare weekly counts again.

Turn this into a plan for your store

The Free Profit Audit scans your store, sizes your biggest profit leaks and builds a 90-day plan.

Free Profit Audit