They are two different tools that work as a pair. GA4 is the analytics platform that collects and reports on what people do on your site. GTM is the tag management system that places the tracking code, including the Google tag that sends data to GA4.
In this guide you will get a plain-English role split, a disambiguation table for GA4, GTM, the Google tag and gtag.js, the minimal setup order for a typical US site, and the exact situations where you can skip GTM entirely.
The path in 7 steps
The steps of this page, in order.
-
01 One-line answer Two tools, two jobs: one measures, one delivers tags.
-
02 Who does what GA4 collects and reports; GTM deploys and manages the tags that feed it.
-
03 Clear up the names GA4, GTM, the Google tag and gtag.js are four different things.
-
04 Build the minimum Create the GA4 property, create the GTM container, fire the Google tag through GTM.
-
05 Or skip GTM Small sites on a CMS integration can often run GA4 without GTM at all.
-
06 Fix common errors Double tracking and missing tags are the two mistakes beginners hit first.
-
07 Decide and act Pick your path, follow the order, and avoid breaking existing tracking.
01 / 10
Are Google Tag Manager and Google Analytics the same thing?
No, GA4 measures behavior, GTM delivers the code that does the measuring, and they are separate products.
GA4 (Google Analytics 4) is the platform that stores your traffic and event data and turns it into reports: users, sessions, events, conversions. GTM (Google Tag Manager) is a free tool that adds and updates tracking tags on your site, so a tag, a small piece of code that sends information somewhere, for example to Google Analytics or Google Ads, can change without editing the site by hand.
Google designs them to work together, and you can run either one alone. One delivers code, the other keeps the data.
Google Analytics 4 (GA4)
The reporting platform. Your traffic and event data lands here and becomes reports on users, sessions, events and conversions. Built for anyone who needs to read what visitors actually do.
- Role
- Measures and reports behavior
- Output
- Reports: users, sessions, events, conversions
Key pointLog in to GA4 to read results, not to change tracking.
Google Tag Manager (GTM)
The delivery layer. It adds and updates tags on your site through a container, without a developer touching the site code each time. Built for whoever manages tracking changes.
- Role
- Delivers and updates tags
- Output
- Tags fired on your pages
Key pointOpen GTM to add or fix a tag, not to read traffic.
02 / 10
Who does what: GA4 or Google Tag Manager?
GA4 owns the data and the reports; GTM owns the deployment and the timing of every tag.
GA4 is where the data lands and where you read it: it collects events, stores them in your property, and turns them into reports like dashboards and explorations. GTM never stores your analytics data. It holds a container, the bundle that carries all your tags, triggers and variables for one site, and its output is a published container version that your pages load.
A trigger is the condition that decides when a tag fires, such as a page view or a button click. Each tag then sends data to a destination, a product like GA4, Google Ads or Floodlight. Your GA4 property and your GTM container are both yours, but they sit in separate accounts and you edit them in separate screens.
03 / 10
What is the Google tag, and how is it different?
The Google tag (it starts with GT-) is one measurement tag you install once, then point at destinations like GA4 and Google Ads.
The Google tag and gtag.js, Google's JavaScript library, work together: gtag.js is the code file, while the Google tag is the single measurement tag (its ID starts with GT-) you paste into that file or load through a tool. You install it once and point it at destinations such as GA4 and Google Ads, as Google's documentation for the Google tag describes.
It replaced the GA4 Configuration tag: Google's developer documentation states existing configuration tags were upgraded to the Google tag automatically, with no action needed on your side. gtag.js sends data only to Google services; third-party and custom tags go through GTM.
GA4, GTM, the Google tag, and gtag.js side by side
| Name | What it is | What identifies it | What it does |
|---|---|---|---|
| GA4 | A measurement product (analytics) by Google | Measurement ID: G-XXXXXXX | Collects and reports user behavior in Google Analytics |
| GTM | A tag management system (container) | Container ID: GTM-XXXXXXX | Loads and manages many tags, including Google and non-Google tags |
| Google tag | A single Google measurement tag | Tag ID: GT-XXXXXXX | Sends data to Google destinations such as GA4 and Google Ads |
| gtag.js | A JavaScript library | A script URL in your site code | Lets you add Google tags directly without a tag manager |
Scope check: GA4 measures, GTM manages tags, the Google tag identifies a Google measurement tag, and gtag.js is the code that loads it.
04 / 10
What is the smallest setup that actually works?
Create the GA4 property, create the GTM container, then fire the Google tag through GTM, in that order.
Start with GA4: create the property and copy its measurement ID. Nothing can receive data until that ID exists, so doing it first avoids wiring a tag to a destination that doesn't exist yet.
Then create the GTM container, the GTM bundle that holds all your tags, triggers and variables for one website, and install its snippet on every page. Only after that add the Google tag inside GTM, point it at your GA4 measurement ID, test in preview mode, then publish.
-
Create the GA4 property
In the GA4 admin, set up the property and its data stream, then copy the measurement ID (the G-XXXXXXX string). This is the address your data will be sent to.
-
Create the GTM container
One container per website. Copy the container snippet and place it on every page, ideally in the head section, so it loads site-wide.
-
Add the Google tag inside GTM
Create a Google tag in the container, enter the GA4 measurement ID as its destination, and set it to fire on all pages. Use Preview mode to confirm it fires once before publishing.
-
Publish and verify
Publish the container, then check Realtime in GA4 to confirm your own visit shows up. If a CMS plugin also injects the Google tag, remove it, that is the classic double-tracking cause.
05 / 10
Do you even need Google Tag Manager?
Small sites already using a CMS integration can often run GA4 without GTM at all.
Run GA4 alone when your CMS integration already loads the Google tag and you only track page views and a few basic events. GA4 and GTM are separate products (Google's documentation), so skipping GTM costs you nothing.
CMS integration only
- Setup takes minutes in WordPress, Shopify or Wix
- No code to maintain
- Covers page views and basic events
- Limited to what the connector exposes
- Hard to add ad pixels or consent tools
Small sites with no developer and simple tracking needs.
Gtag.js in the site code
- Full control from your own code
- No extra tool to learn
- Sends data only to Google services
- Every new tag means editing and redeploying code
- Third-party tags need manual work
Sites with a developer who changes tracking rarely.
Google Tag Manager
- Add buttons, forms, scrolls and third-party tags without shipping code
- One container for every tag
- Free tier exists
- Extra tool to configure and audit
- Mistakes can fire tags site-wide
Anyone tracking events or third-party tools regularly.
06 / 10
Is GTM still free, and is it still relevant?
Yes, GTM has a free tier and is still the standard way to deploy Google tags; free versus enterprise is a separate question.
As of November 2026, GTM is free, and Google's Tag Manager setup guide still recommends it as the starting point for deploying the Google tag and Analytics. A tag is a small piece of code on your page that sends information somewhere, like GA4 or Google Ads. GTM also manages many third-party and custom tags, which a plain gtag.js install cannot do.
GTM itself is free. Google also sells Tag Manager 360 inside its enterprise Marketing Platform, but most sites never need it, so choose GTM for what it does, not for its price.
You need more than one destination
If tags must reach GA4 plus Ads, Floodlight or a third party, GTM gives one place to manage them.
You want to change tags without a developer
Publishing a new container version is faster and safer than editing site code for every tracking change.
You rely on Google's current guidance
Google still recommends Tag Manager to start, and supports the Google tag for Analytics inside it.
07 / 10
What goes wrong when you set up both?
Most often, the same GA4 tag fires twice, once from your CMS integration and once from GTM.
Symptom: a day or two after you publish, GA4 shows roughly double the page views or conversions you expect. The cause is almost always a duplicate Google tag: your CMS already injects it, and a GTM tag fires a second copy.
Fix: decide one delivery path per tag, CMS or GTM, never both. In GTM, use Preview mode to check which tags fire on a page view before you publish live. A trigger is the condition that fires a tag; a destination is where it sends data, such as GA4 or Google Ads.
Count the Google tag
Use GTM Preview and your page source to confirm only one Google tag loads per page.
Map each trigger to one destination
For every GTM tag, note its trigger and destination. Two tags sending the same hit to GA4 is the bug.
Test in Preview before publishing
Click through key pages and events in Preview. Check GA4 DebugView for single hits, not pairs.
Compare before and after
Write down yesterday's GA4 page views, publish, then compare today's numbers. Doubling means a duplicate.
08 / 10
What should I do next?
Pick your path, GTM or no GTM, then follow the order below so nothing fires twice.
Your path depends on what you track today. If you already get basic pageviews through a CMS integration and need nothing else, change nothing, revisit when you add events. If you need event or third-party tracking, build in this order: GA4 property, then container, then the Google tag inside GTM.
Cross-check every step against Google's developer documentation for the Google tag and Tag Manager support before you publish. These pages are the source of truth, not blog tutorials.
09 / 10
Frequently asked questions
10 / 10
Sources, data and disclaimer
Sources
- Google for Developers: Google tag and GA4 tag options
- Google for Developers: Set up and install Tag Manager
- Google for Developers: The Google tag (gtag.js)
Disclaimer
Checked in November 2026. Google renames and merges tags from time to time, so confirm details in the official documentation before you change a live setup.









