{"id":4437,"date":"2026-08-03T17:18:51","date_gmt":"2026-08-03T14:18:51","guid":{"rendered":"https:\/\/ivitskiy.com\/blog\/enhanced-conversions-google-ads\/"},"modified":"2026-08-04T00:13:04","modified_gmt":"2026-08-03T21:13:04","slug":"enhanced-conversions-google-ads","status":"publish","type":"post","link":"https:\/\/ivitskiy.com\/blog\/en\/enhanced-conversions-google-ads\/","title":{"rendered":"How Enhanced Conversions Improve Website Attribution"},"content":{"rendered":"\n
In short:<\/strong> enhanced conversions add a hashed customer identifier to an existing Google Ads conversion, giving Google another way to connect a website enquiry or purchase with an earlier ad interaction. They do not create sales and only improve an existing Google Ads conversion<\/a> that is already tracked. Use them when the Google Ads action already works, the form collects supported first-party data, and your business can transmit it under the consent and privacy rules that apply.<\/div>\n\n\n\n

Enhanced conversions address an attribution gap, not a sales gap. Your booking system or CRM may already contain the enquiry, and the Google Ads tag may already record the event, yet Google might not confidently connect that event with a previous ad click or view. A hashed customer identifier supplies another matching key.<\/p>\n\n\n\n

\n
Base conversion<\/strong>
The existing Google Ads action must work first.
Check: the original event is recorded.<\/div><\/div>\n
Match<\/strong>
Supported first-party data is normalized, hashed and matched.
Check: field quality and tag diagnostics.<\/div><\/div>\n
Consent<\/strong>
Collection and transmission must follow applicable policy.
Check: consent and privacy setup.<\/div><\/div>\n<\/div>\n
Source: Google Ads Help.<\/div>\n\n\n\n
\"Enhanced<\/figure>\n\n\n\n

Separate the customer outcome from its Google Ads attribution<\/h2>\n\n\n\n

Google describes enhanced conversions<\/a> as an addition to existing conversion tracking. When a person submits an enquiry or purchases on the website, the tag can take supported contact data provided directly to the business, hash it, and send it with the conversion. Google compares that hash with signed-in Google accounts and may connect the conversion to an ad interaction.<\/p>\n\n\n\n

\n
Stage<\/th>What the business already sees<\/th>What enhanced conversions add<\/th><\/tr><\/thead>
A customer submits a form or completes a purchase<\/td>The enquiry or sale already exists in the business system<\/td>No new sale is created<\/td><\/tr>\n
The Google Ads conversion tag fires<\/td>The website sends a measurement event<\/td>A hashed customer key accompanies the event<\/td><\/tr>\n
Google connects the event with advertising<\/td>Attributed conversions appear in the ad report<\/td>The hash provides another way to match the event with a click or view<\/td><\/tr>\n<\/tbody><\/table><\/figure>\n\n\n\n

The feature can improve measurement accuracy, but it does not promise to recover every missing connection. It cannot invent an enquiry that never happened, and it cannot replace a correctly defined base conversion when the original tag is wrong.<\/p>\n\n\n\n

Use only supported first-party customer data<\/h2>\n\n\n\n

Matching uses first-party data that a customer provided directly to your business during the conversion. Supported examples include email, name and home address, or phone number. Google identifies email as the preferred option. Address matching requires first name, last name, postal code, and country. Phone requirements differ between the Google tag and Google Tag Manager instructions, so your implementer should follow the requirements for the chosen method.<\/p>\n\n\n\n

Before transmission, the contact is transformed with the one-way SHA256 hashing algorithm. This produces a standardised unreadable value that can be compared with another hash but cannot be reversed through an ordinary decoding step to reveal the original email. In a standard setup, the Google tag can normalise and hash the data automatically. A manual implementation can send a prepared hash.<\/p>\n\n\n\n

Hashing does not remove a business’s privacy responsibilities. Google’s customer data policies<\/a> require businesses to disclose third-party sharing for ad measurement and obtain consent where legally required. When consent mode applies, the relevant status for sending advertising user data must also be configured correctly.<\/p>\n\n\n\n

Check the tag, form, and conversion page before setup<\/h2>\n\n\n\n
    \n
  1. Locate the working Google Ads conversion.<\/strong> Identify the exact event or page where the tag records an enquiry or purchase. Enhanced conversions extend that measurement rather than repair it.<\/li>\n
  2. Select a supported field.<\/strong> Email is Google’s preferred identifier. Do not add unnecessary form questions when an existing field already meets the requirements.<\/li>\n
  3. Make the data available when the event fires.<\/strong> If a customer enters contact details on an earlier screen, the site must make the value available to the conversion code later. The email does not need to be displayed on the confirmation page.<\/li>\n
  4. Review disclosure and consent.<\/strong> The owner must confirm that ad measurement use is explained and that any required consent status is passed correctly.<\/li>\n
  5. Enable and test the feature.<\/strong> The setting appears under Goals and Settings. After accepting the terms, an implementer can choose automatic detection, CSS or JavaScript variables, or code. Google lists these approaches in its Google tag setup guide<\/a>.<\/li>\n<\/ol>\n\n\n\n

    Ask for evidence of implementation, not a screenshot of the switch<\/h2>\n\n\n\n
    \n
    Task<\/th>Typical owner<\/th>Evidence for the business owner<\/th><\/tr><\/thead>
    Define the conversion and where it fires<\/td>Paid search or analytics specialist<\/td>The action name and exact page or event<\/td><\/tr>\n
    Check the form and contact availability<\/td>Website administrator or developer<\/td>Which field is available to the tag and when<\/td><\/tr>\n
    Configure hashing and transmission<\/td>Developer or tag specialist<\/td>An implementation that uses only the required fields<\/td><\/tr>\n
    Review disclosure and consent<\/td>Owner with the person responsible for privacy<\/td>Clear website notice and the applicable consent status<\/td><\/tr>\n
    Run a test and inspect diagnostics<\/td>Analytics specialist with the developer<\/td>Confirmation that the tag receives a hashed value<\/td><\/tr>\n<\/tbody><\/table><\/figure>\n\n\n\n

    If an agency cannot show where the conversion fires, which contact field is used, and what the test produced, implementation is not complete. An enabled switch proves that a setting was accepted, not that customer data was available or transmitted correctly.<\/p>\n\n\n\n

    A useful owner review is to ask for the conversion event, selected identifier, consent behaviour, and diagnostic result together, then resolve any missing piece before judging attribution changes.<\/p>\n\n\n\n\n\n

    Decide whether your website is ready<\/h2>\n\n\n\n

    Enhanced conversions make sense when the enquiry or purchase occurs on the website, a dedicated Google Ads conversion already works, the form collects a supported contact, and the team can transmit it under the applicable data rules. In that situation, the feature adds a useful matching key to an established measurement process.<\/p>\n\n\n\n

    Fix the foundation first if the reported conversion is only a button click, the tag does not record the actual enquiry, or nobody knows where the event fires. When a sale closes away from the website, Google provides enhanced conversions for leads, which is a different scenario from enhanced conversions for web.<\/p>\n\n\n\n

    When this does not apply<\/h2>\n\n\n\n