# How to improve Event Match Quality on Meta

> Improve Event Match Quality by sending hashed email and phone, click and browser IDs, IP and user agent with every server event. Seven steps with checks.
- **Author**: Marxx
- **Published**: 2026-11-19
- **Category**: Tracking
- **URL**: https://marxx.ai/library-guides/how-to-improve-event-match-quality

---

Improve Event Match Quality by sending more customer details with each server event: hashed email and phone first, then the click ID (fbc), browser ID (fbp), IP address and user agent. Send the same events through the pixel and the Conversions API, and deduplicate them, so Meta misses fewer events.

## What the score means

Meta gives each web event sent through the [Conversions API](/glossary/conversions-api) a score from 0 to 10. It reflects the quality of the customer information you send and the share of events that match a Meta account. Meta uses the last 48 hours of data, so send events steadily (Meta Business Help, checked 2026-10-20).

Better matching helps Meta deliver your ads to people likelier to act, and attribute actions back to your ads.

## Which details matter most

Meta ranks the details it can use.

| Priority | Details |
|---|---|
| High | Email address, click ID |
| Medium | Facebook Login ID, date of birth, country, phone number, external ID, browser ID |
| Low | Lead ID, first name, surname, city, postcode |

## The 7 steps

1. **Check the score.** In Events Manager, open your Purchase or Lead event. Events Manager also lists recommended actions.
2. **Ask for email and phone early.** Collect them at the first checkout step or on the lead form, not after payment.
3. **Hash contact details.** Meta says its systems do not accept unhashed contact information. Trim spaces and make email lowercase before hashing with SHA-256. For phone, remove symbols, letters and leading zeros, and include the country code, such as 91 for India (Meta for Developers, updated 9 Jan 2026).
4. **Send fbc and fbp.** These come from the _fbc and _fbp cookies, and fbc can be built from the fbclid in the ad URL. Do not hash them.
5. **Send IP address and user agent.** Do not hash them. Meta says they are added automatically for browser events but you must set them up for server events, and sending both may improve matching.
6. **Add an external ID.** Use your customer ID or loyalty ID. Meta recommends hashing it.
7. **Run the pixel and the API together.** Meta calls this a redundant setup. Send the same events both ways and deduplicate them, so a purchase counts once. See [how to set up Meta Conversions API](/guides/how-to-set-up-meta-conversions-api).

Get consent before you share data. Meta tells advertisers to hold the lawful permissions and any consent they need before they share information with it.

## A worked example

Say your store gets 1,000 purchases a week. Before the fix, your checkout asks for email only after payment.

| Detail on the Purchase event | Before | After |
|---|---|---|
| Email | 250 purchases | 950 purchases |
| Phone | 0 | 800 purchases |
| IP and user agent | 1,000 | 1,000 |
| fbp | 700 | 1,000 |

You moved email and phone to the first checkout step, and fixed the server so it sends the browser cookie. Each event now carries more details. Wait 48 hours and read the score again. Your score may not jump to 10, and that is fine. Use Meta's recommendations to find the next gap.

## Mistakes to avoid

- Sending unhashed emails or phone numbers
- Hashing the IP address or the click ID
- Sending the server's IP instead of the buyer's
- Sending a test event once and never checking again

## FAQ

### What is a good Event Match Quality score?

Meta's help page sets no target score. Raise the score by acting on the recommendations in Events Manager.

### Does a higher score lower my cost per purchase?

Meta says better matching can result in better ad performance and lower cost per action. Track your own cost per result before and after.

### Does the pixel alone give me a score?

Meta says Event Match Quality is available for website events sent through the Conversions API. Learn how the two compare in [pixel vs Conversions API](/compare/pixel-vs-conversions-api).

---
- [More Tracking articles](https://marxx.ai/library-guides/category/tracking)
- [All articles](https://marxx.ai/library-guides)