Google Ads Enhanced Conversions: A Complete Guide for Web and Leads

Google Ads conversion tracking is no longer just a matter of placing a tag on a thank-you page. Browser restrictions, consent choices, cross-device journeys and sales that complete inside a CRM can all prevent an ordinary website conversion tag from seeing the complete outcome.

Enhanced conversions helps close part of that measurement gap. It supplements existing conversion data with consented, first-party customer information such as an email address or telephone number. That information is normalised and hashed using SHA-256 before Google uses it for matching.

This does not replace standard Google Ads conversion tracking. It improves the matching available to it. For lead-generation businesses, it can also connect later CRM outcomes—such as a Qualified Lead or Closed Sale—with the advertising interaction that generated the original enquiry.

The result can be more complete measurement and better-quality information for automated bidding. However, enhanced conversions is not a cure for poor tracking design. Duplicate tags, weak sales-stage definitions, missing consent controls or inaccurate CRM data will still produce unreliable results.

What Are Google Ads Enhanced Conversions?

Enhanced conversions is a first-party data feature within Google Ads. When a customer supplies information directly to a business—for example, by completing a form, booking an appointment or purchasing online—that information can be sent to Google in hashed form and matched with data from consented, signed-in Google users.

Google can then use the match to attribute eligible conversions to ad interactions such as clicks and video views that might otherwise be difficult to observe.

Enhanced conversions works alongside the underlying conversion action. The standard conversion still needs a clear event, such as:

• A completed purchase

• A successfully submitted enquiry form

• A booked appointment

• A Qualified Lead recorded in a CRM

• A Closed Sale or Converted Lead

The enhanced data improves matching; it does not decide whether the business event genuinely happened.

Google has now combined Enhanced Conversions for Web and Enhanced Conversions for Leads into a unified on/off setting. The account can accept user-provided data from website tags, Data Manager and supported API connections without forcing the advertiser to select only one method.

This consolidated control does not make the two measurement use cases identical. Website conversions and later CRM conversions still have different triggers, data flows and implementation requirements.

Enhanced Conversions for Web vs Enhanced Conversions for Leads

The most important decision is not which toggle to select. It is what business event you are trying to measure.

A service company can use both. Enhanced Conversions for Web can strengthen measurement of the initial enquiry, while Enhanced Conversions for Leads can report when that enquiry becomes qualified and later turns into revenue.

An ecommerce business may primarily use Enhanced Conversions for Web for online purchases. If orders are later confirmed, amended or completed in another system, it may also send backend conversion data with the same transaction ID so Google can deduplicate the event correctly. Our separate guide explains the distinction between website and offline conversion tracking for ecommerce.

How Enhanced Conversions for Web Works

Enhanced Conversions for Web supplements an existing website conversion action.

A typical process is:

1. A user engages with a Google advert and visits the website.

2. The user completes an eligible website action, such as submitting a form or placing an order.

3. The Google Ads conversion tag records the conversion event.

4. Consented first-party customer data available during the conversion journey is normalised and hashed.

5. Google attempts to match that data with consented, signed-in Google user data and eligible ad interactions.

6. The conversion action reports the matched result in Google Ads.

This is particularly useful when the ordinary advertising identifier is unavailable or when a customer interacts on one device and converts on another.

Google’s official overview of enhanced conversions explains that the feature supplements—rather than replaces—the existing conversion.

How Enhanced Conversions for Leads Works

Enhanced Conversions for Leads is the current upgrade path from conventional offline conversion import. It combines later sales outcomes with user-provided data and available advertising identifiers.

A typical lead-generation process is:

1. A prospect interacts with a Google advert.

2. The prospect completes a form, call, chat or booking action.

3. The business stores the contact, attribution data and consent status in its CRM.

4. The sales team or an automated process updates the record as the lead progresses.

5. A selected CRM event—such as Qualified Lead or Closed Sale—is sent to Google Ads with the required identifiers, timestamp, value and unique Order ID.

6. Google matches the later event with eligible ad interactions and reports it against the relevant conversion action.

The important difference is that the initial website enquiry and the later commercial outcome are separate events. A form submission tells Google which adverts generate leads. A Qualified Lead or Closed Sale tells Google which adverts generate the right leads.

For a detailed implementation model, see our Google Ads CRM integration guide and offline conversion tracking guide.

What Customer Data Can Be Used?

Enhanced conversions can use first-party information that a customer supplies directly to the business. Depending on the implementation, supported data can include:

• Email address

• Telephone number

• First and last name

• Home address details

Email and telephone number are normally the most practical identifiers for lead-generation businesses. Name and address should be sent only when required fields are available and the data has been collected for an appropriate purpose.

The source data needs to be formatted consistently before hashing. For example, telephone numbers should include the correct country code, while email addresses should be trimmed and normalised. A technically successful upload can still achieve poor matching if the source data is incomplete, stale or incorrectly formatted.

Hashing Does Not Make the Data Anonymous

Google uses the SHA-256 one-way hashing algorithm for customer data used by enhanced conversions. Hashing transforms the normalised source value into a fixed string before matching.

This is a security and data-processing control, but it should not be described as automatic legal compliance or complete anonymisation. The business still controls why the data was collected, what users were told, whether the required consent was obtained, how long data is retained and which systems receive it.

For UK advertisers, the implementation should be assessed against UK GDPR, PECR, Google’s customer-data policies, the organisation’s privacy notice and its consent-management design. Consent Mode communicates consent choices to Google tags; it does not provide a consent banner or determine the organisation’s lawful basis.

Benefits of Enhanced Conversions

Enhanced conversions can improve advertising measurement, but the benefit depends on data quality, volume and implementation accuracy.

More Complete Conversion Measurement

Hashed first-party data provides an additional matching signal when other identifiers are unavailable. This can recover eligible conversions that an ordinary tag might not associate with an advert.

It is better to describe this as improved measurement coverage than guaranteed extra sales. Enhanced conversions can change the number of conversions Google can attribute without changing the number of customers the business actually acquired.

Better Cross-Device and Engaged-View Attribution

Matching against consented, signed-in Google users can help connect journeys across devices. Enhanced Conversions for Leads can also support engaged-view attribution where eligible, which is particularly relevant to video-led journeys.

Lead-Quality Feedback

For lead generation, the greatest strategic benefit is not recovering an extra form submission. It is sending later outcomes back to Google Ads.

If the CRM reports Qualified Leads, Sales Opportunities and Closed Sales accurately, campaign evaluation can move beyond cost per lead towards:

• Cost per Qualified Lead

• Cost per Sales Opportunity

• Customer acquisition cost

• Revenue and pipeline value

• Return on advertising spend

This is a central part of improving Google Ads lead quality.

Stronger Inputs for Smart Bidding

Automated bidding can only optimise towards the conversion actions and values it receives. Clean lower-funnel data can help Google distinguish enquiries that became customers from low-value or irrelevant leads.

This does not mean every CRM stage should immediately become a primary conversion. Deeper events must first be validated, imported consistently and allowed to accumulate enough volume. The relationship between measurement and bidding is covered in our guides to primary and secondary conversions and value-based bidding.

Greater Measurement Durability

Enhanced conversions adds consented first-party data to the measurement architecture instead of relying on a single browser identifier. It can therefore make attribution more resilient, although it does not eliminate the effects of consent choices, browser controls, data loss or platform modelling.

What Enhanced Conversions Does Not Do

Enhanced Conversions is often over-sold. It does not:

• Replace the ordinary Google Ads conversion event

• Repair a form trigger that fires before a successful submission

• Prevent duplicate conversions unless unique identifiers and event logic are designed correctly

• Make poor-quality CRM data reliable

• Turn every imported lifecycle stage into a useful bidding signal

• Guarantee GDPR or PECR compliance simply because data is hashed

• Automatically make Google Ads revenue identical to CRM or finance revenue

• Replace Customer Match or automatically create every remarketing audience

Google now offers a separate conversion-based customer-list control. Audience activation and conversion measurement may use related first-party data, but they are different purposes with different settings and governance requirements.

Planning the Measurement Architecture Before Setup

Do not begin in Google Tag Manager. Begin by defining what should count as a conversion.

Define the Initial Website Conversion

The initial action should represent a genuine completed event, not a button click that can occur before validation fails.

Examples include:

• A confirmed form submission

• A completed appointment booking

• A successful checkout

• A completed registration

Use a direct Google Ads conversion action when Google Ads bidding is the main use case. Importing a GA4 key event into Google Ads can be useful for cross-channel reporting, but Google’s current Enhanced Conversions for Web setup does not support conversions created by importing Analytics goals in the same way as a native Google Ads conversion action.

Define the CRM Funnel

A practical lead-generation structure might be:

Use objective, auditable definitions. “Qualified Lead” might require a valid service need, eligible location, realistic budget and successful contact. A salesperson merely opening a record should not qualify it.

Google Ads now supports Qualified Lead and Converted Lead categories and a lead-funnel reporting structure. The categories should reflect the business meaning of the event rather than being chosen only because they sound lower-funnel.

Select the Source of Truth

The CRM or sales platform should be authoritative for lead status, opportunity value and revenue. Google Ads is the advertising attribution and optimisation system, not the master customer database.

Store important data in permanent fields rather than relying only on temporary automation tags. Useful fields can include:

• Original source and campaign data

• GCLID and other available Google advertising identifiers

• Email and telephone number

• Lead-created timestamp

• Conversion timestamps for important lifecycle events

• Opportunity or order ID

• Value and currency

• Consent status and collection context

Import status, error response and last successful sync

How to Set Up Enhanced Conversions for Web

The exact interface changes over time, but the implementation principles remain consistent.

1. Audit the Existing Conversion Action

Confirm that the standard website conversion is accurate before adding enhanced data. Test that:

• The tag fires only after success

• It does not fire again on an ordinary page refresh

• Conversion value and currency are correct

• Ecommerce purchases include a unique transaction ID

• Consent signals are applied correctly

• Duplicate GA4 and Google Ads actions are not both included as primary goals

2. Turn On Enhanced Conversions

Within Google Ads, open the Goals area, review the customer-data settings, turn on enhanced conversions and accept the applicable data terms and policies.

Google has consolidated the former Web and Leads controls. Older screenshots and instructions may still show separate panels or force the user to choose one setup method. Those interfaces should not be treated as the current account design.

3. Allow User-Provided Data in the Google Tag

If Google Tag Manager is used, Google currently recommends configuring enhanced conversions through a Google tag deployed in the container with the relevant Google Ads account as a destination.

The Google tag can obtain user-provided data through:

• Automatic detection

• Specified CSS selectors or JavaScript variables

• A controlled code or data-layer implementation

Automatic detection can be quick to deploy, but it gives the advertiser less explicit control over which fields are read. For important or complex implementations, a structured data-layer or code-based approach is normally more stable than relying on page text or fragile CSS classes.

Where selectors are used, stable element IDs are preferable to presentation classes that may change during a website redesign.

4. Apply Consent Controls

Connect the Google tag with the site’s consent-management platform and Consent Mode configuration. User-provided data should be collected and transmitted only when the applicable terms and consent parameters permit it.

Do not assume the tag’s presence proves the consent implementation is correct. Test consent granted and consent denied states separately.

5. Test the Data and Event Together

Use Google Tag Manager Preview, Tag Assistant and browser developer tools to confirm:

• The intended conversion event fires

• The Google tag is present on the relevant pages

• User-provided data is available at the correct moment

• The source data is not sent in plain text where hashing is required

• Consent parameters reflect the user’s choice

• Transaction IDs, values and currencies are populated dynamically

• The implementation does not expose customer information in URLs

6. Review Google Ads Diagnostics

Google Ads provides enhanced-conversion diagnostics and coverage information. Allow for processing delay, then check whether the setup is receiving eligible data and whether warnings identify missing, malformed or inconsistent fields.

Do not judge the implementation solely by whether the standard conversion appears in the interface. A normal conversion can record successfully while its enhanced data is missing.

How to Set Up Enhanced Conversions for Leads

Enhanced Conversions for Leads has two connected parts: capture appropriate first-party data during the website lead journey, then import later business outcomes using matching data.

1. Configure Website Data Capture

Use the Google tag or Google Tag Manager to make the relevant consented user-provided data available when the initial lead is created. Ensure auto-tagging is enabled and retain GCLID where it is available.

Even when the website tag can collect GCLID automatically for enhanced-conversion matching, continue storing and importing existing GCLIDs where possible. Google recommends retaining these direct advertising identifiers to maximise attribution accuracy.

2. Create the Offline Conversion Actions

Create actions for the small number of later outcomes that genuinely matter. Google recommends the Qualified Lead and Converted Lead categories for this use case.

Examples might include:

• Qualified Lead

• Appointment Attended

• Sales Opportunity Created

• Converted Lead or Closed Sale

• Revenue Confirmed

Avoid importing every CRM stage. Overlapping events can inflate reporting and make it unclear what Smart Bidding is being asked to achieve.

3. Choose the Import Route

Google has moved current and future offline and Enhanced Conversions for Leads API development towards the Data Manager API. New builds should not copy legacy Google Ads API examples without checking access and migration requirements. The Google Ads Data Manager guide explains the available connection layer in more detail.

4. Map the Required Fields

The precise requirements depend on the connection, but a robust event commonly contains:

• Google Ads conversion action

• Conversion time with the correct time zone

• Hashed email and/or telephone number where required

• GCLID when available

• Unique Order ID

• Conversion value

• Currency

The Order ID should be unique to the individual event and must not contain customer-identifying information. It supports deduplication, troubleshooting and later conversion adjustments.

5. Normalise, Hash and Validate

Some Google-controlled tagging methods hash correctly formatted data automatically. Some file, CRM or API routes require the sending system to normalise and hash designated fields before upload.

Do not hash an already hashed value again. Double hashing prevents matching. Document which system owns formatting and hashing so that the CRM, middleware and Google connection do not each attempt the same transformation.

6. Test the Full Lifecycle

Testing only the website form is insufficient. Create a controlled test lead and move it through the complete journey:

1. Submit the form with permitted test data.

2. Confirm the CRM stores the expected attribution fields.

3. Change the record to the chosen lifecycle stage.

4. Confirm the integration sends one event.

5. Check the timestamp, value, currency and Order ID.

6. Review the integration log and Google Ads diagnostics.

7. Repeat the stage update to confirm a duplicate is not created.

7. Validate Before Using the Event for Bidding

Start important new CRM events as secondary or otherwise prevent them from changing campaign bidding while validation is underway. Reconcile Google Ads counts against the CRM over several sales cycles.

Only introduce a lower-funnel action into bidding when:

• Its business definition is clear

• Events arrive consistently and promptly

• Duplicates and rejected records are controlled

• Conversion values are commercially meaningful

• The campaign has enough signal for the selected bidding approach

• Sales staff apply lifecycle stages consistently

Google recommends measuring correctly categorised lower-funnel actions for multiple conversion cycles before switching optimisation towards them. A gradual change protects campaigns from a sudden reduction or distortion in the bidding signal.

Using Zapier for Enhanced Conversions for Leads

Zapier remains a supported connection option, but the old “Send Offline Conversion” screen should not be treated as a permanent specification. Field names, connection routes and Google’s account-level settings have changed.

A well-designed Zap should do more than connect a CRM trigger to a Google Ads action. It should:

1. Trigger only when an exact lifecycle condition is met.

2. Filter out records missing required identifiers or timestamps.

3. Map the correct conversion action.

4. Format the conversion time and time zone consistently.

5. Send user-provided data and GCLID where supported and available.

6. Pass value, currency and a stable unique Order ID.

7. Record success or failure back in the CRM or an integration log.

8. Prevent the same lifecycle transition from sending repeatedly.

9. Alert an owner when an upload fails.

Zapier is useful when the workflow is linear and a native connection does not meet the requirement. If the automation needs several systems, extensive branching, bulk reconciliation or complex retry logic, a more controlled integration may be appropriate.

See our separate guide to Zapier offline conversion tracking for Google Ads for the automation-specific design.

Using HubSpot, Salesforce, HighLevel and Other CRMs

CRM capability should be verified at implementation time rather than assumed from an old product-edition list.

Google Ads Data Manager supports direct connection routes for platforms including HubSpot and Salesforce. Other CRMs may provide native workflows, marketplace applications, Zapier connections or an API route.

Check:

• Which contact, lead, deal or opportunity object is sent

• Whether email, telephone number and GCLID are available

• Whether the integration supports values, currencies and Order IDs

• How it handles several contacts associated with one deal

• Whether updates create a new event or adjust an existing one

• Which subscription tier or permission is required

• Whether the integration is standard offline import or a complete Enhanced Conversions for Leads implementation

For B2B sales, do not report every contact on a multi-contact opportunity as a separate Closed Sale. The conversion architecture should represent the commercial event, not simply the number of CRM records associated with it.

Enhanced Conversions in Google Analytics 4

The old article incorrectly treated GA4 Enhanced Measurement as the switch for enhanced conversions. They are different features.

GA4 Enhanced Measurement automatically collects certain website interactions such as scrolls, outbound clicks and site search. It does not enable hashed first-party customer matching.

Enhanced conversions in Google Analytics uses user-provided data collection. The property must be linked with Google Ads, the relevant data terms and settings must be accepted, and the Google tag must be configured to collect eligible user-provided data.

GA4 can use this data to improve cross-channel attribution and linked-product reporting. That does not mean every Google Ads account should replace its native Google Ads conversion actions with imported GA4 key events. Choose the measurement source according to the reporting and bidding requirement, then avoid placing duplicate actions in the primary conversion goal.

Google documents the current distinction in its guide to enhanced conversions in Google Analytics.

Common Enhanced-Conversion Mistakes

Calling the Google Tag a Third-Party Tag

The Google tag is a script supplied by Google, but when it is placed on the advertiser’s own website it participates in first-party measurement. Enhanced conversions supplements the tag with first-party customer data; it should not be explained as first-party data “replacing a third-party Google tag”.

Firing on the Form Button Instead of Success

A click can occur even when required fields are missing, validation fails or the server rejects the form. Trigger the conversion from a confirmed success event, thank-you state or reliable data-layer event.

Sending Plain Customer Data in URLs

Never place email addresses, telephone numbers or names in page URLs, query strings or visible tracking parameters. URLs can appear in analytics systems, server logs, browser history and referrer data.

Assuming Automatic Detection Is Always Best

Automatic detection is convenient, but dynamic forms, iframes and single-page applications can make collection unreliable. Explicit data-layer variables or controlled code generally provide better governance and stability for complex sites.

Losing GCLID in the CRM

Enhanced user-provided data complements advertising identifiers. It is not a reason to stop collecting GCLID. Preserve it where available and retain the wider attribution context needed for reconciliation.

Importing Every CRM Update

If a workflow sends the same Qualified Lead each time a record is edited, reported conversions will be inflated. Use a unique Order ID and event-state logic to make the integration idempotent.

Making All Funnel Stages Primary

If Website Lead, Qualified Lead, Opportunity and Closed Sale are all primary within the same campaign goal, Google may optimise towards a mixture of outcomes with very different values. Decide which event represents the objective and use secondary actions for observation where appropriate.

Treating Hashed Data as Automatically Compliant

Hashing does not remove the need for transparency, data minimisation, consent controls, retention rules or a defensible legal basis. Privacy review is part of the implementation, not a statement added afterwards.

Failing to Reconcile Data

Google Ads, the CRM and finance system answer different questions. Exact totals may not match because attribution windows, event times, deduplication and modelling differ. However, unexplained gaps, duplicate spikes or missing values still require investigation.

How to Test and Monitor Enhanced Conversions

An implementation should have an operating routine, not just a launch test.

Website Checks

• Test each eligible form and checkout route

• Test consent granted and denied states

• Confirm user-provided data is present only at the intended event

• Check transaction IDs and values are dynamic

• Retest after website, form or tag-container releases

Google Ads Checks

• Review the conversion action status

• Open enhanced-conversion diagnostics

• Review coverage and data-quality warnings

• Compare conversion volumes before and after the change

• Investigate sudden shifts rather than assuming all uplift is incremental business

Low-volume accounts may not receive detailed diagnostics immediately. Google notes that some alerts require sufficient recent conversion volume before the platform can evaluate the implementation reliably.

CRM and Integration Checks

• Compare source records with sent events

• Track rejected and retried uploads

• Monitor duplicate Order IDs

• Review missing identifiers

• Reconcile values and currencies

• Confirm sales-stage definitions are still being followed

• Assign a named owner for failed integrations

Frequently Asked Questions

Does Enhanced Conversions Replace Standard Google Ads Conversion Tracking?

No. Enhanced conversions supplements the ordinary website or imported conversion event with additional first-party matching data. The base conversion action and trigger still need to work correctly.

Are Enhanced Conversions for Web and Leads Still Different?

Yes in practical use, even though Google has unified the account setting. Enhanced Conversions for Web improves matching for a website event. Enhanced Conversions for Leads imports a later CRM or offline outcome and connects it with the lead journey.

Do I Still Need GCLID?

Retain and import GCLID whenever it is available. Google recommends continuing to use direct advertising identifiers alongside user-provided data. Enhanced matching should be an additional route, not an excuse to discard useful attribution fields.

Can Enhanced Conversions Improve Lead Quality?

Enhanced Conversions for Web alone mainly improves measurement of the existing web action. Lead-quality optimisation comes from reliably importing meaningful later outcomes such as Qualified Leads, Converted Leads and revenue, then using the validated signals appropriately in reporting and bidding.

Is Google Tag Manager Required?

No. Enhanced conversions can be configured through the Google tag, Google Tag Manager and supported data or API connections. Choose the route that provides reliable data, appropriate control and maintainable ownership.

Can Enhanced Conversions Work With Forms in an Iframe?

They can be more difficult because the parent page may not have access to fields inside a cross-domain iframe. Use a supported native integration, a reliable success event and a controlled data-passing method rather than assuming automatic detection can read the form.

Should I Use GA4 or a Native Google Ads Conversion Action?

For Google Ads optimisation, a direct Google Ads conversion action is often preferable because it is designed for Ads measurement and supports the current Google Ads enhanced-conversion workflow. GA4 conversions remain valuable for cross-channel analytics. Avoid counting both as primary versions of the same business event.

Does Enhanced Conversions Create Remarketing Audiences?

Not automatically as a general consequence of enabling measurement. Google provides a separate conversion-based customer-list setting. Customer Match, conversion-based lists and enhanced conversion measurement should be governed as distinct use cases.

Is Enhanced Conversions Fully GDPR Compliant?

No technology can make that blanket promise. Google provides hashing, policy terms and consent-aware tag behaviour, but the advertiser remains responsible for its legal basis, transparency, consent implementation, data minimisation and handling under applicable law.

How Long Until Enhanced Conversion Results Appear?

Tag testing can confirm technical behaviour immediately, but Google Ads diagnostics, coverage and reported impact take time to process. Google advises allowing roughly a month before expecting the full Enhanced Conversions for Web impact view.

Should Qualified Leads or Closed Sales Be Primary Conversions?

They can be, but only after validation and with sufficient volume for the bidding strategy. Start by measuring the events, reconcile them with the CRM and observe them across multiple sales cycles before changing optimisation.

Enhanced Conversions Implementation Checklist

Before launch, confirm that:

• The ordinary website conversion is accurate

• Enhanced conversions is enabled and the relevant data terms are accepted

• User-provided data is collected only for an appropriate purpose

• Consent Mode and the consent-management platform are tested

• Email and telephone fields are normalised correctly

• No customer information appears in URLs

• GCLID and other available attribution identifiers are retained

• CRM lifecycle stages have objective definitions

• Conversion times, values and currencies are correct

• Each imported event has a stable unique Order ID

• Duplicate prevention and failed-event logging are in place

• New lower-funnel events are validated before bidding uses them

• Google Ads diagnostics and CRM reconciliation have an ongoing owner

Final Thoughts

Enhanced conversions should be treated as part of a wider measurement system, not an isolated tracking option.

For ecommerce, it can improve the matching of completed website purchases. For lead generation, its greater value is connecting advertising with the sales outcomes recorded after the initial enquiry. That enables campaign decisions based on Qualified Leads, customers and revenue rather than treating every form submission as equally valuable.

The strongest setup combines accurate website conversion tracking, consented first-party data, retained advertising identifiers, a well-structured CRM, reliable event imports and carefully selected bidding goals.

If you need help auditing an existing implementation or connecting Google Ads with your CRM and sales pipeline, One PPC can review the website tags, data fields, lifecycle stages, import method and bidding configuration as one end-to-end system.

Contact One PPC to discuss enhanced conversions, CRM integration and revenue-based Google Ads measurement.