Identity data is inconsistent
Spaces, casing, local phone formats, and placeholder values weaken otherwise useful fields.
Event Match Quality
Give Meta stronger match signals, not more noise.
Build server events with useful, properly formatted customer and browser information so Meta has a better chance of connecting conversions to accounts and ad interactions.
Normalize identity data Preserve browser context Send complete event details
EmailPhoneFBPFBCSource URLEvent ID
Signal coverageAccurate · normalized · connected
Where tracking breaks
Event Match Quality starts before the API request.
A perfect-looking JSON object cannot recover data that was never captured, was formatted incorrectly, or was separated from the original visit.
Browser context is missing
The server event cannot benefit from identifiers that were discarded on the page.
The event source is vague
Meta receives the conversion but little context about where it happened.
More fields create more noise
Inaccurate or fabricated values do not become useful merely because the payload is larger.
Hashing happens too early
Data is hashed before normalization, producing a different result from the expected value.
Consent is ignored
A technically complete payload can still be inappropriate if the data was not lawfully collected or permitted.
The controlled path
Move from a loose collection of signals to one traceable event.
Simple CAPI keeps the implementation focused: capture the useful data, connect it to the conversion, send it through a protected endpoint, and validate the result.
Capture accurate source data
Collect only the values you are permitted to process and can keep connected to the event.
Normalize before hashing
Trim and format identity fields consistently, then hash the required values.
Preserve browser identifiers
Carry available FBP, FBC, user agent, source URL, and click context into the server event.
Use a stable event ID
Keep one identifier across browser delivery, server delivery, and retries.
Monitor diagnostics
Review changes over time rather than treating one score as a permanent result.
Email
Before: " Demo.User@Example.COM "
Normalized: "demo.user@example.com"
Hashed: "[sha256 value]"
Phone
Before: "(514) 555-0199"
Normalized: "15145550199"
Hashed: "[sha256 value]"Practical coverage
Useful signal coverage.
Use accurate values, preserve ownership, and validate the event before relying on campaign reporting.
EmailPhoneExternal IDFirst and last nameCity and regionPostal code and countryFBP and FBCIP and user agentEvent source URLEvent ID
Built for controlled implementation.Keep client credentials out of page code, collect only permitted data, and preserve a clear boundary between client configurations.
Review privacy principles Frequently asked questions
The parts people usually discover after launch.
Resolve the implementation details before the campaign starts spending money.
What is Meta Event Match Quality?+
It is Meta’s assessment of how effectively the customer information parameters in an event may help match it to Meta accounts.
Is Event Match Quality the same as attribution?+
No. Matching, attribution, and reporting are related but separate processes.
Which parameters affect matching?+
Useful identity fields, browser identifiers, click context, user agent, IP when appropriate, event source, and consistent formatting can all contribute.
Should email and phone be hashed?+
Meta expects certain customer information fields to be normalized and SHA-256 hashed before transmission unless the integration handles that step for you.
What Event Match Quality does Simple CAPI achieve?+
Our tested client setups have reached a minimum of 9.3 Event Match Quality across more than 25 implementations using the included setup method.
Why does 9.3+ Event Match Quality matter?+
It shows that the configured event is giving Meta strong customer and browser matching information for measurement and optimization.
How long does Meta take to update the score?+
Updates are not always immediate. Use recent event diagnostics and parameter coverage alongside the displayed score.
Simple CAPI workspace
Build the event once. Hand off one controlled installation.
Create a client-specific Lead or Schedule endpoint and validate the exact event Meta receives.
Create your endpoint First eligible script is free after account verification.