Event match quality
How it works
For events from the Conversions API, Meta checks which customer information comes along and how well it matches Meta accounts. That includes email address, phone number, external ID, IP address, user agent and the _fbp and _fbc cookies. The result is a score up to 10 per event type, shown in Events Manager together with hints about which parameters are missing. Meta doesn't publish the exact weighting. The rule of thumb: more and better customer information raises the score.
Why it matters
An event Meta can't match to a user still arrives, but it helps neither attribution in Meta nor the algorithm's learning. A low EMQ means part of your conversions don't improve the campaign. Events from the CRM often lack browser data such as cookies, so the email address and phone number have to carry the match on their own.
TSO merges visitors and identifiers into people. That way even a later deal can bring along the contact details from the first form, hashed with SHA-256 when sent.
Example
A real estate agent sends leads through the Conversions API with only IP address and user agent. Events Manager shows a score of 4 for "Lead" and recommends sending email address and phone number.
After the change, a hashed email, a hashed phone number and the _fbc cookie go along as well. A few days later the score is 8. Meta can now match far more leads to a person and an ad click.
Common mistakes
- Wrong normalization: an email with capital letters or spaces produces a different hash and matches no account. The parameter is there, but it doesn't help.
- Only watching the number: a high EMQ is of little use if the events themselves are wrong, for example counted twice or sent without a value.
- Dropping fields without thinking: every field you withhold can make matching worse. Which data you want to send and are allowed to send is a privacy decision you should make on purpose, not leave to whatever the setup happened to do.