Definition:
An enhanced conversion is a Google Ads measurement feature that supplements an existing conversion action with first-party data provided by the user, such as an email address or phone number. The data is normalised and hashed with SHA-256 before it is sent to Google.
Its purpose is to strengthen attribution and measurement when common signals, such as certain cookies or identifiers, cannot by themselves reveal the entire relationship between an ad interaction and a conversion. It is not a CRO technique or a method that directly increases the percentage of users who convert.
Google officially calls the feature Enhanced conversions. It can be used for online conversions and offline outcomes originating from leads, provided that the setup, data and applicable consent meet the platform’s requirements.
Índice de contenidos
How enhanced conversions work
When a person completes a measured action, the tag or integration can collect first-party data that the person has provided. The information is normalised, transformed with SHA-256 and sent with the conversion data.
Google attempts to match the hashed values with accounts that were signed in when they interacted with an ad. If a valid match is found, the platform may attribute the conversion more accurately to the relevant campaign. This process supplements the conversion tag; it does not replace it.
The result depends on data quality and availability, the technical setup and the existence of a match. Therefore, enabling the feature does not guarantee that every conversion will be recovered or that measured volume will increase by a specific proportion.
Website and lead measurement
Enhanced conversions cover two measurement contexts that Google has brought together under a unified setting. The distinction remains useful for understanding when information is captured and where the commercial outcome occurs.
- Website conversions: first-party data is sent when a purchase, registration or another online event is measured with a Google Ads conversion action.
- Lead outcomes: data captured in a form is combined with imported offline conversions, such as a sale or qualified opportunity confirmed later.
The feature should not be confused with a general conversion. It also does not apply in the same way to conversions measured solely by importing Google Analytics goals. Google’s documentation states that a compatible Google Ads conversion action is required.
Data, hashing and privacy
Supported identifiers may include email address, phone number, name and postal address, depending on the implementation method. Not every field has to be sent, but each one must use the required format. Email is generally the preferred signal, while phone numbers must follow the international E.164 format.
Before hashing, values are normalised to prevent differences in capitalisation, whitespace or formatting. They are then processed with SHA-256, a one-way algorithm. Hashing reduces exposure during transmission, but it does not by itself make every use anonymous or remove legal obligations.
The organisation must determine what information it may collect, document its purpose and comply with Google’s customer data policies, applicable law and consent signals. Sensitive categories and unnecessary fields must not be sent. Consent Mode and the state of ad_user_data may also affect processing.
Implementation in Google Ads
Implementation begins with a properly configured conversion action. It is also necessary to identify where the tag fires, which event represents the conversion and when user-provided data is available.
- Enable Enhanced conversions and accept the customer data terms in Google Ads.
- Choose a compatible data source, such as the Google tag, Google Tag Manager, Data Manager or an API connection.
- Define the fields that will be collected and confirm that they are normalised in the correct format.
- Apply consent and limit collection to the data needed for the authorised measurement purpose.
- Complete a test conversion and review diagnostics before assessing results.
The tag can automatically detect data, use CSS selectors or JavaScript variables, or receive values through code. The appropriate choice depends on the site’s architecture and the level of control required. The official Google Ads documentation should take precedence when available options change.
Validation and measurement limits
A correct setup is checked first in the tag and then in the conversion action diagnostics. Google may take time to show the feature’s impact, so a successful technical test does not amount to an immediate reporting result.
- Activation: verify that the setting and data source match the implementation method.
- Formatting: confirm that fields are normalised and that any hash generated before transmission is valid.
- Event: check that data is sent when the correct conversion fires.
- Consent: review whether collection and processing follow the configured signals.
- Diagnostics: resolve coverage, matching or implementation warnings before interpreting performance.
Enhanced conversions can add signals to measurement and bidding strategies, but they do not replace a coherent measurement architecture. Deduplication, goal definitions, conversion values and the quality of imports remain necessary to interpret results.
Within a Google Ads account, their usefulness should be assessed through diagnostics, coverage and changes in conversion actions, without automatically attributing every variation to this feature.