Free EMQ Scorer — Estimate Your Event Match Quality

Event Match Quality (EMQ) is Meta's 0–10 score for how reliably the events your server sends match real user identities in Meta's graph. Higher EMQ means the algorithm sees a cleaner conversion signal, which translates into more accurate attribution and lower effective CPA over a 4–6 week window.

EMQ is reported per event type in Events Manager. A site running pixel-only with no CAPI typically scores 4–5; a properly configured CAPI implementation with hashed email, phone, fbp, fbc, IP, and user agent scores 8–10. The gap between the two is often 25–40% in measured ROAS.

Post-iOS 14, EMQ is the highest-leverage operational metric in a Meta account. Most teams chasing creative or targeting wins still have an EMQ of 5 — fixing that single number outperforms most other optimizations.

Email (em) and click ID (fbc) carry the highest weight. Email is the strongest first-party identifier; fbc captures users who arrived via a Meta ad click and is the cleanest attribution path back to a campaign.

Phone (ph), fbp cookie, IP address, and user agent are the next tier. fbp is browser-side and travels with the pixel; IP and user agent are server-recorded and matter most when other identifiers are missing.

Name fields (first name, last name) are weak alone but combine well with zip code for partial-match recovery when email is missing. External ID is useful for tying customer relationships to Meta's graph for retargeting and lookalikes.

Start by mapping which fields your existing CAPI payload includes. The most common gap is missing email — a checkout or lead form has it, but the server-side event handler is not passing it through. Fix that and the score moves 1.5–2 points immediately.

Next, add fbp and fbc by reading the cookies on the request. fbp comes from Meta's pixel; fbc is built from fbclid in the URL. Pass both with every event.

Hash all PII with SHA-256 before sending — Meta requires it, and unhashed fields are silently dropped without affecting your raw event count. Many teams discover their EMQ is low because Meta is rejecting unhashed identifiers they thought were being matched.

EMQ does not directly determine which conversions are attributed to your ads — it determines whether Meta can link the conversion event back to the user who saw the ad. Low EMQ means Meta sees a conversion event but cannot match it to anyone in its graph, so the conversion is dropped from attribution.

The downstream consequence: your reported ROAS is lower than your actual ROAS, and the algorithm receives weaker conversion signals so optimization decays. Both effects compound — attribution looks worse, the algorithm has less to optimize on, real performance drifts down.

A rebuild from EMQ 4 to EMQ 8 typically shows up as 15–30% lift in measured ROAS plus a separate 10–20% lift in actual algorithmic optimization over the following six weeks.

Sending unhashed PII. Meta rejects it silently. The event still counts, but EMQ does not credit the field. Always hash with SHA-256 before serialization.

Skipping fbp and fbc cookies. These are the fastest free wins — both are sitting in the request headers, available without any product change. Many CAPI implementations forget to read them.

Assuming pixel-only is enough. Pixel events are dropped or suppressed at high rates by browser privacy features. Server-side CAPI with proper field coverage is the only reliable path to high EMQ on iOS Safari and increasingly on Chrome.

For a deeper rebuild walkthrough — including event deduplication and the order in which to add fields — see the post-iOS 14 attribution rebuild use case.