Understanding Enhanced Conversions in Google Ads
Enhanced conversions are a feature that supplements the basic conversion pixel with first‑party data supplied at the time of a conversion event. When a user completes a purchase or submits a lead form, the advertiser’s site can send hashed customer information such as email address or phone number back to Google. Google then matches this data to its own user identifiers, improving the confidence of the conversion signal without relying solely on cookies.
How Enhanced Conversions Strengthen Attribution
Standard conversion tracking can miss conversions when third‑party cookies are blocked or when users clear their browsers. By providing a direct, consented data point, enhanced conversions reduce the gap between clicks and recorded conversions. This higher fidelity feed allows data‑driven attribution models to allocate credit more accurately across touchpoints, especially in multi‑channel journeys where the last click may not reflect the true influence of earlier interactions.
Preparing Data and Privacy Compliance
Before any tag is placed, advertisers must verify that they have a legitimate basis to collect and share user identifiers. This typically involves:
Obtaining explicit consent through a clear privacy notice and an opt‑in mechanism that aligns with regional regulations such as GDPR or CCPA.
Hashing the data on the client side using SHA‑256 before it is transmitted to Google. The hash process must follow Google’s specification to ensure a match can be made.
Maintaining a data retention policy that defines how long the hashed identifiers are stored and when they are purged.
Choosing an Implementation Method
Google offers three primary paths to send enhanced conversion data:
The first method uses the Global Site Tag (gtag.js) directly on the conversion page. This approach is straightforward for single‑page sites but can become cumbersome when multiple conversion types exist.
The second method leverages Google Tag Manager (GTM). GTM provides a modular environment where the data layer can be populated with the necessary fields and a dedicated tag can handle the hashing and transmission.
The third method is server‑side tagging. By moving the hash and transmission logic to a server endpoint, marketers gain greater control over data handling and can align the process with existing server‑side data pipelines.
Step by Step Setup Using Google Tag Manager
Below is a concise workflow that walks through the GTM implementation without using a bulleted list.
First, create a data layer variable on the conversion page that captures the raw email address after the user submits the form. The variable should be named dlv – rawEmail and reference event.email in the data layer push.
Second, add a custom JavaScript variable called js – hashedEmail. Inside the script, read the value from dlv – rawEmail, apply crypto.subtle.digest('SHA-256', new TextEncoder().encode(email)), convert the result to a hex string, and return the hash. This step ensures the hashing happens in the browser before any data leaves the site.
Third, configure a new Google Ads conversion tag. In the tag settings, enable the enhanced conversions toggle and map the hashedEmail variable to the email field. Leave the default conversion ID and label unchanged.
Fourth, create a trigger that fires on the form submission event. This trigger should listen for the same data layer push that supplies the raw email so the tag runs only when a conversion is confirmed.
Fifth, publish the container and use the Google Tag Assistant preview mode to verify that the hashed value appears in the request payload. The request URL will contain a parameter named email_hash with a 64‑character SHA‑256 string.
Finally, navigate to the Google Ads interface, open the conversion action settings, and enable the “Enhanced conversions” toggle. Google will begin processing the hashed identifiers within a few hours.
Validating the Data Flow
After the tag is live, validation is essential to confirm that Google receives the enhanced data correctly. In the Google Ads UI, the conversion action page shows a status indicator for enhanced conversions. A green checkmark means the data is being processed without errors.
For deeper diagnostics, open the network tab in the browser developer tools during a test conversion. Look for a request to https://www.googleadservices.com/pagead/conversion/ that contains the email_hash parameter. Ensure the hash length is exactly 64 characters and that the request returns a 200 HTTP status.
If the status shows a warning, revisit the hashing script to verify that the input string is trimmed and lower‑cased, as Google’s matching algorithm expects a normalized format.
Troubleshooting Common Issues
One frequent obstacle is mismatched data formats. Google requires the email address to be in plain ASCII, lower‑cased, and without surrounding whitespace before hashing. Including a trailing space or an uppercase letter will prevent a match and cause the enhanced conversion to be dropped.
Another typical problem arises from consent management platforms that block the data layer push until a user accepts tracking. In such cases, the GTM tag will never receive the raw email variable. The solution is to place the data layer push inside the consent callback so it only fires after explicit permission.
Server‑side implementations often encounter issues with missing request headers that Google uses for matching. Ensure the server forwards the User‑Agent and IP‑Address headers unchanged when relaying the conversion request to Google’s endpoint.
Measuring Impact on Attribution Models
Once enhanced conversions are operational, the next step is to observe how attribution metrics shift. In the Google Ads attribution report, compare the conversion counts and value attribution before and after activation. Marked increases in assisted conversions and a higher share of credit for upper‑funnel interactions indicate that the enhanced data is filling gaps previously attributed to “unknown”.
For a more granular analysis, export the conversion data to BigQuery and join it with first‑party session logs. This enables a side‑by‑side view of cookie‑based versus enhanced conversion signals, helping you quantify the lift in match rate and the reduction in “last click only” bias.
Finally, incorporate the refined attribution data into budget allocation decisions. When the model shows that display or video campaigns are receiving more credit after enhanced conversions, consider shifting a portion of the spend toward those channels to capitalize on the newly uncovered influence.
Leave a Reply