Definition
Enhanced conversions is a Google Ads feature in which the customer details already collected at checkout, such as email address, phone number and billing name and address, are hashed in the browser and sent alongside the conversion so Google can match the order to an ad interaction it would otherwise have missed. The store never sends readable personal data: the values are converted to an irreversible hash before they leave the page.
What a purchase conversion sends when the feature is configured
- Standard conversion payload
- Conversion action, order value, currency, transaction id and the ad click identifier if one is present
- Added user-provided data
- Email address, phone number in international format, first and last name, street, city, region, postal code and country
- How it is transmitted
- Each field normalised, lowercased and trimmed, then hashed with SHA-256 in the browser before the request is sent
- Where the values come from
- The order confirmation page or the checkout completed event, not a form the shopper is asked to fill in again
- Prerequisite in the account
- The customer data terms accepted in Google Ads and the conversion action configured to accept enhanced conversions
- Typical implementation paths
- The Google tag directly, Google Tag Manager with a user-provided data variable, a server container, or the Google Ads API for order adjustments
An illustrative field list rather than a required set. More matched fields give more chances to find a match, and a single reliable field such as a normalised email is enough to be worth implementing.
Why it matters
Enhanced conversions matter because a growing share of purchases can no longer be tied to a click by cookies alone. Browsers shorten or discard storage, people switch from a phone to a laptop before buying, and privacy settings remove the identifiers that used to carry the connection. When conversions go unrecorded, the bidding models learn from an incomplete picture and hold back on audiences that were actually working. Recovering those orders through hashed first-party data gives smart bidding better training signal and gives the store a conversion count closer to its own order records. It also underpins conversion modelling in regions where consent limits what can be stored.
Where it goes wrong
- Hashing on the server after sending readable values from the page, which puts personal data on the wire that never needed to be there
- Skipping normalisation, so email addresses with capital letters or trailing spaces and phone numbers without a country code hash to values that can never match
- Reading the fields from the wrong place on Shopify, where theme code does not run in the checkout and the values have to come from a custom pixel or a server-side source
- Announcing a conversion increase without checking the baseline, since the count changes for many reasons and the honest comparison is the store's own order records
- Leaving consent out of the design: the feature is not a way around a visitor's choice, and the tag configuration has to respect the signals the consent banner sets
Questions about enhanced conversions
Is sending customer data for enhanced conversions compliant with privacy law?
It can be, and the responsibility sits with the store. Google requires you to accept its customer data terms and to have the right notice and legal basis for sharing the data. In practice that means your privacy policy describes the practice, the consent tooling controls whether the tag fires, and hashing happens before anything leaves the visitor's browser. Take the compliance question to your own counsel rather than to a tag setup guide.
How do enhanced conversions differ from server-side tagging?
They solve different halves of the same problem and work well together. Enhanced conversions improve who a conversion can be matched to by adding hashed identity. Server-side tagging changes the route the event takes, sending it from a first-party endpoint the store controls. A store can run either alone, and many run the hashed data through the server container so the identity handling lives in one place.
How do you check that enhanced conversions are working?
Google Ads reports a diagnostic status on the conversion action showing whether user-provided data is being received and whether it is usable. Beyond that, watch the ratio of recorded conversions to real orders in the store admin over several weeks. A one-off comparison proves little, but a persistent gap that narrows after implementation is the outcome you are looking for.