Enhanced conversions
enhanced conversions for leads / hashed email matching / first-party data matching / UET enhanced conversions
Enhanced conversions send a hashed version of your customer's email address or phone number to the ad platform, which matches it against its own signed-in account holders. Both platforms describe it as a replacement for third-party cookies, and both match against their own user base.
Both platforms describe the same machinery in almost the same words, which is usually a sign a definition has settled rather than a vendor writing a brochure.
Microsoft says enhanced conversions supplement existing conversion tracking using first-party data, and that first-party data is more reliable than third-party data. It then names the substitution directly: instead of using a third-party cookie with the Microsoft user ID, enhanced conversions allow the use of first-party information such as an email address or phone number. Google describes its version as supplementing the existing conversion tags by letting advertisers send hashed first-party customer data from the website in a privacy-safe way.
The part worth reading slowly is what the hash is compared against. Microsoft says it attributes hashed emails or phone numbers to the relevant ad campaign by matching advertiser data to user activity on Microsoft properties. Google says the hashed customer data is compared to hashed customer data of signed-in Google accounts. In both cases your customer is being looked up in the platform's own directory of account holders.
There is a prerequisite that decides whether this is even possible, and Microsoft states it plainly: first-party customer data, an email address or phone number, has to be available on the page where your conversion tracking tag fires. So it works on a confirmation page that knows who just converted, and not on one that does not.
Google publishes a figure for the benefit, and it is worth quoting as its own claim rather than as a finding. It reports that advertisers using first-party data alongside click IDs for offline measurement saw a median 10% increase in conversions compared with standard offline conversion imports.
In practice
This is usually presented to a business as a tracking improvement, which it is, and rarely as a data decision, which it also is. The question to settle before switching it on is not whether hashing protects the address, since hashing is real, but whether your consent arrangements cover sending customer contact details to an advertising platform for matching at all.
Not the same as
- Offline conversion import
- That sends back a click ID for a sale that happened later. This sends contact details so the platform can identify the person.
- Uploading a customer list
- That builds an audience to advertise to. This attributes a conversion that already happened.
Why it matters to you
The industry is replacing third-party cookies, and both platforms say so in their own documentation for this feature. The replacement is first-party data, which means the data is yours and the decision to send it is also yours. That is a better position than the old one, and it only stays better if somebody actually makes the decision rather than accepting a default during a setup call.
What to ask or check
- 01Does our consent notice cover sending hashed contact details to an advertising platform?
- 02Which pages carry the customer's email or phone at the moment the tag fires?
- 03Was this switched on deliberately, or during a setup someone else ran?
What people get wrong
That hashing means nothing identifiable is shared. The hash is the point of comparison: both platforms match it against hashed data they already hold for their own signed-in users, which is how the attribution works at all.
Red flags
- Enabled during a setup call with no discussion of what data leaves the site.
- A consent notice that predates the feature and never mentions advertising platforms.
- A promised accuracy gain quoted without saying which platform reported it.
Who owns it
You do: it is your first-party data and your consent notice. The platform supplies the matching and states in its own documentation what it matches against.
Where you will see it
In the conversion goal setup on both platforms, usually as a switch during creation.