Conversion Tracking & Data

Enhanced Conversions vs Google Tag

In short: Both sit in the path that reports a web conversion to Google Ads, but one is required infrastructure and the other is an optional add-on. Google Tag is the delivery mechanism - it's what fires the conversion event at all. Enhanced Conversions is layered onto that same event: hashed first-party details like email or phone, sent alongside the standard conversion so Google can match it to a signed-in user the cookie alone would have missed. You need the Google tag installed regardless, it isn't a choice; Enhanced Conversions is the choice you make on top of it once your confirmation step already captures customer details worth hashing.

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 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	Google Tag
What it is	An optional enhancement to an existing conversion event.	The base delivery mechanism that reports the conversion at all.
Required for tracking to work at all	No - conversions still count without it, just with lower match quality.	Yes - without it there's no conversion event to report in the first place.
What data it adds	Hashed customer fields - email, phone, or address.	The base conversion signal - that an action happened, and when.
Where you turn it on	A setting on the conversion action, backed by a data feed you wire up.	Installed once, site-wide, as the measurement snippet.
What happens if misconfigured	The toggle does nothing if no hashed fields actually reach it - conversions keep counting normally.	Conversion tracking stops entirely, or duplicates if an old snippet is left in place.
Dependency	Cannot function without the Google tag or equivalent already running.	Functions independently; Enhanced Conversions is optional on top of it.

What actually separates them.

The Google tag alone reports that a conversion happened; Enhanced Conversions adds who it happened to, using hashed fields the base tag wouldn't otherwise send.

Enhanced Conversions cannot function without the Google tag, or an equivalent conversion tracking setup, already running - it's an add-on, not a standalone tracking method.

Turning off the Google tag stops conversion tracking entirely; turning off Enhanced Conversions only reduces match quality, since conversions still count from cookie-based matching.

The Google tag needs no customer-supplied data to function; Enhanced Conversions is inert without user-provided fields actually reaching it, the toggle alone does nothing.

Enhanced Conversions is a setting plus a data feed you have to wire up correctly; the Google tag is the base install everyone needs regardless of whether Enhanced Conversions is ever turned on.

Which one should you use?

Use Enhanced Conversions when

Your confirmation page or backend already captures email or phone at the moment of conversion.
You've noticed conversion counts drifting down and suspect cookie-based matching is missing signed-in users.
You want first-party data working harder without standing up a whole new tracking system.
You're comfortable hashing fields correctly - lowercase, trimmed - before they reach the tag.

Use Google Tag when

You have no conversion tracking installed yet - this is the prerequisite step before anything else.
You're debugging why no conversions are recording at all, before considering any enhancement.
You need page views and remarketing lists working, not just conversion counting.
You're setting up a new site and need the base measurement layer before layering anything on top.

Common questions.

Do I need Enhanced Conversions if I already have the Google tag installed?

Not strictly - conversions will still count from cookie-based matching. But Enhanced Conversions typically recovers additional conversions the cookie missed, so it's worth adding once you have customer data available at the point of conversion.

I turned on Enhanced Conversions but nothing changed. Why?

The setting does nothing on its own. Check that hashed customer fields are actually being passed to the tag at the moment of conversion - a toggle with no data feed behind it has no effect.

Can Enhanced Conversions work without the Google tag?

No, it rides on top of your existing conversion tracking setup, whether that's the Google tag installed directly or deployed through GTM. There's no path to send it independently of a base conversion event.

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