Conversion Tracking & Data

Enhanced Conversions for Leads vs Offline Conversion Import: Which Join Key to Use

In short: Both get a delayed, offline outcome - a qualified lead, a signed contract, a closed sale - back into Google Ads so bidding can learn from revenue instead of just form fills. Offline Conversion Import is the general upload process: you store an identifier through your CRM, then push the outcome, time, and value back later. Enhanced Conversions for Leads is a specific join method used inside that process - it hashes the lead's email or phone at the form itself, so a match can happen even if a gclid never made it into your CRM. Most working setups use ECL as the identifier inside an offline conversion import rather than treating them as separate systems. Use ECL when your CRM is the weak link for click IDs; lean on classic gclid-based import when your CRM reliably preserves it and you want the cleanest click-level match.

By the AdFlint research team · Fact-checked against current Google and Meta platform behavior · Last reviewed July 2026

Enhanced 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 definition

Offline Conversion Import

Uploads conversions that happened outside the website, such as a signed contract or a phone sale, back to the ad platform.

You store the click identifier, gclid for Google or the lead's hashed details, capture the outcome in your CRM, then upload conversion time and value so bidding learns which clicks produced revenue. It is essential for anything with a sales cycle. Uploads fail most often on window and timezone problems: a conversion recorded after the click-through window closes, or timestamps submitted in the wrong account timezone, is discarded.

Full definition

Side by side.

The differences that actually change what happens in your account.

	Enhanced Conversions for Leads	Offline Conversion Import
Join key used to match the upload	Hashed email and/or phone number, captured the moment the lead form is submitted.	Usually the gclid stored in the CRM record, though the same hashed identifiers ECL uses are also accepted.
What breaks the match	Inconsistent normalization - mixed case, stray whitespace, or a stripped plus-sign in an email before hashing.	A gclid that never made it into the CRM field, got truncated, or came from a different account's click.
When you set it up	At the lead form itself, before you know the outcome - it's a capture-time decision.	At upload time, whenever the deal closes - the capture-time work is just making sure an identifier survived.
Where it's configured in Google Ads	A toggle on the conversion action plus a small tag or lead-form-listener change.	The conversion action's Import source, then a recurring upload via UI, Sheets, Zapier, or the API.
Attribution precision	Probabilistic - Google matches hashed identifiers against its own signed-in user data, so some matches are modeled.	Deterministic when gclid is intact - the upload points at the exact click, keyword, and ad.
What it needs from your CRM	Nothing extra - the hashed identifier travels with the lead record once the tag is set up.	A dedicated field that survives every handoff between your form, your CRM, and your sales team.
Typical use case	Long, messy sales cycles where the CRM changes hands enough times that gclid gets dropped along the way.	Any offline outcome - a phone sale, a signed contract, an in-store visit - where you control the pipeline end to end.
Failure mode	Silent match-rate decay - fewer conversions attribute back, with no error message telling you why.	Rejected rows - conversions uploaded outside the click-through window or with the wrong timezone are dropped outright.

What actually separates them.

ECL is a join method you configure at the point of lead capture; OCI is the recurring upload process you run afterward, and the two normally combine rather than compete.

Losing a gclid kills a classic offline import row outright, but the same lead can still match under ECL because the hashed identifier travels independently of the click ID.

ECL's match quality depends entirely on hashing hygiene at the point of capture; OCI's depends on pipeline integrity - whether the stored identifier survives every system it passes through.

OCI can run with only a gclid and no PII at all, which matters if your privacy policy or legal team won't sign off on hashing customer contact data.

ECL's modeled matching can report more conversions than a gclid-only import would surface from the identical lead list, so a jump in conversions after enabling ECL reflects better matching, not new demand.

Which one should you use?

Use Enhanced Conversions for Leads when

Your CRM changes ownership multiple times between form fill and closed deal, and gclid keeps getting dropped along the way.
Sales reps update lead status manually and there is no reliable field carrying a click identifier.
You already collect email and phone at the lead form and can hash them without new legal sign-off.
You're seeing a gap between clicks reported by Google Ads and leads showing up in your CRM, and you suspect it's a matching problem, not a volume problem.
You want match resilience across devices, since a lead might click on mobile but call in from a landline.

Use Offline Conversion Import when

You control the full pipeline from ad click to closed deal and can guarantee gclid survives every handoff.
The conversion is something other than a lead - an in-store visit, a phone sale, a signed contract - where hashed identity matching would add complexity you don't need.
You need airtight, deterministic attribution to a specific keyword or ad for reporting, not a probabilistic match.
Legal or privacy review won't approve hashing and transmitting customer PII, so gclid is the only identifier you're allowed to use.
You're uploading conversions from a source, like a POS or booking system, that already logs gclid as a matter of course.

Common questions.

Do I have to choose between Enhanced Conversions for Leads and Offline Conversion Import?

No - in most accounts ECL is the identifier you select inside an offline conversion import setup, not a separate system. You can even upload with both gclid and hashed identifiers on the same conversion action so Google matches on whichever one survived.

Why did my offline conversions drop after I enabled Enhanced Conversions for Leads?

Check that the hashed values you upload later match, after normalization, the ones the tag hashed at the lead form. A mismatch in lowercasing, whitespace, or which field you hashed - phone with or without a country code, for example - produces silent non-matches rather than an error.

How long can I wait before uploading an offline conversion?

You're bound by the click-through conversion window set on the conversion action, commonly somewhere between 30 and 90 days depending on how it's configured. A conversion uploaded after that window closes, measured from the original click, gets rejected regardless of which identifier you used to match it.

Does Enhanced Conversions for Leads work without a website form?

It needs a capture point where you can hash the customer's email or phone before you know the outcome, which is almost always a web or app lead form. A conversion that starts as a cold call with no prior digital touchpoint has no hashed identifier to attach, so it falls back to whatever offline import method you have for that channel.

Or stop choosing between them.

AdFlint picks the setting, writes the ads, and keeps optimizing inside the Google and Meta accounts you already own.

Try AdFlint free See how it works

Related comparisons

All comparisons