Google Tag Manager - what marketers actually need to know
Google Tag Manager sits between your website and your analytics and advertising platforms. Understanding what it does - at a conceptual level, not a coding level - changes how effectively you can manage tracking, diagnose data problems, and implement new measurement capabilities.
Most marketers interact with GTM either not at all - leaving everything to a developer - or only to copy-paste tag snippets without understanding what they are doing. Neither extreme is ideal. A working conceptual understanding of GTM lets you diagnose tracking problems, brief developers accurately, and understand why your conversion data looks the way it does.
What GTM actually is
GTM is a tag management system. Instead of editing your website's code every time you want to add or change a tracking tag, you install GTM's container code once and then manage all your tracking through GTM's interface. When you want to add a Google Ads conversion tag, a GA4 event, or a Meta Pixel, you add them to GTM rather than asking a developer to add them to the site code. This gives marketers more control over tracking implementation without requiring code access.
The three concepts that matter: tags, triggers, variables
Tags are the tracking code snippets you want to fire - a Google Ads conversion tag, a GA4 event, a LinkedIn Insight Tag. Triggers define when a tag fires - when someone loads a specific page, clicks a button, submits a form, or scrolls to a certain depth. Variables are values that tags use or that define trigger conditions - the URL of the current page, the value of a form field, the text of a clicked element.
When you understand this three-part structure, most tracking implementations make intuitive sense. "Fire the Google Ads purchase conversion tag on the order confirmation page" translates directly to: Tag = Google Ads conversion, Trigger = Page View on URL containing /order-confirmation, Variable = the revenue value from the page.
The most common GTM problems
Tags firing on the wrong pages - often because a trigger condition is too broad and the tag fires on every page view rather than just the intended one. Double-counting conversions - because both a GTM tag and a hardcoded tag are firing on the same page, or because the conversion tag fires multiple times on the same session. Tags not firing at all - because a trigger condition references a variable that does not exist on the page or a class name that changed when the website was updated.
Google Tag Assistant - a Chrome extension - shows you exactly which tags are firing on any page and whether they are firing correctly. Running Tag Assistant on your key conversion pages takes five minutes and answers most common tracking questions without needing developer involvement.
What you should know how to do
You do not need to build GTM implementations from scratch. You do need to be able to check whether existing tags are firing correctly using Tag Assistant, understand what a trigger condition means when a developer explains it, and identify when a tracking problem is a GTM configuration issue versus a website code issue. That level of knowledge makes you a significantly better partner for the developers and analytics specialists you work with.
Found this useful?
Start a conversation - no pitch, no pressure.