GA4 vs Google Tag Manager: What Each Does and When You Need Both

“Do we have GA4 or Tag Manager?” comes up often in marketing reviews, and the honest answer is frequently “both, and nobody is sure who set them up”. The two tools come from the same company, share logins and appear in the same setup guides, so they get treated as alternatives. They are not. One is where your measurement data lives and gets reported. The other is a way of putting tracking code on your website without editing the website itself.

This guide explains what each one does, where the Google tag (gtag.js) fits between them, when a site can run without Tag Manager, when Tag Manager pays for the effort, and who in your company should be allowed to change it.

The short answer: one measures, the other delivers

Google Analytics 4 (GA4) is a measurement and reporting product. Google organises it in three levels: an account, which is “a collection of properties whose data is owned by a single legal entity”; a property, which “represents data for one user base”; and a data stream, which is “the source of data from an app or website” (Google Analytics Help: account structure). The property is where you read traffic, landing pages, events and key events, and where you decide which actions count as leads.

Google Tag Manager (GTM) is, in Google’s words, “a tag management system that allows you to set up and manage tags on your site without changing your website’s code” (Tag Manager Help: Introduction to Tag Manager). You install a container once, and from then on you manage three things in a web interface:

• Tags: pieces of code that send data to a service such as GA4, Google Ads or another advertising platform.
• Triggers: rules for when a tag fires, for example on every page, or when someone taps a WhatsApp button.
• Variables: reusable values, such as a page URL or a click text, that tags and triggers refer to.

A useful way to explain it to a board: GA4 is the accounting system, Tag Manager is the team that collects the receipts and files them in the right place. You read traffic and lead reports in GA4, not in Tag Manager. GA4 does not decide by itself what a quotation request is on your site, unless something tells it.

Where the Google tag (gtag.js) fits

The confusion usually starts here. To send any data to GA4, a site needs the Google tag, which Google describes as “a single tag you can add to your website that allows you to use a variety of Google products and services”. It replaced the older name: “The global site tag (gtag.js) is now the Google tag” (Analytics Help: About the Google tag).

So there are two ways to put that Google tag on a site:

1. Directly, by pasting the Google tag snippet into the site, or by entering the tag ID in a website builder or CMS integration. Google lists this option alongside platform integrations for builders such as Shopify, Wix and Squarespace and WordPress plugins (Analytics Help: Set up Analytics for a website).
2. Through Tag Manager, by creating a Google Analytics or Google tag inside the GTM container and publishing it (Tag Manager Help: Set up Google Analytics in Tag Manager).

Google’s own comparison sets out the difference. The Google tag “can only send data to Google services”, and changing what it tracks means writing code. Tag Manager “can send data for Google tags, third party tags, and custom tags”, is managed from one web interface and lets teams “collaborate with others using workspaces, and version control tags”; both are free (Tag Manager Help: Google Tag Manager vs. gtag.js). Google’s developer guide puts the practical test simply: gtag.js needs one snippet per page and someone comfortable changing JavaScript, while Tag Manager needs two snippets and is then managed from its own website (Google for Developers: Introduction to tagging).

When a site can skip Tag Manager

Tag Manager is not mandatory, and adding it to a site that does not need it creates one more system to own. Google presents the Google tag on its own as a good fit for marketers without a web development team on hand, or for sites on a CMS, when the default metrics such as page views, clicks and scrolls are enough (Google Tag Manager vs. gtag.js).

That default is more than many owners expect. With enhanced measurement switched on in the GA4 data stream, GA4 can collect page views, scrolls, outbound clicks, site search, embedded YouTube video engagement, file downloads and form interactions without extra code (Analytics Help: Enhanced measurement events). Note that the automatic form events record that a form was started or submitted; they are not a reliable definition of a qualified lead on their own.

A site can reasonably run on the Google tag alone when most of these are true:

• It is a small corporate or brochure site with a handful of pages.
• GA4 is the only measurement tool, or GA4 plus a Google Ads account using the same Google tag.
• Leads come through one form with a thank-you page, so a page view of that page can be marked as a key event.
• Nobody plans to add other advertising pixels or chat and heatmap tools.
• The website is rarely changed, and when it is, the same developer handles it.

For example, a consultancy with a five-page site, one contact form and no paid advertising gains little from a GTM container that nobody will open.

When Tag Manager pays off

The case for Tag Manager grows with the number of platforms, the number of events and the number of people who need to change things. It usually earns its place when:

• You advertise on several platforms. Google Ads, Meta, LinkedIn, TikTok or Snapchat each need their own tag or pixel. The Google tag only talks to Google services; Tag Manager handles third-party and custom tags as well.
• You track many specific actions. Separate events for quotation forms, phone taps, WhatsApp taps, catalogue downloads and brochure requests are easier to build and maintain as triggers than as code scattered across templates. Our guide to tracking forms, calls and WhatsApp clicks as GA4 key events covers which of these to mark as leads.
• Marketing changes faster than development. A new landing page, a new campaign tag or a new button should not wait in a developer’s queue. Tag Manager lets a trained marketer make the change and test it before it goes live.
• You need consent to control tags. Tag Manager has a consent initialisation trigger, per-tag consent settings and a Consent Overview page, and supports Google’s consent types such as analytics_storage and ad_storage (Tag Manager Help: consent mode support). Consent choices change what is measured; see cookie consent and Consent Mode for GCC websites. This is not legal advice.
• Several sites or agencies are involved. One container per website, as Google recommends (Tag Manager Help: Create an account and container), gives each site one place where all its tracking is visible.

One caution applies whichever way you go. A phone or WhatsApp tap tracked through GTM is an intent signal: it shows that someone opened the dialler or the chat, not that a conversation happened or a lead was qualified. Treat it as a strong signal and confirm the lead in your CRM or sales log.

A decision table for business owners

The last row matters more than it looks. Google’s comparison page notes that Tag Manager fully supports Google Ads and Google Marketing Platform tags, so “there is no need to deploy additional code using gtag.js on your site if Tag Manager is already in use”. In practice, a GA4 tag that loads both from the theme code and from Tag Manager risks sending the same page views and events twice, so checking where each tag fires is an early step in any tracking review.

Governance: who has publish rights, workspaces and versions

Tag Manager can change what runs on every page of your website, so it deserves the same care as access to the website itself. Google’s permission levels give you the controls (Tag Manager Help: Managing users and permissions):

• Account level: Admin can create containers and manage user permissions; User can view basic account information.
• Container level: Read (view only), Edit (create workspaces and make edits, but not create versions or publish), Approve (create versions, but not publish) and Publish (full rights, including publishing).

Changes are made in a workspace and only take effect when published; each publish creates a version, “a snapshot of a container configuration at a particular time”, and an earlier version can be restored (Tag Manager Help: Publishing, versions, and approvals). Formal approval workflows are a Tag Manager 360 feature, so on the free version the approval step is a matter of process, not software. Before publishing, Preview mode connects your site to Tag Assistant “so that you can inspect which tags fired and in which order” (Tag Manager Help: Preview and debug containers).

GA4 has its own, separate roles: Administrator, Editor, Marketer, Analyst and Viewer, with options to hide cost or revenue metrics from some users (Analytics Help: Access and data-restriction management). How you use these roles is a matter of company policy rather than a Google rule. As a starting point, we suggest:

1. The company owns the GA4 account and the GTM account, under a company email address, with at least two internal administrators.
2. Agencies and freelancers get Edit or Approve in GTM, and Editor or Marketer in GA4, not ownership.
3. Publish rights in GTM sit with one or two named people.
4. Every published version has a clear name and description, for example “Added WhatsApp click event, homepage and contact page”.
5. Every change is previewed before publishing, and checked again in GA4 after publishing.
6. Access is reviewed when a supplier or employee leaves.

This is also how RX works: when we implement analytics and tracking for client websites, the GA4 property, the Tag Manager container and the Google Ads account stay in the client’s name.

Common confusions, answered briefly

• “Tag Manager is the new Google Analytics.” No. Tag Manager is where tags are set up and published; the traffic and lead reports you read come from GA4.
• “If we install GTM, GA4 starts working.” Only if a Google Analytics or Google tag is set up inside the container, with the right tag ID, and the container is published.
• “We have GA4, so our leads are tracked.” Not necessarily. Unless forms, calls or WhatsApp taps are captured as events and the right ones are marked as key events, GA4 mostly shows visits.
• “The Google tag and gtag.js are different things.” They are the same; gtag.js is the older name for what Google now calls the Google tag.
• “Edit access is harmless.” Edit cannot publish, but Publish can change every page. Treat publish rights like website admin rights.
• “Two data layers are fine.” Google notes that Tag Manager and gtag.js rely on a single global window.dataLayer array, and using several can cause tags to miss data (Google for Developers: The data layer).
• “GA4 and Google Ads should show the same numbers.” Not necessarily. The two products can use different counting and attribution settings, and consent choices affect what each records. Look for a stable, explainable relationship between the two rather than identical totals, and check the setup first if the gap suddenly changes. If ad clicks arrive but leads do not, see why ads get clicks but no conversions.

If you are not sure which of these applies to your site, start with an inventory: which GA4 properties exist, which Tag Manager containers exist, who has access to each, and which tags actually fire on your key pages. RX offers that as a tracking audit, followed where needed by a setup and integration project or monthly management; you can see the scope on our analytics and tracking service page.