
Event match quality indicates how well Meta can associate the events you send with real people on its platforms. The better it is, the more effectively the system optimises and builds audiences. Improving it depends on sending useful, correct data obtained with consent.
The essentials in a definition
Event match quality on Meta indicates how reliably the events you send are associated with people on the platform. It improves with appropriate parameters (such as hashed email and phone, where permitted and with a legal basis), click identifiers and deduplication. The Conversions API, Meta’s help pages and the GDPR define what is possible and permitted.
What it means
When an event arrives, the platform tries to link it to a user using identifiers the advertiser provides (for example, email, phone, browser identifiers), with privacy handling. The more valid, correct identifiers, the better the match. It is an indicator of measurement quality, not a goal in itself.
More good signal, better optimisation.
How to improve
Send relevant parameters consistently and correctly, with suitable formatting and hashing where required. Capture data with well-designed forms and clear consent. Send server events in addition to the pixel. Avoid empty or incorrect fields. Keep consistency between browser and server events.
Clean data is worth more than data in volume.

Improving event match quality
- Send useful, correct identifiers
- Capture data with clear consent
- Complement the pixel with server events
- Monitor the score by event
Privacy
Collect only what is necessary, with transparency and legal basis. Respect removal requests. Do not use data in ways people would not expect. Document what data you send and why. Review privacy policies and the consent banner. Privacy protects trust and reduces legal risk.
Technical quality and respect go together.

Better matching comes from cleaner data, not more data.
Monitor
Track the score by event in the events manager. Analyse differences after site or integration changes. Check event coverage and errors. Investigate sudden drops. Record improvements and results in optimisation and cost per result.
Monitoring avoids silent losses.
Decision table
| Factor | Improves | Caution |
|---|---|---|
| Click identifiers | Associates event with ad | Store and send correctly |
| Hashed email and phone | More matches | Legal basis and minimisation |
| Consistent parameters | Fewer errors | Correct format |
| Deduplication | Unique events | Common identifier |
Common mistakes to avoid
- Sending data without consent. It breaches privacy.
- Inconsistent formats. They reduce matching.
- Measuring quality and not acting. The indicator only helps if it guides fixes.
How to measure the result
Track the quality indicator by event, parameter coverage and campaign performance.
Limits and exceptions
Quality depends on consent and available data. Requirements and indicators change; confirm the documentation. This content is not legal advice; handle personal data with minimisation.
Illustrative example
Illustrative example: a store sees low match quality on purchase events. It starts storing the click identifier, sending hashed email from customers who consented and fixing field formats. Quality improves and optimisation becomes more stable.
In practice: checkpoints
Create a table with the parameters sent in each event and their status: sent, missing, in the wrong format or without legal basis. Fix first those that most improve matching and that you have permission to use. Normalise email, phone and address formats before hashing, and validate deduplication with the event identifier. Track each event’s score over the weeks. Make sure forms and checkout capture the information in a clean way, store the click identifier from the moment of arrival and keep records of consent. Review the quality indicator after site changes, since new forms or checkout steps are a common reason for quality to fall. Remember that a high score does not by itself guarantee better results, so keep an eye on the final business metrics too.
Frequently asked questions
What is a good score?
The highest you can reach with legitimate, correct data.
Can I send any data?
No. Only what is necessary, with legal basis and consent.
How do I check?
In the events manager, by event.
Which parameters should I prioritise?
Those that most increase association and that you have a legal basis to use.
Does it guarantee better performance?
It helps optimisation, but other factors count.
Improve matching with click identifiers, hashed parameters with a legal basis, consistent formats and deduplication, and use the indicator to guide fixes.
Sources and recommended reading
- Meta for Developers: Conversions API
- Meta Business Help Centre
- General Data Protection Regulation (GDPR)
Last editorial review: October 2026. Informational content; always confirm current conditions in the official sources before deciding.