Cookies don't last as long as they used to, and many conversions can no longer be tied back to the ad click that led to them. Enhanced conversions are Google's way of filling some of that gap with data your customers have already given you.
What they are.
When someone converts on your site, the Google Ads tag can send first-party data they provided, such as an email address, name, home address or phone number, alongside the conversion. Before it leaves the browser, it's hashed with SHA256, a one-way algorithm.
Google compares the hash with hashed data from signed-in Google accounts that engaged with your ads, and credits the ad when they match.
The result is more conversions measured, and better data for bidding to learn from.
Web or leads.
- Enhanced conversions for web are for conversions that happen on the website, such as a purchase or a sign-up
- Enhanced conversions for leads are for sales that happen off the website, such as a lead from a form that closes later by phone. The tag captures hashed data when the form is sent, and you later import the closed sales with the same hashed data.
Google says the two will soon be combined into a single on and off setting, with existing accounts moved over automatically. For leads, Google also says that from 15 June 2026, uploads moved to its Data Manager API and are blocked in the Google Ads API, so older upload scripts need checking.
Setting them up.
In Google Ads, the setting sits under Goals, Settings, in the "Enhanced conversions" section. Turning it on asks you to accept the customer data terms, and Google says no user-provided data is collected until you do. You then choose a method:
- The Google tag, for sites using it directly
- Google Tag Manager, using a User-Provided Data variable. It can detect the data automatically, read it from the page with CSS selectors, or take it from code, which is the most reliable when the data is in the dataLayer.
- The Google Ads API, for businesses sending conversions from their own systems
Format the data before it's hashed: trim spaces, use lowercase, and write phone numbers in E.164 format with a plus sign and country code. Data hashed in the wrong format won't match anything.
Consent and the customer data terms.
Enhanced conversions use personal data, so consent matters. In Consent Mode v2, when ad_user_data is denied, Google lists enhanced conversions among the features switched off. Make sure your banner sets that signal, not just ad_storage.
Google's customer data policies apply too. You must tell customers that you share their information with third parties, and get consent for it where the law requires. You can't upload data you know relates to children under 13, and conversions in sensitive categories, such as health, can't be measured with enhanced conversions.
Your privacy notice should say plainly that hashed contact details are shared with Google for ad measurement.
How to check they're working.
- Convert on your site with Chrome's developer tools open, and look for the
emparameter in the Google Ads conversion request - Repeat with consent refused, and check the data isn't sent
- After about 72 hours, open the diagnostics for the conversion action in Google Ads and look for warnings
- After about 30 days, check the impact Google reports in the conversion actions table
The diagnostics often show a low match rate when the data is captured from the wrong field, or when the conversion page no longer has the email on it. That's usually a tagging fix, not a reason to give up on the feature.
Marc Alexander sets up enhanced conversions as part of conversion tracking, with consent handled through Consent Mode v2. The GA4 mini audit checks whether yours are sending what Google expects.
Sources.
- Google Ads Help: About enhanced conversions
- Google Ads Help: Set up enhanced conversions for web using the Google tag
- Google Ads Help: Set up enhanced conversions for web using Google Tag Manager
- Google Ads Help: About enhanced conversions for leads
- Google Advertising Policies Help: Customer data policies
- Google for Developers: Consent mode overview
Checked on 31 October 2026.