Event Match Quality 2.5/10: The 6 Fields You Are Missing (And What They Cost You)

By Hanuman Sihag, Head of Innovation Chamber & SEO Lead at ICG.

If your Meta Ads account shows an Event Match Quality score below 6.0, your bid algorithm is flying partially blind. Here is exactly what EMQ is, why most healthcare clinics score 2.5/10, and the specific fields that fix it.

What EMQ actually measures

Meta Catalyst IQ Audience Size analysis showing the fatigue and saturation curves for each audience segment in a Meta Ads account" width="1200" height="675" loading="lazy" decoding="async" style="width:100%;height:auto;display:block;">

Event Match Quality is Meta's score (0-10) for how confidently it can match a conversion event back to a specific ad click. When a patient clicks your Meta ad on Tuesday and calls to book an appointment on Thursday, Meta needs to connect those two events to know the ad worked.

The match happens through customer identity data, hashed fields you send alongside the conversion event. More fields = more ways to match = higher EMQ = more conversions correctly attributed = better bid optimisation.

EMQ below 4.0: Meta matches fewer than 40% of your conversions to ad clicks. Your ROAS data is significantly understated. Smart bidding targets are set too low.

EMQ 6.0-8.0: Meta matches 70-85% of conversions. Bid algorithm has enough signal to optimise accurately. Cost-per-patient begins to reflect reality.

EMQ above 8.0: Near-complete attribution. Every ad rupee's outcome is tracked. This is the goal.

The 13 fields Meta supports

Meta evaluates up to 13 customer identity fields when matching a conversion. Most healthcare CRM CAPI integrations send 2. The 6 highest-impact missing fields for a typical IVF, dermatology, or dental clinic:

1. External ID (the CRM lead ID)

Your CRM assigns every lead a unique ID (e.g., LS-00432812 in LeadSquared). This is the most reliable persistent identifier across sessions. Sending it as external_id lets Meta link the conversion event back to the original ad click even when the patient changed devices or cleared cookies. Most CRM integrations do not send this field. Impact on EMQ: significant.

2. Click ID (fbc)

When a patient clicks your Meta ad, Meta appends a unique fbclid parameter to the landing page URL. This is the strongest possible match signal, it directly connects the conversion to a specific ad click. Capturing fbc requires a snippet on your landing page that reads the URL parameter and passes it to your form submission. If your landing page developer has not added this, you are missing the most powerful EMQ field.

3. Browser ID (fbp)

The fbp cookie is set by the Meta pixel when the patient first visits your website. It persists across sessions and identifies the browser instance. Sending fbp alongside the conversion event gives Meta a second session-level identifier. Requires the Meta pixel to be active on the landing page.

4. IP Address

The patient's IP address at the time of form submission. Combined with phone and email, it provides a geographic match signal. Sent as part of the API request from your server, no additional tracking required, just include it in the CAPI payload.

5. User Agent

The browser and device string from the patient's session (e.g., "Mozilla/5.0 Chrome/124 Mobile"). Combined with IP, it helps Meta match mobile-to-desktop journeys where the same patient switched devices. Available from the HTTP request headers.

6. City and State

Your clinic's CRM almost certainly captures the patient's location, either from the form or from the phone number STD code. Hashing and sending city and state adds two more match dimensions.

Why most clinics score 2.5/10

The default LeadSquared to Meta CAPI integration sends Phone (✓), Email (sometimes ✓), and nothing else. That is a 2-field submission on a 13-field standard. EMQ 2.5/10 is the inevitable result.

The fix requires middleware, a layer between the CRM and the CAPI endpoint that enriches the event payload with landing page session data before firing to Meta.

The EMQ to ROAS relationship

At EMQ 2.5/10: Meta attributes roughly 30-40% of your conversions. Your ROAS dashboard shows ₹3 return for every ₹1 spent. You are likely at ₹5-6 return in reality.

At EMQ 6.0/10: Meta attributes 70-80% of conversions. Smart bidding tightens its targets. CPL drops 15-25% on the same creative and audience.

At EMQ 8.0/10: Attribution is near-complete. Every campaign optimisation decision, budget, bid, creative, audience, is made on accurate data.

The math: for an IVF clinic spending ₹10L/month on Meta Ads, moving from EMQ 2.5 to 6.0 is worth ₹1.5-2.5L/month in ROAS improvement on unchanged spend. That is not an estimate. It is derived from the 15-25% ROAS lift that consistently appears in accounts we have upgraded.

See the Beacon identity enrichment architecture that brings EMQ from 2.5 to 6+.