{"id":307,"date":"2026-07-13T19:07:00","date_gmt":"2026-07-13T17:07:00","guid":{"rendered":"https:\/\/www.lukaswojcik.com\/blog\/?p=307"},"modified":"2026-10-24T00:46:31","modified_gmt":"2026-10-23T22:46:31","slug":"tutorial-implementing-google-ads-enhanced-conversions","status":"publish","type":"post","link":"https:\/\/www.lukaswojcik.com\/blog\/en\/digital-marketing\/tutorials-en-digital-marketing\/tutorial-implementing-google-ads-enhanced-conversions\/","title":{"rendered":"Tutorial: Implementing Google Ads Enhanced Conversions"},"content":{"rendered":"

Enhanced conversions supplement Google Ads measurement with hashed customer data. A suitable match can enable additional advertising attribution. Complete recovery of missing conversions or a particular improvement is not guaranteed.<\/p>\n

This example covers an email address at a confirmed website purchase. The purchase itself must be measured correctly independently of the enrichment. The setup requires suitable consent handling; hashing does not make an email address anonymous.<\/p>\n

\"Email
The supported tag processes email for matching. Hashing does not replace consent or prove a successful match.<\/figcaption><\/figure>\n

1. Prerequisites and the Google tag<\/h2>\n

Enhanced conversions must be enabled in Google Ads and the required customer data terms accepted. Google describes a unified setting for web and leads from April 2026. Older instructions requiring a choice between collection methods therefore do not match every interface.<\/p>\n

The GTM container needs a Google tag with the correct Ads account as a destination. Collection is configured under Allow user-provided data capabilities. This example maps a variable explicitly; automatic scanning of the entire page is not required.<\/p>\n

2. Supply data with the confirmed event<\/h2>\n

A data layer is a shared browser data structure. A dedicated event name makes the additional processing explicit. The example below only passes data to GTM and is not complete purchase tracking. Application code must reach this branch only after a confirmed purchase and permission for the processing; the snippet does not check consent.<\/p>\n

window.dataLayer = window.dataLayer || [];\nwindow.dataLayer.push({\n  event: 'ads_purchase_ready',\n  transaction_id: 'ORDER-123',\n  customerData: { email: 'customer@example.com' }\n});<\/code><\/pre>\n
GTM Data Layer Variables read customerData.email<\/code> and transaction_id<\/code>. A Custom Event trigger for ads_purchase_ready<\/code> aligns execution with data availability. An existing purchase trigger must not send the same conversion again. The unique transaction ID belongs in the conversion event’s designated transaction field.<\/p>\n
Alternatively, a DOM Element Variable can read the text of a stable element such as #customer-email<\/code>. A visible element is not proof of a new purchase. On dynamic pages, an explicit event after data is ready is more reliable than visibility alone.<\/p>\n
3. Map and hash customer data<\/h2>\n
A User-Provided Data variable uses Manual configuration to map the email variable. Current Google guidance describes configuration through the Google tag or the user_data<\/code> parameter; event-specific values can override tag-wide values. The older conversion-tag checkbox is no longer a universal menu path.<\/p>\n
When an unhashed email is supplied, the supported Google tag performs the required processing before transmission. Prehashed values require the documented field intended for that format; hashing twice prevents a suitable match. Neither raw email nor its hash belongs in an ordinary GA4 event parameter forwarded indiscriminately from the data layer.<\/p>\n
4. Validate before publishing<\/h2>\n
GTM Preview shows the event, available variables and consent state. With ad_user_data=denied<\/code>, customer data must not be sent for advertising enrichment. Account switches, confirmation-page reloads and missing email addresses also need checks.<\/p>\n
The network request’s em<\/code> parameter can indicate enrichment data; an empty marker is insufficient. A hash in the request proves neither a successful account match nor a legally compliant overall setup. Google Ads conversion diagnostics provide an additional check, typically after about 48 hours.<\/p>\n
\n
Questions and answers<\/h2>\n
Which rules apply to prehashed CRM data?<\/h3>\n
The chosen interface’s rules are mandatory. Current Google Ads API documentation requires lowercase and removal of surrounding whitespace; gmail.com and googlemail.com also require removing dots and the plus suffix before the @. Other domains retain dots and plus suffixes. SHA-256 follows normalization. An arbitrary normalization rule can alter valid addresses.<\/p>\n
Does Consent Mode protect data already in the data layer?<\/h3>\n
Google tag controls do not prevent other scripts from accessing data already present in the browser. Customer data should be supplied only for the intended purpose. Later events and account switches must not accidentally reuse stale values; clearing data and controlling access are part of the implementation.<\/p>\n
What if the address appears after the tag fires?<\/h3>\n
Previously sent requests do not acquire later values. The event must align with data availability. For data available on an earlier page, Google also documents a dedicated user-provided data event tag; a second purchase event is not an appropriate substitute.<\/p>\n<\/div>\n
\n
Sources<\/h2>\n