Meta Conversions API integration: identity-resolved conversions, sent server-side

What Meta Conversions API is

Meta runs advertising across Facebook, Instagram and its audience network, and is the single largest acquisition channel for most DTC brands.

Meta’s delivery system is only as good as the conversions it can see. Its Conversions API exists because browser-side signal degraded, and Event Match Quality is Meta’s own measure of how many identifiers you attached to each event it received.

How Meta Conversions API works

Meta’s delivery system decides which people to show an ad to by learning from conversions advertisers report back. Historically that reporting came from the browser pixel; as browser signal degraded, Meta built the Conversions API so the same events could be sent server-to-server. Each event carries customer parameters (hashed email and phone, external ID, click ID) and Meta attempts to match them to a person on its side. Event Match Quality is Meta’s 0 to 10 score for how reliably it can match an event, and it is scored per event type. Browser and server events for the same purchase are collapsed using a shared event_id.

01

Send complete conversions

Conversions reach Meta through its server-side API with restored click IDs and hashed identifiers attached, so more of what you send is matched on arrival, and the conversions you never saw stop being invisible.

02

Optimize on the customer you want

Map any order attribute to the conversion Meta receives (profit rather than revenue, new customers rather than repeat buyers, high-value orders rather than every checkout), so the platform learns from the buyers worth acquiring.

03

Pixel and CAPI without double-counting

One install is the source of truth for both browser and server events, deduplicated on event ID, so Event Match Quality rises without purchases being counted twice.

Standard events, mapped for you

PageView, ViewContent, AddToCart, InitiateCheckout and Purchase reach your pixel as Meta standard events of the same name, with content_ids, value and currency in Meta’s structure. NC Purchase and RC Purchase custom events mark orders from new and returning customers, and the standard Purchase still fires on every order.

Every available match key

Each event carries hashed email, phone, first and last name, city, state, zip and country, plus fbc, fbp, external_id, IP address and user agent when Upstack has them. Personal data is hashed with SHA-256 before it leaves Upstack.

Deduplication on event_id

The default Tracking Method is Browser + Server: Upstack loads the Meta tag and sends the same events from its servers with the same event_id, and Meta keeps one. It works as long as the Pixel ID in Upstack matches the pixel on your store. Choose Server if you don’t want the Meta tag in the browser.

Click IDs that outlast the browser

An ad click adds fbclid to the URL, and Meta’s pixel stores it as the _fbc cookie. Meta treats a click ID as valid for 90 days. Upstack keeps click IDs past that window, restores them across sessions and devices through its identity graph, and always sends the most recent one.

What to expect from EMQ

Meta takes 24 to 48 hours to score new events. The gain shows up mainly on PageView, ViewContent and AddToCart; Purchase EMQ stays largely unchanged, because checkout already collects email, name and address. As a guide, 7.0 or higher is good and below 5.0 points to missing identity data.

Which orders Meta receives

First subscription orders are sent as Subscription Initial and count as purchases. Renewals stay out of Meta so optimization stays on prospecting. Order Source Exclusions can also keep sources such as POS or draft orders from feeding Meta.

How to verify it’s working

• Upstack’s Destinations page shows the Meta destination as Healthy.
• In Events Manager, the Overview and Test Events tabs list server events with a Server badge.
• Visit your store with ?fbclid=ABC123 in the URL, check out, and confirm the Purchase event carries the click ID (Meta receives it as fbc).
• Wait 48 hours before troubleshooting an EMQ of 0.0. Meta scores new events on its own schedule, and Upstack reads the score every 4 hours.

Common problems and fixes

EMQ stays at 0.0 while events look normal.

The token is missing ads_read plus ads_management or business_management. Generate a new one as a Business Manager admin, paste it, click Update Configuration and allow up to 8 hours.

Purchases show up twice in Meta.

Another sender is active: Shopify’s Facebook & Instagram data sharing, a pixel app, the Conversions API Gateway or another CAPI app. Turn it off, and the warnings should clear within 24 hours.

“Low rate of pixel events covered by Conversions API.”

For Upstack customers this generic Meta prompt is a false positive. Don’t click Review solution or install the Gateway or another CAPI app.

“Server sending expired fbclid value in fbc parameter.”

It comes from returning customers whose last Meta ad click was more than 90 days ago. No action is needed: Meta still matches on email, phone, IP address and external ID.

The destination turns Unhealthy.

The token expired, was revoked (often after a password change) or came from another Business Manager. Generate a new token from the account that owns the pixel and update the destination.

Meta and Upstack report different conversion counts.

Meta defaults to 7-day click and 1-day view, while Upstack’s Attribution report defaults to first click over 7 days. Compare Meta 7-day click with Upstack last click, 7-day: a 5 to 15% gap is normal.