What is Event Match Quality (EMQ)?

Event Match Quality (EMQ) is Facebook's 0-10 score that measures how well the customer information you send with each conversion event matches a known Meta user profile. A higher score means Meta can attribute more conversions to ads, which improves campaign performance.

Definition

Meta calculates EMQ per event using the customer parameters you send: email, phone number, first name, last name, city, zip, country, date of birth, gender, external_id, the Facebook click ID (fbc) and browser ID (fbp). Each parameter must be correctly hashed (SHA-256) before transmission. EMQ is reported per event source in Events Manager and ranges from Poor (under 4) to Great (above 7). Stores sending only a single parameter from the browser pixel typically sit around 4-6; sending the full set server-side via the Conversions API lifts the score to 8 or higher.

Why it matters

Meta's ad delivery uses EMQ to decide how aggressively to optimize against your conversions. A low EMQ means Meta is unsure which user actually converted, so it discounts the event in attribution and optimization. The downstream effect is wasted ad spend, weaker Smart Audiences, and lower ROAS - even though your ads may be performing well. Lifting EMQ is one of the highest-ROI changes most stores can make.

Check it on your site

Match quality starts with what your browser events carry. Our free Meta Pixel and CAPI checker shows whether the _fbp and _fbc cookies are set and how long Safari keeps them, and whether each event has the event_id and parameters Meta needs. It cannot read your server events, so it complements the score in Events Manager.

Run the Meta Pixel and CAPI checker

AxiTrace adds SHA-256 hashed email and phone, fbp and fbc and ad click ids to every server event. See what the AxiTrace Conversion API sends with each order.

Frequently asked questions

What is a good Event Match Quality score?

Meta classifies 8.0 and above as Great, 6.0-7.9 as Good, 4.0-5.9 as Okay, and under 4.0 as Poor. Most stores running only the browser pixel sit in the Okay range; reaching Great almost always requires sending events server-side via the Conversions API with first-party customer data.

How do I improve my EMQ score?

Send more customer parameters - at minimum email, phone, external_id, and the click IDs (fbc, fbp). Hash them correctly (SHA-256, lowercase, trimmed). Send via the Conversions API, not just the pixel, because the browser blocks or drops many fields. Deduplicate against the pixel using a shared event_id so Meta does not penalize duplicates.

Ready to track conversions
accurately?

Join e-commerce teams who stopped guessing and started measuring. Free plan, no credit card, setup in minutes.

10,000 free visits/month · All 9 ad platforms · Full dashboard