Enhanced conversions not working
The conversion action shows Check enhanced conversions, the diagnostics data quality is Needs attention or No recent data, or coverage and match rate stay empty after setup.
Steps checked against the platforms' documentation on November 20, 2026.
Quick answer
Most often the user data simply isn't present when the conversion tag fires, so the em parameter is sent empty. Open the conversion action's Diagnostics tab to read the alert, then run a test conversion and check the conversion hit for tv.1~em followed by a long hashed string. If the hit is fine, confirm the customer data terms are accepted and the method selected in Google Ads matches how you send the data.
1. User data isn't available on the page where the conversion fires
Google requires the customer data to exist on the page where the conversion tag fires. Forms that redirect to a thank-you page lose the email field, and automatic detection or CSS selectors then find nothing. Diagnostics report this as Missing user-provided data or Missing user data fields.
How to check
- 1Go to
Goals>Summary, hover over the action's status, selectDetails, then open theDiagnosticstab and read the alerts. - 2Run a test conversion with Tag Assistant and open the conversion hit. Look for the
emparameter:tv.1~emfollowed by a long string means hashed data was sent;tv.1~emwith nothing after it means it was empty. - 3In GTM Preview, select the conversion event and check the
Google Ads Enhanced Conversionsobject underVariables.
How to fix
- 1Capture the email (and phone or address if collected) at submission and push it to the
dataLayerwith the success event, then read it with a User-Provided Data variable inCodeorManual configurationmode. - 2If the data only appears on an earlier page, use a user-provided data event tag on that page, as Google suggests.
- 3Remove fields the form doesn't collect rather than sending them blank, and re-test until the hit shows a hashed value.
2. Customer data terms not accepted
Enhanced conversions data isn't processed until someone accepts the customer data terms, and data sent before acceptance is not processed retroactively. Diagnostics show Enhanced conversions not in use.
How to check
- 1Open the action's
Diagnosticstab and look forEnhanced conversions not in use. - 2Go to
Goals>Settings, expandEnhanced conversionsand check whetherTurn on enhanced conversionsis ticked and the terms are agreed.
How to fix
- 1Have an admin on the client account accept the terms and save. The client should do this or approve it, since the terms bind the advertiser.
- 2Treat data before that date as lost for enhanced conversions and note it for reporting.
3. The method selected in Google Ads doesn't match how the data is sent
In the enhanced conversions settings you choose Google tag, Google Tag Manager or the Google Ads API. Google warns data may not be processed if it arrives through a different method than the one selected. Agencies migrating from a hard-coded tag to GTM, or adding a server-side or API setup, often forget to change this.
How to check
- 1Go to
Goals>Settings>Enhanced conversionsand note the selected method. - 2Check how the site actually sends user data: a
user_dataparameter in GTM, agtagsnippet, automatic detection in the Google tag, or API uploads. - 3If you use the API alongside the tag, look in diagnostics for alerts such as
Tag and Ads API order IDs don't matchorMissing transaction ID from conversion event.
How to fix
- 1Set the method to the one actually in use and save.
- 2Avoid running two collection methods for the same action without a reason. If you do combine tag and API, send the same order ID from both and include a transaction ID in tag hits.
- 3Re-check diagnostics after about 48–72 hours.
4. Data is badly formatted or hashing fails
Diagnostics alerts such as Setup has incorrect data formatting, User email data field is incorrectly formatted or User address data field is incorrectly formatted mean the values arrive but can't be matched. Error codes in the em parameter also point to the cause: e1 is an unsupported browser, e2 is a SHA-256 hashing failure, e3 means the page isn't served over HTTPS.
How to check
- 1Inspect the
emvalue in Tag Assistant fore1,e2ore3. - 2Log the raw values your variable returns in GTM Preview: look for whitespace, capitals, placeholder text, or phone numbers without a country code.
- 3If you hash yourself, compare your output with a known SHA-256 hash of the same normalized test email.
How to fix
- 1Trim whitespace and lowercase emails before hashing. Format phone numbers with a
+and country code, 11–15 digits, no spaces, dashes or brackets. - 2For addresses, send
countryas a 2-letter ISO code with first name, last name and postal code together, as all four are required when address is used. - 3Serve the conversion page over HTTPS, send values as strings, and let the Google tag hash plain values unless you have a reason to pre-hash.
5. ad_user_data consent is denied
When ad_user_data is denied, personal data collection for advertising is disabled, and Google lists hashed first-party data for enhanced conversions as affected. A CMP that never sets this signal, or maps it to the wrong category, leaves coverage near zero even though the tag works.
How to check
- 1In Tag Assistant, open the conversion event's
Consentview and check the state ofad_user_dataafter you accept the banner. - 2Repeat a test with the banner declined and confirm the behaviour matches what the client's consent policy intends.
How to fix
- 1Update the CMP integration so
ad_user_datais set by default and updated on acceptance, alongsidead_storage,ad_personalizationandanalytics_storage. - 2Make sure the consent update happens before the conversion tag fires on the success page or event.
Stop it happening again
- Design forms so the email is pushed to the
dataLayerwith the success event, not left on a previous page. - Include an
emparameter check in every release QA for pages that carry a conversion tag. - Keep the enhanced conversions method in Google Ads in line with the live implementation and record it in the client's tag map.
- Review the
Diagnosticstab monthly. Alerts need at least 20 conversions in 7 days to appear, so low-volume actions need manual checks. - Re-test consent signals whenever the CMP or banner configuration changes.