Conversion Tracking & Data

Enhanced Conversions for Leads vs Google Tag

In short: Both are part of reporting a conversion back to Google Ads tied to an ad click, but they cover different halves of the timeline. The Google tag handles the immediate, on-site half: firing the event when the form is submitted and capturing the gclid. Enhanced Conversions for Leads handles the delayed half: it hashes the lead's email or phone at that same submission, then lets you upload the outcome - qualified, closed, revenue - weeks later using that hashed identifier instead of the click ID. The Google tag is mandatory infrastructure for any lead form; add Enhanced Conversions for Leads specifically because your sales cycle closes after the standard click-through window would otherwise expire.

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

Google Tag

A single site-wide snippet, gtag.js, that collects measurement data and routes it to Google Ads and Analytics destinations.

One tag on every page handles page views, conversions, and the linker that preserves the gclid in a first-party cookie, then distributes data to whichever destination IDs you configure. It is the simplest correct install for a site without a tag manager. The usual failure is leaving legacy conversion snippets in place next to it, which produces duplicate conversions, or omitting the tag from the actual confirmation page.

Full definition

Side by side.

The differences that actually change what happens in your account.

	Enhanced Conversions for Leads	Google Tag
What it captures	A hashed customer identifier at the moment of form submission.	The base form submission event and the gclid from the originating click.
When it fires	Twice - once at submission, again as a later upload when the outcome is known.	Once, at the moment the form is submitted.
What ties the later outcome to the click	The hashed identifier captured at submission, not a click ID.	Not applicable on its own - the tag's job ends at submission.
Required for basic lead tracking	No - basic lead counting works without it.	Yes - without it, no lead conversion records exist at all.
Depends on	A CRM or sales process that eventually reports an outcome to upload.	Nothing beyond the form page itself.
Common breakage	Inconsistent hashing normalization between the submission hash and the later upload hash.	The tag missing from the actual confirmation page, or a legacy snippet left in place.

What actually separates them.

The Google tag fires once, at form submission, and its job ends there; Enhanced Conversions for Leads has a second act - an upload of the outcome that happens days or weeks later using the identifier hashed at that first moment.

Standard offline conversion reconnection needs the gclid to tie a later outcome to a click; Enhanced Conversions for Leads instead reconnects using the hashed customer identifier, which survives even after the click ID window has closed.

The Google tag requires no CRM integration to function; Enhanced Conversions for Leads is useless without a CRM or sales process that eventually reports back an outcome to upload.

A broken Google tag means no lead conversion records at all; a broken Enhanced Conversions for Leads setup still lets basic lead counting work, you just lose the ability to optimize on which leads actually closed.

The Google tag needs no normalization logic; Enhanced Conversions for Leads breaks quietly if the hashing normalization - lowercase, trim, strip - differs between the form-submit hash and the later upload hash, since a mismatch never links up.

Which one should you use?

Use Enhanced Conversions for Leads when

Your sales cycle runs weeks or months past the standard click-through conversion window.
You want Smart Bidding to optimize toward closed deals, not just form fills.
Sales qualifies or disqualifies leads in a CRM, not on the website.
You already capture email or phone at the lead form and can hash it consistently.

Use Google Tag when

You haven't set up basic lead form conversion tracking yet.
You just need to confirm the form submission event fires and the gclid gets captured.
You're troubleshooting why no leads are recording, before adding any enhancement on top.
You need remarketing or page-level tracking beyond the lead conversion itself.

Common questions.

Do I still need a gclid if I'm using Enhanced Conversions for Leads?

No, that's the point of the feature - it reconnects the later outcome using the hashed identifier instead of the click ID, which matters once the standard click-through window has already closed.

Why didn't my uploaded lead outcome match back to the original click?

The most common cause is inconsistent hashing - the identifier hashed at form submission has to normalize, case and whitespace included, exactly the same way as the identifier hashed at upload, or the two records never link.

Can I use this without the Google tag installed?

No, the Google tag has to capture the form submission and hash the identifier at that moment. Without it, there's nothing for the later upload to reconnect to.

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