Meta event match quality: what it really measures

Event match quality is the 0 to 10 score that Meta assigns to each event sent through the Conversions API, measuring how well that event's data can confirm that it belongs to a real account on the platform. It appears in Events Manager, next to each data source, and many operations only notice it when the cost per lead rises for no apparent reason.

What event match quality measures, in practice

Each server event sent to Meta carries a set of parameters: hashed email and phone, the browser identifier (fbp), the click identifier (fbc), the IP, the user agent and, when it exists, an external_id coming from your own CRM. Meta compares these parameters with what it already has registered in Facebook and Instagram accounts and tries to confirm that the conversion event happened with a real person from its base.

The more parameters match with confidence, the higher the score, and that score is not decorative: it feeds directly into campaign optimization. An event with strong matching becomes a reliable signal for the algorithm to learn who converts; a weak event enters as a guess, and ad delivery optimizes for the wrong audience.

Why the score drops when parameters are missing

The most common reason is simple: the form or the CRM does not store email and phone alongside the event that goes back to Meta. Without those two fields, little is left to confirm identity, even when IP and user agent are present.

The second reason is the loss of fbc and fbp. We have already shown here how the fbclid becomes the fbc as soon as the click happens, and how that data disappears when nobody captures it at the exact moment the form is submitted. Without fbc, the conversion event loses precisely the parameter that weighs most in matching, because it directly links the ad click to the business result.

The third reason is identity fragmentation: the same lead appears with one email in the form and another in the CRM, or with the phone saved with and without the ninth digit. Each variation without standardization is one less chance for Meta to recognize that it is the same person. It is the same problem we described in the unified marketing and sales funnel, only here the effect shows up directly in the Events Manager score.

Practical steps to improve event match quality

Improvement happens parameter by parameter, not with a single setting. The order below prioritizes what usually yields the fastest gain first.

• Send hashed email and phone on every server event: confirm that your CRM or the tool that fires the event is sending both fields, always hashed with SHA-256, even when the phone comes unstandardized.
• Capture fbc and fbp at the moment of the form and return them at conversion: if your operation does not yet store this data, it is the point that raises the score fastest, because it links the original click to the sale or opportunity event.
• Add the external_id coming from your CRM: a workflow that receives lead data via webhook can carry this identifier along with the record, without depending on someone copying field by field.
• Standardize email and phone before sending: lowercase letters, no spaces, phone always with the country code. Standardization reduces the fragmentation that keeps Meta from recognizing the same person.
• Run a monthly check for parameters that arrive empty: the same data hygiene routines that the operation already uses for the CRM can catch an integration that stopped sending email or phone before the score drops for good.

After each change, go back to Events Manager and compare the data source's score in the previous week with the following week. It is the most direct way to confirm whether the adjustment really took.

What the score does not guarantee on its own

A high event match quality score does not, on its own, fix a funnel with poorly defined stages or a CRM without a filling standard. It confirms that the data sent has quality to be recognized, not that the lead's entire journey is well designed. It works as the first sign of tracking health, not the only one.

Frequently asked questions

Does event match quality exist for every type of event? Today it is officially documented only for events sent via web through the Conversions API. For other event types, Meta's own guidance is to talk to the account representative.

Is there a minimum score considered good? Meta does not set a universal number. What matters more than chasing a fixed value is tracking the trend of your own account: if the score rises after each parameter added, the path is right.

Is it safe to send email and phone to Meta? Yes, as long as the sending follows the API standard: both fields are converted to a hash before leaving your server, and Meta never receives the data in plain text.

Improving event match quality is, in practice, a matter of standardization: the same identity parameters that strengthen the CRM are the ones Meta uses to confirm that the event is real. Whoever already organizes this standard for campaign naming and UTMs has less adjustment ahead here. To close this standard in one go, Laiki's Data Management Playbook brings together campaign naming, the UTM manual and the custom fields guide in a single free document.

Official source on the score and matching parameters: Conversions API Best Practices, Meta for Developers.