A tag is a small piece of code that does one thing. For example, it tells Google Analytics 4 (GA4) that a page was viewed. Or it tells an ad network that someone made a purchase. Without GTM, every such tag would have to be written directly into the website’s code. With GTM, the site’s code contains GTM and a data layer (more on that in a moment), and everything else is set up in GTM’s interface.<\/p>\n\n\n\n
GTM is not new. Google launched it on October 1, 2012<\/a>, and according to W3Techs<\/a> it runs on 45.1% of all websites as of October 9, 2026. That’s a third-party estimate, but the order of magnitude is right: you’ll run into it almost everywhere.<\/p>\n\n\n\n Picture a mail envelope. A developer puts it on the website once, and it’s sent to every visitor along with the page content. What goes into the envelope is then up to the analyst or marketer: GA4 measurement, a social media pixel, ad scripts. Nobody has to reopen the site’s code for that.<\/p>\n\n\n\n Here’s what it looks like without the envelope.<\/p>\n\n\n\n I had a client, an e-shop, where the developers spent a week implementing GA4 including events. The next week it was Meta Pixel (formerly Facebook Pixel). The week after that, another platform. Every tool meant another round of developer work: brief, development, testing, deployment. And until deployment, the measurement simply waited.<\/p>\n\n\n\n With GTM it’s different. Developers deploy GTM once. Most further scripts are then added to the site by whoever owns the measurement, through the GTM interface. A new tool stops being a week-long development project and becomes a change in settings.<\/p>\n\n\n\n Tracking a new button, tweaking an event, or swapping an ad account ID is, in the site’s code, yet another task for busy developers. In GTM it’s usually a simple edit that you can test before it goes live.<\/p>\n\n\n\n This is where beginners get tangled most often, so briefly.<\/p>\n\n\n\n Example: a website has GA4, Google Ads and a social media pixel. GTM is what brings those three things onto the site. GA4 is what actually counts the visitors. Google Tag Manager vs Google Analytics, then, isn’t an either-or choice: they do different jobs and usually work together.<\/p>\n\n\n\n Do you need Google Tag Manager if you only have GA4? Not necessarily. But with every additional tool it becomes more useful.<\/p>\n\n\n\n Developers install GTM on the site. From your GTM account you get two snippets of code<\/a>: one goes as high as possible in the page’s head, the other right after the opening Tags often need data that GTM can’t see on the page by itself. For example, the contents of a cart, an order value or an order ID. This information is passed to GTM by the data layer (dataLayer, as developers call it)<\/strong>: a place where the website stores information and GTM picks it up. Technically it’s a JavaScript array (a list)<\/a> to which the website keeps adding messages with information for tags.<\/p>\n\n\n\n Developers fill it. That matters, because you’ll sometimes hear that with GTM you don’t need a developer. You do. Neither GTM nor the data layer works without them: developers put GTM on the site and populate the data layer.<\/p>\n\n\n\n When do you need a data layer?<\/p>\n\n\n\n The amount of developer work varies a lot. Passing just the order value into the data layer is a small change. Full e-commerce events (product view, cart, payment) take much longer. An experienced analyst can help you decide what level of effort fits your project and your situation, so nobody builds something that never gets used. For advanced readers, I cover working with the data layer in a separate article<\/a>.<\/p>\n\n\n\n It can:<\/strong><\/p>\n\n\n\n It can’t:<\/strong><\/p>\n\n\n\n Five concepts that everything else is built on:<\/p>\n\n\n\n Put together: when<\/em> (trigger) this<\/em> happens, do<\/em> (tag) that<\/em>, with these values<\/em> (variables).<\/p>\n\n\n\n A trigger in GTM behaves like Maxwell’s demon<\/a> at the door between two chambers: for every tag it decides whether it gets through. The only difference is that the demon sorted molecules by speed, whereas a trigger sorts tags by when and where they should fire. A badly configured demon lets in what should have stayed out.<\/p>\n<\/div>\n<\/div>\n\n\n\n GTM has a point-and-click interface where you set up tags, triggers and variables. You mostly don’t need to write code: you pick the tag type from a list and fill in the details in a form.<\/p>\n\n\n\n At the top you switch between three tabs: Workspace<\/strong> (where everything is configured), Versions<\/strong> (the container’s history) and Admin<\/strong> (users, permissions and container settings). In the workspace’s left-hand menu you’ll find:<\/p>\n\n\n\n Setting up one tag then looks like this:<\/p>\n\n\n\n Variables come in two kinds. Built-In Variables<\/strong> (page URL, clicked element and others) you just switch on. User-Defined Variables<\/strong> you create yourself, for example for the order value from the data layer.<\/p>\n\n\n\n No change in GTM goes live right away. It goes through four steps. The fifth point isn’t a step but an emergency brake, in case something goes wrong.<\/p>\n\n\n\n A practical tip: always go through preview before you publish. A mistake in a workspace takes minutes to fix. A mistake that has been sending bad data to GA4 for weeks can’t be repaired retroactively: GA4 doesn’t reprocess data it has already processed, and what wasn’t sent can’t be filled in.<\/p>\n\n\n\n The envelope has a flip side. Whatever goes into it reaches every visitor of the site, and that holds for any script. Whoever has Publish<\/strong> permission can put anything in.<\/p>\n\n\n\n There are four container access levels<\/a> (besides No access):<\/p>\n\n\n\n Give Publish only to people who truly need it. Being an agency contractor, a temp or a former colleague is no reason to hand it over. Access should go to whoever really needs it, and only for as long as they need it. Attacks, real-world examples and concrete recommendations are in my article on Google Tag Manager security risks<\/a>.<\/p>\n\n\n\n Watch the account-level role too. An account Administrator manages users and their permissions, so they can grant themselves Publish. The Administrator role is therefore just as sensitive as Publish.<\/p>\n\n\n\n Yes. Both GTM and the Google tag are free<\/a>. The paid variant, GTM 360, is aimed at large companies.<\/p>\n\n\n\n Not necessarily. GA4 works fine with the Google tag placed directly on the site. GTM pays off once you want more tools or more events and don’t want to hand every change to developers.<\/p>\n\n\n\n The container loads asynchronously, so the mere fact that a site uses it doesn’t block the page. But a larger container, meaning more tags, is linked to worse responsiveness (INP, which is how quickly a page reacts to a click), and different kinds of tags weigh on a site differently. That’s why it pays to remove tags you don’t need. More in the article on the impact of GTM on page speed<\/a>.<\/p>\n\n\n\n There’s also server-side GTM, which moves part of the work out of the visitor’s browser, as I describe in the article on server-side tracking and sGTM<\/a>. It is, however, a separate project with its own server.<\/p>\n\n\n\n The tool alone doesn’t guarantee compliance. Compliance comes from a properly configured cookie banner (CMP) and tags that respect consent. GTM helps you set all of that up.<\/p>\n\n\n\n Under a strict reading of GDPR (in Germany, for example), though, using GTM itself can be a problem, because visitors’ IP addresses and other network identifiers are transferred to Google’s servers. More on the conflict between GTM and GDPR<\/a>.<\/p>\n\n\n\n The paid variant for large organizations. It adds unlimited workspaces, an approval workflow and contractual support. Pricing is on request, and you can find a comparison on Google’s page<\/a>.<\/p>\n\n\n\n The basic way to get started with Google Tag Manager has four steps:<\/p>\n\n\n\n Until you publish something, nothing changes on the live site.<\/p>\n\n\n\n Getting started with GTM and want to know what’s next? Once in a while I send a short email with what I’ve learned working with GTM and GA4. <\/p>\n\n\n\nWhy do we need GTM when code can go straight into the HTML<\/h2>\n\n\n\n
GTM, GA4 and Google tag: who does what<\/h3>\n\n\n\n
\n
How GTM gets onto the website and what the data layer is<\/h2>\n\n\n\n
<body><\/code> element. The second one is a fallback for browsers without JavaScript, and you don’t strictly have to deploy it. It does come in handy if you want to verify the site in Google Search Console via GTM<\/a>: Search Console looks for it right after <body><\/code>, so verification passes without any further change to the code (it works for URL-prefix properties, not domain properties). Usually the whole thing means a single edit in the site’s template. After that, GTM just waits for whatever you put into it.<\/p>\n\n\n\nThe data layer: a channel between the website and GTM<\/h3>\n\n\n\n
\n
What GTM can do (and what it can’t)<\/h2>\n\n\n\n
\n
\n
Core concepts<\/h2>\n\n\n\n
\n
![\"V\u011bd\u011bli](\"https:\/\/www.sabatka.net\/wp-content\/uploads\/2026\/04\/null-did-you-know.png\")
<\/figure>\n<\/div>\n\n\n\nLab note<\/strong><\/strong><\/h3>\n\n\n\n
How you work in GTM<\/h3>\n\n\n\n
![\"\"](\"https:\/\/www.sabatka.net\/wp-content\/uploads\/2026\/10\/google-tag-manager-interface-1024x506.png\")
<\/figure>\n\n\n\n\n
\n
How a change gets onto the website<\/h3>\n\n\n\n
\n
Who should get Publish permission<\/h2>\n\n\n\n
\n
Frequently asked questions<\/h2>\n\n\n\n
Is Google Tag Manager free?<\/h3>\n\n\n\n
Do I need Google Tag Manager if I have GA4?<\/h3>\n\n\n\n
Does GTM slow down my website?<\/h3>\n\n\n\n
Is GTM GDPR compliant?<\/h3>\n\n\n\n
What is GTM 360?<\/h3>\n\n\n\n
How to get started with GTM<\/h2>\n\n\n\n
\n