Enhanced Conversions vs Enhanced Conversions for Leads
In short: Both attach hashed customer identity to a conversion so Google can match it past cookie and click-ID loss, and both use the same SHA-256 hashing approach, but they're built for opposite timing. Enhanced Conversions enriches a conversion that fires in the same session, like a checkout confirmation. Enhanced Conversions for Leads is built for outcomes confirmed weeks later in a CRM, using a two-step upload instead of a single live tag. EC generally supplements a conversion that already has a GCLID; ECL is designed to work even when no GCLID was ever captured at all. If the value is known the moment the tag fires, use EC; if the value only becomes clear after your sales team works the lead, use ECL.
By the AdFlint research team · Fact-checked against current Google and Meta platform behavior · Last reviewed July 2026
Enhanced Conversions
Sends hashed first-party customer data with a Google Ads web conversion so Google can match it to a signed-in user.
At the conversion, your page or server passes email, phone, or address fields hashed with SHA-256; Google matches them against signed-in accounts and recovers conversions the cookie alone would have missed. Turn it on whenever the confirmation step already captures customer details. The frequent mistake is enabling the setting without actually supplying the fields, since the toggle does nothing if no user-provided data reaches the tag.
Full definitionEnhanced Conversions for Leads
Captures hashed lead details at form submission so a sale closed later in your CRM can be uploaded back without a click ID.
The lead form hashes the email or phone at submit; when that lead becomes qualified or closed, you upload the same hashed identifier with the outcome and Google reconnects it to the original ad click. It is the practical way to optimize on revenue for offline sales cycles. The recurring problem is inconsistent normalization, meaning lowercase, trim, and strip formatting, which quietly destroys match rates.
Full definitionSide by side.
The differences that actually change what happens in your account.
| Enhanced Conversions | Enhanced Conversions for Leads | |
|---|---|---|
| What conversion it enriches | An existing real-time web conversion - a purchase or signup - fired on the same visit. | A lead-status change confirmed later in your CRM, well after the original visit. |
| Timing | Near-real-time - hashed data rides along with the conversion tag as it fires. | Two-step and asynchronous - hash at form submit, then upload again when the outcome is known. |
| Click ID dependence | Usually supplements a conversion that already has a GCLID from that session. | Built to work even when no GCLID was ever captured, hashed identity alone can carry the match. |
| Setup effort | A toggle plus supplying verified fields on an existing tag, typically minutes. | CRM integration work plus mapping lead-status changes to a later upload. |
| What it reports as | Incremental lift on conversions that already existed. | New conversions - often converting a lead action into a qualified or closed value it never had before. |
| Failure mode | The toggle silently does nothing if no user-provided data reaches the tag. | Inconsistent normalization between the value captured at lead time and the value uploaded at close quietly kills match rate. |
| Typical use case | Ecommerce checkout or straightforward signup with a confirmation page. | B2B or service lead gen with a sales cycle between form fill and close. |
What actually separates them.
EC enriches a conversion that already fires in the same session; ECL is built for outcomes confirmed long after the visit, through a separate CRM upload.
EC generally supplements a conversion that already has a GCLID; ECL is designed to work even when no GCLID was ever captured at all.
EC is essentially a one-time tag configuration; ECL requires an ongoing pipeline - capture at lead time, then push again when the CRM outcome changes.
EC shows up as incremental lift on conversions you already had; ECL can add conversions and values that never existed in the account before.
Both hash identity the same way, but EC's data usually arrives automatically as part of the page's tag lifecycle, while ECL's data arrives on whatever cadence your CRM integration runs.
Which one should you use?
Use Enhanced Conversions when
- You run an ecommerce checkout or signup flow where the conversion and confirmation happen in one session.
- Your confirmation page already captures verified email or phone.
- You want a quick, low-effort improvement to an existing conversion action.
- You're not dealing with a multi-week sales cycle.
Use Enhanced Conversions for Leads when
- You run B2B or service lead gen where leads qualify or close well after the click.
- Your CRM tracks lead status changes you can hook an upload to.
- You want bidding to optimize toward qualified or closed leads, not raw form submissions.
- You rarely capture a clean GCLID at the point of lead capture.
Common questions.
Are Enhanced Conversions and Enhanced Conversions for Leads the same setting?
No, they're related but configured differently. Standard enhanced conversions enrich a conversion that fires in the same session; enhanced conversions for leads is built specifically for lead-gen businesses where the valuable outcome is confirmed later in a CRM, and it uses a separate upload step rather than a live tag.
Can I use both on the same account?
Yes. It's common to run standard enhanced conversions on quick-conversion actions like a demo request confirmation, and enhanced conversions for leads on that same lead once it's qualified or closed in the CRM - they're not mutually exclusive, they cover different points in the funnel.
Which one do I need if my sales cycle takes weeks?
Enhanced conversions for leads. Standard enhanced conversions assumes the meaningful outcome is knowable at the moment the tag fires; if the real value only becomes clear after your sales team works the lead, you need the CRM upload workflow that ECL is built around.
Or stop choosing between them.
AdFlint picks the setting, writes the ads, and keeps optimizing inside the Google and Meta accounts you already own.
Related comparisons
- Conversions API vs Meta Pixel
- Google Tag vs Meta Pixel
- Google Tag Manager vs Meta Pixel
- Meta Pixel vs Server-Side Tagging
- Enhanced Conversions for Leads vs Meta Pixel
- GA4 Conversion Tracking vs Meta Pixel
- Conversions API vs Google Tag Manager
- Conversions API vs Server-Side Tagging