Enhanced Conversions

Enhanced conversions is a Google Ads feature that adds hashed first-party customer data to a web conversion you already track. When someone buys or signs up on your site, your conversion tag captures details they gave you, such as email address, name, home address, or phone number, and sends them to Google in hashed form. Google uses that data to match the conversion to people who were signed in to a Google account when they engaged with your ad. It supplements your existing conversion tracking. It does not replace the tag, and it does not add a new conversion action by itself. Because the match uses accounts that were signed in when the person engaged with your ad, it will not recover every missed conversion. It recovers the share where the shopper was signed in somewhere Google can match, so expect a partial lift, not a full repair.

The hashing is SHA-256, a one-way function, so the raw details are not transmitted. Google normalizes and matches the hashed values inside a confidential computing environment. With Google Ads tags and the Google tag gateway, the data is also encrypted before it leaves the browser. With server-side Google Tag Manager, it goes to your server container first and the Google Ads tag encrypts it there. Google reports only privacy-safe conversions from the match, which means you see recovered conversions as normal rows in your conversion columns, not as a separate line item. The setup path depends on your site. Google's help page for the feature describes the Google tag gateway and server-side Google Tag Manager as paths, and links a separate guide for configuring the web version, so follow the guide that matches the tag you actually run.

The feature rides on the settings around it. It needs an existing website conversion action, and the customer fields must be present on the page or in the data layer when the conversion fires, usually the order confirmation step. Smart Bidding benefits because more of your real conversions are counted, so strategies like Target CPA and Target ROAS see a fuller picture. Google has said it is merging enhanced conversions for web and for leads into one on and off setting from April 2026, so the settings screen you see may differ from older tutorials. If you already run a consent banner, make sure the customer data is only passed when your own privacy policy and the user's choices allow it. The feature does not change what you may collect. It changes what happens to data you collect legitimately.

The most common mistake is switching the setting on and supplying nothing. The toggle does nothing if no user-provided data reaches the tag. Other problems: collecting fields only on a page after the conversion fires, sending unformatted values, or having a checkout that uses a hosted payment page where the email is never visible to your tag. A different error is treating it as a way to track people who refused consent. It matches data you already collected under your own privacy terms and does not bypass them. Watch for pages that show the confirmation before the details exist in the data layer, and for single-page checkouts where the tag fires before the form values are read. In both cases the tag fires with nothing to hash, and diagnostics will say so.

To check whether it works, open the conversion action's diagnostics and look at the enhanced conversions status and any flagged data issues. Then compare conversion counts for the action before and after, over similar periods and with the same conversion window. This week, confirm your confirmation page exposes at least email or phone to the tag, turn the setting on, and review diagnostics a few days later. If the status shows missing or badly formatted fields, fix the page before judging the result. Judge it over a full conversion window, not a single day, because late conversions fill in over time. Record the count before and after, and keep the comparison period the same length.