Conversion Tracking & Data

GA4 Conversion Tracking vs Google Tag: Layer or the Pipe Beneath It

In short: Both are involved in getting conversion data into Google Ads, but one is the pipe and the other is a configuration built on top of it. Google Tag is the pipe - the actual code on the page that collects events and ships them wherever it's configured to go. GA4 conversion tracking is a layer built on top: GA4 receives events through the Google tag, and you decide inside GA4 which ones count as key events and whether to import them into Google Ads as conversion actions. The Google tag has to be running regardless, it's the delivery infrastructure; GA4 conversion tracking is the choice of using GA4's event definitions, rather than a standalone Ads conversion tag, as your source of truth.

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

GA4 Conversion Tracking

Defines key events in Google Analytics 4 and optionally imports them into Google Ads as conversion actions for bidding.

GA4 collects events through the Google tag, you mark the meaningful ones as key events, the term that replaced conversions in GA4 in 2024, and import them into Google Ads. It suits teams that want one measurement layer across paid and organic. The classic error is importing a GA4 key event that duplicates a native Google Ads conversion, then leaving both in the Conversions column and bidding on doubled numbers.

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.

	GA4 Conversion Tracking	Google Tag
What it is	A configuration decision inside GA4 about which collected events matter.	The code that physically collects and sends events in the first place.
Where events actually get collected	Nowhere on its own - it relies entirely on the Google tag's collection.	In the browser, via the Google tag.
Where you mark something as a conversion	Inside the GA4 admin interface, as a key event.	Not applicable - the tag just delivers whatever events you've coded it to send.
Also produces	Funnels, audiences, and organic-channel reporting inside GA4.	Nothing beyond delivery - it has no reporting interface of its own.
What happens without it	No key events are marked, nothing gets imported into Google Ads from GA4.	No data reaches GA4 or Google Ads at all.
Duplication risk	An imported key event overlapping a native Google Ads conversion tag counting the same action.	Legacy conversion snippets left running alongside it.

What actually separates them.

The Google tag is what physically collects and sends events; GA4 conversion tracking is a configuration decision made inside GA4 about which of those already-collected events matter.

Without the Google tag, GA4 receives nothing and there's no event to mark as a key event in the first place; GA4 conversion tracking has no independent data collection of its own.

A native Google Ads conversion action built directly off the Google tag and a GA4 key event import can both end up feeding the same Conversions column - pick one path per action or the same real event gets counted twice.

GA4 conversion tracking also builds funnels, audiences, and organic-channel reporting from the same event; a bare Google tag pointed only at Google Ads produces none of that, it's ads-conversion-only.

Renaming or redefining a key event inside GA4 requires no change to the Google tag or the page; changing what the Google tag itself collects requires a tag or dataLayer change.

Which one should you use?

Use GA4 Conversion Tracking when

You want one shared definition of a conversion used across GA4 reporting, audiences, and Google Ads bidding.
Marketing and analytics both need visibility into the same event data, not two separate tracking setups.
You're already using GA4 for organic traffic and want ads conversions defined the same way.
You want to build remarketing audiences or funnels from the same events that feed bidding.

Use Google Tag when

You haven't installed any measurement layer yet - this comes first, always.
You want the simplest possible path: Google Ads only, no analytics layer involved.
You're troubleshooting why GA4 shows no events at all, before touching key event settings.
Ads conversion tracking is the only need; you have no use for broader analytics reporting.

Common questions.

Do I need both a Google Ads conversion tag and a GA4 imported key event for the same action?

No, pick one path per conversion action or you risk double counting the same real-world event in your Conversions column.

Why is my GA4 key event count zero even though the site gets traffic?

Check that the Google tag is actually installed and firing on the relevant page first. GA4 conversion tracking has nothing to mark as a key event if the underlying tag never sent the data.

Is a key event the same thing as a conversion in GA4?

Yes, GA4 renamed conversions to key events in 2024. It's the same concept - marking specific events as the ones worth counting and optionally importing into Google Ads.

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