Enhanced conversions are one of the few ways to close the tracking gap created by cookie restrictions. But they only work if the data is captured correctly, hashed properly, and matched to Google accounts. A misaligned setup will show zero match rate and provide no value.
What are enhanced conversions in Google Ads?
Enhanced conversions supplement standard conversion tracking by sending hashed first-party customer data (email, phone, name) alongside the conversion event. Google matches this data against signed-in Google accounts to attribute conversions that would otherwise be missed due to cookie restrictions or cross-device behavior.
What data does enhanced conversions use?
Email address (most reliable and highest match rate), phone number, full name and address. Data is hashed with SHA-256 before leaving the browser or being sent to Google. Google uses the hashed data for matching only, not for targeting or audience building.
What is the difference between enhanced conversions for web and for leads?
For web: customer data is captured at the point of conversion directly from the confirmation page or checkout thank-you page. For leads: customer data is sent later via the Google Ads API or CRM integration when the lead is qualified or the opportunity closes. Web is for ecommerce transactions; leads is for B2B and professional services that have a sales cycle between lead and closure.
How do you check if enhanced conversions are working?
Open the conversion action settings in Google Ads. Enhanced conversions should be enabled. The Diagnostics tab shows match rate as a percentage (the percentage of conversions that Google could match to signed-in accounts). A match rate above 40% is healthy. GTM preview mode should show enhanced conversion data in the tag firing summary.
What mistakes break enhanced conversions?
The tag fires before form data is present in the page, leaving fields blank. Data is not hashed correctly in custom implementations (Google handles hashing automatically in GTM, but custom code often gets it wrong). Consent signals are blocking data collection entirely. Any of these will result in zero match rate.
| Setup Area | What To Check | Common Issue | Risk Level |
|---|---|---|---|
| Google Ads conversion action | Enhanced conversions toggle enabled in conversion settings | Feature disabled or applied to wrong conversion | High |
| GTM configuration | Enhanced conversion fields mapped to correct form field variables | Wrong variable mapped (blank or incorrect field) | High |
| Data hashing | Google handles SHA-256 hashing automatically in GTM | Custom implementation uses wrong hashing method | High |
| Form field capture | Tag fires after form data is present in DOM | Tag fires before form populates confirmation fields | Medium |
| Match rate | Check Diagnostics tab in Google Ads for match rate | Match rate below 40% suggests data quality issue | Medium |
| Consent | Data is only sent when user has consented (GDPR/CCPA) | Data sent without consent signal can cause compliance risk | High |
| Privacy policy | Customer data use disclosed in privacy policy | Enhanced conversions not mentioned | Medium |
GTM setup
- –Enhanced conversions feature is enabled in the Google Ads conversion action settings
- –GTM tag type is set to "Google Ads Conversion Tracking" with enhanced conversions section expanded
- –Variables for email, phone, first name, last name are mapped to the correct data layer or DOM fields
- –Tag fires on the correct trigger (form submission confirmation, not form start)
Website and form
- –Customer data (email, phone, name) is present in the page or data layer at the time the tag fires
- –Tag does not fire on page load before form submission completes
- –Confirmation page or thank-you page is the trigger point, not the form page itself
CRM and leads setup
- –For enhanced conversions for leads: GCLID is captured and stored with the lead record
- –Customer data is included in the offline conversion upload alongside the GCLID
- –Upload includes hashed email or phone (or Google handles hashing via API)
Privacy and consent
- –Consent Mode is configured to withhold enhanced conversion data when consent is not granted
- –Privacy policy discloses collection and use of hashed customer data for advertising measurement