What is CAPI match rate?

CAPI match rate is the proportion of your pixel (browser) events that Meta successfully matches to the corresponding Conversions API (server) event. A higher match rate means Meta has better signal to optimize toward purchases, especially in iOS 14.5+ and cookie-restricted environments.

attribution
Admaxxer is a DTC analytics platform with built-in Meta + Google ad ops. Anyone who has set up Meta's Conversions API eventually asks: what is CAPI match rate? It is the share of browser pixel events that Meta deduplicates with a matching server-side CAPI event — and it has become one of the most important signal-quality metrics for Meta ad accounts since iOS 14.5 and ITP eroded cookie reliability. ## The short answer CAPI match rate is the proportion of your pixel (browser) events that Meta successfully matches to the corresponding Conversions API (server) event. A higher match rate means Meta has better signal to optimize toward purchases, especially in iOS 14.5+ and cookie-restricted environments. ## Full answer ### Why match rate matters Meta's ads delivery models are trained on events. When a browser pixel event fires (say `Purchase`) but the corresponding CAPI call never arrives or arrives without matching user identifiers, Meta discards signal quality. Higher match rates raise EMQ (Event Match Quality), which Meta uses to decide how much to trust your signal for bidding and targeting. ### How the metric is computed At a rough level: ``` CAPI Match Rate = (Events with both pixel + server + matching ID) / (Total pixel events of that type) ``` Meta itself reports a version of this in Events Manager. Admaxxer computes its own view from raw pixel and CAPI logs so you can slice by event name, device, browser, or campaign. ### Drivers of a low match rate - **Missing user identifiers** — email, phone, `fbc`/`fbp` cookies, IP, user agent. More hashed identifiers per event = higher match. - **Missing `event_id`** — required for deduplication between pixel and CAPI. - **Timing drift** — CAPI events that arrive hours late lose deduplication with the pixel event. - **Ad blockers** — clients that strip the pixel cause unmatched server events. Solvable by firing CAPI for all traffic, not just traffic the pixel confirmed. ### What Admaxxer does Admaxxer tracks CAPI match rate per event name per day as a first-class metric. When it drops, you see it as an alert on the dashboard rather than discovering it two weeks later in Events Manager. The accelerator brief also uses match rate as an input: creatives shipping to an account with a weak match rate are called out, because you cannot trust those ROAS numbers until signal quality is repaired. ## Related questions - [What is blended MER?](/faq/what-is-blended-mer) - [Which Shopify events does Admaxxer track?](/faq/which-shopify-events-does-admaxxer-track) - [How does Admaxxer connect to Meta Ads?](/faq/how-does-admaxxer-connect-to-meta-ads)

Related Questions

What is a good Meta CAPI match rate?

Most healthy ecommerce accounts sit in the 70 to 95 percent range on purchases. Below 60 percent usually indicates missing identifiers, event_id mismatches, or CAPI coverage gaps.

Does Admaxxer send CAPI events for me?

Admaxxer measures and reports match rate from your existing pixel and CAPI setup. Creating CAPI events is handled by your server or tag manager; Admaxxer ensures you see the match-rate health in one place.

Why does my CAPI match rate fluctuate?

Match rate can drop when identifiers like hashed email or fbp cookies are missing, when event_id is inconsistent between pixel and CAPI, or when CAPI events arrive too long after the pixel event for deduplication.

Still have questions?

See the full documentation or start a 7-day free trial — no credit card required.

Try Admaxxer Free