Enhanced conversions not working?
Enhanced conversions usually fail for one of four reasons: the feature isn't switched on in the Google Ads account, the tag doesn't pick up customer data at the moment of conversion, consent stops the data being sent, or the data is in the wrong format. The conversion action's diagnostics and a test order will tell you which.
Symptom
You turned on enhanced conversions, but Google Ads still shows a warning on the purchase conversion action, or the diagnostics say no or little customer data is received. Or nothing obviously changed and you can't tell whether it works.
Enhanced conversions add hashed first-party data, such as the customer's email address, to a conversion that is already being sent. If the base conversion doesn't record, fix that first: see Google Ads conversions not recording.
Possible causes
- Cause A: not enabled at account level. Enhanced conversions must be turned on in the Google Ads conversion settings, with Google's customer data terms accepted. Google's setup help says that since April 2026 enhanced conversions for web and for leads are a single setting, and you no longer choose between implementation methods.
- Cause B: the tag finds no data. With automatic detection, the tag may not find an email on the confirmation page, or may pick up the wrong one, such as a newsletter field. With manual setup, a CSS selector or JavaScript variable may point at an element that doesn't exist on that page.
- Cause C: consent. If the visitor hasn't granted the advertising consent signals Google's consent mode uses, including
ad_user_data, user-provided data shouldn't be sent, and your setup may correctly withhold it. - Cause D: data quality. Email addresses with spaces or capitals, phone numbers not in international format, or values hashed in the wrong way before sending.
- Cause E: two routes, one configured. The Shopify Google and YouTube app sends the conversion, but you configured enhanced conversions in Google Tag Manager (GTM), or the reverse.
How to check
- Check the account setting. In Google Ads, Goals, Settings, look at the enhanced conversions section: whether it is on, and any message about terms or eligibility.
- Check the conversion action's diagnostics. Open the purchase conversion action and look for its diagnostics view. Note the status and any warning about missing or badly formatted data.
- Find what sends the conversion. Shopify app, GTM, plugin or hard-coded tag. Enhanced conversions must be set up on the same route. In GTM, open the Google Ads conversion tag and check whether user-provided data is included, and from which variable.
- Place a test order. With consent accepted, watch the conversion request in DevTools. Look for a parameter carrying hashed user data alongside the label and order ID. Then repeat with consent declined and note the difference.
- Inspect the source data. On WooCommerce, check the email is on the thank-you page or in the dataLayer when the tag fires. On Shopify with a custom pixel, check that the checkout data the pixel receives includes the email and phone, and how your code passes them on.
Illustrative manual setup with the Google tag, with invented customer data:
gtag('set', 'user_data', {
email: 'jane.example@example.com',
phone_number: '+447700900123',
address: { first_name: 'Jane', last_name: 'Example', postal_code: 'SW1A 1AA', country: 'GB' }
});
The phone number uses international format. If you hash values yourself before sending, follow Google's normalisation and hashing rules exactly, or let the Google tag do the hashing.
What the result means
- Setting off, or terms not accepted: cause A. Nothing else matters until that is done.
- Conversion request has no user data with consent granted: cause B or E.
- User data only with consent granted: expected behaviour, cause C. Coverage will reflect your consent rates.
- Data sent but diagnostics show low quality or match rates: cause D.
Limitation. Enhanced conversions improve how conversions are matched to ad interactions. They don't create conversions that were never sent, and diagnostics in Google Ads can take days to reflect a change. A healthy setup can still show modest coverage if many customers decline consent. Judge it over weeks, not the morning after.
How to fix it
- Turn the feature on, and accept the customer data terms if appropriate for your business.
- Configure it on the same route that sends the purchase conversion. One route.
- Supply the data explicitly where possible (a dataLayer value or the checkout data in a custom pixel) rather than relying on page scraping.
- Normalise: trim and lower-case emails, use international phone format, and send only fields you actually collect.
- Respect consent. Don't send user-provided data when advertising consent is denied.
- Re-test with a fresh order, then review diagnostics over the following days.
What not to do
- Don't send customer data without a lawful basis and a privacy notice that covers it.
- Don't put raw email addresses in URLs, page titles or Google Analytics 4 (GA4) parameters while setting this up.
- Don't hash twice, or hash before normalising.
When to request help
Our Google Ads and Meta conversions service checks the conversion route, the enhanced conversions setup, consent behaviour and data quality, with evidence from test orders and Google Ads diagnostics. It doesn't promise better campaign results, only correctly configured signals.
Related guides:
- Google Ads conversions not recording?
- Why are purchase events counted twice?
- Shopify GTM is in the theme. Is checkout covered?
Not sure what's wrong?
Send us your store address. Mikael will review the visible tracking signals and explain what can be checked from your public pages.
Sources and updated date
- Google Ads Help: About enhanced conversions
- Google Ads Help: Set up enhanced conversions for web using the Google tag
- Google Ads Help: Set up enhanced conversions for web using Google Tag Manager
- Google Ads Help: About consent mode
- Google for Developers: Set up consent mode on websites
- Shopify Developer docs: checkout_completed
Last checked against official documentation: 18 November 2026.