What are enhanced conversions in Google Ads and how do I set them up correctly?

What enhanced conversions actually do

Enhanced conversions take the first-party data a customer already gave you at checkout or on a lead form, hash it with SHA-256, and send it alongside the conversion event. Google matches that hashed identifier against signed-in Google accounts to attribute the conversion back to an ad click that the cookie alone lost.

The problem they solve is recovery. Safari and Firefox cap or strip third-party cookies, iOS limits click identifiers, and consent banners block a slice of traffic outright. So a real conversion happens, but Google never connects it to the click that drove it. That click looks like wasted spend. Smart Bidding then optimizes against an incomplete picture. Enhanced conversions hand Google a second way to make the match, so more of your real conversions show up in the account and bidding gets a cleaner signal.

The data never leaves in plain text. Email, phone, first name, last name, and address get hashed in the browser or on the server before transmission. Google compares hashes, not raw values.

The two types are not the same setup

Google ships two separate products under the same name, and people conflate them constantly.

Enhanced Conversions for Web improves measurement for conversions that already fire on your site, like a purchase or a form submit. It supplements the existing conversion with hashed user data so more of those events match. This is the e-commerce path.

Enhanced Conversions for Leads is for businesses that close offline. The lead submits a form, you send the hashed email with the lead, and later you upload the offline conversion (the closed deal) keyed to that same email. Google ties the ad click to the eventual sale. If you run a service business and close on the phone or in person, this is the one you want.

Pick the wrong type and the tag fires but nothing reconciles. Confirm which model matches how the business makes money before you touch anything.

The three setup paths

Google Tag (gtag.js) with automatic collection. The lightest path. You enable enhanced conversions in the conversion action settings, and the tag scrapes user data from the page using CSS selectors or automatic detection. It works, but it is fragile. A theme update that renames a field or moves the confirmation data breaks the scrape silently. I treat automatic collection as a starting point, not a finished build.

Google Tag Manager with manual variables. The path I default to. You capture email, phone, and address into dataLayer variables at the point the user submits, then map those variables into the conversion tag’s user-provided data fields. It survives front-end changes because you control where the data comes from, and you can see the values flowing in GTM Preview before you publish.

The Google Ads API or offline import. For leads that close in a CRM. You push the hashed identifier and the conversion value back through the API or a scheduled upload. This is where value-based bidding gets real fuel, because you can send the actual deal size, not a flat lead value.

What decides your match rate

Setup is half the job. The match rate is what tells you whether it worked, and a few things move it.

Send more fields. Email is the strongest single identifier, but email plus phone plus name plus address gives Google more chances to land a match. Most setups send only email and leave match rate on the table.

Normalize before you hash. Lowercase the email, strip whitespace, format the phone in E.164. Hash a messy string and it will not match the clean hash on Google’s side. GTM’s built-in user-provided data variable handles normalization for you, which is one more reason I prefer it over hand-rolled hashing.

Respect consent. Under Consent Mode v2, enhanced conversions only fire when the user grants ad_user_data and ad_storage. If consent is denied, the data should not be sent. Bolting enhanced conversions onto a site with no consent signal is a compliance problem, and in the EEA it will also throttle what Google can model.

How to verify it is live

Do not trust a green checkmark. Open the conversion action in Google Ads and look at the diagnostics for that action. Within a couple of days of real traffic you should see a recorded match rate. A healthy web setup commonly lands somewhere in the 60 to 90 percent range depending on how many fields you send and how clean the data is. A match rate near zero means the data is not arriving, the hashing is wrong, or consent is blocking it.

Cross-check in GTM Preview or the browser network tab that the user-provided data fields actually carry values when the conversion fires. An empty field hashes to nothing and matches nothing.

Where this sits in the stack

Enhanced conversions are one layer, not the whole tracking system. They make your existing conversion measurement more complete. They do not fix a conversion that never fires, a checkout event that breaks on mobile, or a lead form that GTM cannot see. Get the base conversion firing reliably first, confirm it in a controlled test, then layer enhanced conversions on top to recover the matches the cookie lost. Built in that order, you get a measurable lift in recorded conversions and a Smart Bidding signal that reflects what actually happened.