Enhanced conversions in Google Ads add hashed first-party customer data to your existing conversion measurement so Google can match conversions with earlier ad interactions. Set them up by choosing the correct data flow for on-site actions or later lead outcomes, passing properly formatted user data only when consent allows it, and verifying both the tag and the account diagnostics.
The common failure is not a missing switch. It is a data path that works for one form, one browser or one type of visitor, then quietly sends empty or inconsistent values everywhere else.
What enhanced conversions do
Standard Google Ads conversion tracking records an action such as a purchase, submitted form or qualified lead. Enhanced conversions supplement that measurement with first-party data supplied by the customer, such as an email address, phone number or postal address.
The data is normalized and hashed with SHA-256 before Google processes it for matching. Google compares the hashed value with hashed data associated with signed-in Google accounts. This does not expose a readable email address in Google Ads, but hashing is not a substitute for consent, data minimization or a clear privacy policy.
If an older implementation guide refers to AdWords enhanced conversions, it is referring to the feature now managed inside Google Ads.
Google has combined the account setting for web and lead implementations, but the two data flows still solve different measurement problems. Google’s current enhanced conversions documentation explains the unified setting.
Web and lead implementations are not interchangeable
| Question | Enhanced conversions for web | Enhanced conversions for leads |
|---|---|---|
| Where does the important outcome happen? | On the website | Later, after the website visit |
| Typical action | Purchase, application or submitted form | Qualified lead, booked appointment or completed sale |
| Where is customer data captured? | In the website conversion flow | On the lead form and again in the CRM or sales system |
| What must be sent later? | Usually nothing beyond the website conversion event | The offline outcome and matching identifiers |
| Best fit | Ecommerce and completed on-site actions | Lead generation with a meaningful sales process |
Example: Say a campaign has a $50 target CPA and the website form is counted as its primary conversion. Enhanced conversions for web can support measurement of that submitted form.
If the business later decides that only qualified leads should guide bidding, the lead implementation can import that downstream outcome. The team should not count the form and the qualified lead as if they were the same primary business result.
Before changing the tags, decide which event represents the outcome the buyer actually wants. Enhanced conversion tracking improves the signal attached to that event. It does not decide whether the event itself is useful.
This is also where call and form definitions matter. If both are primary conversions, they need comparable rules. Our guide to counting calls and forms the same way covers that part of the measurement plan.
Choose the setup route that matches the site
An enhanced conversions Google Ads setup can use Google Tag Manager, the Google tag or an API connection. Lead programs also need a reliable route for sending later outcomes through Google Ads Data Manager or a supported API connection.
Choose based on the current tracking architecture. Do not add another tag manager, duplicate a working conversion tag or scrape values from the page merely because a guide used that method.
Google Tag Manager
Google Tag Manager is usually the practical route when the existing Google Ads conversion tags already live there. There are three common ways to make user-provided data available:
- A User-Provided Data variable mapped to stable data layer variables.
- Manual mapping from page elements or JavaScript variables.
- Automatic collection when the site structure and consent implementation support it.
A deliberate data layer is usually easier to maintain than a CSS selector tied to a form theme. A selector such as #email can stop working after a redesign, while a named data layer field can remain stable across layouts.
For an on-site conversion, make sure the user data is available when the conversion event fires. If the email is collected on one step and the conversion fires on another, preserve the value through the approved implementation rather than assuming the confirmation page still contains it.
Google’s Tag Manager setup guide covers automatic, manual and code-based configurations.
The Google tag
Use the Google tag route when the site already sends Google Ads conversions directly through gtag.js. The user_data object can carry the approved identifiers with the conversion event.
Keep the implementation close to the source of truth. If the checkout application already exposes a validated email and phone number, use those values. Do not scrape a formatted confirmation message if structured values are available.
API and lead imports
An API route gives the engineering team more control over formatting, event timing and deduplication. It also creates more places for a quiet failure, so ownership and monitoring need to be explicit.
For leads, collect an eligible identifier on the form and retain the click identifier when available. When the lead reaches the agreed stage, send the offline conversion with the same normalized customer identifier and a stable deduplication key.
The web event and later CRM event must refer to the same person consistently. [email protected], [email protected] and a blank CRM field are not equivalent inputs until the normalization and mapping rules handle them correctly.
Implement the complete data path
Treat setup as a short measurement project, not a checkbox.
Map the conversion before touching the tag
Write down:
- The Google Ads conversion action.
- The exact event that should trigger it.
- Where the email, phone number or address becomes available.
- Which consent signal must be present.
- Whether the outcome happens on the website or later.
- Who owns the website tag, consent platform and CRM import.
For lead programs, define the downstream status precisely. “Qualified lead” should correspond to one stable CRM state, not several statuses interpreted differently by different users.
Enable enhanced conversions
In Google Ads, review the enhanced conversions setting under the conversion and customer data controls. Accept the applicable customer data terms, then confirm which conversion actions should receive user-provided data.
Enabling the setting does not prove that a tag is sending usable values. It only permits Google Ads to process eligible data when the implementation supplies it.
Normalize identifiers consistently
Email addresses should be trimmed and converted to lowercase. Phone numbers should include the country code and follow a consistent international format. Address matching requires the required name, country and postal fields.
Google tags can hash correctly formatted data before it reaches Google’s servers. If your team hashes the values before passing them to the tag or API, use hexadecimal SHA-256 and follow Google’s normalization rules first. Hashing an incorrectly formatted value preserves the error.
Do not put customer data in page URLs. Query strings can travel into browser history, analytics tools, server logs and unrelated integrations.
Handle consent before data collection
The consent platform should initialize before the Google tag attempts to use customer data. For regions where consent is required, the ad_user_data signal controls whether data related to advertising may be sent. ad_storage controls advertising-related storage.
Test both consent paths. A granted path should send the intended identifiers. A denied path should respect the denial. A banner that updates after the conversion tag fires can leave the account with inconsistent behavior.
Google’s consent mode reference describes the relevant consent signals. Your privacy or legal team should decide what the business may collect and under which conditions.
This same discipline applies when implementing Meta’s server-side measurement. The platforms differ, but consent timing, event definitions and deduplication still need explicit checks. See the Meta Conversions API checklist for agency accounts.
Common mistakes and the checks that catch them
The conversion fires before the data exists
A form listener may fire when the visitor clicks Submit, while validation or an asynchronous request is still running. The conversion records, but the user data variable is empty.
Trigger the conversion only after the success condition is confirmed. In a single-page application, listen for the application’s success event rather than relying on a page view that may never occur.
The same action fires twice
A thank-you page tag, a form-success listener and an imported CRM event can all count the same outcome. Enhanced conversions do not deduplicate unrelated conversion actions automatically.
Use transaction IDs or stable event identifiers where supported. Decide whether an on-site lead and a later qualified lead are separate funnel stages or competing versions of the same primary goal.
Automatic collection works on only part of the site
Automatic collection can appear healthy during one desktop test and miss a different form, mobile layout, embedded form or checkout path. The account then receives enhanced data for only part of its eligible conversions.
Test every template that can produce the conversion. If coverage varies, map stable data layer variables instead of depending on page detection.
A selector breaks after a site change
A developer changes a field ID, a form vendor replaces its markup or the confirmation page stops displaying the email address. The standard conversion still fires, so the failure is easy to miss.
Give critical fields stable names in the data layer. Include enhanced conversion checks in the release checklist for form, checkout and consent changes.
The lead import uses different data
The website sends an email, but the CRM later stores a shared office address, a corrected address or no identifier at all. The import completes without providing the matching value expected from the form.
Preserve the original eligible identifier alongside the cleaned CRM record. Continue retaining click IDs where available. Do not make email matching carry the entire process if the lead system can maintain stronger attribution inputs.
Hashing is treated as consent
Hashed customer data is still being processed for advertising measurement. A technically correct hash sent without the required consent is not a correct implementation.
Check the consent state in the same browser session in which you test the conversion. Do not infer consent from the presence of a banner cookie without confirming what the tag received.
Tag Assistant is treated as the finish line
Use Google Tag Manager preview mode or Tag Assistant to trigger a test conversion. Confirm that the conversion tag fires once and that the enhanced conversions parameter is present, populated and free of formatting errors.
Then check Google Ads. Open the conversion action, review its status and inspect enhanced conversions diagnostics for missing fields, empty values, formatting problems or gaps in coverage. Google explains the available checks in its enhanced conversions diagnostics guide.
Repeat the check after meaningful site releases. A working launch test does not protect the implementation from a later form or consent change.
Frequently asked questions
What are enhanced conversions in Google Ads?
Enhanced conversions supplement existing Google Ads conversion tracking with hashed first-party customer data, such as an email address or phone number. Google uses that data to help match a conversion with an earlier ad interaction.
What is the difference between enhanced conversions for web and for leads?
Enhanced conversions for web support conversions completed on the website, such as a purchase or form submission. Enhanced conversions for leads connect customer data collected online with qualified leads, sales or other outcomes recorded later.
Do enhanced conversions need consent?
Enhanced conversions need the appropriate consent wherever applicable, and hashing does not remove that obligation. Your tag and consent platform should send the correct ad storage and ad user data signals before customer data is processed.
How do you check enhanced conversions are working?
Trigger a real test conversion in Tag Assistant or Google Tag Manager preview mode and confirm that the conversion fires once with a populated enhanced conversions parameter. Then review the conversion action and enhanced conversions diagnostics in Google Ads for missing, empty or incorrectly formatted data.
Are enhanced conversions worth setting up?
They are worth evaluating when an advertiser already has sound conversion actions and collects eligible first-party data with the required consent. They improve the measurement input, but they do not repair duplicate tags, weak lead definitions or broken CRM imports.
What Ads Arsenal adds to the measurement workflow
Ads Arsenal reads the actual numbers from Google, Meta and TikTok and presents recommended account changes with the reasoning and supporting data. Nothing changes until a buyer approves it, and approved changes are checked after they land and can be rolled back.
Design partners also get Conversion Arsenal on the same login. It provides first-party, server-side tracking of leads and sales by landing page and channel, with ad spend, cost per lead and MER on one screen. Feeding lead value and closed sales from Conversion Arsenal back into Ads Arsenal is coming.
Ads Arsenal is in a free design-partner beta for agencies and in-house teams running real spend on Google, Meta and TikTok. Become a design partner.