YourTracking

Meta Conversions API on Shopify

The Conversions API sends your store’s events to Meta from a server, so a blocked browser does not stop them. What it does, the Shopify setting that turns it on, how Meta keeps a sale from counting twice, and what Event Match Quality tells you.

YourTrackingChecked on 3 min read

What the Conversions API is

The Meta pixel reports from the shopper’s browser. The Conversions API reports from a server: Meta describes it as a direct connection between your marketing data and the systems that optimize your ad targeting and measure results [1]. Server events belong to a dataset and are used for measurement, reporting and optimization in a similar way to pixel events [2].

Meta recommends using both, with the same events sent through the pixel and the Conversions API. It calls this a redundant setup, and says the Conversions API can share events “that the Pixel may lose due to network connectivity issues or page loading errors” [3].

The Shopify setting: data sharing

Shopify’s Facebook & Instagram app has three data-sharing levels [4]:

LevelWhat it usesAd blockers
StandardThe Meta pixel only, from customer browsing.“A browser-based ad blocker can prevent the Meta pixel from sharing data.”
EnhancedThe Meta pixel and the Conversions API. The purchase goes from Shopify’s servers to Meta’s, with the customer’s name, location, email address and phone number for matching.“Data sent from server to server can’t be blocked by browser-based ad blockers.”
MaximumAs Enhanced, and “updated with Facebook’s latest advertising technology”.As Enhanced.

To set it, open your Shopify admin, then Sales channels, Facebook & Instagram, Settings, Data sharing settings. Switch on customer data sharing, choose the level and connect your pixel [4].

Two details from the same page: the pixel tracks PageView, ViewContent, Search, AddToCart, InitiateCheckout, AddPaymentInfo and Purchase, and an event’s value is the order’s total price, “including duties, taxes, and discounts” [4].

How Meta keeps a sale from counting twice

With the pixel and the Conversions API both sending, Meta has to recognize the two copies of one purchase. It merges a browser copy and a server copy when [5]:

  • the pixel’s eventID matches the Conversions API’s event_id, and the event names match;
  • both arrive within 48 hours of the first copy.

Of its second method, which matches on the browser ID or your own customer ID, Meta says it “does not deduplicate events when only using one event source, that is browser-only or server-only” [5]. So two tools that both send your purchases from a server can count a sale twice. Send each event from one place.

The same goes for two pixels. Shopify’s advice: remove Meta pixel code you once added to your theme, or “your store will have more than one pixel on it, which can result in duplicate or incorrect data in your reports” [6].

Event Match Quality

For website events sent through the Conversions API, Events Manager shows an Event Match Quality score from 0 to 10. Meta works it out from the customer details sent with the event and the share of events matched to Meta accounts, over the last 48 hours [7]. Meta ranks the details like this [7]:

PriorityCustomer details
HighEmail address, click ID
MediumPhone number, external ID, browser ID, date of birth, country, Facebook Login ID
LowFirst name, surname, town or city, postcode, lead

Contact details must be hashed: Meta’s systems “are designed to not accept customer information that is unhashed Contact Information” [8]. Only matched events are used for attribution and ad delivery; the rest still count in basic measurement [3].

Check it in Events Manager

  • Events received. Events Manager shows most events it receives, while Ads Manager shows the ones attributed to your ads, so Ads Manager reads lower [9].
  • Match quality. Events Manager shows each event’s score and Meta’s suggestions to raise it [7].
  • Test events. For a developer, the Test events tab in Events Manager shows whether a server event arrived and was formed correctly [10], and which copies were removed as duplicates [3].

Sources

Each source is the platform’s own page, read on 20 October 2026. Links open in a new tab.

  1. 1Meta Business Help CentreAbout Conversions APIRead on 20 October 2026.
  2. 2Meta for DevelopersConversions APIRead on 20 October 2026; the page says it was updated 28 September 2026.
  3. 3Meta for DevelopersBest Practices, Conversions APIRead on 20 October 2026; the page says it was updated 28 June 2026.
  4. 4Shopify Help CenterFacebook data sharingRead on 20 October 2026.
  5. 5Meta for DevelopersHandling Duplicate Pixel and Conversions API EventsRead on 20 October 2026; the page says it was updated 28 June 2026.
  6. 6Shopify Help CenterMeta pixelRead on 20 October 2026.
  7. 7Meta Business Help CentreAbout event match qualityRead on 20 October 2026.
  8. 8Meta for DevelopersCustomer Information ParametersRead on 20 October 2026; the page says it was updated 9 January 2026.
  9. 9Meta Business Help CentreDifferences between event counts in Meta Ads Manager, Ads Reporting and Events ManagerRead on 20 October 2026.
  10. 10Meta Business Help CentreTest your server events using the test events toolRead on 20 October 2026.

More guides

Start your 14 days now.

Two minutes to connect with our free Shopify app. 14 days of YourTracking free. Cancel anytime.

Start 14-day free trial