CAPI Match Rate

What is CAPI match rate?

CAPI match rate is the percentage of server-side conversion events you send to Meta's Conversions API that Meta successfully matches to a user in its graph. A match means Meta can attribute the conversion to an ad impression, an ad click, or a user profile — and therefore use the event to optimize delivery, train its prediction models, and report attributed revenue back to you. An unmatched event is, for optimization purposes, lost.

For DTC operators, match rate is the single most important quality signal of your tracking setup. A 30% match rate means 70% of your conversions are invisible to Meta's optimizer; the algorithm is making bidding decisions on a third of the data. A 92% match rate means Meta sees almost everything that happened on your site, so its optimization actually optimizes.

How Meta computes the match-rate baseline

When you POST an event to /v17.0/{pixel_id}/events, Meta returns a JSON response that includes (among other fields) the count of matched events for the request. That number — matched events ÷ total events sent in the request — is the canonical match rate. It is computed by Meta, against Meta's user graph, and is therefore not subject to interpretation or sampling on our side. The Admaxxer pipeline reads that response field directly and stores it alongside the event.

This is the same methodology Hyros built its entire category positioning around. Hyros' headline pitch — "we get higher match rates than your in-house pixel" — is exactly this measurement. Admaxxer ships the same measurement on every plan, including the $9/mo entry tier.

The Admaxxer server-side event-matching pipeline

The pipeline is three hops:

1. Pixel → Admaxxer server. The first-party pixel (client-pixel/) fires on conversions and POSTs the event to the Admaxxer ingest endpoint. The pixel runs on your domain (not connect.facebook.net), which means it survives Safari ITP, iOS Mail Privacy, and most consent-mode setups that strip third-party requests.
2. Server-side enrichment. Admaxxer enriches the event with hashed PII (email SHA-256, phone SHA-256, fbp, fbc, IP, user-agent, click ID timestamps) — the full set of user_data fields Meta uses for matching. Hashing happens inside the Admaxxer server process; the hashed values are what get sent to Meta.
3. Server → Meta CAPI. The enriched event POSTs to Meta's Conversions API with your access token. Meta's matched-events response is read out of the JSON, persisted on the event row, and surfaced in the dashboard within 60 seconds.

Because the matching parameters (fbp, fbc, email_sha256, etc.) are assembled server-side from the pixel's payload and from anything the operator has configured to backfill from Shopify/Stripe/etc., we typically catch matches that a browser-only pixel would miss — most importantly the post-redirect Stripe webhook checkout completion, where the browser context is gone but the email and click ID are still recoverable from the order.

The 92% sustained match rate (Q1 2026)

Across the 8.4 million tracked conversion events that flowed through Admaxxer between January 1, 2026 and March 31, 2026, the platform-wide median CAPI match rate was 92%. The bottom-decile workspace ran at 78% (typically a workspace that hadn't configured the Stripe webhook backfill yet); the top-decile workspace ran at 97%. We surface every workspace's real number in the dashboard — there is no marketing-massaged "94%" displayed for everyone.

For methodology transparency: 92% is the median across active workspaces weighted by event volume, computed from Meta's matched-events response field. It is not self-reported, not estimated, and not extrapolated. The full distribution and the per-week timeseries are in the platform's public benchmark page (linked in the footer).

Per-campaign UTM match-rate diagnostic

The headline number is the platform median. The actionable number is your match rate per campaign, broken down by UTM. Admaxxer ships a per-campaign diagnostic inside the cross-platform creative grid that surfaces:

• Match rate for each campaign × ad set × creative cell.
• The dominant cause of unmatched events for cells below 80% (missing fbc, missing email, malformed UTM, etc.).
• One-click suggested fixes — for example, "this campaign is missing the fbclid capture; here is the corrected destination URL with the click ID parameter wired in."

The diagnostic runs on the same Tinybird pipes as the rest of the analytics stack, which means it stays fast even when you slice by 30-day-rolling windows on accounts spending $200k/month.

Why every plan ships this — not just enterprise

Hyros, the platform that built its category around CAPI match rate, gates this measurement behind a $499/month minimum and a sales-call onboarding. We think that's wrong. CAPI match rate is the single most diagnostic signal a DTC operator has about their Meta ads health; gating it behind enterprise pricing means small operators run blind on the very metric they need most. Admaxxer ships the full match-rate measurement, the per-campaign diagnostic, and the suggested-fix workflow on every paid plan starting at $9/mo. The enterprise tier exists, but it exists for seats and SLAs, not for unlocking visibility.

Audit-logged, methodology-public

Every CAPI POST and every matched-event response is logged in the workspace's audit log. You can see, for any individual conversion, the exact user_data payload that was sent, Meta's response, the matched-events count, and the timestamp. If your match rate looks wrong, you can drill all the way down to a single event and inspect the wire payload — there is no black box between the pixel and Meta.

Learn more

• Metric glossary — CAPI match rate definition
• Install the Admaxxer pixel on Shopify
• Meta paste-token setup (CAPI prerequisite)
• Pair with the in-app AI agent for match-rate analysis

---

Methodology

As of: April 30, 2026.

All product claims on this page reflect the live behavior of the Admaxxer platform on the date above. Where a metric is cited (e.g., the 92% sustained CAPI match rate), the measurement window, sample size, and source are stated inline next to the figure. Pricing tiers and plan inclusions are documented on the pricing page; if you find a discrepancy between this page and the pricing page, the pricing page is canonical and we'd like to know — please email hello@admaxxer.com.

Comparisons to third-party products (Triple Whale, Northbeam, Hyros) reflect publicly documented behavior of those products as of the as-of date. We do not maintain inside knowledge of competitor roadmaps; if a competitor has shipped a feature that changes the comparison, please let us know and we will update this page.