To improve Event Match Quality on Meta lead events, send the Lead from your server with everything the form and the click legitimately provide: hashed email and phone, the click ID, your own external ID, the browser ID, plus the visitor’s IP address and user agent. A lead form can carry both of Meta’s high-priority parameters, so it can reach Meta’s 6.0 recommendation. Wait 48 hours, then read the score of the Lead event, not the PageView.
What the score measures
Event Match Quality is Meta’s score from 0 to 10 for how well the customer information on a server event can be matched to a Meta account. Two ingredients go into it: the quality of the information you send with the event, and the share of those events Meta matched.
- It applies to website events sent through the Conversions API, with the action source set to website, standard or custom.
- Every event has its own score. A weak PageView says nothing about your Lead.
- The window is the last 48 hours, so the number moves with fresh traffic and not with a fix alone.
- A Pixel-only setup has no score to read. The Browser can send the same values through advanced matching, which helps matching, but the number in Events Manager belongs to server events.
Why it matters is what Meta does with an event it cannot match. Only matched events can be used for ads attribution and delivery optimisation, while unmatched ones stay useful for basic measurement. A Lead that does not match is a lead the system behind your campaigns never learned from.
The parameters Meta ranks, and where a lead form gets them
| Parameter | Meta priority | Where a lead landing page finds it | Hashed |
|---|---|---|---|
| high | the form’s email field | yes | |
| Click ID | high | the _fbc cookie, or built on the server from fbclid in the URL | no |
| Phone | medium | the form’s phone field | yes, digits only with country code |
| External ID | medium | your own lead or click ID | yes |
| Browser ID | medium | the _fbp cookie | no |
| Country | medium | a form field, or the country code of the phone number | yes |
| First and last name | low | the form’s name fields | yes |
| City and postal code | low | only if the form asks for them | yes |
| Birthdate | medium | rarely on a lead form, and not worth a new field | yes |
| Facebook Login ID | medium | only if visitors log in with Facebook | no |
| Lead ID | low | only for Instant Form leads | no |
| IP address | not ranked | the request that submits the form | never |
| User agent | not ranked | the same request’s headers | never |
The last two rows are not optional in practice: the user agent is required for website events sent through the Conversions API, and Meta’s developer guidance counts the IP address among the high quality parameters. Both are free, because the server handling the submission already has them.
Count what a form gives you: email and phone from the fields, the click ID from the URL, your own ID, the browser ID from the cookie, and two request headers. That is both high priority parameters and several medium ones. The one thing a PageView can never have is the email, because nobody has typed anything yet.
Normalise and hash before sending
Meta’s systems are not designed to accept plain contact information. Normalise first, then hash with SHA-256, because a value that is hashed in the wrong form is a valid-looking string that matches nothing.
- Trim spaces, then lowercase the email. Send the hash, not the address.
- Send the phone as digits only, with the country code, then hash.
- Send the country as a lowercase two-letter code.
- Send names lowercased and without punctuation.
- Leave a field out when it is empty rather than filling it with a default. A placeholder that repeats across events is worse than a missing value, and Meta reports it as one.
- Keep the same normalisation on the browser and on the server, so a value sent by both sides produces the same hash.
Meta’s reference shows the expected hash for its own example values, which makes a useful test before you blame the audience for a low score.
Six fixes, in order of effect
- Send the Lead from your server, with the form data. The score is calculated on Conversions API events, so this is where the gains are.
- Capture the click and browser identifiers on the landing page visit. If there is no
_fbccookie, build the click ID on the server from thefbclidin the URL and keep it with the lead. - Pass the visitor’s real IP and user agent, taken from the request that submits the form, never your own server’s or a proxy’s address.
- Add an external ID, hashed, and use the same format in the browser copy of the event.
- Check the event name and ID pairing. A Lead sent twice under different names produces two unmatched events rather than one matched pair, and Meta Pixel and CAPI deduplication shows how to read that tab.
- Wait 48 hours, then read the score of the Lead event.
Why the score stays low after a fix
Meta’s Dataset Quality API reports diagnostics per match key, and they map closely onto the usual lead generation mistakes.
| Diagnostic | Usual cause on a lead setup |
|---|---|
| Empty IP | the server never copies the visitor’s IP into the event |
| Mismatched IP | your server’s or proxy’s address is sent instead of the visitor’s |
| Relay IP | the visitor browses through a privacy relay; complete the rest of the event |
| IPv4 | an IPv4 address sent where IPv6 would match better, often because the landing page domain answers over IPv4 only |
| FBC coverage | the click ID is taken only from a cookie that never gets written, and never built from the URL |
| Email placeholder | a default value filled in when the field was empty |
| Phone placeholder | the same on the phone field |
A wrongly normalised value appears in none of these. It hashes to something valid and matches nothing, which is why a test against Meta’s example outputs is worth ten minutes.
One more thing before you change the form: Meta warns that sending a parameter does not make a match certain. One parameter alone may not be enough, and the person may not have a Meta account. For leads from your own ads the second case is unlikely, since they clicked one of your ads, but the email typed into a form is not always the one on the person’s account. That is why the phone and the click ID go next to it.
What the score does not tell you
A high score means Meta recognised the people behind the events. It says nothing about whether those people were worth calling, and it does not make Meta’s lead count equal to the leads you received. Budget decisions still belong on your own count, as Facebook lead quality sets out.
DropCPL sends the Lead to Meta from the server with a shared event ID, the click cookie and the browser ID, and counts the lead on the landing page that received it, so the score and the cost per lead describe the same submissions. The mechanics of the payload are in Event Match Quality for lead generation, the browser half is in Meta Pixel setup, and the diagnostics behind the score are in what is the Meta dataset quality API.