Meta Ads match parameters: the email and phone Meta never receives

What are match parameters?

Match parameters (in Spanish, parámetros de coincidencia) are the user data your pixel can send along with each event. Not just "a $X purchase happened" — but also "this purchase was made by this person, with this email, this phone, this name, in this city."

Meta uses that information to make a match: it searches its user base for someone with that email or phone who has a Facebook or Instagram account. If it finds them, it can:

• Attribute the conversion to the ad that user saw
• Exclude the buyer from acquisition campaigns (so you don't spend on someone who already bought)
• Add them to retargeting audiences more precisely
• Use their profile to build lookalike audiences that look more like your real buyers

If Meta can't make that match because it never got the data, the event is left "orphaned" — Meta knows it happened, but can't connect it to any specific user. And all optimization degrades.

What is EMQ and why does it matter so much?

Event Match Quality (EMQ) is the score Meta gives to the quality of your events, on a scale of 1 to 10. A high EMQ means Meta can match your events to real user profiles on its platform. A low EMQ means events arrive without enough data to make that match.

EMQ is calculated based on how many match parameters arrive and how well they arrive. A Purchase event with only the browser's IP and user agent scores an EMQ of 2-3. The same event with email + phone + name + city can reach 8-9.

EMQ has a direct impact on your results. With low EMQ:

• Your buyer audiences are imprecise — the lookalike doesn't really know who to resemble
• Conversion attribution is worse — sales that happened don't get connected to the ads that drove them
• The optimization algorithm works with half the data — it spends more to find similar buyers
• Your real CPA goes up, even if reported ROAS doesn't show it yet

You can read more about EMQ in our in-depth article: what EMQ is and how to raise it.

The parameters with the most impact, in order

Meta has a list of user parameters it accepts. They don't all carry the same weight. These are the ones that raise EMQ the most:

• Email (em). The most important parameter. Meta can match more than 80% of emails if they belong to active accounts on its platforms. It's the most reliable identifier because people use the same email everywhere.
• Phone (ph). Second in weight. With the rise of WhatsApp Business, many buyers have their number linked to Meta accounts. It must be sent with the country code and no spaces (e.g. 5491112345678).
• First name (fn) and last name (ln). Not enough for a match on their own, but they complement email and phone when there's doubt.
• City (ct), state/province (st) and postal code (zp). Location data that helps Meta validate the match and build precise geographic segments.
• Country (country). Critical to avoid false cross-country matches. Many Argentine buyers share the same email as someone in Mexico or Spain.

All of these parameters must be sent hashed (using SHA-256) to protect user privacy. Meta matches against its own hashed base — it never sees the real email, only the cryptographic fingerprint. You can find the technical details in Meta's official documentation.

Why doesn't the browser pixel send this data?

This is the root of the problem. Meta's standard pixel is a JavaScript snippet that runs in the buyer's browser. For it to send the user's email, that email has to be available on the page at the moment the pixel fires — and on most checkouts, it isn't.

The pixel fires when the user lands on the order confirmation page. By then, the form has already been submitted and the browser no longer has access to the email the user typed. Tiendanube and Shopify send some information, but they rarely send the full set of parameters — email + phone + name + address — consistently on every event.

The fix is to send that data from your server, not from the user's browser. Your server does have access to all the order data after the purchase: email, phone, name, shipping address. It can hash them and send them to Meta via the Conversions API (CAPI) with no browser, no cookies, no ad blockers involved.

The real impact on audiences and lookalikes

The clearest example of why this matters is lookalike audiences. When you create a buyer lookalike in Meta, you're telling it: "find people similar to the ones who bought from me."

If your purchase events arrived without email or phone, Meta doesn't really know who those people are. It knows they bought, but their profiles are incomplete. The lookalike it builds on that base is imprecise — similar to "someone who bought on a website," not to "your ideal customer."

With well-matched events — EMQ 7 or higher — Meta can say: "these people are between 28 and 45, live in Buenos Aires, follow these pages, have this estimated income level, bought this and that before." The resulting lookalike is much more precise, and acquisition cost goes down.

That's the difference match parameters make in practice. Not in lost sales — in data quality, audience quality and cost per result.

How Escalafy solves the match parameter problem

The Escalafy server-side pixel sends every Purchase event to Meta with the full set of user parameters: email, phone, name, city, state/province and postal code — all hashed, all from the server, with no dependence on the buyer's browser.

But there's more: because Escalafy already has your business's real costs connected (product cost, fees, shipping, installments, ad spend), the event that reaches Meta doesn't just carry the sale value — it comes with profitability context. You can see in Escalafy whether that sale was profitable, without waiting for month-end close.

Other tracking tools give you back the event with the buyer's parameters. Escalafy gives you that plus the real profit in real time behind every sale.

FAQ about Meta match parameters

How can I see my current EMQ?

In Meta Business Manager, go to Events Manager → select your pixel → the "Overview" tab shows Event Match Quality for each event type (ViewContent, AddToCart, Purchase). A score under 5 on Purchase is a sign that parameters are missing.

Is the customer's email enough, or do I need every parameter?

Email alone already improves EMQ significantly. But combined with phone and name, the effect is bigger — especially for users who have a phone number registered with Meta but a different email from the one they bought with. Sending every parameter you have is always better than sending just one.

What happens if the buyer doesn't enter an email at checkout?

If it's a guest purchase without a required email, that parameter isn't available for the event. That's why, from a data standpoint, it's important to make email mandatory at checkout — not just for communications, but for the quality of your advertising data.

Do I need to deduplicate events if I use pixel + CAPI?

Yes. If the browser pixel and the server both send the same Purchase event, Meta would count it twice. Deduplication works by sending the same event_id on both channels — Meta discards the duplicate. This is a critical part of implementing server-side correctly. You can read more in our article on event deduplication in Meta Ads.

Do match parameters also work for Google Ads?

Google has its own system: Enhanced Conversions, which works in a similar way. It also uses the buyer's email and phone to improve conversion matching. The principle is the same — first-party data sent with the conversion event. You can read about it in our article on Google Ads Enhanced Conversions.