Tag Manager

A Rough Guide to Google Tag Manager: Uses, Benefits & SEO

A Rough Guide To: Google Tag Manager

TL;DR:
Google Tag Manager is a free tag management system that lets you deploy and control analytics, advertising and other tracking without repeatedly changing the underlying website code. I use GTM for everything from GA4 and conversion tracking to custom event measurement and some SEO implementations. This guide explains what GTM does, how tags, triggers and variables work, its main uses and advantages, its impact on website performance, and where it can be useful for SEO.

Why I use Google Tag Manager

In the last 18 months, digital marketing discussions focused heavily on the launch of GA4 and the upcoming retirement of Universal Analytics. During this time, Google Tag Manager (GTM) also gained prominence as the recommended method for implementing GA4.

As a Google Tag Manager consultant, I have used GTM for all GA4 setups. GTM’s flexibility allows capturing comprehensive user engagement data on client websites.

Many clients were not familiar with GTM but expressed interest in learning more about it when I mentioned using it for their GA4 setup.

If you’re among those intrigued by the potential of GTM and want a clearer understanding, this guide is as good a starting point as any (in my opinon anyway).

What is Google Tag Manager?

Google Tag Manager (GTM) is a free tag management system from Google that allows you to add, manage and control tracking and other code on a website without having to repeatedly change the website’s underlying code.

Rather than adding Google Analytics, Google Ads, Meta, Hotjar and other tracking scripts directly to the website, you can manage them from a GTM container installed on the site.

GTM can also be used for much more than simply installing tracking codes. I use it to track specific user interactions, capture additional data from websites, control when tags fire and, where necessary, implement certain technical or SEO changes when modifying the website directly isn’t practical.

The basic principle is relatively simple: tags determine what happens, triggers determine when it happens, and variables provide the information needed by the tags and triggers. I’ll explain each of those in more detail below.

Organic Digital GTM Account

What can you use Google Tag Manager for?

Google Tag Manager is probably best known for installing analytics and advertising tags, but its capabilities go considerably further than that.

Some of the things I regularly use GTM for include:

  • Google Analytics 4 tracking – deploying GA4 and sending custom events and parameters.
  • Conversion tracking – measuring form submissions, purchases, phone clicks and other important actions.
  • Advertising tags – implementing Google Ads, Meta and other advertising or remarketing tags.
  • Click tracking – measuring internal links, outbound links, buttons, banners and other clickable elements.
  • Form tracking – recording form submissions and other form interactions.
  • Scroll and visibility tracking – measuring whether users reach particular parts of a page or see specific elements.
  • Capturing website data – using variables and the data layer to pass additional information into analytics and marketing platforms.
  • Controlling when tags fire – limiting tracking to particular pages, URLs, events, users or other conditions.
  • SEO implementations – GTM can also be useful as a fallback for certain technical SEO changes when you can’t modify the website directly.

One of the main reasons I use GTM so extensively is that these different requirements can all be managed through the same container rather than implementing each piece of tracking independently in the website code.

What are the main features of Google Tag Manager?

GTM has several features that make it considerably easier to manage, test and maintain tracking implementations than adding individual scripts directly to a website.

Centralised tag management

Tags for analytics, advertising and other platforms can be managed from a single GTM container rather than being implemented separately throughout the website.

Preview and debugging

GTM’s Preview mode lets you test an implementation before publishing it. You can see which tags fired, which didn’t, what triggered them and the values available to your variables. I use this extensively when building and troubleshooting tracking.

Triggers and variables

Tags don’t simply have to fire on every page. Triggers let you control precisely when something happens, while variables allow you to capture and pass information dynamically. We’ll look at these in more detail below.

Version history

Each published container creates a version, giving you a record of previous implementations and the ability to return to an earlier version if something goes wrong.

User permissions

GTM provides different levels of account and container access, which is useful when several people or agencies are working on the same implementation.

Custom HTML and JavaScript

You’re not limited to Google’s built-in tag templates. GTM can also run Custom HTML and use Custom JavaScript variables, which considerably expands what you can do with it.

What is the difference between Google Tag Manager and Google Analytics?

Google Tag Manager and Google Analytics perform different jobs, although they’re commonly used together.

Google Tag Manager manages and deploys tags. It controls what tracking or other code runs, when it runs and what information is passed to it.

Google Analytics 4 collects and reports data. It receives information about page views, events, users and other interactions and makes that data available for analysis.

For example, I might use GTM to detect when somebody submits a contact form and then send a generate_lead event to GA4. GTM handles the detection and sends the event, while GA4 receives and reports it.

GTM isn’t an alternative to Google Analytics. It’s the mechanism I generally use to implement and control the tracking that sends data to GA4.

How do tags, triggers and variables work in Google Tag Manager?

Tags, triggers and variables are the building blocks of most Google Tag Manager implementations.

The easiest way to think about them is:

  • Tags determine what GTM should do.
  • Triggers determine when it should happen.
  • Variables provide the information needed to make it happen.

For example, you could use a trigger to detect a contact form submission, variables to capture information about that interaction, and a GA4 tag to send the resulting event to Google Analytics.

What Are Tags?

Tags are the tracking or code that GTM executes when the required conditions are met.

They can be used to send information to platforms such as Google Analytics and Google Ads, or to run other code through GTM.

For example, a GA4 event tag might send an event when somebody submits a form, clicks a particular link or completes another interaction you want to measure.

GTM includes templates for commonly used platforms, while Custom HTML tags provide considerably more flexibility when a built-in template isn’t available.


GA4 Tag

GA4 Tag

What Are Triggers?

Triggers determine when a tag should fire.

They can respond to page views and user interactions such as clicks, form submissions, scrolling and element visibility, or use conditions based on URLs, variables and other information available to GTM.

For example, rather than firing a GA4 event tag on every page, you could configure a trigger so it only fires when somebody successfully submits a particular form.

This ability to define exactly when tags should run is one of the reasons GTM can handle considerably more sophisticated tracking than simply adding scripts directly to every page.

Form Submission Trigger

Form Submission Trigger

External Link Click Trigger

External Link Click Trigger

What Are Variables?

Variables store or return values that tags and triggers can use.

GTM includes built-in variables for commonly needed information such as the page URL, hostname, click URL and click text. You can also create your own variables to retrieve information from the data layer, page elements, cookies, JavaScript and other sources.

For example, a variable could return the URL of a link somebody clicked. A trigger could then use that value to decide whether an event should fire, while the same value could be passed to GA4 as an event parameter.

Variables are where GTM starts becoming particularly powerful because they allow your tracking to respond dynamically to what’s happening on the website.

Examples Of Variables Available On A Page

Examples Of Variables Available On A Page

Is Google Tag Manager easy to use?

Google Tag Manager is relatively easy to get started with, but there’s a big difference between installing a simple tag and building a reliable tracking implementation.

Basic tasks such as adding GA4 or firing a tag on a particular page are fairly straightforward. Things become more complicated when you start working with custom events, data layers, form tracking, JavaScript variables, consent requirements and websites where the information you need isn’t readily available to GTM.

The Preview and debugging tools make experimentation considerably easier, but I’d still test the arse off anything before publishing it, particularly when the data is being used for conversion tracking or advertising.

That’s one of the things I like about GTM. You can start with relatively simple implementations, but there’s a lot more you can do with it once you understand how tags, triggers, variables and the data layer work together.

What are the advantages of Google Tag Manager?

The main advantage of Google Tag Manager is the amount of control it gives you over tracking and other tags without requiring a website code change every time something needs to be added or adjusted.

Some of the advantages I find most useful are:

Centralised management

Analytics, advertising and other tags can be managed from one container rather than being scattered throughout the website code.

Faster implementation

Once GTM is installed correctly, many tracking changes can be made without waiting for a developer to deploy new website code.

More flexible tracking

Triggers and variables allow you to measure interactions that aren’t necessarily available through standard analytics tracking, including particular clicks, forms, elements and website states.

Testing before publishing

Preview mode lets you inspect what’s happening before changes go live, while container versions provide a history of published implementations.

Reusable implementations

Once you’ve developed a reliable approach to something such as form tracking or outbound link measurement, the underlying technique can often be adapted for other websites and requirements.

Better separation of tracking from website functionality

Keeping analytics and marketing tags within GTM can make them easier to identify, maintain and troubleshoot than having unrelated tracking scripts implemented in different parts of a website.

What are the limitations of Google Tag Manager?

Google Tag Manager is extremely flexible, but that doesn’t mean everything should be implemented through it.

Some of the main limitations and risks are:

It doesn’t remove the need for developers

GTM can reduce the number of website changes needed for tracking, but more complex implementations often still require development work. A well-structured data layer, for example, may need information to be pushed from the website into GTM.

It’s possible to break things

Custom HTML and JavaScript give you considerable freedom, which also means poorly written or incorrectly configured tags can cause problems. Changes should always be tested before they’re published.

Containers can become difficult to manage

Over time, GTM containers can accumulate old tags, duplicate tracking, inconsistent naming and triggers nobody is quite sure are still needed. I’ve seen plenty of containers where years of additions have made troubleshooting considerably harder than it needs to be.

GTM doesn’t make third-party scripts free

Adding a script through GTM doesn’t remove its performance cost. If your container loads numerous analytics, advertising, heatmap and other third-party scripts, those scripts can still affect website performance.

It’s not always the best implementation method

Just because something can be done through GTM doesn’t mean that’s where I’d choose to do it. I’ve used GTM as a workaround for things such as structured data and robots directives when direct website changes weren’t practical, but I’d generally prefer to implement those changes within the website itself where possible.

Does Google Tag Manager affect website performance?

Yes, Google Tag Manager can affect website performance, but the important distinction is between GTM itself and the tags you deploy through it.

GTM loads tags asynchronously, but that doesn’t mean everything added to a container is free from a performance perspective. Analytics scripts, advertising pixels, heatmaps, Custom HTML and other third-party tags still require browser resources and can contribute to additional JavaScript execution, network requests and main-thread work.

This is where GTM bloat can become a problem. Over time, a container can accumulate tags that are duplicated, no longer needed or firing far more often than necessary.

I wouldn’t remove GTM simply because a performance test identifies scripts loaded through it. Instead, I’d look at what the container is actually loading and whether every tag needs to be there.

Some of the things I’d check include:

  • tags firing on every page when they only need to run on particular pages
  • old advertising or tracking tags that are no longer required
  • duplicate analytics implementations
  • unnecessary Custom HTML and third-party scripts
  • tags firing multiple times for the same interaction
  • whether triggers can be made more selective

GTM can make tracking easier to manage, but a badly maintained container can still contribute to website bloat. Good tag management includes periodically reviewing what’s being loaded, not simply continuing to add new tags indefinitely.

How can Google Tag Manager be used for SEO?

Google Tag Manager isn’t an SEO tool in the traditional sense, but I’ve found it extremely useful for both SEO measurement and certain technical implementations.

One of its biggest uses for SEO is measurement. GTM can track interactions that help you understand what users do after arriving from search, including internal link clicks, downloads, form submissions, telephone clicks and engagement with particular page elements.

It can also be useful for technical SEO implementations when you can’t make the required change directly to the website. I’ve used GTM to implement or control things such as:

  • structured data
  • robots noindex directives
  • conditional changes based on URLs or page content
  • tracking across different website environments
  • custom analytics events for SEO landing pages and user journeys

I treat GTM as a fallback for technical changes rather than automatically choosing it over a direct website implementation. If I can add structured data or a robots directive properly through the website, that’s generally where I’d rather do it.

Where GTM becomes particularly useful is when the CMS, platform or development process prevents you from making the change you actually need. In those situations, it can give you another route to solving the problem.

I’ve covered several practical examples elsewhere, including implementing noindex with Google Tag Manager, tracking link and banner clicks and using Local Business schema and GTM across multiple store locations.

When should you use Google Tag Manager?

Google Tag Manager makes the most sense when you need more control over how tracking and other tags are implemented and maintained.

I’d particularly consider using GTM when:

  • you’re implementing GA4, Google Ads or other marketing and analytics platforms
  • you need to track interactions that aren’t measured automatically
  • several different tags need to be managed across the website
  • tracking requirements are likely to change regularly
  • you need to use variables or the data layer to capture additional information
  • you want to test and debug tracking before publishing it
  • direct changes to the website are difficult and GTM provides a practical alternative

For a very simple website with minimal tracking requirements, GTM isn’t necessarily essential. But once tracking becomes more sophisticated, I find having a properly managed GTM container considerably easier than maintaining lots of separate implementations.

Is Google Tag Manager worth using?

For most websites where I’m implementing anything beyond very basic analytics, yes.

Google Tag Manager gives me considerably more control over what gets measured, when tags fire and what information is passed to analytics and advertising platforms. It also gives me a practical way to test and debug implementations before they go live.

The important thing is not to treat GTM as a dumping ground for every script you might ever want to add to a website. Containers need maintaining, unnecessary tags can affect performance, and some changes are still better implemented directly within the website.

Used properly, though, GTM is one of the most useful tools I work with for analytics, conversion tracking and the occasional SEO problem that would otherwise be difficult to solve.

If you need help planning, implementing or troubleshooting a more complex setup, take a look at my Google Tag Manager consultancy.

Useful Google Tag Manager Resources

To help you understand and make the most of tools like Google Tag Manager, I’ve curated a list of resources that are both insightful and practical:




About The Author

I'm Dave Ashworth, a freelance SEO and website optimisation consultant with a background in development and a focus on fixing what's broken, improving what's working, and helping businesses grow through clear, practical SEO.

I combine hands-on technical know-how with years of experience in analytics, content strategy and platform optimisation. Whether it's an audit, a migration, or ongoing performance support, my work's about making websites stronger, faster, and easier to understand for - users, search engines and AI platforms.

When I'm not writing guides or sharing insights, I'm working directly with clients to solve problems, track results, and keep their sites moving in the right direction.

Dave Ashworth

get in touch

If you need some expert website optimisation and configuration, want to find out more, or even just have a question, fill in the form below as I will always be happy to help