What Event Match Quality measures
Meta describes Event Match Quality as an indication of how effective the customer information sent with a server event may be at matching it to a Meta account. Matched events help Meta attribute the conversion to your ads and deliver the ads to people who are more likely to act.
The score runs from 0 to 10 and is calculated for each event from the quality of the customer information you send and the share of event instances Meta matched to accounts. It covers website events sent through the Conversions API with the action source set to Website, for standard and custom events, and it uses the last 48 hours of data.
Meta's parameter priorities and what SignalBridge sends
The priority column is Meta's, from its Business Help Center article on event match quality. The last column describes SignalBridge and is not part of Meta's documentation.
| Parameter | Key | Meta priority | SignalBridge |
|---|---|---|---|
| em | High priority | Sent when the data is on the event. Normalised and hashed with SHA-256 whenever an email is captured or supplied. | |
| Click ID | fbc | High priority | Sent when the data is on the event. Read from the _fbc cookie, or built from the fbclid in the landing URL. Sent unhashed. |
| Facebook Login ID | fb_login_id | Medium priority | Not sent. Not sent. |
| Birthdate | db | Medium priority | Not sent. Not sent. |
| Country | country | Medium priority | Sent when the data is on the event. Converted to an ISO two-letter code and hashed when an address is captured. |
| Phone number | ph | Medium priority | Sent when the data is on the event. Reduced to digits with the country code and hashed when a phone number is captured. |
| External ID | external_id | Medium priority | Sent on every event. Your ID, hashed, when you supply one. Otherwise a hashed visitor identifier scoped to your pixel. |
| Browser ID | fbp | Medium priority | Sent when the data is on the event. Read from the _fbp cookie and sent unhashed. |
| Lead ID | lead_id | Low priority | Not sent. Not sent. Lead ads data is outside the website events SignalBridge forwards. |
| First name | fn | Low priority | Sent when the data is on the event. Lowercased, letters only, hashed. |
| Last name | ln | Low priority | Sent when the data is on the event. Lowercased, letters only, hashed. |
| City | ct | Low priority | Sent when the data is on the event. Letters only, lowercased, hashed. |
| Zip or postal code | zp | Low priority | Sent when the data is on the event. Lowercased and hashed. A US ZIP+4 is cut to the first five digits. |
What Meta does not publish
Many guides label a score of 1 to 3 as poor, 4 to 6 as fair and 7 to 10 as great. Meta's documentation does not define score bands, and it publishes no figure linking a score to cost per result. Meta says better event match quality may result in better ad performance and lower cost per action, which is a direction, not a number.
That is why this checker counts parameters and does not return a score. Use the score in Events Manager as a trend to watch, and use the suggestions Meta shows beside each event to decide what to add.
What to add first
Work down Meta's priority order, and only send what you have a lawful basis to collect.
- Email. Capture it at checkout and on every lead form, and pass it with the event. It is the most valuable single parameter.
- Click ID (fbc). Store the fbclid from the landing URL when a visitor arrives from a Meta ad, and send it with the later conversion as fb.1.<click time>.<fbclid>, or keep the _fbc cookie the Pixel sets.
- Phone. Include the country code and send digits only before hashing.
- External ID. Use the same customer or user ID on every event and across channels, so Meta can link a visitor's events.
- Browser ID (fbp). It comes from the Meta Pixel's _fbp cookie, so keep the Pixel running next to the Conversions API.
- Name, city and postal code. Low priority, but nearly free when you already collect an address.
Formatting decides whether a match happens
A parameter that is present but formatted wrongly will not match. Meta expects each personal field to be normalised and then hashed with SHA-256: trimmed and lowercased text, phone numbers as digits with the country code, names without punctuation, countries as two-letter ISO codes and US states as two-letter codes.
The click ID, browser ID, IP address and user agent are the exceptions: they are sent as they are, not hashed. Hashing them breaks the match.
Consent and sensitive data
Meta's Business Tools Terms require you to have lawful rights to collect, use and share the data before you send it, to hash contact information as described in its developer documentation, and not to share sensitive information. Sending more parameters is only an improvement when each one was collected properly. Where consent is required, an event from a visitor who declined should not be sent at all.
How to read your real score
In Events Manager, open your dataset and look at the Overview. Event match quality is listed per event. Open an event to see the parameters Meta received and its recommendations. Allow up to 48 hours after a change, since the score is calculated from the last 48 hours of events.
Questions about this tool
What is a good Event Match Quality score?
Meta does not publish a threshold. Compare against your own history and read the suggestions in Events Manager. SignalBridge raises an alert when an event scores below 6 and has dropped by at least a point from its recent median; that is our alerting rule of thumb, not a Meta figure.
Will a higher score lower my cost per result?
Meta says better event match quality may result in better performance and lower cost per action, but it publishes no figure for how much. Be wary of guides that quote exact percentages.
Why do different events have different scores?
Each event is scored on the customer information it carries. A Purchase usually has email, phone and address from checkout, while a PageView rarely has more than the browser identifiers.
Does this apply to Meta Pixel events?
Meta states that event match quality is available for website events sent through the Conversions API. The Pixel still matters because it supplies the browser ID and click ID that server events reuse.
Do I need to send every parameter?
No. Send what you collect, in Meta's priority order. A missing birthdate or Facebook Login ID is normal for most shops.
Are IP address and user agent counted?
SignalBridge sends both with each server event, and Meta needs them for website events. They are not in the priority table in Meta's help article, so this checker leaves them out.
Why does the checker count parameters instead of scoring?
Because the score depends on what Meta actually receives and matches, and Meta does not publish the formula. Any number we showed you would be invented.
Are my selections stored?
No. They stay in your browser for the visit and are not sent anywhere.
Sources
- Meta Business Help Center: About event match qualityThe 0 to 10 scale, the 48-hour window, the website-events scope and the parameter priority table.
- Meta for Developers: Conversions API customer information parametersWhich fields are hashed and how each is normalised.