Skip to content
Faisal Mahmud TusherDigital marketing, SEO & analytics
with Faisal Tusher

Google Ads & PPC › Troubleshooting

Enhanced Conversions Not Working

Why Google Ads enhanced conversions show errors or recover nothing and how to fix it: terms, missing user data, hashing, a broken base tag and consent.
Troubleshootingintermediate8 min readUpdated

First, read the diagnostics tab and a tagged test conversion

Each conversion action in Google Ads has a diagnostics view, and for enhanced conversions it reports whether hashed data is arriving, flags common implementation problems and shows a status that moves through stages as data is validated. Read the exact wording on the affected action, not the account summary, because the feature can be on for one action and missing on another. Then complete a real test conversion with Tag Manager preview or the tag assistant running, and look at three things on the conversion step: whether the conversion tag fired, whether the user-provided data variable held an email or phone number at that moment, and whether consent for advertising data was granted.

Those readings sort the causes into two groups. Diagnostics that flag a problem, or a test in which the data was empty or the tag never fired, mean the implementation is broken somewhere in the chain. Diagnostics that say recording, a test in which everything fired with data, and a conversion count that barely moved mean the feature may be working exactly as designed. The setup routes themselves, Google tag, Tag Manager and API, are described in the enhanced conversions guide and are not repeated here. If the feature is recording correctly and the remaining gap spans other vendors too, the comparison of enhanced conversions and server-side tagging covers when a server container is the next step.

Diagnosis table

Diagnosis

SymptomCheckLikely causeFix
Diagnostics show the feature off or not set up for the actionAccount customer data terms; enhanced conversions setting on that actionCustomer data terms not accepted or the feature not enabled for the actionAccept the terms; enable the feature for the account or the action and choose the data source
Diagnostics report missing or no user-provided dataData variable on the conversion step in previewUser-provided data not captured on the conversion pagePush the values into the data layer before the tag fires, or fix the selectors
Data arrives but matches poorly, or diagnostics flag formattingRaw values before hashing; how the API or upload hashes themData sent unhashed, badly formatted or normalised wronglyNormalise as Google documents before hashing, or let the tag hash
No enhanced data and the base action records nothing recentConversion action status; whether the tag fires on the success pageBase conversion tag itself not firingFix the base tag first using the conversions-not-tracking diagnosis
Data appears for some visitors only, often by regionConsent state on the conversion step for declining visitorsConsent not granted, so the data cannot be sentWire the banner to consent mode correctly; accept that declined visitors send nothing
Diagnostics healthy, counts flatBefore-and-after comparison by device and campaignRecording correctly but recovering little because click IDs already matchedAccept the result; judge the feature where identifiers were weakest

Fix, verify and prevent each cause

Terms not accepted, or the feature off for this action

Enhanced conversions cannot be enabled until the account accepts Google's customer data terms, and the setting can be applied account-wide or per conversion action with a choice of how the data will be supplied. An account where the terms were never accepted, or where the feature was switched on for an older action and not for the one now used in bidding, will show nothing for the action that matters.

Fix: confirm the terms in the account's conversion settings, then enable enhanced conversions for the specific action and choose the method that matches the implementation, as the enhanced conversions guide describes; the help page on enhanced conversions sets out the requirements.

Verify: the action's diagnostics move from not set up to receiving data once live conversions arrive.

Prevent: whenever a new conversion action replaces an old one, copy its enhanced conversions setting as part of the change.

The page never supplied the customer's details

The most common technical failure is an empty variable. The tag fires on the thank-you page, but the email address the customer typed two steps earlier is no longer on the page, the data layer push happens after the tag fires, or automatic detection picked up the newsletter box instead of the checkout field. The diagnostics report missing data, and preview shows the variable blank at the moment of conversion.

Fix: push the email and phone into the data layer at the moment of conversion and read them from there in Tag Manager (GTM), or specify the exact selectors or variables when using the Google tag, following the setup notes in the enhanced conversions guide.

Verify: a fresh test shows the variable populated on the conversion step and empty elsewhere, and diagnostics stop flagging missing data.

Prevent: add the data layer values to the developer checklist for any change to the checkout or lead form.

Values formatted so they never match

Hashing is deterministic: a capital letter, a stray space or a phone number without its country code produces a different hash from the one Google holds, so nothing matches and no error appears. When the Google tag or the Tag Manager conversion tag hashes the data, normalisation is handled; when the business hashes before an API or file upload, or sends values in an unexpected form, it is not.

Fix: inspect the raw values before hashing, apply the normalisation Google documents for each field (email trimmed and lower-cased, phone in international format, names and address parts per the field rules), and hash only after normalising, or move to a route where the tag does the hashing.

Verify: diagnostics stop reporting formatting issues and, for upload-based leads, the share of uploaded rows that match rises on the next upload.

Prevent: keep the normalisation in one shared function that every upload uses.

The base tag is not firing

Enhanced conversions cannot enhance a conversion that is never recorded. If the action reports no recent conversions, an inactive tag or an unverified status, the enhanced data is the wrong place to look.

Fix: diagnose the base action first, following the conversions not tracking diagnosis: tag placement, Tag Manager triggers and publishing, consent, auto-tagging and action settings, with the build steps in the conversion tracking setup tutorial. The conversion tracking help page describes how the base tag records conversions.

Verify: the base action records test and real conversions, and the enhanced diagnostics then begin to receive data.

Prevent: monitor the base action's status after every site release, before anyone looks at the enhanced layer.

Where a consent banner is in place, a visitor who declines advertising data should send no enhanced data, and the diagnostics will show data arriving only for those who agreed. That is compliance, not a fault. The fault is a banner that is not wired to consent mode correctly, so that visitors who agreed are treated as declining, or defaults that are never updated after a choice.

Fix: check in preview that the consent update fires before the conversion tag and carries the visitor's choice for advertising data, as the consent mode guide describes, and confirm the privacy notice discloses the sharing.

Verify: for a test visitor who accepts, the conversion step shows consent granted and the enhanced data present; for one who declines, neither is sent.

Prevent: retest consent and conversion tags together whenever the banner or its vendor changes.

Working, with little left to recover

The feature recovers conversions the click identifier was losing, so its gain is proportional to what was lost. In an account with short purchase cycles, mostly desktop traffic and high consent rates, the click identifier already matched most conversions, the diagnostics say recording, and the counts barely move. That is a correct result.

Fix: compare a stable period before enabling the feature with a similar period after it, by device and campaign, rather than reading the total, as the enhanced conversions guide recommends; expect gains where journeys are long or cross devices, where storage is restricted, and in lead businesses using the leads variant.

Verify: any rise is concentrated where identifiers were weakest, which is the feature's signature.

Prevent: record the expected effect before enabling the feature, so a small change is not later read as failure.

Prevention: data capture tested with every form change

Enhanced conversions break quietly, usually because someone changed a form, a checkout step or a consent banner without knowing the tag depended on it. The defence is to make the dependency visible. Document, beside each conversion action, where the customer data comes from (a data layer key, a selector or an upload), which team owns that source, and which consent signal gates it. Add a test conversion with preview running to the release checklist for any change to forms, checkout, thank-you pages, the data layer or the banner, and read the action's diagnostics a few days after each release.

Keep the measurement expectations honest at the same time. Enhanced matching changes how many conversions are counted and therefore what Attribution assigns to each campaign, so note the date it was enabled on the reporting dashboards. Where a server-side route is used for leads, keep a single upload path rather than running a click-identifier import beside it, which double counts. Meta's equivalent, described in the Conversions API entry, has its own diagnostics; teams running both should test them together, since one data layer usually feeds both.

Illustrative example — not a real result

A furniture retailer's enhanced conversions stop matching

A furniture retailer has run enhanced conversions for web through Tag Manager for a year. In March the diagnostics for its purchase action change to report missing user-provided data on 92% of conversions, two weeks after a checkout redesign. Purchases in Google Ads fall by about 6%, while orders in the shop are steady. In preview, the purchase tag fires on the confirmation page, but the email variable is empty: the new checkout pushes the customer's email into the data layer after the confirmation page loads, and the tag fires first. The developers move the push ahead of the event that triggers the tag. A test order shows the variable populated, the diagnostics return to recording within a week, and reported purchases recover to their previous share of shop orders.

Common mistakes

Enabling the feature on an action whose base tag is broken. Reading recording as recovering. Hashing values without normalising them. Letting automatic detection guess the field on a complex checkout. Sending data regardless of consent. Judging the feature on the account total instead of where identifiers were weakest.

Frequently asked questions

The diagnostics say recording, so why have conversions not increased?

Recording means Google is receiving usable hashed data; it does not say how many extra conversions were matched, and Google does not show enhanced-matched conversions as a separate column. If most conversions were already matched through the click identifier, because the sales cycle is short, traffic is mostly desktop or consent rates are high, there is little left to recover. Compare a stable period before and after enabling the feature, and look for a rise where the click identifier was weakest.

Do we need to hash the email address ourselves?

Not when the Google tag or the Google Ads conversion tag in Tag Manager collects the data, because the tag hashes it before sending. When data is sent through the API or an upload, hashing and normalisation are your responsibility, and a value that is not trimmed, lower-cased or formatted the way Google documents will produce hashes that never match.

Can enhanced conversions fix a conversion action that records nothing?

No. The feature supplements a conversion tag that already fires; it does not replace it. If the base action shows no recent conversions or an inactive tag, diagnose that first with the conversions-not-tracking page, then return to enhanced conversions once the base count is reliable.

Terms used on this page

Also related

Sources

  1. About enhanced conversions — Google Ads Help
  2. About conversion tracking — Google Ads Help

Related