Event match quality: what it is and why retail events score low

A conversion event Meta can't tie to a person is a conversion Meta can't learn from. Event match quality is the number that tells you how often that tie succeeds.

What is event match quality?

Event match quality (EMQ) is a score, rated poor to great, that Meta assigns to each type of conversion event you send through the Conversions API. It measures how well the customer information attached to an event lets Meta match that event to a Facebook or Instagram account.

The match is the whole point. Meta's delivery system can only learn from a purchase if it knows which user bought. An event with weak identifiers arrives, fails to match anyone, and teaches the algorithm nothing. EMQ is Meta's own read on how many of your events clear that bar.

You find the score per event in Events Manager, under the data source's event detail view. Meta documents the parameters and grading in its Conversions API customer information parameters reference.

What parameters set the score?

Each conversion event can carry a set of customer-information parameters. More parameters, better-quality parameters, and correctly hashed parameters all raise the match rate. The common ones:

1. Email (em), hashed with SHA-256. The single strongest identifier in most setups.
2. Phone number (ph), hashed, in full international format with country code.
3. First name, last name, city, state, zip, and country, each hashed.
4. Click ID (fbc) and browser ID (fbp), captured from the Meta click and the _fbp cookie, sent unhashed.
5. IP address and user agent, which help Meta place the event even when personal fields are thin.

The click ID carries a lot of weight because it ties an event directly to a specific ad click. When fbc is present and accurate, Meta already knows which click it belongs to before it ever checks an email.

Why do off-site retail events score low?

Here is the structural problem. When a shopper clicks a Meta ad and buys on Amazon or Walmart, the purchase fires inside the retailer's systems. The retailer knows the buyer's email, address, and payment details. You don't, and the retailer does not pass them to you.

So any event you can construct for that sale is built from what you could capture before the shopper left: an IP address, a user agent, and maybe the click ID if you grabbed it on the way through. No email, no phone, no name, which are exactly the high-weight parameters a retailer-bound flow can't supply.

The result is predictable. The event matches poorly or not at all, EMQ sits at the bottom of the scale, and the conversions that make up most of your revenue arrive as the weakest signal in your account. The same blindness runs through off-site ROAS: the retailer holds the identity, the sale, and the receipt, while your ad account sees a click and then nothing.

What does a low score actually cost?

A low EMQ doesn't just dent a report. It degrades the input Meta uses to decide who sees your ads next.

Meta's delivery leans on matched conversions to build its model of a buyer. Events that fail to match are discounted or dropped, so the campaign learns from a thinner, less representative slice of your actual customers. That weakens everything downstream, including any lookalike audiences built from retail buyer signals, because the seed set skews toward the events that happened to match.

The arithmetic is blunt. If 7 of 10 purchases happen at a retailer and those events match poorly, Meta is tuning delivery on the 3 it can see clearly. Decisions made on that visible slice aren't cautious. They're built on the wrong sample.

How to compare event signal quality

Not every conversion event has the same raw material to work with. Here is the gap between a DTC checkout and a retailer handoff, laid out by parameter:

A checkout you own hands Meta a full identity set. A handoff to a retailer hands over a browser fingerprint and little else, which is why the two score so differently even for the same ad and the same buyer.

Raising a weak score means capturing whatever strong identifiers you legitimately can before the shopper leaves (click ID first), then sending a clean server-side event for the handoff itself rather than letting the sale disappear into a system you don't report on. The ceiling is still lower than a first-party checkout. A matched handoff event beats no event at all.

Where to start

• Website: www.pixamp.io. Pixamp sends Meta ad traffic to retailers and returns the buyer-intent signals to Meta. First 1,000 clicks free, no card required.
• How it works: www.pixamp.io/#how-it-works. The three-step setup: connect Meta Business Manager, add a retailer button, launch. Live in under an hour.
• Book a demo: www.pixamp.io/#contact. A 20-minute walkthrough on a real retailer page, with the founding team.

If your retail sales land in Events Manager as poor-match events, the signal Meta learns from is the weakest part of your account. Fixing the handoff is where the score starts to climb.