Skip to content

Definition

Event Match Quality (EMQ)

Meta's score out of 10 for how well the customer information sent with your Conversions API web events can be matched to Meta accounts.

Event Match Quality is shown per event in Events Manager and is also available through the Dataset Quality API. Meta calculates it from which customer information parameters your server sends, the quality of those values, and the share of events matched to a Meta account. It is currently available only for web events.

The parameters that feed it include hashed em (email), ph (phone), fn and ln (names) and location fields, plus unhashed client_ip_address, client_user_agent, fbp and fbc. Personal fields must be normalized and hashed with SHA256; IP address, user agent, fbp and fbc must not be hashed.

Low scores usually come from server events that carry only an email (or nothing), from IP address and user agent being taken from the server rather than the visitor's browser, from hashing values that should be sent raw, or from not passing fbp and fbc through to the server.

Related terms

Meta Conversions API (CAPI)
Meta's server-to-server connection for sending web, app, offline and messaging events from your server or CRM directly to a Meta dataset.
fbp and fbc
Meta's first-party browser ID (_fbp) and click ID (_fbc) cookies; passing both to the Conversions API, unhashed, helps match server events to ad clicks.
First-party data
Customer information shared directly with a business by the customer, such as the email on a lead form or a purchase record in the CRM.
action_source (Meta Conversions API)
A required Conversions API field that tells Meta where a conversion happened, such as website, phone_call, physical_store or system_generated.

Sources

Checked against the official documentation in November 2026. Platforms change; check the source for current details.

All glossary terms

Got an account that doesn't add up?

Send us one account. We review it for free and send a short video of what's working and what isn't.