If your Meta Event Match Quality (EMQ) is stuck at 4–6, you’re not broken — you’re just under-sending. EMQ climbs as you attach more (hashed) customer parameters to each event, and there’s a clear order of impact. Here’s the ladder to a consistent 8+ on your Purchase event. (New to EMQ? Start with what’s a good EMQ score.)
Why 4–6 is the ceiling for “email only”
Meta matches your event to a real profile using the identifiers you send. Email alone gets you to about 5–6 — decent, but it leaves matches (and attribution) on the table, especially since iOS and cookie loss mean fewer browser signals. Each additional identifier gives Meta another way to match.
The parameter ladder (in order of impact)
| Step | Add this | Why |
|---|---|---|
| 1 | Email (hashed) | Baseline ≈ 5–6 |
| 2 | Phone (hashed, E.164 format) | Biggest single jump |
| 3 | First + last name, city, state, zip, country (hashed) | Broadens matching |
| 4 | fbp + fbc (Meta browser cookies) | Strong browser-side match |
| 5 | external_id (e.g. customer/order id, hashed) | Cross-session match |
| 6 | Send it all server-side via CAPI | Reliable, un-blockable delivery |
Where each value comes from on Shopify
- Email, phone, name, address, city, zip, country — Shopify’s checkout already collects these; pass them into your Pixel/CAPI event (hashed).
fbp/fbc— read from the visitor’s browser cookies (_fbp,_fbc).fbccomes from thefbclidin the ad click URL, so make sure it’s captured on landing.external_id— use the Shopify customer id or order id, hashed consistently.
Meta hashes personal data (or expects it pre-hashed with SHA-256), so you never expose raw customer info. Send parameters through both the Pixel and CAPI with a shared
event_idso the sale is counted once — see Pixel + CAPI deduplication.
Verify, then wait
Check the Purchase event’s EMQ in Events Manager → your dataset → Events. After a change, EMQ updates in 24–48 hours and settles over 3–5 days — don’t judge it same-day. Aim for a stable 8+; chasing 9–10 hits diminishing returns.
FAQ
What raises EMQ the most? Adding a hashed phone number on top of email, then name/address/zip/country and fbp/fbc — sent via CAPI.
Why is my EMQ stuck at 4–6? You’re likely sending email only, or missing fbp/fbc and a server-side CAPI copy of the event.
Do I need CAPI for a high EMQ? For a consistent 8+, practically yes — the server-side event delivers the full hashed parameters reliably.
Related
Sources
- Niblin — Meta CAPI Event Match Quality
- Analyzify — How to improve Meta Event Match Quality
- CustomerLabs — Improve your Event Match Quality
- Stape — How to improve Facebook Event Match Quality