Low Event Match Quality score in Meta Events Manager
Events Manager shows a low Event Match Quality score for key events such as Lead or Purchase, often on events sent through the Conversions API.
Steps checked against the platforms' documentation on November 20, 2026.
Quick answer
Event Match Quality is low when the event carries little customer information Meta can match, usually only an IP address and user agent. Click the score on the Pixel's Overview to see which parameters are being sent, then add properly normalised and hashed email and phone, plus fbp, fbc and external_id, for visitors who have consented.
1. The server event only carries IP address and user agent
The server tag fires on the conversion but never receives the form data, so it sends client_ip_address and client_user_agent and nothing else. This is common on lead forms where the server-side setup was copied from a page-view template.
How to check
- 1On the Pixel's
Overviewin Events Manager, click the Event Match Quality score for the event and review which customer information parameters are received. - 2Complete a test conversion with
Test Eventsopen and inspect the parameters on the server event.
How to fix
- 1Pass the email, phone and name from the successful form submission into the server event as
em,ph,fnandln. - 2Add
country,ct,standzpwhere you collect them. - 3Only send what the visitor has submitted and agreed to share.
2. Data is hashed without normalising it first, hashed twice, or not hashed
Meta requires SHA-256 hashing for fields such as em and ph, after normalising them. A hash of John@Example.com will not match a hash of john@example.com. Tools that hash automatically can also end up hashing an already hashed value.
How to check
- 1Take one test lead and normalise it yourself: trim and lowercase the email; reduce the phone to digits with the country code and no leading zeros.
- 2Hash the normalised values with SHA-256 and compare them with what the payload sends.
- 3Check whether your server container, plugin or CRM integration hashes for you before you add your own hashing.
How to fix
- 1Normalise before hashing: email trimmed and lowercase; phone as digits only including country code; names lowercase without punctuation;
countryas a lowercase two-letter ISO code such asus. - 2Hash once, in one place.
- 3Do not hash
client_ip_address,client_user_agent,fbporfbc. Meta says these are sent unhashed.
3. fbp and fbc are missing or malformed
The _fbp and _fbc cookies are set by the Pixel. If the server does not read them, or the visitor arrived with fbclid before the cookie existed, the click ID never reaches the event. Lowercasing the click ID also breaks it, because Meta says it is case sensitive.
How to check
- 1Click a test ad or add
fbclidto a test URL, convert, and confirm the server event inTest Eventsincludesfbcandfbp. - 2Check the
fbcvalue followsfb.<subdomainIndex>.<creationTime>.<fbclid>and the click ID keeps its original case.
How to fix
- 1Read
_fbpand_fbcfrom the request cookies and send them with every server event. - 2If
_fbcis missing butfbclidis in the URL, buildfbcyourself in Meta's format, with the creation time in milliseconds. - 3Refresh stored values rather than reusing an old click ID.
4. external_id is not used
Meta recommends including external_id and event_id for all events. A stable ID such as a CRM contact ID helps Meta connect events from the same person across browser and server.
How to check
- 1In
Test Events, check whether browser and server events carry anexternal_id, and whether it is the same value on both.
How to fix
- 1Send one consistent identifier, such as the CRM contact ID, as
external_idon both the Pixel and the Conversions API events. - 2Use the same format everywhere you send it.
5. The IP address is the server's, a relay's, or empty
Server-side setups often send the IP of the server, proxy or CDN instead of the visitor's. Meta's Dataset Quality API flags issues such as empty IP, relay IP, IPv4 sent where IPv6 is available, and mismatched IP addresses.
How to check
- 1In
Test Events, compareclient_ip_addresson the server event with your own public IP while testing. - 2Check how your server or server container reads the visitor IP from forwarded headers.
How to fix
- 1Pass the visitor's real IP address through to the server event, and send IPv6 when the visitor has one.
- 2Do not substitute a fixed or placeholder IP. Meta also flags placeholder emails and phone numbers.
6. Consent limits what you can send
When visitors decline marketing cookies, you should not send them Pixel events or identifiers, so overall match quality falls. That is expected. The problem is when consented visitors also lose data because consent is passed to the server incorrectly.
How to check
- 1Accept cookies in a private window, convert, and check the server event in
Test Eventscarries email, phone,fbpandfbc. - 2Check your server setup reads the consent state for each event rather than applying the most restrictive setting to everyone.
How to fix
- 1Pass the visitor's consent state with each event and send full customer information only for those who agreed.
- 2Do not work around a decline to raise the score.
Stop it happening again
- Document how each customer field is normalised and where hashing happens, so nobody adds a second hashing step later.
- Include the
fbc,fbp, email and phone checks in every post-release test conversion. - Review Event Match Quality and its recommendations on the Pixel's
Overviewmonthly for each key event. - Treat a sudden drop in match quality as a tracking incident: it usually means a form or server change broke data passing.