Meta’s Event Match Quality (EMQ) is a 0–10 score of how well the events you send (Purchase, Lead, Add to Cart…) can be matched to a real person on Meta. The higher the score, the better Meta can attribute conversions and optimize your campaigns — which, since iOS App Tracking Transparency and cookie loss, increasingly depends on the hashed first-party data you send, not cookies.
Low EMQ quietly wastes ad budget: Meta optimizes on weaker signal, under-reports conversions, and struggles to find similar buyers. Here’s what “good” looks like and how to get there.
The EMQ bands
EMQ is scored 0–10, per event type (your Purchase event and your Lead event each get their own score).
| EMQ score | Rating | What to do |
|---|---|---|
| 9–10 | Excellent | Maintain; diminishing returns above 8 |
| 8–9 | Target for Shopify | Aim to hold this on Purchase |
| 6–8 | Good | Fine; small gains still possible |
| 4–6 | Typical but weak | Where most Shopify stores sit — improve this |
| Below 4 | Warning | Fix now; matching is poor |
The practical goal isn’t a perfect 10 — returns flatten out between 8 and 10. Aim for a consistent 8+ on your most important event (Purchase).
Where to check it
In Meta Events Manager → Data Sources → your dataset → Events tab, each event shows an Event Match Quality column. Check the Purchase event first — that’s the one your optimization and reporting depend on.
How to raise it: the parameter ladder
EMQ goes up as you send more hashed customer parameters with each event. Roughly:
- Email only ≈ 5–6. This is where many stores are stuck.
- Add phone number — this is the single biggest jump you can make.
- Add name, city, state, zip, country (all hashed).
- Add
fbpandfbc(Meta’s browser cookies) andexternal_idwhere available. - Send it server-side via the Conversions API (CAPI), not just the browser Pixel — server-side data is more complete and less likely to be blocked.
Send 8+ identifiers where you can. Meta hashes personal data (email, phone, name) automatically or expects it pre-hashed — you’re never exposing raw customer data.
Tip: fixing EMQ often goes hand-in-hand with fixing Pixel + CAPI deduplication. Send the richer data through both the Pixel and CAPI with a shared
event_idso Meta counts each purchase once — see our guide on duplicate purchase events.
How long until it moves
EMQ updates 24–48 hours after a change and can take 3–5 days to settle. Make a change, then check again a few days later — not the same afternoon.
FAQ
What is a good Event Match Quality score? 6–8 is good, 8–9 is a solid Shopify target, 9–10 is excellent. Below 4 is a warning. Most Shopify stores sit at 4–6.
Why is my Event Match Quality low? Too few parameters. Email alone gets ~5–6; adding phone, name, address, zip, country and fbp/fbc — ideally via CAPI — raises it.
How do I improve EMQ on Shopify? Send more hashed identifiers per event; adding phone on top of email is the highest-impact step. Target a consistent 8+ on Purchase.
How long does EMQ take to update? About 24–48 hours, and 3–5 days to fully stabilize.
Related
- Fixing double-counted purchases: Duplicate purchase events in GA4 on Shopify
- The full sweep: GA4 ecommerce tracking audit checklist
Sources
- Niblin — Meta CAPI Event Match Quality
- Analyzify — How to improve Meta Event Match Quality
- Upstack — A complete guide to Meta EMQ for Shopify brands
- CustomerLabs — Improve your Event Match Quality
- Meta — About Event Match Quality (Events Manager)