If you want to improve Meta Event Match Quality, start by understanding what the score measures. It is not a grade for your campaigns or your tracking in general. It rates how well the customer information attached to a server event can be matched to a Meta account. More matchable keys, sent correctly, usually mean a better score.
This guide lists the Meta CAPI match keys that matter, says which ones SyncBeacon sends and which it does not, and shows how to check the result in Events Manager. We stick to what Meta documents and what our code does. We do not promise a target score.
What Event Match Quality is
Meta says that if you share server events through the Conversions API, you can see the Event Match Quality (EMQ) for each event in Events Manager. The score is out of 10 and indicates how effective an event's customer information may be at matching it to a Facebook or Meta account. It is available for web events.
It matters because of what Meta does with unmatched events. Per Meta's best-practice guidance, only matched events can be used for ads attribution and delivery optimisation. Unmatched events can still be used for basic measurement. A server event nobody can match is delivered but largely wasted.
The Meta CAPI match keys, and what SyncBeacon sends
Meta lists many customer information parameters. This table compares the main ones with what SyncBeacon includes in a Meta event.
| Key | What it is | SyncBeacon sends it? |
|---|---|---|
em | Email, SHA-256 hashed | Yes, when available and consent allows |
ph | Phone number, hashed | Yes, when available and consent allows |
fbc | Meta click ID, from the ad click | Yes, when captured; built from fbclid if only that is known |
fbp | Meta browser ID | Yes, when captured |
client_ip_address | Visitor IP address | Yes, when present and consent allows |
client_user_agent | Visitor browser string | Yes, when present and consent allows |
fn, ln | First and last name, hashed | No |
ct, st, zp, country | City, state, postal code, country, hashed | No |
external_id | Your own customer or user ID | No |
SyncBeacon also sends the event name, event time, an event_id, the event source URL when it is known, value, currency and action_source set to website.
What this means in practice
- The strongest keys, email and phone, are covered. Names, address fields and external ID are not sent, so there is a ceiling we cannot lift for you.
- IP address, user agent and click IDs come from the browser tracker. An order that arrives only as a store webhook may have less of them unless the visit was captured earlier. SyncBeacon remembers click IDs between the visit and the order, within your plan's click-ID memory period.
- Meta requires at least one strong identifier (email, phone,
fbcorfbp) for SyncBeacon to send an event. Otherwise the event is dropped before the call and the Conversions page shows why.
Practical ways to improve it
- Install the tracker. It captures
fbclid, sets the_fbpcookie, and hashes email and phone in the browser. Without it, server events rely on order data alone. - Check consent. If marketing consent is missing, identifiers such as IP address, user agent and click IDs are removed from the payload, and email and phone are not forwarded. An explicit denial blocks forwarding entirely. A consent setup that is too strict, or not detected, lowers match quality. See how consent is detected.
- Check phone formats. Meta says phone numbers need a country code to be used for matching. SyncBeacon hashes the digits it receives, so numbers stored without a country code will match poorly. Fix the format at checkout if you control it.
- Collect email and phone at checkout. An order event can only carry the contact details your store actually captured, so make sure checkout asks for them where that is appropriate.
- Keep the pixel and server events aligned. Use the same event names and event IDs so the two sources merge instead of competing.
- Do not chase 10 out of 10. A realistic aim is to send every identifier you have, correctly, with consent.
Meta CAPI deduplication
Meta CAPI deduplication is a separate problem, but it affects your numbers more than the score does. Meta recommends running the pixel and the Conversions API together. For Meta to treat the browser and server copies as one event, they must use the same event name and the same ID: the pixel's eventID must match the server event's event_id. Meta says it discards the later duplicate when it sees the same combination for the same pixel within 48 hours.
On Shopify purchases, SyncBeacon uses the order ID as the event ID, and merges its own browser and server events for the same order. Your pixel must reuse that same ID in its eventID; if your pixel generates its own, Meta will not pair them.
How to check it in Events Manager
- Open Events Manager and select the pixel connected to SyncBeacon.
- Choose the
Purchaseevent and look for its Event Match Quality. Meta shows it for server events. If no score appears, check first that server events are arriving. - Open Test Events, place a test order, and confirm the event appears with the Server source.
- In the same view, check that Meta marks the browser and server pair as deduplicated.
- In SyncBeacon's Conversions page, confirm Meta shows as delivered for that order, or read the reason it was not.
Test with your own details. Meta notes that test events may be discarded if they do not match a Facebook or Meta account.
If the score is low: what to check first
| Symptom | Likely cause | What to do |
|---|---|---|
| Many events never appear in Meta | No strong identifier on the order, or consent blocked it | Read the reason on the Conversions page; fix tracker or consent |
| Events arrive but score is low | Only IP and user agent, or a single key | Make sure email, phone and click IDs are captured and allowed |
| Phone numbers rarely match | Numbers stored without a country code | Store international format at checkout |
| Purchases look doubled | Browser and server events use different IDs | Reuse the same event ID in the pixel |
| Score drops after adding a consent banner | Identifiers are removed for visitors who do not consent | Check consent is detected correctly; declined visitors will not match |
Change one thing at a time and give Events Manager time to reflect it. If you change consent and the tracker together, you will not know which one helped.
Common questions
Is a low Event Match Quality score a problem?
It is a signal, not a fault. A low score means Meta has little to match on, so those events help attribution and optimisation less. Look at which keys are missing before you change anything else.
Should I send more data to raise the score?
Only data you are allowed to send. Every key above is personal data or a pseudonymous identifier, so it should follow your consent setup. A higher score bought by ignoring a visitor's choice is not an improvement. Our GDPR-ready explainer covers where the line sits.
Honest limits
- We cannot say what score you will reach. It depends on your data, your consent rate and your traffic.
- Higher quality does not guarantee better campaign results.
- SyncBeacon does not currently send names, address fields or an external ID to Meta.
Related reading
- Meta Conversions API with SyncBeacon
- Server-side tracking
- Facebook pixel not firing: how to fix it
- Meta CAPI for Shopify: pixel vs server-side
Sources
- Meta for Developers, Conversions API best practices
- Meta for Developers, Customer information parameters
- Meta for Developers, Handling duplicate Pixel and Conversions API events
Get started
Send every match key you have
Connect Meta through SyncBeacon and check delivery and match quality in Events Manager.