Google Tag Manager guide: what it is, what it isn't, what it needs

Google Tag Manager is a free tool that lets you manage the tracking code on your website in one place, without touching the source code every time. It doesn’t measure anything itself, and it doesn’t collect consent. Those two mix-ups cost the most money in practice, so this guide starts with what GTM is, then what it isn’t, and ends with a map of every GTM guide on this site.

I worked for Google through a service provider on measurement implementations, including GA4, GTM, Consent Mode and cookie banners. This article is the overview that helps you place the individual guides before you dig into one of them.

1. What Google Tag Manager is: containers, tags, triggers, variables

Google describes Tag Manager as a tag management system (TMS) that lets you update tracking codes and related code fragments on your website without changing the site’s code every time. The product page also says plainly that it’s free. Technically it works like this: you add a short code snippet to every page once, the container code. After that, everything happens in the GTM interface.

Four terms carry the whole system:

• Container: in Google’s words, a collection of tags, triggers, variables and related configurations installed on a website or app. You usually have exactly one per website.
• Tags: the actual snippets that send data. A GA4 event, a Google Ads conversion, the Meta Pixel or the LinkedIn Insight Tag.
• Triggers: the rule for when a tag fires. A page view, a click, a submitted form or an event your website reports.
• Variables: values that tags and triggers carry or check. The conversion ID, the page URL, the order value.

An example makes it concrete. A tag called “Google Ads conversion: enquiry” fires on the trigger “form submitted successfully” and passes the enquiry’s value through a variable. If you leave the conversion value field empty, Google’s help says Tag Manager sends a value of 0. Google Ads then knows an enquiry came in, but not what it’s worth to you.

The data layer: how your website talks to GTM

Many triggers need information only the website has: that an order really went through, what was in the cart, which form was sent. That’s what the data layer is for. Google describes it as an object used by Tag Manager and gtag.js to pass information to tags. The website writes an event into it with dataLayer.push({'event': 'event_name'}), and GTM can fire a trigger on it. A plugin such as GTM4WP or a properly built thank-you page delivers these events. Without them, all you can do is guess from clicks.

Working without risk: preview, publish, versions

The real advantage over code in the theme is the workflow:

1. You change tags in a workspace. Nothing is live yet.
2. Preview opens Tag Assistant. Your site behaves as if the draft were already published, and you see which tags fired, in which order.
3. Submit, then Publish and Create Version, takes it live. Every publish records a version, a snapshot of the container.
4. If something breaks, go to Versions, open the Actions menu next to an earlier version and choose Set as Latest Version, then publish again, or use Publish To… from the same menu.

GTM or the Google tag?

For Google-only measurement there’s also the Google tag (gtag.js), which sits directly in the source code. Google itself says gtag.js can only send data for Google products, while Tag Manager can also send data for third-party and custom tags. My rule of thumb: as soon as a second vendor joins GA4 and Google Ads, say Meta or LinkedIn, GTM is the tidier option. The full decision guide is in GTM vs GA4. Since the October 2026 update the container itself can take over the role of the Google tag. What that changes, and what to check before you switch, is in GTM destination tags.

There’s also a second kind of container: the server-side container. It doesn’t run in the browser but on a server you control, for example in your own Google Cloud project. When that pays off is covered in Server-side tracking with GTM.

2. What Google Tag Manager isn’t: not analytics, not a consent tool

People search “Google Tag Manager vs Google Analytics” because the names sound alike and often come up in the same breath. They do different jobs.

Not an analytics tool

GTM is the courier, not the warehouse. According to Google’s data privacy page for Tag Manager, GTM doesn’t collect, retain or share information about your site’s visitors, and that includes the URLs of pages they visit. It only collects certain aggregated data about tag firing, to monitor stability and performance.

So your visitors’ data ends up wherever the tags send it: in GA4, in Google Ads, at Meta. Reports, audiences and conversions live there, never in GTM. If you look for numbers in GTM, all you’ll find is configuration. The reverse holds too: GA4 doesn’t replace GTM. GA4 analyses, GTM decides which signal arrives at all. How to set up GA4 properly for Google Ads is in Set up GA4 for Google Ads.

Not a consent tool

This is the more expensive mistake. In GTM you can set tags to fire only when consent has been granted. Google tags such as the Google tag, Google Analytics, Google Ads and the Conversion Linker have built-in consent checks. For every other tag you add the check yourself: in the tag under Advanced Settings → Consent Settings → Additional Consent Checks → Require additional consent for tag to fire. The Consent Overview shows which tags have which check.

But GTM doesn’t collect the consent itself. For that you need a cookie banner, your own or a consent management platform (CMP). Consent Mode doesn’t come with one either. Google says so directly: consent mode has no consent banner or widget. It only takes the decision from your banner.

In Germany, § 25 TDDDG governs this. A website may only store information on a visitor’s device or read it from there with consent, unless that’s strictly necessary to provide a service the user explicitly asked for. I measured how often that goes wrong: in my study on tracking before consent, 8.8% of 41,161 reachable German business sites were already sending data to a measurement or advertising service before the first click. On 2,619 of those 3,619 sites, the browser had detected a cookie banner nobody had answered yet.

Then there’s the container itself. In its ruling of 19 March 2025 (case 10 A 5385/22), the Administrative Court of Hanover confirmed the view of the Lower Saxony data protection authority that using Google Tag Manager already requires consent. That’s a single first-instance ruling, not settled case law. If you want to play it safe, load the container only after consent and use Consent Mode in basic mode, which according to Google transmits no data to Google before the visitor interacts with the banner. What the law actually requires is in Tracking and cookie consent in Germany. I’m not a lawyer, and this isn’t legal advice.

Not a substitute for clean events

GTM can only measure what the website shows it. A click trigger on the submit button also counts attempts where a required field was missing. A trigger on the thank-you page, or on a data layer event after a successful send, counts the real enquiries. The difference doesn’t show up in any report. It sits in your choice of trigger.

3. What your Google Ads account needs from GTM, and where the guides are

A container for Google Ads doesn’t need creativity. Three things are mandatory; everything else depends on the business model.

1. Conversion Linker. It captures the click information from your ads’ landing page URLs and stores it in its own cookies and local browser storage on your domain. Google recommends the All Pages trigger. If your container already loads a Google tag on every page, Google says a separate Conversion Linker isn’t needed.
2. A conversion tag on the real outcome. The Google Ads conversion tracking tag needs the conversion ID and conversion label from the conversion action in Google Ads. Value, transaction ID and currency code are optional, but without a value the bidding strategy only learns “enquiry, yes or no”. Enhanced conversions add more signal.
3. Consent signals. According to Google, if you want to keep using measurement, ad personalisation and remarketing, you have to obtain consent from users in the EEA and send the consent signals to Google. That’s Consent Mode v2 with the parameters ad_user_data and ad_personalization alongside ad_storage and analytics_storage. The setup is in Consent Mode v2 setup.

What gets added depending on the business (GA4, events for phone and email clicks, call tracking, a server container) is covered block by block in Google Tag Manager for Google Ads.

You don’t have to build the container from scratch. My free GTM configurator has seven ready-made container templates, including Shopify, WordPress with GTM4WP, Calendly and Consent Mode v2 with Finsweet: pick a template, enter your IDs, download the file and import it into GTM. Preview mode still applies afterwards, because an import isn’t proof that anything fires.

The map: every GTM guide on this site

Topic	Guide	What it’s for
Basics	Google Tag Manager for Google Ads	The building blocks of a container for Google Ads
Basics	Google Tag Manager in WordPress	GTM4WP, Site Kit or the theme editor compared
Update	GTM destination tags	What the October 2026 update changes and how to switch safely
Basics	GTM tracking live setup	GTM and GA4 step by step in a live session
Basics	GTM vs GA4	What each one does, and which setup fits you
Basics	Set up GA4 for Google Ads	Property, key events, import without double counting
Google Ads	Enhanced conversions setup	Hashed customer data for more accurate conversions
Server	Server-side tracking with GTM	Server containers, providers and when it pays
Server	Bing server-side tracking	Microsoft Ads through your server container
Template	Lead-gen container	A ready container for enquiries
Template	Shopify conversion tracking	Purchases with order value to Google Ads
Template	WordPress e-commerce with GTM4WP	GA4 e-commerce events from WooCommerce
Template	Funnel step tracking	Funnel steps as GA4 events
Template	Calendly tracking	Bookings as GA4 events
Template	Perspective funnel tracking	Perspective funnels with Google Ads and GA4
Template	Finsweet Consent Mode v2 for Webflow	Cookie banner and Consent Mode on Webflow
Other channels	Meta Pixel setup	Meta Pixel via GTM plus the Conversions API
Other channels	LinkedIn Insight Tag	LinkedIn conversions through GTM
Other channels	Bing conversion tracking	UET tag and conversion goals for Microsoft Ads
Consent	Consent Mode v2 setup	Banner, GTM connection and testing
Consent	Contao Consent Tool	Consent Mode v2 and GTM in Contao
Consent	Tracking and cookie consent in Germany	What § 25 TDDDG and the GDPR require before you measure
Consent	Study: tracking before consent	50,000 business sites checked in a real browser

If you don’t have time to work through the list, you can have conversion tracking set up for you (in German): GA4, GTM and Consent Mode v2 in one versioned container, with scope and price agreed up front. If you only want your existing tracking checked, the conversion tracking audit covers that.

The bottom line

• Google Tag Manager is a free tag management system: a container of tags, triggers and variables, managed through an interface with preview, versions and a way back to an earlier state.
• It doesn’t measure anything itself and, according to Google, stores no information about your visitors. The numbers live in GA4, Google Ads or at Meta.
• It doesn’t collect consent. The banner comes from you or a CMP, and in Germany the safest setup loads the container only after consent.
• Every Google Ads account needs three things from the container: the Conversion Linker (or a Google tag on every page), a conversion tag on the real outcome with a value, and the consent signals from Consent Mode v2.
• Templates save time. They don’t replace a check in preview mode.

Not sure your container measures what Google Ads needs? If there’s a specific decision to make, such as fixing it yourself or having it set up, or loading the container before or after consent, the Clarity Session is the right step: from €390, a 60-minute video call with up to three links or documents reviewed first. You get a clear recommendation and the next steps in the right order. A full check of account and measurement is the Google Ads audit from €1,900. Whether the session is enough for your question is something you can check first in a free intro call. Book a free intro call.

FAQ

Is Google Tag Manager free?

Yes. Google offers Tag Manager for free, and there’s Tag Manager 360 for large companies. For normal websites, costs only appear when you run a server-side container, because that needs a server you pay for yourself, whether on Google Cloud or with a hosting provider.

What’s the difference between Google Tag Manager and Google Analytics?

GTM deploys tags and decides when which signal goes to which service. Google Analytics receives the data and analyses it. According to Google, GTM doesn’t store information about your visitors; you’ll only find reports in GA4.

Do I need Tag Manager if I only use GA4 and Google Ads?

Not necessarily. The Google tag in the source code is enough for Google-only measurement. GTM pays off once you add several conversions, a second vendor such as Meta or LinkedIn, or frequent changes, because then you can work without a developer and test every change before it goes live.

Can Google Tag Manager load before consent?

There’s no settled answer. On 19 March 2025 the Administrative Court of Hanover confirmed the data protection authority’s view that using Google Tag Manager already requires consent, but that’s a single first-instance ruling. The safe route is to load the container only after the visitor agrees in the cookie banner.