All posts

Enhanced Conversions for Leads Fixes the Match. It Does Not Fix the Signal.

By Rajesh Kumar, Founder, Attribi · · Updated

Of 400 form fills, enhanced conversions for leads lifts the number matched to an ad click from
240 to 340. The CRM shows only 22 of the 400 were qualified buyers. Matching more form fills does
not change which leads were worth having.

Enhanced conversions for leads is the Google Ads feature that matches a sale or qualified lead recorded in your CRM back to the ad click that produced it, using the hashed email address or phone number the lead typed into your form. It recovers leads whose click ID was lost. It does not change which leads you tell Google are worth having, and that second problem is the one most lead gen accounts actually have.

So the argument of this page is simple. Turn it on, because it is cheap and it works. Then stop expecting it to improve lead quality, because it cannot. Lead quality changes when the conversion you upload is a stage your sales team recorded, not the form.

Below: what Google says the feature is, how it differs from enhanced conversions for web, the setup routes (Google tag, Google Tag Manager, GA4, uploads and the Data Manager API), and the 63-day limit that decides whether it can help with your closed deals at all.

How can enhanced conversions for leads be described?

Google describes enhanced conversions for leads as "an upgraded version of offline conversion import that uses user-provided data". In plain terms: you still import CRM conversions, and each one now carries a hashed email or phone as well as the click ID, so Google can match the leads where the click ID went missing.

If you landed here from the Google Ads certification question, that sentence is the description Google itself uses on its help page. The two words that matter in it are "offline conversion import". It is an upgrade to an import. If nothing is ever imported from your CRM, the feature has nothing to upgrade, whatever the settings screen says.

What are enhanced conversions?

Enhanced conversions is the umbrella name for a Google Ads feature that adds hashed, first-party data you collected (usually an email address, sometimes a phone number or name and address) to your conversion measurement. Google matches the hash against signed-in Google accounts to credit conversions that cookies and click IDs missed. There are two kinds: for web, and for leads.

Google hashes with SHA-256 and asks you to normalize first: trim whitespace, lowercase, put phone numbers in E.164 format, and for gmail.com and googlemail.com addresses remove the dots in the part before the @. Its Data Manager API formatting guide also drops a plus sign and everything after it in Gmail addresses, and accepts the hash in hex or Base64. Hash the wrong string and you get a valid-looking hash that matches nobody. The full set of rules, with test values, is in how to hash emails for conversion uploads.

One change to know about in 2026: Google says enhanced conversions for web and for leads are now combined into a single on/off setting in Google Ads, and that Google Ads accepts user-provided data from website tags, Data Manager and API connections at the same time. One switch does not make them one feature, though. They measure different things.

Enhanced conversions for web vs enhanced conversions for leads

Enhanced conversions for web improves conversions that happen on your website, such as a purchase or a self-serve signup: the tag sends hashed customer data at the moment of conversion. Enhanced conversions for leads improves conversions that happen later, offline, for people who started as a website lead: the hashed data travels with the conversion you import from your CRM.

Google's own split is the same: web is for advertisers tracking sales and events on a website, leads is for advertisers tracking offline sales that begin as website leads.

Enhanced conversions for webEnhanced conversions for leads
What it improvesA conversion the website sees: purchase, signup, bookingA conversion the CRM sees later: qualified lead, closed deal
Where the conversion is recordedThe Google tag, on the conversion pageAn import: Data Manager, the Data Manager API, a file or a connector
When hashed data is sentOnce, when the conversion firesTwice: by the tag at form submit, then on the imported conversion
Conversion action typeA website conversion actionAn offline (import) conversion action
Typical businessEcommerce, self-serve SaaSLead gen with a sales step: B2B, real estate, education, services
Upload time limitNot applicable, it fires in the browser63 days from the click on hashed data alone
Fixes lead quality?NoNo, unless the imported stage is a quality stage

Plenty of accounts need both. A SaaS company with a free signup and a sales-assisted enterprise plan has a web conversion (the signup) and an offline one (the signed contract). If your only conversion is a form fill and nothing happens after it in a CRM, enhanced conversions for web is the one you want, and the rest of this page is about a problem you do not have yet.

How does enhanced conversions for leads match a lead to a click?

Five steps: the lead clicks an ad, fills in your form, the lead is stored in your CRM, your sales
team marks the outcome, and the outcome is uploaded to Google Ads with two keys, the click ID and
the hashed email or phone. Google matches on either
key.

It gives the imported conversion a second key. Standard offline conversion import matches on the GCLID alone. Enhanced conversions for leads also sends the hashed email or phone, which Google matches against what its tag saw at form submit and against signed-in Google accounts. If the GCLID survived, it still wins.

The sequence, following Google's help page:

  1. Someone clicks your ad and lands on your site.
  2. They fill in a form. The Google tag sends a hashed copy of the email or phone at that moment.
  3. The lead is stored in your CRM.
  4. Later the lead converts: your team qualifies them, or the deal closes.
  5. You import that conversion with the hashed email or phone, plus the click ID if you have it.

The click ID goes in whenever you have it. Google's wording is "To maximize accuracy, include GCLIDs with your uploaded events whenever possible." The two keys are not alternatives. And the GCLID goes missing more often than people think: the form has no hidden field, the CRM drops a custom field when a lead is converted to a contact, or the person clicked on a phone and filled in the form on a laptop two days later. Fixing the first two is covered in how to capture the GCLID in your CRM.

What does it fix?

The leads you had already lost.

Here is an illustrative month. 400 form fills from Google Ads. On 240 of them the GCLID made it into the CRM. The other 160 have an email and a phone and no click ID. Under plain offline import those 160 are invisible to Google, whatever happens to them later. If the best deal of the quarter is among them, Google never learns which search found it.

With the second key, some share of the 160 can be matched. Not all. Google has to recognize the address or number, and a work email typed into a form is often not tied to any Google account. So the gain is real, and it is a gain in coverage. Say it reaches 340 matched. Hold that number.

What does it not fix?

A two by two grid. Weak match with a form fill signal: Google sees part of the wrong thing.
Strong match with a form fill signal: Google sees all of the wrong thing. Weak match with a CRM
outcome: Google sees part of the right thing. Strong match with a CRM outcome: the only box where
bidding learns from the leads that became
buyers.

Coverage and signal are separate problems, and this feature touches only the first.

Back to the 400. Your sales team works them and marks 22 as qualified: reachable number, real intent, budget that fits. The other 378 are job seekers, brokers, wrong numbers and brochure collectors. If the conversion you import is the form fill, moving the match from 240 to 340 means Google has a clearer view of 340 form fills, and most of those are leads you did not want. You have given the bidding system a sharper photograph of the wrong subject.

The fix for that is what you upload, which is a funnel decision, not a Google Ads setting:

  • Import the stage your sales team records, such as qualified, not only the form fill.
  • Give that stage its own conversion action, so campaigns can bid toward it.
  • Check it has volume. A conversion that happens four times a month is too thin for automated bidding to learn from, which is why closed deals alone rarely work as the bidding target in long sales cycles. The reasoning is in the lead-quality ladder.

One caution so this is not oversold. Importing CRM outcomes does not improve bidding by itself. It gives you a better conversion to bid toward. Campaigns only change behavior once that conversion is the one they optimize for and it has enough volume.

How do you set up enhanced conversions: Google tag, Tag Manager, GA4 or an upload?

Setup has two halves, and the routes split along them. The Google tag, Google Tag Manager and GA4 all handle capture: sending hashed data from your website. An upload (Data Manager, the Data Manager API, a file or a connector) handles the import. Enhanced conversions for web needs only capture. Enhanced conversions for leads needs both.

RouteWhat it doesWebLeads
Google tag (gtag.js)Sends hashed form data from the page; Google's leads guide has you enable "Form interactions" in automatic event detectionYesCapture only
Google Tag ManagerSame capture, configured in your GTM containerYesCapture only
GA4 user-provided data collectionSends hashed data with GA4 events, for GA4 conversionsYesNot covered by Google's GA4 page
Data Manager in Google AdsImports offline conversions from files, CRMs and databasesNoThe import
Data Manager APIYour code or a vendor sends conversions with click IDs and hashed identifiersNoThe import
Google Ads APIWas an upload route for these conversionsNoBlocked from 15 June 2026

A few details worth having before you start.

The terms come first. Enhanced conversions for leads works only after someone accepts the customer data terms: in Google Ads, open Goals, then Settings, find Customer data terms, select View Terms, accept and select Agree. If your conversions are tracked from a manager account, Google says the terms must be accepted from the manager account. Skipping this does not throw an error you would see in the interface. We hit what it does to an API upload, and it is in the Attribi section below.

GA4 is a web route. GA4's user-provided data collection enables enhanced conversions for GA4 conversions. Per Google's Analytics help, it needs the GA4 property linked to Google Ads and an Editor role or above, it is in open beta, it is not available to properties in the Health category, and acknowledging its policy is permanent (you can switch collection off afterwards). Nothing on that page covers importing offline conversions, so for leads it does not replace the upload. If you are deciding between GA4 and GTM as your tagging layer, the trade-offs are in GA4, GTM and CRM measurement architecture.

The import is the half people skip. A setup done entirely in the Google tag or Tag Manager feels finished, because the tag part is quick. But the tag only covers step 2 of 5. If steps 4 and 5 never happen, Google has hashed form data and nothing to match it to. Google's own Google tag setup guide for leads finishes with importing your offline data, for this reason.

The upload route changed in June 2026. Google says offline conversion imports and enhanced conversions for leads uploads move to the Data Manager API, and are blocked in the Google Ads API from 15 June 2026. Any custom script written against the old upload needs moving. The six import routes that still circulate, and which three are worth building on, are compared in Google Ads offline conversion import.

Why does the 63-day limit matter more than the match rate?

Because it decides which conversions the feature can rescue. Google accepts a conversion uploaded with a GCLID up to 90 days after the click, but one that relies on hashed personal data for enhanced conversions only up to 63 days. Past day 63, a lead with no click ID cannot be imported at all.

Offline conversion import (click ID)Enhanced conversions for leads (hashed data)
What Google matches onGCLID, WBRAID or GBRAIDHashed email or phone
Where the key comes fromThe landing page URL, captured by your formThe lead, typed into your form
What breaks itThe click ID never reaches the record you upload fromUnaccepted terms, bad normalization, an address Google does not recognize
Latest upload after the click90 days63 days
Account setupAn offline conversion actionThe same, plus the customer data terms

So the fallback has the shorter window. A deal that closes on day 75 can still be imported with a GCLID and cannot be imported on email alone. If your sales cycle runs past two months, enhanced conversions for leads will not rescue your closed-won uploads for leads that lost their click ID. A mid-funnel stage that happens inside 63 days, such as qualified, still can. That is one more reason to import a qualified stage, and to upload each stage when it happens instead of at month end.

A setup order that works

  1. Accept the customer data terms in Google Ads (Goals, then Settings). It costs nothing and it removes the quietest failure.
  2. Create one offline conversion action per funnel stage you plan to send. Lead, qualified and closed-won is a sensible set.
  3. Set up capture on your forms with the Google tag or Tag Manager, and capture the click ID in a hidden field stored somewhere that survives whatever your CRM does to lead records.
  4. Import each stage when it happens, with the click ID and the hashed email and phone on the same event. The 63 days are counting.
  5. After a week, read the enhanced conversions for leads diagnostics report. After a month, compare the count Google shows for your qualified action with the count in your CRM.
  6. Only then decide which conversion action campaigns should bid toward.

If the diagnostics show a problem, or the counts do not move, the nine causes and the order to check them in are in enhanced conversions for leads not working. This page will not repeat them.

How Attribi handles it

Attribi is the tool I build, so read this section knowing that.

When a lead reaches a stage you have mapped, Attribi uploads it to Google Ads through the Data Manager API with both keys on the event: the click ID its tracker captured at the ad click (GCLID, WBRAID or GBRAID), and the hashed email and phone, normalized to Google's rules including the Gmail dot and plus-sign handling. Lead, qualified and closed-won each go to their own conversion action, and Attribi can create those actions in your account when you connect.

Two things specific to this page:

  • It handles unaccepted terms. When we built the upload, the first request with hashed emails came back rejected as a whole request, not per event, with the reason DESTINATION_ACCOUNT_ENHANCED_CONVERSIONS_TERMS_NOT_SIGNED. Google's API reference describes it as the destination account not having agreed to the enhanced conversions terms. Attribi now resends that request with the click ID only, so leads that have one still match, and puts an "Accept Enhanced Conversions terms" prompt on your Connections page.
  • It keeps the click ID outside the CRM. The tracker holds the click ID against the visitor from the moment of the click (first-party cookie, with local storage as a fallback), so a CRM that drops custom fields on lead conversion does not break the match.

What it does not do: it cannot make Google recognize an email address Google has never seen, a lead with neither a click ID nor a matchable identifier stays unmatched, and it does not set up enhanced conversions for web in your Google tag for you. It also cannot get around the 63-day limit.

What gets sent is on the Google Ads integration page. Conversion uploads are a paid feature, not part of the free plan; pricing has the ladder. Every new workspace starts with 30 days on the Pro plan with no card required, which is enough to run it on a real campaign and check the match yourself.

Frequently asked questions

Is enhanced conversions for leads the same as offline conversion import? No. Offline conversion import matches a CRM conversion to an ad click using the click ID. Enhanced conversions for leads adds a second way to match, using the hashed email or phone the lead provided. Google describes it as an upgraded version of offline conversion import, and both keys can be sent on the same upload.

What is the difference between enhanced conversions for web and enhanced conversions for leads? Enhanced conversions for web improves conversions that happen on your website, such as a purchase, by sending hashed customer data from the tag when the conversion fires. Enhanced conversions for leads improves conversions that happen later in your CRM, by matching the imported conversion to the lead's hashed email or phone.

How long do I have to upload an enhanced conversion for leads? 63 days from the click. Google does not import a conversion that relies on hashed personal data after that. A standard offline conversion with a click ID has 90 days, so long sales cycles should also import an earlier stage, such as qualified.

Can I set up enhanced conversions for leads with GA4 instead of the Google tag? Not fully. GA4 user-provided data collection enables enhanced conversions for GA4 conversions, which are website conversions. Enhanced conversions for leads still needs an import of the outcome from your CRM, through Data Manager, the Data Manager API, a file or a connector.

Why does my enhanced conversions for leads setup show as active while lead quality stays the same? Because the feature improves matching, not the choice of conversion. If the conversion you send is still the form fill, Google sees more of your form fills, including the poor ones. Lead quality changes only when you upload a CRM outcome, such as a qualified lead, and campaigns bid toward it.

Is the customer data shared with Google in readable form? No. The email address and phone number are normalized and hashed with SHA-256 before they are sent, and Google matches on the hashed values.

The takeaway

Enhanced conversions for leads is worth turning on. It recovers leads that click ID import loses, for the price of one accepted checkbox and some care with hashing. Treat it as plumbing: it decides how much of your data reaches Google, and you still decide what that data says. If you want both handled, try Attribi free and map a qualified stage on day one.

Stop hand-hashing emails for every platform.

Attribi normalises and hashes each email the way Google, Meta, LinkedIn, TikTok and Microsoft expect, then uploads the conversion for you.

No credit card. Free up to 500 visitors a month. New workspaces start with 30 days on Pro.