Meta Ads

Advanced Matching

Also called AM, manual advanced matching

Sending hashed customer details with an event so Meta can connect it to the right person's account.

Quick facts: Advanced Matching

Category
Meta Ads
Also called
AM, manual advanced matching
Level
Advanced
Affects
Attribution accuracy, audience quality, reported results
Where to see it
Meta Events Manager (Advanced Matching, Event Match Quality), Meta Pixel Helper
In this article4
  1. How advanced matching works
  2. Why advanced matching matters
  3. Where advanced matching goes wrong
  4. What to do about it

How advanced matching works

When someone converts on your site, Meta has to decide which person that was before it can credit an ad. Cookies and browser identifiers do part of that job, but they fail often — a different device, a browser that blocks storage, a private window. Advanced matching adds a second route. Alongside the event, the site sends identifying details the customer has already given you: email address, phone number, first and last name, city, postcode, country.

Those details never leave the browser in readable form. Each one is hashed first, meaning it is converted into a fixed string of characters that cannot be reversed back into the original. Meta hashes the details it holds in the same way and compares the two strings. Identical strings mean the same person; nothing readable has changed hands in either direction.

There are two versions. Browser-side advanced matching is switched on in Events Manager and lets the pixel pick fields up from forms automatically. Manual advanced matching, and the equivalent when events are sent from your server, means you pass the fields deliberately — more work, and far more reliable.

Why advanced matching matters

Attribution and audiences both depend on identification. An event Meta cannot attach to a person still counts in aggregate, but it cannot credit the ad that produced it, cannot exclude that buyer from a campaign, and cannot feed a lookalike. Reporting understates results and delivery learns more slowly.

It matters most where identification is hardest: mobile-heavy traffic, people who browse on a phone and buy on a laptop, and businesses whose customers arrive through in-app browsers. That describes most Nepali audiences, so the difference here is larger than the same setup would make in a desktop-heavy market.

Where advanced matching goes wrong

Formatting causes most failures. Values must be normalised before hashing — lowercase, no spaces, no punctuation — and phone numbers need the country code, so a Nepali number stored locally without its dialling code will not match anything. Hash the wrong way round, hash an already-hashed value, or hash a formatted string, and every comparison fails silently.

The other mistake is scope. Advanced matching is for details the customer gave you in the ordinary course of business. Scraping fields from a page they did not submit, or passing data belonging to someone who never consented, is a legal problem regardless of the hashing, because hashed personal data is still personal data under most privacy law.

What to do about it

Turn on browser matching, then improve on it deliberately: pass email and phone from the checkout or enquiry form where you know the values are real. Send the same fields from the server too, which is the practical reason for pairing the pixel with the Conversions API. Watch the event match quality figure in Events Manager after each change; it is the only feedback you get on whether the fields are landing.

Say plainly in your privacy policy which details are shared and in what form, and make sure your consent tool actually stops the fields being sent when someone declines.

Do and do not

Do

  • Normalise values to lowercase and strip spaces before hashing
  • Include the country code on every phone number
  • Watch event match quality after each setup change

Do not

  • Hash a value that has already been hashed
  • Collect fields the customer never knowingly submitted
  • Send matching data when consent has been declined

Questions people ask about this

Is advanced matching safe for customer privacy?

The details are hashed before they leave the browser, so Meta receives scrambled strings rather than readable email addresses or phone numbers. That is a real protection, but hashed personal data is still personal data under most privacy law. You still need a lawful basis, a privacy policy that says what is shared, and a consent tool that genuinely blocks it when someone declines.

Why is my event match quality low?

Usually because too few fields are being sent, or because the ones sent are badly formatted. Phone numbers without a country code, addresses with stray spaces or capitals, and values hashed before being normalised all fail to match. Check a real conversion in Events Manager, confirm which fields arrived, and fix the formatting before adding more fields.

Do I need advanced matching if I already use the Conversions API?

They complement each other rather than replace each other. The Conversions API is about how the event reaches Meta; advanced matching is about which identifying details travel with it. An event sent from your server with no customer details attached is just as hard to attribute as a browser event. Send the same normalised fields through both routes.

Related terms

Found this useful?

Share it, or ask an AI to summarise it

Back to the glossary

Knowing the term is the easy part

Applying it to your own site and budget is the work. Book a call and I will tell you what actually applies to you.