Google Ads requires reliable conversion signals to evaluate and optimize campaigns. Enhanced Conversions expand existing conversion tracking with additional first-party data that users provide, for example, in a form or checkout. Used correctly, they supplement existing measurement—they do not replace it.
What Are Enhanced Conversions?
Enhanced Conversions are a Google Ads feature designed to supplement existing conversion events. When a person completes a conversion and provides supported first-party data in the process, this data can be hashed prior to transmission. Google uses the hashed information as part of its own matching and measurement logic.
The sequence is critical: first, the standard conversion event must function properly both functionally and technically. Only then can Enhanced Conversions be meaningfully configured as an additional layer. The feature is not a substitute for a clean conversion definition, a correctly firing tag, or transparent value and transaction data.
Why Do Enhanced Conversions Exist?
Conversion measurement takes place in an environment where browser signals can be restricted. Cookie settings, browser privacy mechanisms, device switches, and consent all influence which signals are available and to what extent. Enhanced Conversions do not provide a blanket guarantee for additional conversions. However, they can offer an additional, privacy-conscious attribution method when suitable first-party data and the necessary prerequisites are present.
For Google Ads, the quality of a conversion signal is relevant because it can influence reporting and automated bidding strategies. Therefore, setup is not about collecting as much data as possible, but about a clean, consistent implementation with a clear conversion action and appropriate data sources.
What Data Can Be Used?
Google supports specific user-provided information for Enhanced Conversions. This includes, in particular, email address, phone number, as well as name and address. Which fields are available and permissible in a specific setup should always be verified against the current Google Ads documentation and your own privacy assessment.
Prior to transmission, the data is hashed using SHA-256. Hashing is a one-way transformation: a hash value is generated from an input, which is not intended to be easily reversed. This does not automatically make data anonymous and does not replace a legal or technical review. It is part of a defined transmission and matching logic, not a bypass of privacy requirements.
Enhanced Conversions with Google Tag Manager
Conceptually, the path looks like this: Form or Checkout → User Data → GTM or Google Tag → Hashing → Google Ads. In Google Tag Manager, the correct conversion action is configured and connected to the data available at the actual conversion step. For forms, this might be the confirmed submission action; for e-commerce, a successful purchase.
Personal data should not be written to the dataLayer unnecessarily or insecurely. The primary purpose of the dataLayer is to provide business events and parameters in a structured manner. If sensitive data is required for the chosen Google Tag implementation, the technically designated path should be used, and access, timing, consent, and data minimization should be carefully reviewed.
Enhanced Conversions and Consent
Enhanced Conversions do not bypass consent requirements. Tags and data transmissions must align with the intended consent setup. This applies both to firing the conversion event and to processing supplementary data. How Consent Mode, website, CMP, and Google Ads interact is explained in our article on Consent Mode v2 Conversion Tracking.
A privacy-compliant implementation does not start in Tag Manager. It requires coordinated decisions regarding purpose, data sources, consent logic, information obligations, and technical access points. This article does not constitute legal advice; the specific assessment should be carried out with the responsible data protection officers.
Enhanced Conversions vs. Standard Conversion Tracking
Standard conversion tracking measures the defined action itself: such as a form submission, a purchase, or a registration. The conversion event must fire clearly, the trigger must be correct, and, if applicable, value, currency, or Transaction ID must be transmitted accurately. Enhanced Conversions supplement this event with appropriately available first-party data that is hashed prior to transmission.
Both levels must work together. If the conversion event does not work, Enhanced Conversions will not fix the measurement. If no suitable user data is available, the enhancement cannot be used effectively. The best sequence is therefore: define conversion, test event, check consent, add Enhanced Conversions configuration, and test again.
Testing Enhanced Conversions
The first check takes place in GTM Preview. Does the correct conversion action fire only on the intended event? Which variables are available at that moment? Do the fields match the actual form or checkout? Also check the Google Tag settings and verify that multiple tags are not inadvertently sending the same conversion.
Afterwards, Google Ads Conversion Diagnostics help evaluate the configuration. Check whether data arrives at the appropriate conversion action and whether Google displays setup recommendations. Diagnostics, GTM Preview, and a real test conversion complement one another: a successful preview test is important, but does not immediately reflect every subsequent processing step in the advertising system.
Common Mistakes
No suitable user data is available at the conversion step, or an incorrect form field is read.
The wrong conversion action or an unsuitable Google Tag configuration is used.
Consent is misinterpreted, or data is processed regardless of the intended consent status.
The actual conversion event does not work, fires twice, or transmits incorrect values.
Different implementation methods are not properly coordinated, leading to unclear data flows.
When errors occur, a step-by-step analysis is worthwhile: first the standard conversion, then data availability, consent, tag configuration, and finally the Google Ads Diagnostics. This helps distinguish technical issues from missing prerequisites.
Enhanced Conversions and Server-Side Tracking
Server-side tracking can complement the overall architecture of a measurement setup, but it is not a prerequisite for Enhanced Conversions. Which combination makes sense depends on the website, consent, data flows, and current Google guidelines. You can find more fundamentals in the article on Server-Side Tracking.
Professional Implementation of Conversion Tracking
Data Flakes supports the conception, implementation, and quality assurance of Google Ads conversion tracking—from conversion definition via GTM to alignment with consent and web analytics.
Get Your Google Ads Conversion Tracking Audited
Even after go-live, changes to the website, consent, or GTM can have an impact. Conversion Tracking Monitoring and Data Flakes Sentinel help make relevant anomalies visible earlier during ongoing operations.
Frequently Asked Questions about Enhanced Conversions
What are the benefits of Enhanced Conversions?
They supplement existing Google Ads conversion tracking with hashed first-party data, provided that suitable data is available and the prerequisites are met. A blanket increase in conversion volume cannot be inferred from this.
Are Enhanced Conversions the same as Consent Mode?
No. Consent Mode controls how Google tags operate according to consent status. Enhanced Conversions are an additional measurement feature and must adhere to applicable consent requirements.
Are email addresses transmitted to Google?
Supported user-provided data can be hashed via SHA-256 prior to transmission. Which data is used and under what conditions must be verified in the specific setup.
Can I set up Enhanced Conversions with GTM?
Yes, Google Tag Manager can support the configuration. Prerequisites are a correctly configured conversion action, data available at the right time, and an aligned consent setup.
How do I verify the implementation?
Use GTM Preview for events, triggers, and variables, perform a real test conversion, and then check Google Ads Conversion Diagnostics as well as the selected conversion action.
How to Achieve a Structured Setup
Before configuration, it should be clear which conversion action is to be enhanced and where the data actually originates in the process. For a lead form, this usually only makes sense after successful validation and confirmation. For a checkout, relevant information is generally only established with certainty once the order is completed. If fields are read too early, values will be missing or inputs will be included that never resulted in a conversion.
Create a simple audit trail for the setup: document the conversion action, trigger the event in the browser, check data availability and consent, verify the GTM tag in Preview, and track the results in Google Ads later. This procedure should also be repeated whenever changes are made to forms, checkout, consent management, or tags. This keeps the implementation traceable rather than relying on one-off tests.
Clear accountability is particularly important. Marketing defines which conversion is relevant for optimization. Development provides the necessary technical information at the appropriate time. Analytics checks data quality and consistency. When these roles jointly refer to the same definition, many subsequent discrepancies and unnecessary rework can be avoided. This creates a solid foundation for continuous campaign management.
Regular testing, clean documentation, and coordinated responsibilities keep the setup resilient over the long term.