Enhanced conversions for leads , hashed and merged into one setting

What enhanced conversions for leads actually sends#

Google is blunt about what enhanced conversions for leads does under the bonnet. Google Ads Help, 2026 describes enhanced conversions as a feature built to improve the accuracy of conversion measurement and unlock more powerful bidding, and it works by supplementing the existing conversion ping rather than replacing it. Nothing about the original conversion action changes. Hashed first party identifiers, most often an email address, simply ride alongside the tag Google Ads already fires, whether that tag lives on a website form or in an imported offline event.

The hashing mechanism is named plainly too: enhanced conversions for leads uses a secure one-way hashing algorithm called SHA256 on first party customer data before anything leaves the account. SHA256 turns an email address into a fixed length string that cannot be reversed back into the original address. That one-way transform is hashed email conversion matching in practice: Google Ads compares two independently hashed strings, not two raw email addresses, so a match can be confirmed without either side exposing the underlying contact detail. The identifier goes to earth, and only the match survives above ground.

A short word on scope, since the two names get muddled constantly. Enhanced conversions for web tags a live website event, a purchase or a form submit, the moment it happens. Enhanced conversions for leads is the offline cousin: it supplements imported CRM events, the sale that closes three weeks after the enquiry, with the same SHA256 hashed identifiers. For the broader anatomy of conversion measurement, from action statuses to counting rules, folkfox's conversion tracking entry is the place to start; this one stays fixed on what enhanced conversions for leads adds on top.

The June 2026 merge: one setting, not three#

Until recently, setting this up meant picking a lane and staying in it. Enhanced conversions for web sat behind its own toggle, enhanced conversions for leads sat behind another, and each demanded a single implementation method chosen up front, the Google tag, Google Tag Manager or the Google Ads API, with no mixing. That structure is being retired. Google Ads Help, 2026 states plainly that enhanced conversions for web and enhanced conversions for leads will soon be combined into a single on/off setting, starting in June 2026 (checked 11 August 2026).

The practical payoff is stated in the same update: advertisers no longer need to choose a single implementation method like the Google tag, Google tag Manager or the Google Ads API (Google Ads Help, 2026). Existing accounts do not need to lift a finger. Anyone who has already accepted Google's customer data terms is migrated to the merged status automatically, so the June 2026 date is a quiet cutover, not a deadline to race against.

That last row matters for anyone with a custom pipeline. From 15 June 2026, offline conversion imports and enhanced conversions for leads uploads move onto the Data Manager API and are blocked from the classic Google Ads API route, so a developer token that has not sent a request in the run up to that date risks losing legacy access entirely.

Why enhanced conversions for leads matters past the 90 day window#

Pure GCLID matching has a ceiling, and Google names it directly. Offline conversion imports run on a click-to-conversion cycle that is less than 14 days or 90 days, depending on the data source. That is the hardcoded edge GCLID-based CRM matching lives inside: the click record only stays fresh for so long, and once the window shuts, an offline conversion has nothing left to match against, however genuine the sale.

For anything with a short sales cycle that ceiling is academic. For anything with a longer one, a considered purchase, a B2B enquiry, a quote that takes six weeks to close, it is a genuine gap. This is the exact terrain enhanced conversions for leads was built to sit inside. It is, in Google's own words, an upgrade to offline conversion import that uses user-provided data, such as email addresses, to supplement imported offline conversion data (Google Ads Help, 2026), letting an advertiser import user-provided data in addition to the identifiers already imported through GCLID (Google Ads Help, 2026).

Be precise about what that buys you. Layering hashed identifiers through enhanced conversions for leads on top of the GCLID does not officially stretch the 90 day cycle itself; Google has not published a longer window for the hashed route specifically. What it does is give Google Ads a second matching signal the moment a CRM record lands, rather than one expiring cookie carrying the entire weight of attribution. For any pipeline where the lead-to-sale gap regularly runs past three months, a second signal beats a single scent trail that goes cold on day 91.

Google Ads Data Manager: the codeless way in#

For any account without an engineering queue, Google Ads Data Manager is where enhanced conversions for leads becomes a form to fill in rather than code to write. Connect Google Cloud Storage, Amazon S3, HTTP, SFTP, gSheets, Salesforce or HubSpot, map the columns, and Data Manager does the cunning, unglamorous burrow work behind the scenes. It will normalise relevant PII fields, perform hashing and encoding, and push the data to the API on your behalf (Google Ads Data Manager Help, 2026). No pre-formatting, no manual SHA256 step: Data Manager hashes the data using the SHA256 algorithm, the industry standard for one-way hashing (Google Ads Data Manager Help, 2026).

Import timing still follows a connector-specific rhythm worth planning around. For Google Cloud Storage, Amazon S3, HTTP, SFTP and gSheets, Google Ads Data Manager imports conversions from 90 days ago in every run (Google Ads Help, 2026), while Salesforce and HubSpot connectors take a 14 day first pull before switching to incremental syncs. Either way, the codeless route only closes the gap between your CRM and the API; it never removes the underlying 90 day matching ceiling covered above.

Advertisers building their own pipeline rather than using Data Manager reach the same endpoint through the Google Ads API. For privacy considerations, the API documentation requires that email address, phone number, first name, last name and street address must be hashed using SHA-256 before being imported (Google Ads API documentation, 2026), and every upload has to populate the user_identifiers field with that normalised, hashed data before Google Ads will accept the conversion at all (Google Ads API documentation, 2026).

Consent: without ad_user_data, the enhancement drops#

None of the hashing above moves an inch without the right consent signal. Google names the specific flag: the ad_user_data consent type is required for measurement use cases, such as enhanced conversions and tag-based conversion tracking (Google Tag Manager Help, 2026). Deny it and the consequence is spelled out just as directly: using personal data for online advertising is disabled, including use cases supported by user_id and user-provided data (Google Tag Manager Help, 2026). The hashed identifier is simply never sent.

The Google tag documentation confirms the same gate from the other direction. Regardless of the collection method, user-provided data collection will not begin at all until an account has accepted Google's terms of service, and if the Google tag detects user-provided data presented for a destination that has not accepted those terms, the data will not be collected or processed by Google (Google Ads Help, 2026).

Through Tag Manager the same principle holds for the cookie side: if Consent Mode is implemented, the ads cookie is subject to the ad_storage consent status of the Consent Mode feature, where implemented (Google Ads Help, 2026), and Consent Mode's ad_storage setting more broadly controls the usage of Google Ads cookies and IDs from the Google Analytics tag and Firebase SDK in Google Ads (Google Ads Help, 2026).

The consented, compliant version of enhanced conversions for leads is not a workaround for consent, it is built on top of it. Skip the consent signals and every hashed identifier, every SHA256 string, every carefully mapped CRM field simply goes nowhere.

How can an advertiser set up enhanced conversions for leads?#

Once consent and hashing are understood, setting up enhanced conversions for leads is mostly a sequence of routine, checkable steps rather than a single clever trick.

That last step catches more setups than any of the others. The enhanced conversions diagnostics report ties data quality directly to coverage: what percentage of your eligible conversion events include sufficient user provided data over time (Google Ads Help, 2026). A tag installed correctly on a form with three fields still reports low coverage, not because the tag is broken, but because there is genuinely little to hash. Widening the form, adding an email field where only a phone number was asked for, moves that number more reliably than any tag reinstall.

Practitioners moving from a pure offline conversion import setup have one more small habit to add. A Google tag configured for enhanced conversions for leads collects GCLIDs automatically, but Google's own guidance is to keep importing existing GCLIDs to ensure offline conversions are properly attributed to specific ad clicks (Google Ads Help, 2026), rather than assuming the new hashed identifiers make the old habit redundant. For the wider measurement picture this setup feeds into, from action statuses to conversion windows, folkfox's attribution models entry is the natural next stop.

Frequently asked questions#