Meta EMQ Score Checker
Meta’s Event Match Quality (0–10) decides how much of your conversion signal actually matches to a user. Tick the identifiers your Conversions API sends to estimate your band — and see exactly what to add next.
Event Match Quality scores how reliably your server-side events match to Meta users, on a 0–10 scale. Aim for at least 6, ideally 8+. Email is the single strongest identifier, then phone, then click and browser IDs. Tick what you send to estimate your band and find the biggest gap — usually a missing email captured too late in the funnel.
Meta EMQ Score Checker inputs and result
| Score | Band | Read |
|---|---|---|
| 8–10 | Great | Strong matching; attribution and optimization fully fueled |
| 6–7 | Good | Solid; add email/phone to push higher |
| 4–5 | OK | Usable but leaking signal; prioritize email |
| 0–3 | Poor | Most events won’t match; fix before trusting data |
How to use this tool
- List what your Conversions API actually sends.Check your server-side setup (GTM server container, partner, or direct API) for the user_data fields it includes on each event.
- Tick each identifier above.Email and phone carry the most matching power; click IDs, browser ID, and external ID add incremental lift.
- Read your estimated band.Aim for 6+, ideally 8+. The score weights identifiers by how much they help Meta match an event to a person.
- Close the biggest gap first.If email is missing, add it — it is the single largest lift. Then phone, then click IDs.
- Export and re-check after changes.Copy a share link, download the CSV, or print a one-page PDF, then re-run after you add identifiers.
RGM Expert Says
Event Match Quality is the number we check first on any account that lost signal after iOS changes, because a low score quietly caps everything downstream — optimization, attribution, audience building. A pixel that “fires” but matches poorly is worse than it looks: Meta is optimizing on a fraction of your real conversions.
The lift is almost always about identifiers, not infrastructure. Email is the heaviest signal by far, so the highest-leverage fix is capturing it earlier in the funnel and attaching it (hashed) to every subsequent event in the session — not just the purchase. We routinely take accounts from a “4” to an “8” by backfilling earlier events with an email collected at step one of checkout.
One caution: chasing a perfect 10 has diminishing returns, and some identifiers (date of birth, full name) raise privacy questions for thin gains. Get to a strong, stable 8 with email, phone, click ID, and the browser identifiers, make sure consent is handled correctly, and spend the rest of your energy on creative and structure.
How it works
Event Match Quality scores, on a 0–10 scale, how reliably the customer information your server sends can be matched to a Meta user. The more high-quality identifiers you send, the better the match:
Not all identifiers are equal. Email is the strongest, then phone, then click and browser IDs:
- Hashing — identifiers are SHA-256 hashed before sending; you never transmit raw PII.
- Match rate — the share of your events Meta can tie to a user; EMQ is its proxy.
- Server-side — the Conversions API sends events from your server, recovering signal the browser pixel loses.
EMQ scoring and the relative weight of identifiers are documented by Meta (see the Conversions API dataset-quality docs). This estimator is RGM’s weighting of those signals; your real score is shown in Events Manager.
A firing pixel is not a matching pixel
After App Tracking Transparency and browser tracking limits, a large share of conversions never reach Meta through the browser. Server-side events via the Conversions API recover them — but only if they carry enough identifiers to be matched. An account can have a perfectly “healthy” pixel and still feed Meta a thin, poorly-matched signal that caps performance.
That is why EMQ is a leading indicator worth watching like a vital sign. A jump from a 4 to an 8 often lifts reported conversions and tightens optimization without changing a single ad — you simply gave the system more of the truth. Conversely, a setup that scores poorly will make even great creative and structure underperform, because the algorithm is learning from a distorted sample.
The trap is treating tracking as a one-time engineering task. Identifiers drift, consent settings change, and a site redesign can quietly drop the email field that was carrying your match rate. Re-checking EMQ on a cadence — and after every site change — is the unglamorous discipline that keeps the whole account honest.
Match-quality reference
Orientation, not gospel. Real scores appear in Meta Events Manager and vary by funnel stage.
| Signal | Relative weight | Note |
|---|---|---|
| Email (hashed) | Highest | The single biggest lift |
| Phone (hashed) | High | Crucial at checkout |
| Click ID (fbc) / fbp | Medium | Captured automatically when present |
| Name / location / DOB | Low | Small gains, bigger privacy footprint |
What operators say
Server-side tagging utilizes many of the concepts that are familiar to anyone who has worked with Google Tag Manager: there are tags which fire on triggers and pull in data from variables.
The highest-leverage tracking fix is rarely infrastructure — it is capturing the email earlier and attaching it to every event in the session.