Meta Conversions API
SyncBeacon sends your store orders to the Meta Conversions API (the Facebook Conversions API) from the server, deduplicates them against your pixel with a shared event ID, and shows every delivery in the dashboard.
Works with
Shopify · WooCommerce · Shopware
Connects to
OpenAI Ads · Meta Ads · Google Ads · Microsoft Ads · Pinterest · Snapchat · X ads · TikTok (upcoming) · GA4 (coming soon)
Built for modern ecommerce
Simple to set up · EU-hosted · GDPR-ready · Secure event processing
Conversion events we support
PageView · ViewContent · Search · AddToCart · InitiateCheckout · AddPaymentInfo · Purchase
Also supported
OrderCancelled · Lead · CompleteRegistration
Last updated:
The Meta Conversions API (CAPI) lets a server report a purchase straight to Meta instead of waiting for a browser to do it. You will also see it called the Facebook Conversions API, which is the same interface under its older name. The data lands in the same Events Manager dataset as your pixel events and feeds the same optimisation and reporting.
The reason to use it is simple: a browser pixel only fires if the page loads, the script isn't blocked and the shopper stays long enough. A server-side event is sent after the order exists, so it doesn't depend on any of that. For the background, read our server-side tracking guide.
The usual question is Meta pixel vs CAPI. The honest answer is that they see different things, and Meta is built to receive both and merge them. SyncBeacon doesn't ask you to remove your pixel.
| Browser pixel | Conversions API via SyncBeacon | |
|---|---|---|
| Where it runs | In the shopper's browser | On the SyncBeacon relay (EU infrastructure) |
| Purchase trigger | Thank-you page loads with the script intact | The store's order webhook |
| Affected by ad blockers and tracking prevention | Yes | Not for server-side purchases |
| Strong at | Page views, browsing behaviour, cookies | Order value, currency, hashed email and phone |
| Needs consent handling | Yes | Yes, see the consent section below |
Purchases on Shopify are captured from order webhooks. Browser-side events depend on your theme and on the SyncBeacon script.
Our deeper comparison for Shopify is in Meta Conversions API for Shopify: pixel vs server-side.
If the pixel and the server both report the same order, Meta needs to know it's one order. It does that by comparing the event name and the event_id. Meta CAPI deduplication only works when both sides send the same ID.
SyncBeacon always sends an event_id. On Shopify, the purchase event ID is the order ID. Browser and server events SyncBeacon itself receives for the same order are merged into one event before anything is forwarded. One limit to know: for the match against your own Meta pixel, the pixel has to send the same ID too. If it doesn't, Meta may count a purchase twice, and you'll see that in Events Manager. Failed deliveries are retried automatically, up to 24 attempts, and reuse the same ID, so a retry doesn't create a duplicate.
Event match quality (EMQ) is Meta's score for how well an event can be tied to a person. Meta calculates it, and we don't promise a number. What we can show is the data that goes into the request:
| Parameter | Sent by SyncBeacon | Notes |
|---|---|---|
| Email and phone | Yes | SHA-256 hashed before the event is stored or sent |
| fbc and fbp | Yes | fbc can be rebuilt from fbclid if the raw value is missing |
| IP address and user agent | Yes | Browser-originated data; removed when marketing consent is missing |
| Value and currency | Yes | From the order |
| event_id | Yes | Used for deduplication |
| Name, address, city, ZIP | No | Not sent today |
An event needs at least one strong identifier: hashed email, hashed phone, fbc or fbp. Without one it is dropped rather than sent with nothing to match on. Store orders normally carry an email, so in practice the main thing that lowers match quality is missing consent. When marketing consent is missing, identifiers such as IP, user agent and fbp/fbc are removed before forwarding. If you want the tactical side, see how to improve Meta event match quality.
Connect your store
Shopify through OAuth, WooCommerce through the free plugin, or Shopware with an integration key. See Shopify, WooCommerce and Shopware.
Connect Meta
In Integrations, log in with Facebook and choose the Pixel or Dataset ID that should receive the events.
Keep your pixel running
Leave the browser pixel in place so Meta can merge both sources. Place one test order.
Check delivery and deduplication
Open the Conversions page to see the status per destination, then look at your dataset in Events Manager for server events and deduplicated purchases.
The same relay also delivers to Google Ads, Pinterest, Snapchat, X and OpenAI Ads. If you'd rather walk through the connection without a developer, the Meta CAPI guide covers it step by step.
Supported today
Stores: Shopify · WooCommerce · Shopware
Ad platforms: OpenAI Ads · Meta Ads · Google Ads · Microsoft Ads · Pinterest · Snapchat · X ads
FAQ
Yes. Facebook Conversions API is the older name for the Meta Conversions API. It is the same server-to-server interface, and the events arrive in the same Events Manager dataset as your pixel events.
Keep it. The pixel sees browsing behaviour that a store order doesn't contain, and Meta merges pixel and server events when they share an event name and event_id. SyncBeacon sends the server side of that pair.
Every event carries an event_id, and on Shopify the purchase ID is the order ID. Meta uses it to deduplicate. Your own pixel has to send the same ID for the match to work on that side.
Meta scores it, so we can't predict it. The usual causes are missing consent (identifiers are stripped), no fbc or fbp because the visitor never landed with a Meta click, and the fact that SyncBeacon doesn't send name or address fields.
A connected store, a Facebook login with access to the ad account, and the Pixel or Dataset ID. No Google Tag Manager container or developer work is needed for the supported stores.
If the visitor explicitly denied marketing consent, the event is stored but not forwarded to Meta. If there is no banner signal at all, your own consent setting decides, and identifiers are removed when marketing consent is missing.
Get started in minutes. No developer required for Shopify, WooCommerce, or Shopware setup.
Solutions
Compare
Learn