Meta Conversions API: Setup, Shopify and Deduplication
What the Meta Conversions API does, how to turn it on in Shopify, how deduplication and Event Match Quality work, and the November 2026 changes.
Sara
Co-founder & CTO

The Meta pixel runs in the shopper's browser, and browsers now have plenty of reasons not to send what it collects. The Meta Conversions API is the server-side route for the same events, and for most online stores it is no longer optional if Meta is expected to see the purchases its ads produce. This guide covers what it is, how to switch it on in Shopify, how to stop it double-counting, what changes in November 2026, and how to check whether what Meta reports matches your orders.
The short answer: run the Conversions API alongside the pixel, and check both with Arktis
The Meta Conversions API, often still called the Facebook Conversions API, sends conversion events from a server or platform to Meta instead of from the browser. Meta recommends running it alongside the Meta pixel, with a shared event ID on each event so the two copies are deduplicated. On Shopify, you switch it on by setting the Facebook & Instagram channel's customer data sharing to Enhanced or Maximum.
The Conversions API improves what Meta receives; it does not tell you whether Meta's numbers are right. For that independent check, Arktis is the clear winner for an online store: it captures the fbclid on landing and holds it against the visitor across sessions, syncs Meta ad spend per campaign once a day through a direct connection, matches Shopify orders back to a visit, and counts conversions per UTM campaign and per ad platform. Arktis does not send events to the Conversions API. Plans are $49, $149 and $349 a month, with a 7-day free trial on Growth.
| Meta pixel | Conversions API | Arktis | |
|---|---|---|---|
| Runs in | The visitor's browser | A server, server to server | Your site plus Shopify orders |
| Sends data to | Meta | Meta | You, nothing goes to Meta |
| Browser ad blockers | Can stop it | Cannot block it | Orders still arrive from Shopify; the click behind them can be lost |
| Job | Reporting and ad optimisation | Reporting and ad optimisation | Checking Meta's numbers against your own orders |
Key takeaways
Pixel only is a partial picture: ad blockers, declined consent and browser cookie limits all remove events. The Conversions API recovers some of that, but only if the server events carry good customer information, which Meta scores as Event Match Quality out of 10, and only if every event pair shares an event_id. Three changes matter this autumn: Meta has been counting only link clicks as click-through since a rollout that began in March 2026, Meta's changelog lists Marketing API v24 as available only until 10 November 2026, and a Pixel setting that Meta turns on by default, Measure conversions on customer devices, can add conversions to your reports from 12 November according to PPC Land. Whatever Meta reports, reconcile it against your own orders.
What the Meta Conversions API is
Meta's developer documentation describes the Conversions API as a way for advertisers to send web, app and physical store events to Meta through a single endpoint. In practice, a web integration posts events such as Purchase to an events endpoint for your pixel, with the event name, the time, the page and a block of customer information.
That customer information is what makes a server event useful. Meta's documentation lists the fields: email, phone, name, city, postcode and country must be hashed with SHA-256 before sending, while the client IP address, user agent and the fbc and fbp values must be sent unhashed. The fbc value is the Meta click ID stored in the _fbc cookie on your domain, which can also be generated from the fbclid on the landing URL, and fbp is the browser ID in the _fbp cookie.
Why the pixel alone under-reports
Three things stop browser events reaching Meta. The first is ad blockers: Shopify's own help page on Meta data sharing says data sent from server to server cannot be blocked by browser-based ad blockers, which a browser pixel can be.
The second is consent. Where a store's consent banner holds the pixel back until the visitor agrees, the pixel will always see fewer purchases than you took. That is correct behaviour, and it is one reason a pixel-only count sits below your order count.
The third is storage. Safari limits how long cookies set by scripts survive, as our guide to Safari tracking protection explains, so a pixel that relies on a JavaScript cookie to remember the click can lose it sooner in Safari.
Meta's own guidance is to run the Conversions API alongside the pixel rather than replacing it, which it calls a redundant setup, so that one route can cover events the other drops.
How to set up Conversions API on Shopify
For most stores the setup is a setting. From your Shopify admin, go to Sales channels, then Facebook & Instagram, then Settings, and click Data sharing settings. In the customer data sharing section, turn on customer data sharing, choose a level, and connect the pixel you want to use if you have not already.
The three levels do different things. Standard uses the pixel only, collecting data from customer browsing behaviour in your store. Enhanced adds Facebook's Conversions API to the pixel. Maximum uses the Conversions API and the pixel and, in Shopify's words, is updated with Facebook's latest advertising technology. Shopify says the shared customer information includes the customer's name, location, email address and phone number. It also notes that, depending on when you installed the Facebook & Instagram channel, the data-sharing levels offer different privacy settings.
Two housekeeping steps finish the job. If you ever pasted Meta pixel code into your theme, remove it: Shopify's Meta pixel help page warns that leftover theme code means more than one pixel on the store, which can result in duplicate or incorrect data in your reports. And update your privacy policy, which Shopify asks merchants to keep up to date so customers have this information.
Stores on custom stacks send the events themselves, through a partner integration, server-side tagging or direct calls to the API. If that is you, the version your code calls now matters, which is covered below.
Deduplication with event_id
If the pixel and the server both send a Purchase, Meta needs to know it is one purchase. The rule is exact: the pixel's eventID must match the Conversions API's event_id, and the pixel's event name must match the server's event_name. Meta only deduplicates events received within 48 hours of the first event with that ID, and where the two copies do not differ meaningfully, it generally prefers whichever arrived first.
There is a fallback that compares event_name with fbp or external_id, but Meta documents that it generally only works when the browser event arrives first and the server event second. Do not rely on it. Generate one ID per order, use it in both places, and check Meta's deduplication key feedback after launch.
Event Match Quality
Event Match Quality is Meta's score, out of 10, for how effective the customer information on your server events may be at matching them to Meta accounts. Meta calculates it from which parameters arrive, their quality, and the share of events it can match, and it is currently available only for web events.
The practical levers are the fields above. Send a hashed email and phone on every purchase, pass the fbc and fbp values from the browser, and include the IP address and user agent. Meta's dataset quality metrics sit alongside the score: event coverage, meaning the seven-day average share of pixel events also covered by the Conversions API, deduplication key feedback, data freshness, and an estimate of additional conversions reported.
What changed in 2026
Meta announced on 3 March 2026 that click-through attribution for website and in-store conversions would include only link clicks, starting later that month for campaigns optimising for those conversions. Conversions after shares, saves and other non-link actions move into engage-through attribution, the new name for engaged-view, and an engaged view of a video ad is now 5 seconds rather than 10. Meta said the aim is reporting that aligns better with third-party tools like Google Analytics. If your click-through purchases fell in March, check this before you blame the integration.
For custom integrations, versions matter. Meta's Marketing API changelog lists v24.0 as available only until 10 November 2026 and v25.0 until 23 February 2027. Version 26.0 was released on 29 July 2026 and version 27.0 on 4 November 2026, and the changelog gives no end date yet for either. A server integration still pinned to v24 has reached that version's end date and should be moved to a newer version and retested straight away.
Measure conversions on customer devices
Meta's Business Help Center describes a Pixel setting in Events Manager called Measure conversions on customer devices. With it on, the match between an ad view and a purchase happens on the customer's device, using information the customer already shared with you, such as an email, and temporary, non-identifying device information. Meta says it then receives only confirmation that a purchase happened and which campaign to attribute it to.
Meta says the setting is turned on by default for eligible pixels, works alongside your existing Pixel and Conversions API setup rather than replacing it, and does not change your attribution window or attribution model. Its help pages say it is not active for people located in the EU and UK, and they list the pixel installed directly on the page and a website that requires people to log in to an account with an email or mobile phone number as what is needed.
Meta's help pages give no start date. PPC Land reported on 27 October 2026 that the panel in Events Manager reads "Measurement starting November 12, 2026". Meta's own instructions put the switch in Events Manager, under Data sources, your pixel and Settings.
For reconciliation, the consequence is simple: on eligible sites Meta-reported purchases can rise from that date with no change in the orders your store took. Mark 12 November on any chart that compares Meta with your orders, so a jump in Meta's figure is not read as a jump in sales. Our guide to Meta's on-device conversions setting covers whether to leave it on before Black Friday.
How to check Meta's numbers against real orders
Start with counts, not attribution. Compare purchase events Meta received in a week with the online orders in Shopify for the same week. A gap below your order count is expected; a figure above it means duplicates.
Then compare attributed results. Take a store where Ads Manager reports 150 purchases from Meta ads in a month, while the store can match 110 orders to visits that arrived with a Meta click, as an example. The difference is not necessarily an error: Meta also credits engage-through conversions, after shares, saves and engaged video views, and from 12 November may count conversions matched on the customer's device, while an order-based view only sees the clicks it recorded. The point is to know the size of the gap before spending against it.
Arktis gives you the order-based side. It holds the fbclid and UTM parameters against the visitor across sessions, syncs Meta spend per campaign once a day, and counts conversions per UTM campaign and per ad platform. Its Models view compares five rule-based models, first-touch, last-touch, linear, time-decay and position-based, per ad platform, so you can see how much the answer depends on the model. For Meta's own figure in the comparison, use Ads Manager.
Where Arktis does not fit
Arktis is a measurement layer, not a data pipe to Meta. It does not send Conversions API events, so it will not raise your Event Match Quality or give Meta's algorithm more signal. If Meta's optimisation is starved of purchases, the fix is the Conversions API itself, set up through Shopify or a server-side tool.
It also sees only what its tracker and your orders record. Arktis does not know which people saw an ad without clicking it, so a purchase that follows a video view, share or save with no click is invisible to it by design, which is exactly why its numbers and Meta's will never match exactly.
Next steps
To have Arktis count conversions per UTM campaign and per ad platform, from matched orders and the conversion events its tracker records, start the 7-day Growth trial, or compare plans on the pricing page. Related reading: Shopify Thank you page tracking after the upgrade, fbclid tracking and attribution, why Facebook Ads and Shopify disagree and server-side tracking for e-commerce. The free Facebook ads calculator works out the numbers without an account.
Sources
Meta for Developers: deduplicate pixel and server events, what the API sends, the recommendation to run both, event_id rules, the 48-hour window and the fbp fallback, accessed 9 November 2026
Meta for Developers: customer information parameters, hashing rules and the fbc and fbp values, accessed 9 November 2026
Meta for Developers: Dataset Quality API, Event Match Quality and related metrics, accessed 9 November 2026
Meta: changes to click-through attribution, link clicks only, engage-through and the 5-second threshold, published 3 March 2026
Meta Marketing API changelog, version dates for v24.0 to v27.0, including v24.0 available until 10 November 2026, accessed 9 November 2026
Meta Business Help Center: about measuring conversions on customer devices, how the setting works, on by default, not active in the EU and UK, accessed 9 November 2026
Meta Business Help Center: how to turn on measuring conversions on customer devices, the login and pixel requirements, on by default for eligible pixels and where to switch it off, accessed 9 November 2026
PPC Land: Meta Pixel will count more conversions from Nov 12, the 12 November date shown in Events Manager, published 27 October 2026
Shopify Help Center: Facebook data sharing, the Standard, Enhanced and Maximum levels, setup steps and ad blockers, accessed 9 November 2026
Shopify Help Center: Meta pixel, the warning about leftover pixel code in the theme causing duplicate data, accessed 9 November 2026
Frequently Asked Questions
What is the Meta Conversions API?
The Meta Conversions API, also called the Facebook Conversions API, sends conversion events such as purchases to Meta from a server or platform instead of from the visitor's browser. Meta recommends running it alongside the Meta pixel, with a shared event ID so duplicate events are removed. Because the events travel server to server, browser ad blockers cannot stop them.
How do I set up the Conversions API on Shopify?
In your Shopify admin, go to Sales channels, Facebook & Instagram, Settings, and click Data sharing settings. Turn on customer data sharing and choose Enhanced or Maximum, both of which add the Conversions API to the Meta pixel. Remove any pixel code you pasted into your theme, because Shopify warns that a second pixel can cause duplicate or incorrect data.
How does Conversions API deduplication work?
Meta treats a pixel event and a server event as one when the pixel's eventID matches the server's event_id and the event names match. Deduplication only applies to events received within 48 hours of the first event with that ID. A fallback using fbp or external_id exists, but Meta says it generally only works when the browser event arrives before the server event.
What is a good Event Match Quality score?
Event Match Quality is scored out of 10 and indicates how effective the customer information on your server events may be at matching them to Meta accounts. It is calculated from which parameters you send, their quality and the share of events matched, and is available only for web events. Sending a hashed email and phone, the fbc and fbp values, IP address and user agent on every purchase is the practical way to raise it.
Does the Conversions API make Meta's reported conversions accurate?
It makes them more complete, not independently verified. Meta still reports conversions under its own attribution rules, including engage-through conversions, and its Measure conversions on customer devices setting, on by default for eligible pixels and not active for people located in the EU and UK, can add conversions Meta could not match before. To check the numbers, compare them against your own orders in a tool that does not depend on Meta, such as Arktis.
Free tools for this topic
From the blog
Try Arktis free for 7 days
Attribution tracking, session recordings, and AI automation in one platform. Set up in 2 minutes, free for 7 days.
Start 7-day free trialWritten by
Sara
Co-founder & CTO
Sara architects Arktis's technical infrastructure, specializing in AI agents and real-time data processing systems.