How enhanced conversions work
Browsers now block or shorten many of the cookies that conversion tracking used to rely on, so a sale can happen without Google being able to connect it back to the click that caused it. Enhanced conversions close part of that gap using information the customer gave you anyway.
When someone converts, the details already on the page — usually an email address, sometimes a phone number, name or address — are turned into an irreversible hash before they leave the browser or your server. The plain values never reach Google. That hash is sent alongside the conversion, and Google compares it with the hashed details of signed-in accounts that saw or clicked your ads. Where the two agree, the conversion is credited to the right campaign.
There are two versions. Enhanced conversions for web improve the conversions you already record on the site. Enhanced conversions for leads carry the same hashed identifier through your sales process, so that when a lead becomes a customer weeks later you can upload that outcome and attribute it to the original click.
Why enhanced conversions matter
Bidding is only as good as its feedback. If a share of real sales never reaches the account, automated bidding is optimising towards an incomplete picture, and it will quietly underbid on the audiences and keywords whose results went missing. Recovering those conversions usually improves the bidding before it improves any report.
For anything with a long sales cycle — education consultancies, property, business-to-business services, remittance sign-ups — the leads version matters more than the web version, because the money arrives long after the click and would otherwise never be connected to it at all.
Where enhanced conversions go wrong
The commonest fault is silent: the setting is switched on but the customer details are never actually captured, because the confirmation page shows a thank-you message without the email in the page or in the data layer. Google reports the feature as active while matching almost nothing.
Consent is the second problem. In regions covered by consent requirements, sending customer data without a valid marketing consent is not acceptable, and consent settings have to be wired in properly rather than assumed. The third is double counting, where the same conversion is sent through both the tag and an upload without a shared order identifier to reconcile them.
How to act on it
Decide first whether the data exists. If your thank-you page or your data layer carries an email address, this is worth doing; if not, that is the job to fix before touching the setting. Then choose one implementation route — the Google tag, Tag Manager, or the API — rather than mixing them, and confirm in the diagnostics that details are genuinely being received rather than trusting the toggle.
Treat it as an upgrade to a working setup, not a replacement for one. If the underlying conversion tracking is already misfiring or counting the wrong actions, better matching only spreads the error further. Fix the foundation, then improve the match rate, and give the account time before comparing figures, since matching applies from the day it starts working.
