Raising Meta Event Match Quality to 8 and above
Event Match Quality scores how well Meta can attach your events to real people, and a low score means your conversions are landing with weaker attribution than you paid for. The score responds to a small number of parameters rather than to all of them: email and phone hashed correctly carry most of the weight, then external ID, then the click and browser cookies. Sending more fields badly moves it less than sending the right five properly — and normalization before hashing is where most implementations lose their points.
Free30 minutesNo obligation
Event Match Quality · what breaks
The situation, as it usually presents — Event Match Quality
- 01
EMQ sitting in the low single digits
On events that matter.
- 02
Attribution weaker than spend justifies
Meta can't match what it can't identify.
- 03
Parameters sent but apparently ignored
Usually because they're malformed.
Event Match Quality · the fix
What changes — Event Match Quality
Match quality at 8 or above
Guaranteed in writing for server-side builds.
Identifiers normalized before hashing
The step most implementations skip.
Click and browser cookies carried server-side
Where they were being dropped.
Event Match Quality · architecture
Why this pattern keeps recurring — Event Match Quality
EMQ is a signal-quality score, and the reasons it stays low are consistent across almost every account we open.
- 1
Hashing a malformed value produces a valid, useless hash
Nothing errors. Meta simply never matches it, and the payload looks complete.
- 2
fbc only exists if fbclid was captured
Miss the capture on landing and every subsequent event is missing the strongest click signal Meta has.
- 3
External ID is the most under-used field
A stable customer ID lifts matching materially and costs nothing to add.
- 4
Coverage is per event
A high overall score can hide a Purchase event at 3, which is the one that matters.
Event Match Quality · diagnose
How the root cause gets found — Event Match Quality
In this order. Each step rules out a class of cause, so the last one usually has a single explanation standing.
- 01
Read EMQ per event, not overall
Purchase is the one to look at.
- 02
Inspect a real payload
Confirm which parameters are actually present.
- 03
Check normalization before hashing
Case, whitespace, phone format.
- 04
Confirm fbc and fbp are being captured
And forwarded, not regenerated.
- 05
Look for double hashing
Client hashes, server hashes again.
Event Match Quality · prove
How the work is proven — Event Match Quality
Against the client's own records, not a dashboard turning green.
Source of truth
Meta Events Manager match quality per event, over seven days
- EMQ at 8 or above on the primary conversion event.
- Parameter coverage read per event from a real payload.
- Normalization verified against Meta's specification.
- fbc and fbp confirmed present on server events.
- Reconciled over a fully closed window, matched on ID rather than on totals.
- Payload evidence captured from real transactions and handed over.
- The same reconciliation repeated 30 days later.
Event Match Quality · free audit
What we check in the free audit
- Read EMQ per event, not overall
- Inspect a real payload
- Check normalization before hashing
- Confirm fbc and fbp are being captured
- Look for double hashing
Checked against
Meta Events Manager match quality per event, over seven days
Free30 minutesNo obligation
Event Match Quality · when not to buy
Why there are no client numbers on this page — Event Match Quality
Most agency case studies lead with a percentage. This one doesn't, and the reason is worth stating.
- We don't publish client results we can't substantiate. An audit of this site in August 2026 found named testimonials and before-and-after figures that had never been measured — all of it was removed, and nothing has replaced it that isn't checkable.
- The results that do exist belong to clients under agreement. Publishing anonymised numbers without their sign-off would be the same problem in a thinner disguise.
- What we will commit to in writing is 95%+ conversion accuracy and 8+ Meta Event Match Quality, reconciled against your own order records. That is checkable by you, which a case study percentage never is.
- For proof from actual clients, the video testimonials on the site are real people describing their own rebuild. That is the strongest evidence we have, and it isn't a number we wrote.
Event Match Quality · what we deliver
What the work involves — Event Match Quality
Current parameter coverage measured
Per event, not overall.
Normalization corrected
Lowercase, trimmed, phone in E.164 without punctuation.
External ID added
A stable customer or order identifier, hashed.
fbc and fbp carried into server events
Both, from the browser, at the time of the event.
Written guarantee
95%+ tracking accuracy
Measured against Meta Events Manager match quality per event, over seven days. Miss it and we keep working at no cost.
Pricing
Pick the package that fits your ad spend
Browser-side starter
$400One-time fee · lifetime ownership
Repairs the fault in your existing browser-side setup and verifies it on a live transaction. Honest about its ceiling: it fixes this instance, not the class.
- Root cause fixed, not worked around
- Verified on a live transaction
- Reconciled against your own records
- Written handover
1st-party server-side
Recommended$800One-time fee · most popular
Removes the class of failure rather than this instance. Money events sent from your order records through a first-party container on your own subdomain, so the browser can no longer lose them.
- First-party server container on your own subdomain
- Money events from your order records, not the browser
- Deduplicated on a shared event ID at every destination
- First-party cookies beyond Safari's 7-day cap
- 95%+ accuracy and 8+ Meta EMQ, guaranteed in writing
Full 1st-party stack
$1,800One-time fee · lifetime ownership
Every paid channel server-side plus the offline loop, for advertisers whose spend makes an attribution leak more expensive than the build.
- Everything in 1st-party server-side
- Pinterest, Snapchat, Reddit and LinkedIn CAPI
- CRM and offline conversion loop
- Refunds reversed at every destination
- Monitoring so the next break surfaces in days
FAQ
Event Match Quality questions, answered
8 or above on your primary conversion. Below 5 means Meta is matching a minority of your events and attribution is materially understated.
No. A malformed parameter contributes nothing and can crowd out attention from the ones that matter. Five correct fields beat ten sloppy ones.
The server, from raw values. Hashing in the browser risks double hashing and makes normalization errors invisible.
It's computed over a rolling window, so give it several days of new events before judging the change.
WhatsApp