GTM vs GA4: What's the Difference?

Olamide Sule, founder of Dolphin Analytics: a digital analytics expert based in London who sets up GA4 and Google Tag Manager for agency and in-house clients.

New clients mix these two up more than any other pair of tools, so here’s the short version we give them. Google Tag Manager and GA4 are not rivals, and you don’t pick between them. GTM installs and controls your tracking; GA4 collects and reports it. We set the two up together for agency and in-house clients most weeks, and when the setup is beyond an in-house team, our Google Tag Manager consultant work covers exactly this.

What is the difference between GTM and GA4?

Google Tag Manager (GTM) and Google Analytics 4 (GA4) do two different jobs, which is why running one never replaces the other. GTM is a tag management system: it deploys and controls the tracking code on your site, including the code for GA4 itself. GA4 is the analytics platform: it receives that data and reports on users, sessions, events and conversions. Picture GTM as the control panel that decides which tracking fires and when, and GA4 as the database and reporting tool the data lands in.

Both are free Google products, both deal with “tags”, and both sit in the same tracking stack, which is why they blur together. The distinction that matters: GTM moves data, GA4 stores and shows it. You can even point GTM at tools that have nothing to do with GA4, like Google Ads or the Meta Pixel.

GTM vs GA4 at a glance

Here’s how the two line up on the things people actually get confused about.

	Google Tag Manager (GTM)	Google Analytics 4 (GA4)
What it is	A tag management system	An analytics platform
Its job	Deploys and controls tracking tags	Collects, stores and reports data
What it handles	GA4, Google Ads, Meta Pixel, LinkedIn Insight Tag, consent	Users, sessions, events, conversions, audiences
Does it report?	No, it has no reports of its own	Yes, that is the whole point of it
How you change it	Edit tags and triggers in the container, then publish	Configure events, conversions and reports in the property
Runs without the other?	Yes, but with nothing to send it is pointless	Yes, through the hard-coded Google tag
Its identifier	Container ID starts with GTM-	Measurement ID starts with G-

What is Google Tag Manager (GTM)?

Google Tag Manager is a free tool that lets you add, edit and manage tracking tags without touching the site’s source code every time. A tag is a snippet of tracking code: GA4, a Google Ads conversion tag, the Meta Pixel, a LinkedIn Insight Tag. Rather than hard-code each one, you install GTM once, then add and change tags inside the container and publish. GTM decides which tags fire, and on what trigger (a page view, a button click, a form submit), but it keeps none of the data itself. For the full install, see our Google Tag Manager setup guide.

What is Google Analytics 4 (GA4)?

Google Analytics 4 is Google’s analytics platform, the tool that receives tracking data and turns it into reports. GA4 counts users and sessions, records events (a page view, a purchase, a sign-up), marks the important ones as key events and conversions, and builds the audiences and reports you actually read. It is the destination, not the delivery method. GA4 needs the data sent to it, which is where GTM usually comes in. If you’re new to how GA4 structures what it collects, our guide to GA4 sessions and events breaks it down.

How does GTM send data to GA4?

GTM sends data to GA4 through a single Google tag that carries your GA4 Measurement ID. You build the tag once inside the container, and every page load fires it. In GTM, open Tags > New > Tag Configuration > Google Tag, paste your GA4 Measurement ID (the code that starts with G-), set the trigger to Initialization - All Pages, then Preview and Publish. Confirm the hit lands in GA4’s DebugView before you trust it. After that, GTM is the pipe and GA4 is the meter reading what flows through it.

Do you need both GTM and GA4?

Most sites need both, but not all of them. If GA4 is the only tag you will ever run, you can install GA4 on its own with the hard-coded Google tag (gtag.js) and skip GTM entirely. The moment you add a second tag, a Google Ads conversion, the Meta Pixel, consent mode, GTM earns its keep: it holds every tag in one managed container instead of scattered through the code. Running GTM with no GA4 is possible too, say a site that only fires ad-platform tags, but it’s uncommon. The usual, recommended setup is GTM managing GA4 plus whatever else you track.

The mistake that quietly breaks both

Duplicate events are the most common fault we find on a first audit, and installing GA4 twice is a frequent cause: once hard-coded in the site, and again as a tag in GTM. Both fire, so GA4 counts many pageviews and events twice, and every report built on them reads high. It looks like growth; it’s a duplicate. On one engagement, working through the agency Connective3, we found duplicate purchase events inflating bookings across 16 hotels, then gave the group its first accurate property-level view of direct bookings. You can check which tags and pixels are already firing on your own site with our free Sonar scanner: one click, no account. If the numbers already look off, tell us what’s broken, or book a call.

Which should you set up first, GTM or GA4?

Set up GTM first, then GA4 inside it. Create your GTM container and install its snippet on every page. Create the GA4 property next, so you have its Measurement ID. Then add the Google tag in GTM, point it at that Measurement ID, and publish. Doing it in that order means GA4 goes live through the container from day one, so you never have to unpick a hard-coded tag later. Our setup guide walks the full sequence, trigger by trigger.