What Actually Gets Sent
Advanced matching parameters, sometimes called match keys, are sent SHA-256 hashed. You never transmit a raw email address. You normalize it, lowercase it, trim it, hash it, and send the digest. The platform does the same to its own records and compares digests, so neither side reveals a plaintext identifier to the other.
The fifteen parameters split cleanly into two groups, and the split explains almost everything about why affiliate EMQ scores sit where they do.
The five that arrive by themselves. Two Meta browser identifiers, fbc and fbp, plus the client IP address and the user agent. All four come with the click, because the browser and the ad platform put them there. Email is the fifth, and only when your own page collected it. Any competent server-side setup carries these.
The ten that require deliberate capture. Phone, first name, last name, date of birth, gender, city, state, zip, country, and external ID. None of these arrive on their own. Somebody has to ask the customer for them, store them against the click, and forward them with the conversion on purpose.
Five match keys arrive without anyone asking for them; the ten that lift Event Match Quality exist only because somebody collected them and stored them against the click.
Why Advanced Matching Changes Your Cost Per Acquisition
The mechanism is simpler than the jargon suggests. A conversion the platform cannot match to a user is a conversion it cannot learn from. It counts in your total, but it teaches the algorithm nothing about who to find next, because the algorithm never established who this buyer was.
More match keys means more successful matches, and more successful matches means a richer training set for the optimization model. That shows up as a lower acquisition cost on identical budget and identical traffic, which is why Event Match Quality is worth treating as a performance metric rather than a diagnostic. A conversion event with five parameters and one with fifteen are both "a conversion" in your dashboard. They are not the same instruction to the algorithm.
There is a second effect that matters more in 2026 than it did three years ago. Browser-side identifiers keep getting shorter-lived and easier to lose, so the share of conversions that can be matched on click identifier alone keeps shrinking. Hashed identity fields do not decay the same way. As the browser signal weakens, advanced matching is the part of the payload that holds.
Why Affiliates Score Lower Than Ecommerce Advertisers
This is the part that gets skipped in every generic explanation, and it is the whole story for anyone running network offers.
An ecommerce advertiser owns the checkout. The name, email, phone, and billing address are typed into a form on their own domain, so the ten deliberate fields are already sitting in their database when the conversion fires. Advanced matching for them is a configuration task.
An affiliate does not own the checkout. On a ClickBank, CPA network, or vendor offer, the buyer leaves your page and completes the purchase somewhere else. What comes back to you is a postback carrying a click identifier and a payout amount. The identity was collected, just not by you. So the ten fields are not switched off in your setup, they were never available to it. That is a structural position, not a misconfiguration, and it is why a well-built affiliate setup can sit at a mediocre Event Match Quality while doing nothing wrong.
The fix is not a setting. It is capturing identity earlier, on a page you control, before the handoff. An email capture, a quiz, a pre-sell opt-in, a lead form: anything that collects real identity against the click before the customer walks out the door. Then those fields have to survive the round trip and be attached to the conversion when the network postback lands, which is a job your tracker either does or does not do.
Advanced Matching Is Not the Same as CAPI
These two get used interchangeably and they are different things.
The Conversions API is the transport. It is how the event gets from your server to the platform's server without depending on a browser.
Advanced matching is the payload. It is what is inside the event when it arrives.
You can run a perfectly healthy Conversions API integration that fires every conversion reliably and still carry five parameters. The pipe is fine. The contents are thin. Confusing the two is why plenty of buyers who "set up CAPI properly" are surprised their Event Match Quality never moved, and it is why "does this tracker support CAPI" is the wrong question. The better question is how many of the fifteen it can actually carry.
ClickerVolt is built around that second question: it stores identity captured on your pages against the click and forwards all fifteen Meta parameters with the conversion, rather than sending the five that arrive for free. See how the full-parameter signal works. Whatever tracker you run, check your Event Match Quality score before you change anything else, because it tells you in one number how much of your conversion the platform could actually read.
FAQ
What is advanced matching in simple terms?
It is sending hashed customer details, things like email, phone, name, and location, along with a conversion event so the ad platform can identify which of its users made the purchase. Better identification means better optimization, because the algorithm can learn who your buyers actually are instead of just counting that a sale happened.
How many advanced matching parameters does Meta support?
Meta accepts fifteen customer-information parameters on a conversion event. Five arrive without being asked for: the browser identifiers fbc and fbp, the client IP address, the user agent, and an email when your own page collected one. The other ten, phone, first name, last name, date of birth, gender, city, state, zip, country, and external ID, only arrive if you deliberately capture and forward them.
Is advanced matching the same as the Conversions API?
No. The Conversions API is the transport that moves the event from your server to the platform's server. Advanced matching is what is inside that event. A working Conversions API integration can still carry a thin payload, which is why a correct setup does not automatically produce a good Event Match Quality score.
Why is my Event Match Quality score low as an affiliate?
Most likely because the checkout is not on your page. On network offers the customer gives their identity to the vendor, and you receive a postback carrying a click identifier and a payout. The ten identity fields were never available to your tracker. The fix is capturing identity on a page you control before the handoff, then forwarding it with the conversion.
Does advanced matching share personal data with the ad platform?
Not in plaintext. Parameters are normalized and SHA-256 hashed before they are sent, and the platform hashes its own records the same way to compare digests. You should still only collect and forward data you have a lawful basis to process, and reflect it in your privacy policy and consent flow.
