Skip to content

Google AdsPublished 8 min read

Google Ads Enhanced Conversions Setup Guide

Enhanced conversions for web and for leads explained, with a practical GTM setup, normalization rules, diagnostics and the mistakes that quietly break it.

Muhammad Qitmeer, founder of Augere Labs
Muhammad Qitmeer
Co-founder and CEO, Augere Labs
Share

Enhanced conversions send hashed first-party data, such as the email address or phone number someone entered in a form, along with your conversion so Google can match it to a signed-in Google account and recover conversions that cookies alone would miss. Enhanced conversions for web improves online conversion tracking; enhanced conversions for leads uses the same hashed data to match offline outcomes, like a closed deal in the CRM, back to the ad click. For most lead generation accounts with a form that collects an email, setting it up is one of the highest value, lowest effort tracking jobs you can do.

This guide covers both flavors, how to configure them through Google Tag Manager, how to format the data so it actually matches, how to read the diagnostics, and the mistakes we see most often in client accounts.

Enhanced conversions for web vs for leads

The names are similar and the setup overlaps, but they solve different problems.

Enhanced conversions for webEnhanced conversions for leads
What it improvesOnline conversions recorded by the website tagOffline conversions imported later from the CRM
When data is sentAt the moment of conversion, with the conversion tagCaptured at form submit, then matched when you upload the offline outcome
Identifier used to matchHashed email, phone, name and address, alongside the cookieHashed email or phone in the upload, instead of or in addition to the gclid
Typical useRecovering form and purchase conversions lost to browser privacy limitsImporting qualified leads or won deals without relying on stored gclids

Google has been consolidating the two into a single account-level enhanced conversions setting, so depending on when the account was set up you may see them configured together or separately. Either way, the website side is the same: capture the user-provided data at the point of conversion and send it with the tag.

Before you start

  • Access. You need admin or standard access to the client's Google Ads account and publish rights in their GTM container.
  • Customer data terms. Enhanced conversions requires accepting Google's customer data terms in the account. This is a commitment the client makes about how the data was collected and disclosed, so confirm with them that their privacy policy covers sharing hashed data with advertising partners. Do not accept on their behalf without asking.
  • A conversion that already works. Enhanced conversions improves a working conversion tag; it does not replace one. If the base conversion double fires or fires on the wrong action, fix that first. The conversion tracking setup guide covers the basics.
  • Consent. If the site serves visitors in the EEA or UK, consent mode should be in place and the ad_user_data consent signal set correctly, because it governs whether user data can be sent to Google for advertising. See the consent mode v2 implementation guide.

Turning it on in Google Ads

In the client's account, open the conversion settings and turn on enhanced conversions, accept the customer data terms, and choose how data will be provided: through the Google tag, through Google Tag Manager, or through the API. For an agency managing the site's tags in GTM, choose Google Tag Manager. Menu labels move around, so look for enhanced conversions in the account-level conversion settings or on the individual conversion action if the account still uses per-action settings.

If the conversion action is an imported GA4 key event rather than a native Google Ads tag, the website data is collected through GA4 instead. In that case you enable user-provided data collection in the GA4 property and send the data with the GA4 event. The principle is the same; the configuration lives in a different product.

Setting it up in GTM

In the Google Ads Conversion Tracking tag, tick the option to include user-provided data from your website, then select or create a User-Provided Data variable. That variable offers three ways to collect the data.

Option 1: Automatic collection

GTM scans the page for something that looks like an email address or phone number and sends it. It is quick to switch on, but it guesses. On pages with more than one form, or where the confirmation page no longer shows the email, it can pick up the wrong value or nothing. Use it only as a stopgap.

Option 2: Manual configuration

You tell GTM where each field lives, either with a CSS selector pointing at the form input or with an existing GTM variable. CSS selectors work when the conversion tag fires on the same page as the form, at a moment when the inputs still contain the values. They break when:

  • The form redirects to a thank-you page before the tag fires, so the inputs no longer exist.
  • The form clears its fields on success before the tag reads them.
  • A site redesign changes the class names or IDs.
  • The form sits inside an iframe, such as many embedded booking widgets, which GTM on the parent page cannot read.

Option 3: Data layer or code

The most reliable approach is to push the user data into the data layer at the moment of successful submission, then map data layer variables into the User-Provided Data variable.

dataLayer.push({
  event: 'generate_lead',
  form_id: 'quote',
  user_data: {
    email: 'jane@example.com',
    phone_number: '+15555550123'
  }
});

In GTM, create data layer variables for user_data.email and user_data.phone_number, reference them in the User-Provided Data variable, and fire the conversion tag on the generate_lead custom event. This survives redesigns, works on multi-step forms, and the data is available even when the success state replaces the form. It needs a developer or a form plugin that supports custom data layer pushes, which is why many agency setups start with CSS selectors and move to this later.

Normalization and hashing

Matching only works if the data is formatted the way Google expects. When you send plain values through the Google tag or GTM, the tag normalizes and hashes them with SHA-256 before sending. You still need to make sure the raw values are sensible:

  • Email: trimmed of leading and trailing spaces. Lowercasing is handled, but sending a field that contains the name instead of the email is not.
  • Phone: in E.164 format, with a plus sign and the country code, such as +15555550123. A local number without a country code is a frequent reason phone matching fails.
  • Name and address: optional, but if you send them, send first name, last name, postal code and country together. Partial address data is of limited use.

If you hash the data yourself, for example on the server or in a custom template, you must normalize first (trim, lowercase, format the phone), then hash with SHA-256 and send the hex string. Hashing an un-normalized value produces a hash that will never match. Do not hash twice: if you send pre-hashed values, make sure the tag knows they are already hashed.

Verifying the setup

In GTM Preview

Submit the form with a real test email and phone. In the Tag Assistant view, open the conversion tag that fired and inspect its user-provided data. You should see the email and phone values populated. If the fields are empty or undefined, the variable is reading from the wrong place or at the wrong time.

In the network request

In the browser's developer tools, find the conversion request. Enhanced conversion data is sent hashed, so you will not see the email in plain text; you are checking that user data parameters are present at all.

In Google Ads diagnostics

Each conversion action has a diagnostics view that reports on enhanced conversions after data has been flowing for a while, typically a couple of days. It shows whether enhanced conversions data is being received, how much of the conversion volume includes user-provided data, and warnings about formatting or match problems. Common warnings include low coverage (most conversions arriving without user data) and formatting issues with phone numbers or emails.

Coverage is the number to watch. If the form always collects an email but coverage is low, the tag is firing in places where the data is not available, or a second untagged conversion source is also sending hits.

Multi-step forms and booking widgets

Multi-step forms often collect the email on step one and confirm on step three. If the conversion fires on the final step, the email input may no longer be on the page. Push the email into the data layer when it is entered, or have the form push it with the success event. Embedded booking tools in iframes need their own success event passed to the parent page, ideally with the email included, because GTM on the parent page cannot read inside the iframe.

Enhanced conversions for leads: the extra steps

For leads, the website side captures hashed data at form submission. The offline side is where the value appears: when the lead later becomes qualified or closes in the CRM, you upload that outcome with the lead's email or phone. Google matches the hashed identifier back to the original ad interaction, which means you can import outcomes even for leads where the gclid was never captured.

The practical requirements:

  • The CRM must store the same email or phone the person entered on the form.
  • The offline conversion action must be set up to accept uploads with user-provided data.
  • Uploads must happen reasonably soon after the outcome and within the conversion action's window.

The full import process, including how to map CRM stages to conversion actions, is covered in offline conversion import from your CRM.

Common mistakes

  • Relying on automatic collection on a site with several forms. It grabs whatever it finds first, including newsletter fields in the footer.
  • CSS selectors on a redirecting form. The thank-you page has no form, so nothing is sent. Coverage stays near zero and nobody notices.
  • Phone numbers without country codes. Local formats rarely match. Format to E.164 before sending.
  • Hashing un-normalized values. A trailing space or capital letter produces a completely different hash.
  • Turning it on and never checking diagnostics. Enhanced conversions can show as active while sending almost no usable data.
  • Ignoring consent. For EEA and UK traffic, user data should only be sent when the visitor has consented to it. A setup that ignores consent is a compliance problem for the client, not just a tracking problem.
  • Setting it up on GA4 and on the Google Ads tag for the same action. That usually means two sources for one conversion, which is a duplication problem before it is an enhanced conversions problem.

What we check in an audit

  • Whether enhanced conversions is enabled and customer data terms accepted.
  • Which method collects the data, and whether it can read the fields at the moment the tag fires.
  • Phone and email formatting in real test submissions.
  • Coverage and warnings in each action's diagnostics.
  • Consent signals for regions where they apply.
  • Whether the CRM stores the same identifiers, ready for enhanced conversions for leads.

Next step

Enhanced conversions is part of every Google Ads conversion tracking fix we do. If you want to know whether a client's setup is actually sending usable data, the sample audit shows what the report looks like.

Just one quick fix, not a whole account? Our founder takes small fixed-price jobs on Fiverr: Google Ads conversion tracking fix

Frequently asked questions

Do I need enhanced conversions if I already have a conversion tag?

If the form collects an email or phone number, yes. It adds hashed first-party data to the conversions you already track, which helps Google recover conversions that cookies alone would miss.

Is the data sent in plain text?

No. When sent through the Google tag or GTM, values are normalized and hashed with SHA-256 before they leave the browser. If you hash yourself, normalize first so the hashes match.

Which GTM collection method is best?

A data layer push on confirmed submission is the most reliable. CSS selectors work when the tag fires on the same page as the form; automatic collection is a stopgap.

How long before diagnostics show results?

Usually a couple of days of normal conversion volume. Low-volume accounts can take longer before the diagnostics have enough data to report.

What is enhanced conversions for leads used for?

It lets you upload offline outcomes, such as qualified leads or closed deals, using the lead's hashed email or phone instead of a stored gclid, so CRM results can still be matched to ad clicks.

Muhammad Qitmeer

Written by

Muhammad Qitmeer, founder of Augere Labs

Augere Labs is the white-label tracking partner behind marketing agencies. If a client account has numbers you don't trust, I'm happy to look at it with you and tell you straight what's wrong.

Connect on LinkedIn