What is Event Match Quality (EMQ)?

EMQ is Meta's 0-10 score for how well your CAPI event payload matches a real user identity. Higher EMQ = better attribution, better optimisation, lower CPL. Most healthcare clinics in India sit at EMQ 4-6 because they only send hashed email and phone, not full identity stack with FBP, FBC, click ID, IP, user agent, and city.

Why bidirectional instead of one-way?

One-way (CRM → Meta) only sends conversions. Bidirectional sends conversions back to Meta AND pulls Meta-side optimisation signals (ad-set ID, campaign ID, FBP, FBC, placement) into the CRM. This lets the CRM stitch every consult and treatment to the originating ad set without manual UTM tagging.

What is the typical EMQ lift after proper CAPI?

From 5.2 to 8.5+ within 14 days. The CPL improvement that follows is usually 18-26% over 30 days, because Meta's optimiser now sees the full conversion path and stops wasting impressions on low-intent audiences.

Meta Ads · CAPI Architecture · 2026

Meta CAPI + CRM Bidirectional Sync — The Quiet Architecture That Lifts EMQ From 5 to 8.5

Published 27 June 2026 · ICG Editorial · 7 min read

Most Indian healthcare clinics have "set up CAPI" — meaning they send a Lead event with hashed email and phone, watch their Event Match Quality sit at 5.2, and wonder why CPLs keep drifting up. The fix is rarely "more events". It's bidirectional sync between Meta and the CRM, with the full identity stack on every payload. The CPL lift after that is usually 18-26% over 30 days.

Why most healthcare CAPI implementations underperform

A typical clinic CAPI setup sends three fields: hashed email, hashed phone, event name. Meta's Event Match Quality scores this payload at 4.5-5.5 out of 10. The optimiser receives a blurry signal, models a blurry audience, and wastes impressions on low-intent prospects. Meta is not punishing the clinic — it simply cannot match conversions to ad sets with high confidence.

Worse, this setup is unidirectional. The CRM tells Meta "a lead happened". It does not know which ad set the lead came from, so the CRM cannot stitch consults or treatments back to ad-set ID. Every revenue conversation gets stuck at "we got 412 leads last month" instead of "Ad set 7 produced ₹14.2 lakh in treatment revenue".

The bidirectional architecture in plain English

Meta Catalyst IQ runs a six-step sync loop between the Meta Conversions API and the clinic CRM:

Pixel + on-page identity capture: The Meta Pixel writes _fbp (browser ID) and _fbc (click ID) cookies. The lead form captures user agent, IP city, and timestamp.
Lead form submission: All identity fields (email, phone, FBP, FBC, IP, UA, city, ad-set ID from URL parameter) are POSTed to the CRM along with form data.
CRM stores ad-set ID natively: The CRM lead record now carries meta_adset_id, meta_campaign_id, fbp, fbc as first-class fields, not buried in notes.
CAPI Lead event fires: Server-to-server payload with all 9-12 identity fields hashed correctly. EMQ jumps from 5.x to 8.5+.
CRM stage transitions fire CAPI Custom Events: Consult Booked, Consult Showed, Treatment Paid each fire as separate CAPI events with the same identity stack. Meta's optimiser now learns from real revenue.
Meta reports back: Meta Catalyst IQ pulls the Marketing API daily to confirm event-match diagnostics and surfaces ad sets where match rate dropped — fixing the issue before CPL spikes.

The identity stack: what to send and why

Field	EMQ weight	How to source
em (hashed email)	High	Lead form, normalised lowercase, trimmed
ph (hashed phone)	High	Lead form, E.164 format (+91XXXXXXXXXX)
fbp (browser ID)	High	From `_fbp` cookie at form submit
fbc (click ID)	Very high	From `_fbc` cookie when present
client_ip_address	Medium	Server-side at CAPI fire time
client_user_agent	Medium	Forwarded from browser
fn / ln (first/last name)	Medium	Hashed, lowercase
ct (city)	Low	Hashed, lowercase, no spaces
external_id	Medium	Internal CRM lead ID, hashed

Sending all of the above takes EMQ from 5.2 to 8.5+ in 14 days. Sending only email + phone leaves you at 5.5 forever.

The downstream effect — an anonymised dermatology chain

A South India derm chain with 11 clinics ran ICG's CAPI rebuild in Q1 2026. EMQ moved from 5.4 to 8.7 within 12 days. Over the next 30 days:

Average CPL: ₹612 → ₹468 (a 23.5% drop) at the same daily budget
Consult-show rate: 41% → 53% (Meta's optimiser found higher-intent users once it could attribute properly)
Treatment revenue per ₹1 of ad spend: ₹3.80 → ₹5.20
"Unattributable" leads in CRM: 38% → 4% (because every record now carried ad-set ID natively)

No new creative. No new audience. Just the plumbing fixed.

The 5 mistakes Meta Catalyst IQ refuses to ship without checking

Sending PII unhashed — Meta will silently discard the field and EMQ stays low
Sending FBP and FBC from the server instead of cookie — both must be the actual browser cookie value at form-submit time, not a server-generated UUID
Mismatched event_id between Pixel and CAPI — causes duplicate counting; Meta dedupes only when event_id matches exactly
Skipping intermediate funnel events — only sending Lead, never Consult Booked or Treatment Paid — Meta cannot optimise to revenue if it never sees revenue
Manual UTM tagging instead of ad-set ID — UTMs break, marketers forget, ad-set ID via URL parameter is deterministic

The insight

CAPI is not a checkbox. It is the spine of healthcare ad attribution. Until your EMQ is 8.5+, every CPL number on your dashboard is approximate, every audience model is foggy, and 15-25% of your spend is being absorbed by Meta's inability to match conversions to ad sets.

Audit your current EMQ score (free)

We'll pull your Events Manager diagnostics, identify your gap, and quote the rebuild. Most clinics see 18-26% CPL reduction within 30 days of EMQ hitting 8.5+.

Book a free audit → WhatsApp ICG