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.
