The Beginners Guide to Google Tag Manager

Want to start getting the basics of GTM down?

Well, you’re in the right place.

In this Beginner’s Guide, well go over how to use one of the most powerful Tag Management Systems out there, Google Tag Manager.

But wait!

FYI, this post is a simplified version of our FREE Google Tag Manager for Beginners Course, which features step by step video tutorials!

Sign up to the FREE GTM for Beginners Course...

In this written guide, I’m going to introduce you to the Google Tag Manager tool, explain its most useful functions, and teach you how to use it to super-charge your marketing.

But first, let’s understand what Google Tag Manager is exactly and how it can help you..

What is Google Tag Manager and Why Use it?

Google Tag Manager is a type of tool called a Tag Management System. A Tag Management System (TMS) helps you deploy marketing Tags and decide what data to collect with those Tags.

A TMS provides a single, central interface that manages and deploys all Tags. One person or department, usually online marketing, can easily handle the TMS without needing to fuss with code.

This frees up time, resources, and communication channels between departments and expedites the Tag deployment process. A TMS also documents Tag deployment, provides a structural framework, and consolidates all your Tags into one central code snippet.

This is the Google Tag Manager user interface. Everything is designed to be accessible and user-friendly even without coding experience.

But before we dive into the interface, let’s first look at what digital marketing problems Google Tag Manager can help you solve.

Google Tag Manager workspace

Benefits of Using GTM

Easily Install Tracking Codes from Third Parties

Let’s say you have a website where you want to extend the marketing functionality via third-party tools, such as Google Analytics for tracking or Facebook Ads for advertising. Oftentimes, these tools ask you to install tracking code onto your page, which usually look something like this:

Google Analytics Admin tab, with Global Site Tag highlighted on Tracking Code page

These are JavaScript code, and they are referred to as marketing tags. Third-party tools usually ask you to place these codes in the head section of your page’s HTML.

What does that mean? Here is an example of a website with these Tags already installed. We can view the page’s HTML code by right-clicking and selecting View Page Source

Demo website shop page with text “right-click,” menu, and View Page Source item highlighted

This wall of code is the page’s HTML document. If we scroll down, we can see that there are some Google Tags and a Facebook Pixel Tag installed to this website. For every marketing Tag that you want to use, you need to install some of this code.

This is where Google Tag Manager is super helpful. Instead of adding a code snippet for every new Tag, you can install the GTM script to your website just once.

Manage Your Third-Party Tracking Codes

Once your central Google Tag Manager snippet is installed, you can control and deploy Tags through its central management console on the user interface.

If we click on the Tags header in the sidebar, we can see the different codes that are installed through Google Tag Manager. In this example, we have pageview tracking through Facebook Ads, Google Analytics, and Google Ads.

GTM with Tags tab and list of Tags highlighted

For lots of marketing Tags, you can use a Tag template, which means that you don’t have to mess with any code. Instead, you can configure and deploy Tags with the graphical user interface.

As its name implies, Google Tag Manager helps you manage your codes, implement them, and view their configurations using all kinds of neat tools.

For example, Preview Mode will put your browser into a special state that allows you to find information about which Tags have been deployed on a particular page view. You can navigate your website and ensure that your Tags are firing when you expect them to. This is great for debugging without interfering with your data collection from real live users.

Demo website shop Preview and Debug Mode with GTM console highlighted

Interaction-based Tracking

Google Tag Manager is actually very well equipped to fire Tags under specific, defined circumstances. For example, we can fire a Tag when the user clicks on an “Add to Cart” button.

This is one of the most powerful functions of Google Tag Manager: you can define your own triggers to fire on a huge variety of interactions. These can include button clicks, scrolling, element visibility, form submission, and so on.

New Versions Keep Tracking Up-to-Date

When you’re done testing Tags using Preview Mode, you can update your site tracking by publishing new Versions. This is a best-practice system because Google Tag Manager keeps track of all past Versions that have been deployed.

The benefit is that if you ever find that your tracking isn’t working or a mistake has been made, you can easily roll back to a prior version where your tracking was working correctly. You can also name your versions and give them custom descriptions, making it even easier to keep track of updates and changes.

GTM Versions tab showing the Version 2 is Live

Overall, Google Tag Manager is a really awesome tool for handling your marketing Tags efficiently. Through one central management console, you can deploy all your Tags and send their data to a vast array of tracking and advertising tools.

How to Install Google Tag Manager

Now that you see how valuable Google Tag Manager is, let’s learn how to properly install GTM on your website. We’ll also give you some tips about container snippets and where to correctly place them in your HTML codes so that you’ll be ready for your first Tag deployment.

Each content management system (CMS) will have a slightly different setup process, but the general framework is the same. In this tutorial, we will use the most popular CMS, WordPress. 

Set Up Your Google Tag Manager Account

Our journey starts at tagmanager.google.com. You will need a Google account in order to use Google Tag Manager, so if you don’t have one, you should create an account. Otherwise, go ahead and log in.

GTM sign-in with Google account

After logging in, you will be greeted with a list of all your GTM accounts. If you are completely new to this system, you won’t see anything here. Instead, you’ll click on the Create Account button.

GTM All accounts list with Create Account button highlighted

Google Tag Manager accounts can be divided into multiple accounts and Containers. You can have multiple accounts, and within each account you can have multiple Containers. Containers are the snippets, or the central code, that are installed on your website.

The best practice is to name your account after your company or organization. So for example, we’ll use Demo Inc. Next, choose your country and whether you want to share data with Google. Click Continue.

GTM Set-up Account with Account Name, Country, and Continue button highlighted

Next is the Container set-up step. A Container is unique for each website where you install Google Tag Manager, so I’d recommend that you name your Container using your website domain. This way, even if you have multiple Containers on your account, you’ll easily be able to recognize which one is installed on each website.

For this guide, we’ll be installing GTM on the web. There are also Containers available for iOS, Android, and AMP pages, but their setups are completely different. Check out our full (and free) GTM for Beginners course to learn more about these other methods. For now, we’ll select Web and click Create.

GTM Set-up Container with Container name, Web button, and Create button highlighted

Google will ask you to adhere to some terms of service. Check the box to accept the terms, click Yes, and your new Google Tag Manager account will be initiated.

GTM Terms of Service Agreement with checkbox and Yes button highlighted

Install the GTM Code Snippet on Your Website

Once you finish setting up your account, you’ll be greeted with your Google Tag Manager snippet. If you don’t see the snippet when you open up your Google Tag Manager account, you can also click on your Google Tag Manager ID in the topbar to open up this window. The window will also include some installation instructions.

GTM Install Google Tag Manager popup with head tag and body tag

We need to place the first piece of code into the head section of our HTML and the second piece into our body section of the HTML. This will probably be the last snippet that you ever need to install onto your website for tracking, but you’ll need access to the website code itself in order to install it.

There are three different methods of installing this code: work with a developer; install the code using CMS plugins; or install the code manually.

1. Work with a Developer

If you already have a developer working on your website who is responsible for its technical infrastructure, I would consult with them in order to install those correctly. They will probably be happy to do this installation for you.

2. Install via CMS Plugins

If you have a CMS such as WordPress, Shopify, Magento, Joomla, or any other backend system that generates your website, you might be able to install a plugin to install these codes for you. There are many out there, and most will already have a tutorial that explains the installation.

We even have some tutorials teaching you how to install GTM on certain content management systems here at MeasureSchool. Check out our posts for installing GTM on Shopify and Magento, or watch our video to learn how to install GTM on Squarespace.

3. Install Manually on Website

You can also install GTM manually on your website. If you have access to the code of your website and feel comfortable following along, then the rest of this guide will show you how to install GTM using a WordPress website as an example.

Installing GTM Code on WordPress

WordPress is the most used CMS in the world. If you are running a WordPress blog, you can follow along with these instructions. Note that if you’re not running WordPress on your website, these instructions most likely will differ.

Content management systems are normally governed by a theme, which controls the design of the website. To access your theme files in WordPress, log into your backend and click Appearance > Editor.

Notice that I have set up a child theme. This is because I don’t want to lose any of my customizations or changes to my theme when an update is released to the parent theme. It’s always best practice to have a child theme if you’re working in WordPress.

The theme files are listed on the right, where you can click on them to edit them. These are PHP files that govern all the different sites that WordPress generates on my front end.

WordPress dashboard Appearance Editor, with child theme code highlighted

To install WordPress, click on your Theme Header file. You’ll see the openings and closings for both the head tag and the body tag. These are the places that you’ll want to paste the code snippets from Google Tag Manager.

WordPress dashboard Appearance Editor with file Theme Header highlighted and arrows next to head and body code sections

Copy the head section from GTM and paste it as high up as possible in the HTML underneath the opening head tag. This is important because the browser will pass the website from top to bottom, and we want to fire our tracking codes with GTM as soon as possible.

WordPress theme file code with GTM head tag inserted

Next, copy your second GTM code and look for the opening body tag in your theme file. Right underneath, paste your noscript body section of the GTM code.

Lastly, update the theme with your new Tags by clicking Update File. If you can’t do this in your WordPress theme, then you might need to directly access these files via FTP in order to change them.

WordPress dashboard Appearance Editor with Update File button highlighted
Testing

To ensure that Google Tag Manager has installed correctly, reload your website, right-click, and click View Page Source to see the page HTML.

Demo website shop with right-click menu and View Page Source highlighted

If you scroll through, you should be able to find your GTM snippets that you just pasted into your theme file. You can also use Ctrl+F or ⌘+F to search for “Google Tag Manager.” You will be able to find both the head tag and body tag if GTM installed correctly.

You can also verify successful installation by opening Google Tag Manager’s Preview Mode. In the Google Tag Manager interface, click the Preview button.

GTM workspace with Preview button highlighted

After entering Preview Mode, you can reload the page and navigate your website to see if the Preview console appears on all pages. The console won’t show any Tags yet, but you’ll know that GTM was installed correctly.

Demo website shop in GTM Preview and Debug mode with preview console highlighted

Submit Your First GTM Version

With Google Tag Manager installed, we’re now ready to deploy our first tags. But before that, let’s submit our first Version in Google Tag Manager in order to initialize GTM correctly. On the GTM interface, click on Submit

Here, you can name your new version and even give it a description. This is super useful for keeping track of changes to your tracking over time. In this instance, let’s name it Initialization GTM. Click Publish to make the version live.

GTM Submit Changes popup with Version Name and Publish button highlighted

If you click on the Versions tab, you will see that Version 1 is live. You can also return to this tab to see a full history of Version updates.

Audit Your Analytics and Plan Out Your Tags

Before we start implementing Tags, let’s learn how to effectively plan a migration to GTM. This is very important to ensure data quality before the implementation in GTM. In this Google Tag Manager beginner guide, we will use this Tag Plan template, which you can copy and use to document all the Tags and tracking on your website.

Using our Tag Plan, we will document existing tracking Tags on our website that we want to migrate to Google Tag Manager. We can also document anything that isn’t currently tracked that we would like to add to GTM.

Sign up to the FREE GTM for Beginners Course...

Why You Need a GTM Tag Plan

Google Tag Manager is a great tool to organize your tools and deploy new Tags. But in most cases, you’re not actually working with a brand new website, and there will already be some Tags installed on your website. You’ll need to migrate these over to Google Tag Manager.

The first step that we want to take is to plan out our implementation. Using a Tag plan will ensure data quality, which is very important, and provide us with documentation of our implementation. Documentation is really important in case we ever need to explain or investigate an older implementation.

Unfortunately, sometimes it’s the case that nothing was documented, nobody really knows what tracking codes are installed. And if the website is a little bit older, it might be that many codes are installed that are not used anymore. You can prevent these hurdles in the future by writing a Tag plan and keeping it as documentation.

How to Write Your Tag Plan

When writing a Tag plan, our goal is to document our journey so we’ll be able to decipher our tracking later on and see where it was implemented.

You can do this outside of Google Tag Manager. Personally, I do it in this spreadsheet, but any format will work. This document will be super helpful if anybody from your team asks you what codes are installed or what the tracking configuration looks like. On the Tag plan, we can enter all the tools, and we’ll look at different pages, events, and audiences that we want to track.

At this stage, I would encourage you to talk to anybody who is involved in the website and might have something to do with the tracking. This can include marketers or developers who have installed the tracking code on your website. There might even already be some kind of documentation of what was installed, so make use of these if you have them. 

Investigate Existing Tracking and Marketing Tools

If your team doesn’t have documentation of existing tracking or if you want to verify your information, you can look for marketing Tags in the website’s HTML by right-clicking and selecting View Page Source. However, this can be slow and inefficient.

Instead, you can use some helpful browser extensions  to investigate your site’s existing tracking. One of these is the Tag Assistant by Google, which will show you any Tags that are associated with a Google tool.

On this demo website, Google Tag Manager has found Tags for Google Ads, Google Analytics, and our newly-installed Google Tag Manager. Additionally, it shows the global side tag, which deploys the Google Ads and Google Analytics Tags.

Demo website with Google Tag Assistant showing Global site tag, Google Ads Remarketing Tag, Google Analytics, and Google Tag Manager installed

Facebook has a similar browser extension for its pixel called the Facebook Pixel Helper, which will show you all the events recorded and the ID number of the Pixel they were sent to.

If you have other marketing vendors, they might have their own browser extensions specifically for their tools. If you want to have a more general one, you can get the WASP.inspector.

The WASP.inspector is a great extension that add functionality to your Chrome Developer Tools. You can find  it by clicking your Chrome options button (three vertical dots), go to More Tools, then click Developer Tools.

Chrome browser with Customize and Control menu, More Tools, and Developer Tools highlighted

In your Developer Tools, you’ll find a new tab called WASP. If we reload this page, WASP will give us a lot of information of what marketing tags were found and where they came from.

Add Audit Information to Your Tag Plan

As we find tracking tools on our site, we’ll add them to our Tag plan. In the Tag plan, you can add the name of the tool, a description of what it tracks, whether or not the tool is active, and any helpful notes for migration.

I recommend entering certain configuration data in the Notes section in order to make the migration process quicker and easier. For example, we will need account information or tracking ID numbers  during our migration so that GTM knows where to send its Tag information.

For Google Analytics, you will need your account’s Tracking ID. To find the Tracking ID, click on the Admin header in the sidebar (also marked by a gear icon), and under Tracking Info click Tracking Code. The Tracking ID will be listed at the top of the page.

Google Analytics Admin panel with Tracking Code and Tracking ID highlighted

This is the piece of information that we’ll  need later on for Tag migration and deployment. Let’s enter the Google Analytics Tracking ID under the Notes section.

Google Sheets Tag Plan with Google Analytics Tracking ID entered under Notes

You will need similar information from Google Ads. On the Google Ads interface, click on the Tools menu and select Conversions. This Google Ads account is tracking a Purchase conversion on our demo website. Click on it to see its tracking information.

Google Ads Conversions with Purchase conversion highlighted

If you scroll down, you’ll see that Google Ads has an option for Tag setup specifically with Google Tag Manager. Click on this option.

Google Ads Tag setup with Use Google Tag Manager option highlighted

Google Ads will give you some handy instructions for using Google Tag Manager to install your Google Ads Tag. The most important information here is the Conversion ID, so copy this.

Google Ads GTM setup instructions with Conversion ID number highlighted

Paste the Google Ads Conversion ID into the Notes section of your Tag plan.

Google Sheet Tag Plan with Google Ads Conversion ID entered under Notes section

Finally, the Facebook Pixel also has some important identification that we should put in our Tag plan. In the Facebook Events Manager, click on Set up to find some tracking information.

Facebook Events Manager with Set Up button highlighted

To see the Facebook Pixel code, which will have your pixel’s ID number, click on Manually Install the Code Yourself.

Facebook Events Manager Set Up Your Pixel popup with Manually Install the Code Yourself option highlighted

Near the end of the pixel code, you will see a line that begins with id=. The numbers that follow are your pixel’s ID number. Copy the numbers up to the ampersand ( & ) to put into your Tag plan.

Facebook Events Manager Install Pixel Code popup with ID highlighted in script tag

Once you’ve copied all identification and tracking numbers into your Tag plan, you’re ready to migrate any existing marketing Tags into Google Tag Manager.

Google Sheet Tag Plan with Facebook Pixel ID entered under Notes section

We’ve just demonstrated how to find these codes for Google Analytics, Google Ads, and the Facebook Pixel, but if you get stuck searching for an ID number on another tool, leave us a comment and we’ll help you find it!

Plan New Interactions to Track

Next, let’s think about what new information we want to track with Google Tag Manager.

This should be very purposeful and thoughtful.  We don’t want to mindlessly deploy lots of random tracking that gathers unhelpful data that will overwhelm any analysis. It’s far more important to track high-quality data that feeds your marketing goals.

Take a look at your website and take note of important pages and interactions. On an online shop, these might be the homepage, product pages, “Add to Cart” button clicks, the checkout page, and the order confirmation (or “thank you”) page.

As an example, let’s look at this demo website’s order confirmation page. This page is important to our tracking because we will use it as a conversion goal. We’ll copy the URL so that we can insert it into our Tag plan.

Demo website Order Received page with URL highlighted

In our Tag plan template, we have a tab for another sheet called Pages. On this sheet, we’ll paste the portion of the URL after the domain under the column Path (this is anything after .com, .net, etc.).

Google Sheet Tag Plan with Order Received page URL path entered under Path column

Make sure to add a name and description so that you’ll remember what everything is. In this case, we’ll name this page Thank You Page and enter Conversion / Thank You Page as the description.

Google Sheet Tag Plan with Name and Description entered for Thank You page

The Tag plan template also has a tab for an Events sheet, where you can include any interactions that you want to track.

An important interaction for a shop, for example, would be clicks on the “Add to Cart” button. For now, we can just name and define these interactions so that we remember to implement them on GTM later.

Google Sheet Tag Plan with Button Click entered under Events tab

The Tag plan template also has room to track audiences if you’re using tools like the Facebook Pixel. You can fill out each of these sheets with all kinds of tracking tools, pages, events, and audiences that are important to your analysis and marketing goals.

With your Tag plan in place, you’ll be ready to migrate your existing tracking and build new tracking into Google Tag Manager.

Migrate Your Current Tracking to GTM

Next, we’re going to learn how to migrate our existing tracking over to GTM and deploy our Tags through GTM. We’ll use our Tag plan to guide our migration process.

Creating a New Tag

In  Google Tag Manager’s Workspace, click on New Tag. You can also click on the Tags header in the sidebar and click the New button.

GTM Workspace with New Tag button highlighted

Note: Naming Conventions for Tags

You can give custom names to all tags, triggers, and variables in Google Tag Manager. This will help you identify your various Tags and their functions, provided that you have a consistent system for names.

So how do you name a tag correctly? It depends on your preferences.

I normally utilize a naming convention. My naming convention includes the Tag’s tool, purpose, and scope of installation.

In the example below, I’ve named this Tag GA – Pageview – All Pages. First, this tells me that the Tag sends its data to Google Analytics. Second, I know that the purpose of this Tag is pageview tracking. Third, this Tag fires on all pages across my website.

GTM New Tag configuration with name highlighted

This naming convention helps me quickly identify my Tags if I need to make changes to my tracking. If I have multiple Google Analytics Tags, for example, I can see which Tag I need to edit in order to change general pageview tracking.

Tag Configuration

Let’s set up our Tag’s characteristics and functions. To start configuring your Tag, click anywhere in the large Tag Configuration field. 

Choose a Tag Type

First, you’ll be prompted to choose a Tag type. Here, you’ll see a list different tools that you can install via Google Tag Manager. Let’s select Google Analytics – Universal Analytics for this Tag.

GTM list of Tag Types in Tag Configuration, with Google Analytics - Universal Analytics highlighted

Track Type determines what kind of interaction the Tag will send to Google Analytics. We have the ability to send events, transactions, and more. For now, we’ll leave it on the default setting, Page View.

The Google Analytics settings dropdown will ask for a variable that will help GTM know which Google Analytics account should receive data. There probably won’t be any usable variables here, so we’ll have to select New Variable.

GTM Tag Configuration options with Track Type set to Pageview and New Variable option highlighted
Variable Configuration

Let’s build a new settings variable that we can reuse for other Tags that we want to connect to Google Analytics.

The most informative name we can give to this variable is the account number that it represents. Our Tag plan conveniently has this ID number ready, so we can copy if from there and paste it into the variable name.

This is the same information that we’ll enter in our Tracking ID field, and we’ll leave the Cookie Domain field set to auto. Lastly, click the Save button.

GTM Tag Configuration with Google Analytics settings and empty Triggering box highlighted

Triggering Configurations

Once you’ve selected your new variable, you’ll be almost finished building your first Tag in GTM. There are tons more settings that we can configure for this Tag, but let’s keep it simple for now. We don’t even have to worry about any of the other advanced settings.

The final thing we need to set up is the Triggering, which tells GTM under what circumstances the Tag will fire. Click anywhere in the large Triggering field to open up the trigger configurations.

GTM Tag Configuration with Google Analytics settings and empty Triggering box highlighted

Later on, we’ll learn how to build custom triggers that fire in specific circumstances, but for now, we’ll just be using this All Pages trigger. Google Analytics pageview tracking should be deployed on all pages, as Google Analytics will compile and organize that data into sessions and users.

GTM Choose a Trigger popup with All Pages trigger highlighted

Now that we’ve assigned a trigger, we are done configuring our Tag. Click Save, and you’ll see your new Tag listed in your GTM Workspace. 

GTM Tag Configuration settings for Google Analytics Pageview  with Save button highlighted

Testing Your Tag

Before we update our GTM Container and make this Tag live, we should test it to make sure that it’s functioning as intended. There are three good methods that you can use together to test your Tag: GTM’s Preview & Debug Mode; Google Tag Assistant; and verifying data transfer on your tracking tool.

1. Using Preview & Debug Mode

Preview & Debug Mode is easy to access and a good first step in checking your Tag’s function. Once you have new Tags to test in your Workspace, click the Preview button in the topbar of your GTM interface.

GTM Workspace with Tags header, new Google Analytics Tag, and Preview button highlighted

This will put our browser and only our browser into a special state. If you reload your website page, you will see a little GTM debug console at the bottom of your browser.

This console gives us more information about what is happening on our page in terms of tracking and Google Tag Manager. Under the Summary tab, we should see that our new Google Analytics pageview Tag has fired once.

If we click on this Tag, we can also see its configurations and how they interacted with the page.

GTM Preview console with GA Pageview Tag properties highlighted

If you scroll down, you’ll also see a section labeled Firing Triggers. Firing triggers are always evaluated as either true or false for particular events.

In this example under the Page View tab, these events are All Pages and event equals gtm.js, which were both evaluated as true. Because all of the triggers were true, the Tag fired in GTM.

GTM Preview console with Page View Tag and Firing Triggers highlighted
2. Using Google Tag Assistant

Now, we shouldn’t just take Google Tag Manager’s word that our Tag deployed correctly. We can also use the Google Tag Assistant to verify that the Tags are operating on our website. If you open the Tag Assistant, you will see that it picked up a Google Analytics Tag on this page.

Demo website with Google Tag Assistant open, Google Analytics highlighted

You may notice that this Tag is yellow in the Tag Assistant. This is because the Tag is currently firing twice. We expect this because we already have a Google Analytics Tag installed on our page independently of GTM.

We will take care of this later on. Because we’re only in Preview & Debug Mode, the GTM Tag is only live on our own browser. If we remove the hard-coded Tag now, we could miss out on collecting pageview data before we make the Tag live for all users.

For now, the important thing is to make sure that our Tags are functioning as expected. Since GTM’s Google Analytics pageview Tag is firing, we can move on to the last testing step. 

3. Checking Real-Time Report in Google Analytics

The ultimate test is to verify that your tracking tool receives your data. In this case, that tool is Google Analytics.

In Google Analytics, we’ll look for our Tag data in the real-time reporting. Click on Real-Time > Overview to see all the different pageviews that are happening right now on your page from real users.

Now, we could just reload our website page to generate a new pageview and go over to our analytics page to look for our data. If you do, you might see that two pageviews recorded at the same time. This could hint at your Tag firing if you have a low- to medium-traffic website.

Google Analytics Real-Time Overview with page views per second graph highlighted

This is less likely to work if you have a lot of users currently on your website. A helpful trick is to attach something called UTM parameters to your URL.

If you would like to learn more about UTM parameters, you can see our guide How to Create Custom UTM Parameters via GTM. For now, though, you can add the following string to your webpage’s URL and load the new page: ?utm_source=test&utm_medium=test&utm_campaign=test

Demo website page with UTM attached to URL

When your page loads with the UTM parameters attached, you will see a pageview appear at the bottom of your real-time interface called test. This means that your Tag is firing correctly and sending data to Google Analytics.

Google Analytics Real-Time Traffic Sources, with source and medium labeled “test” highlighted

If you click on the test pageview, Google Analytics will filter the real-time results to show only pageviews with these UTM parameters. You can click Content in the sidebar to see where the user who generated the pageview is on your website at that moment.

For the sake of data quality, always verify that your tracking tool is receiving complete data from GTM. After checking GTM’s Preview & Debug Mode, the Google Tag Assistant, and Google Analytics’s real-time report, we know for sure that the pageview tracking code is installed correctly.

Publishing All Changes

Finally, our last step is to publish this new Tag to all our users so that we can start collecting real data. To create a new Container Version, click Submit in your GTM interface topbar. 

GTM Workspace with GA Pageview Tag

Give your Version a name that lets you know what changes were made in this update. If you made lots of changes, you can give a more detailed report in the Version Description. When you’re done, click Publish to make our Google Tag Manager code live on the website.

GTM Submit Changes with Version Name and Publish button highlighted
Removing Redundant Hard-Coded Tags

Now that GTM is actively deploying our Google Analytics Tag, we can go back and remove the hard-coded Tag from Google Analytics.

If we load our webpage now, we won’t see the debug console anymore since we’ve left Preview & Debug Mode. However, we can still use our Tag Assistant. We can see that our Google Analytics code deployed twice because the hard-coded and GTM Tags both fired.

Demo website page with Google Tag Assistant open, 2 Pageview Requests and Same web property ID is tracked twice are highlighted

Because we are moving all of our tracking to GTM, we need to get rid of the hard-coded version. In this example, I’m running a WordPress blog, so I’ll go into the theme editor of my WordPress admin dashboard.

Wherever you edit your website code, find and delete your hard-coded Tag. Don’t forget to update or save any changes that you make.

WordPress Theme Editor with Google Analytics Pageview Tag code highlighted and marked “delete”

Reload your website page again and open your Tag Assistant to check out your Google Analytics pageview code. This time, it should only fire once.

Demo website with Google Tag Assistant open, 1 Pageview Requests is highlighted

This step is super important if you are migrating Tags into GTM rather than making new, original Tags. If you leave both codes deployed, you will collect data twice, which will skew your analysis and interfere with your marketing.

Adding Other Types of Tags

Now that we’ve demonstrated how to build a Tag from our Tag plan for Google Analytics, let’s quickly go over some differences for two other examples: Google Ads and Facebook Ads.

Example 1: Google Ads Remarketing

Our Tag plan already has the necessary information for a Google Ads Tag. All we need to do is create a new Tag and select Google Ads Remarketing as the Tag Type. Enter your Conversion ID, leave the Custom Parameters field as none, and select All Pages as the trigger. Click Save and you’re done.

GTM Tag Configuration for Google Ads Remarketing Tag, with name, configuration, trigger, and Save button highlighted

Example 2: Facebook Ads (Using Custom HTML)

The Google Tag Manager Community Gallery has a template for Facebook Pixel installation, but in this guide, we’ll be using the Custom HTML Tag type. Custom HTML Tags are super versatile, and they let us input any kind of HTML code that we would like to deploy.

(For more details and options on installing a Facebook Pixel with GTM, see our complete training on Facebook Pixel Tracking with Google Tag Manager.)

Remember the Facebook Pixel installation code where you grabbed your pixel ID in the Tag planning stage? You can access it from the Facebook Events Manager by clicking Set up > Manually Install Pixel Code Yourself.

Facebook Events Manager with Set up and Install Pixel popup with Manually Install Pixel Code Yourself highlighted

Paste this into the HTML field in your Tag configuration. Be aware that you need to have script tags around your JavaScript in order for it to work.

GTM Tag Configuration for Facebook Ads Pageview Tag, with name, Tag Type, and HTML highlighted

We want this script to deploy across our whole website, so select All Pages as the trigger. Click Save.

GTM Facebook Ads Pageview Tag with trigger and Save button highlighted

Testing & Publishing

Test your new Tags using Preview & Debug Mode. You can also use the Google Tag Assistant for your Google Ads code and the Facebook Pixel Helper for your Facebook Ads code. Don’t forget to check that your tracking tools are receiving data!

Publish your changes to a new Version so that your Tags are live on your website. Remember to give the updated Version an informative name in case you need to reference any changes later.

GTM Versions showing that Version 3 is Live

Finally, remove any hard-coded Tags in your website’s code. If you have Google Ads or Facebook Ads codes, they’ll look something like this:

WordPress Theme Editor with Facebook Pixel and Google Ads script highlighted

After you delete the hard-coded Tags, check using Preview & Debug Mode and any browser extensions that your GTM Tags are functioning correctly. All of your Tags should fire just once.

GTM Preview and Debug mode with Tags fired in console highlighted

With that, we have successfully migrated our existing codes from our Tag plan into Google Tag Manager and deployed them to all our users.

Conversion Tracking with GTM

Next, let’s learn how we can measure the success of our site with conversion tracking. This is a step-by-step tutorial on the proper installation and configuration of the Facebook Conversion Pixel and Google Ads pixel.

Previously, we installed GTM, wrote a Tag plan, and migrated our existing tracking over to GTM. So now we have data flowing into our account that shows where users are coming from and what they’re doing on our website.

The crucial information that we’re still missing is whether or not users took the actions that we want them to take. This is commonly referred to as conversion tracking.

In order to do conversion tracking, you need to install a tracking code on a specific website, or when the user actually does the conversion action. And with Google Tag Manager, we can do this pretty easily.

Sign up to the FREE GTM for Beginners Course...

What Are Conversions?

Conversions are user actions that define success on your website. Anything that you want your customer to do on your website can be considered a conversion.

For example, on an online shop, conversions might be purchases. Depending on your website goals, conversions can also be certain pageviews, downloads, or subscriptions.

Conversion data is important to send to our paid traffic sources like Google Ads or Facebook Ads. These sources can use this data to tell us how effective our advertisements are at generating paying customers. 

Tracking eCommerce Conversions

So in order to install conversion tracking, we need to pick an interaction that we would define as a measure of success on our website. Since our demo website has a shop, let’s choose a product purchase as a conversion.

When users place an order, they usually see an order received page or a thank you page. Users can only get to this page if they go through the checkout process and purchase the product. Therefore, pageviews for the order received page are a good metric for purchase conversions.

We can track this interaction with Google Tag Manager and send it to our tracking tools. Conversion tracking works differently in different tools. If you’d like to learn how to track conversions with Google Analytics, start with our guide Google Analytics eCommerce Tracking with Google Tag Manager. To learn how to track conversions in Google Ads and Facebook Ads, read on.

Example: Configuring Facebook Ads Conversion Tag

Before we get started, let’s add a Facebook Ads conversion in our Tag plan. This documentation will be important to reference for any future changes.

The tool we are using is a Facebook Pixel. We’ll describe this as a Purchase Event and enter the URL for the order received page under the notes section.

Tag Plan with Facebook Conversion added to Tools tab

PageView Trigger Setup

If we look at our current Tags in GTM, we’ll see that they are all using the All Pages trigger. This is a built-in trigger that deploys our tracking codes on every page where GTM is installed.

But for a purchase conversion, you don’t want to deploy your Tag on every page. You only want to deploy it on the order received page where users have taken the action that we want them to take.

So first, we’re going to build a special trigger that only fires on our order received page. Click on Triggers in the sidebar, then click New.

GTM Workspace with Triggers heading and New button highlighted

In the trigger configuration window, we can choose when our trigger or rule should be evaluated. These trigger types can include pageview, clicks, form submissions, and more. Since our conversion is associated with a specific page, we’ll choose Page View.

GTM list of trigger types with Page View option highlighted

Now we can further restrict or define our trigger so that it only fires in certain circumstances. First, click the Some Pages radio button. Next, we’ll define a variable that must be evaluated as true for the trigger to file. Possible choices include the page hostname, page path, page URL, and referrer. For now, let’s set this as Page URL contains checkout/order-received.

GTM trigger configuration with Some Page Views and Page URL contains checkout/order-received highlighted

Why didn’t I use equals or copy this whole URL for the order received page? Well, in this case, the full URL contains some dynamic variables that change for every individual order. Using the full URL would cause GTM to miss all other purchase conversions, resulting in ineffective tracking.

But checkout/order-received is both universal among order received pages and unique from other website pages. Users also can’t randomly navigate to this URL through the website, so we won’t track non-conversion pageviews.

Give your trigger an informative name and click Save.

GTM trigger configuration with name and Save highlighted

PageView Tag Setup

Now that we’ve defined our trigger, we can get ready to deploy our tracking code. In order to deploy a Facebook Ads tracking code, however, we need part of a different Facebook Pixel code to fire first.

Under Tags in your GTM Workspace, open your Facebook Ads pageview tracking code that we installed during out GTM migration. Notice that there are two parts to this code. The upper part (lines 2-9) deploys your Facebook Pixel, and the lower part (lines 10-11) sends pageview data to your account. If you don’t have this already installed, you will need it in order to deploy your conversion Tag.

To track our conversion, we want to deploy a Tag that looks a little like the lower part of this HTML. In order for this piece of script to work, the upper part of the code must already be initiated.

GTM Facebook Ads pageview Tag configuration with Facebook Pixel code highlighted

Since this Tag fires on All Pages, this piece of code will always initiate. We don’t need to repeat ourselves in the conversion Tag, but we do need to make sure that the pixel code initiates before our conversion Tag.

Note: Tag Firing Priority

To ensure that our Facebook Ads pageview Tag fires before our conversion Tag, we’re going to use an advanced setting called Tag firing priority. This assigns priority to this tag based on a number. The higher the number is, the higher that Tag’s priority.

For example, if you make a Tag’s firing priority 100, then that Tag will fire earlier than all other Tags with a lower priority (the default priority being zero). Let’s assign this Tag a firing priority of 100 and click Save

GTM Facebook Ads pageview Tag configuration with Tag firing priority and Save button highlighted

Conversion Tag Setup

Now that our Facebook Ads pageview Tag can help GTM pick up other Facebook Ads Tags, let’s go ahead and make our Facebook conversion Tag.

In the Facebook Events Manager, click Set up > Manually Install Pixel Code Yourself to see the code for the Facebook Pixel that we installed during our GTM migration. The next section will help us  install and track events, click Continue.

Facebook Events Manager Install Pixel popup with Continue button highlighted

Here, Facebook Ads has a list of special interactions it already recognizes as conversions. Scroll down until you find the Purchase event.

Let’s turn off Send Event Parameters for now just to keep it simple. The script below that will help us build our new conversion tag, so copy it to your clipboard.

Facebook Events Manager Install Pixel Code popup with Purchase event and script highlighted

In GTM, create a new Tag. Again, since there is no Facebook Ads Tag template, we will use a Custom HTML Tag type. In the HTML field, we will paste our Purchase event code.

We don’t have to give this Tag a firing priority, since its default is zero. So this will fire after our Facebook Ads pageview code, which includes the Facebook Pixel initiation code.

Now we can simply attach our purchase pageview trigger that we made earlier. Give your new Tag a name and click Save.

GTM Facebook Ads event Tag configuration with name, trigger, and save button highlighted

Testing Out Your Conversion Tag Works

Finally, let’s test out our Facebook Ads conversion Tag.

We’ll start with the GTM Preview & Debug Mode. In your GTM interface, click the Preview button.

GTM Workspace with Facebook Ads Tags and Preview button highlighted

Reload your website’s order confirmation page. If everything is configured correctly, you should see your Facebook Ads purchase event in the preview console.

You should always do multiple checks when testing and debugging, so let’s also open the Facebook Pixel Helper. You should see your purchase event fired, and if you click on it, you can see more information about the event.

Demo website in GTM Preview & Debug Mode with Tag in preview console and Facebook Pixel Helper

Lastly, it’s always important that your data is actually received in your tracking tool. In the Facebook Events Manager, we can click on the Test Events tab. This will put Facebook into a listening mode that helps you test your events in real-time.

Facebook Events Manager with Test Events tab highlighted

Reload your order received page again, to fire the Tags and send data to Facebook Ads. You should now see a new purchase code in your feed. If so, then everything is working great, and your conversions are now tracked and properly installed with the Facebook Ads.

Facebook Events Manager Data Sources with Purchase Tag highlighted

Example: Google Ads Conversion Tracking

Once you’ve built the right trigger for your order received page, tracking your conversion with other tools is easy. One of the big advantages of Google Tag Manager is its flexibility, since we can reuse elements we’ve already built for new tracking.

Let’s demonstrate this by tracking the same conversion in Google Ads.

Create a Google Ads Conversion Tag

In your Google Ads Conversion actions, select the conversion that you want to track. In this case, we’ll click on Purchase.

Google Ads Conversion action with Purchase action highlighted

Scroll down through the Details tab and click Use Google Tag Manager. Here, you’ll find the Conversion ID that we used earlier and a Conversion Label. Copy both of these, as we’ll need both of them for our conversion tracking.

Google Ads Purchase conversion details with Conversion ID and Conversion label highlighted

To maintain good documentation and make these codes easier to access in the future, paste them into your Tag plan as part of a new Google Ads conversion item.

Tag Plan with Google Ads conversion tracking added to Tools tab

Now we can use this data to quickly and easily build a new Tag. This time, GTM has a template available. Choose the Google Ads Conversion Tracking Tag type, then enter your Conversion ID and Conversion Label. We can leave the other fields alone for now.

Next, simply reuse the trigger that we built for our Facebook Ads purchase tracking. Give your Tag a name and click Save.

GTM Google Ads conversion Tag with name, configuration, triggers, and save button highlighted

Testing Your Tag

Again, remember to test your Tag using tools like GTM’s Preview & Debug Mode, the Google Tag Assistant, and your tracking tool. If the Tag is installed correctly, you should see it fire when you refresh your order received page in both the preview console and the Tag Assistant.

Demo website in GTM Preview & Debug Mode with Google Ads Tag in preview console and Google Tag Assistant

Publish

And then we are ready to publish a new version to all our users. Submit a new version to deploy the changes on your website.

GTM Versions with Version 7 active

And that’s how you can track conversions with Google Tag Manager and forward them to your paid traffic sources.

For more on tracking conversions in Facebook Ads and Google Ads with GTM, see our in-depth tutorials [Complete Training] Facebook Pixel Tracking with Google Tag Manager (2020 Version) and Google Ads Conversion Tracking with GTM.

Interested in tracking conversions in other tools? Check out some of our other guides:

Auto-Event Tracking in GTM

Auto-event tracking is a powerful feature of GTM that picks up interactions like button clicks, form submissions, scrolls, or video plays on our website. Rather than being restricted to specific pages, our tracking can encompass all kinds of user interactions.

When Do I Need to Use Auto-Event Tracking?

Previously, we built Tags using pageview triggers—either for All Pages or Some Pages. Every time GTM deploys, it decides whether or not to fire Tag based on an evaluation of that Tag’s trigger. You can see how GTM does this using the preview console.

Demo website with GTM Preview console showing Tags fired and not fired

If you click on a Tag that uses the All Pages trigger, you can scroll down and see that GTM evaluated the trigger as true. This is signified by the green check marks next to the trigger and its filters.

GTM Preview console with firing triggers evaluated as true

If you click on a Tag that doesn’t fire because it’s trigger is Some Pages, you can scroll down and see that the trigger evaluation was false.

In this example, there is a filter rule stating that the Page URL needs to contain checkout/order-received. Because the URL does not include this string, the trigger is evaluated as false and the Tag does not fire.

GTM Preview console with firing triggers evaluated as false

Remember that triggers are rules that determine whether or not your Tags fire. These triggers are evaluated based on certain events that you see on the left in your preview console: Page View; DOM Ready; and Window Loaded.

Up until now, we have only been evaluating during the Page View event. This event is the point in time at which our trigger is evaluated and checked for certain conditions.

If we want to track user interactions on a page, these actions will come after these three steps. Our goal at the end of this particular lesson is to track a button click. But when this button click happens, GTM isn’t evaluating any triggers.

So we need to let GTM know that something happened that it should evaluate. This is what auto-event triggers do.

How Does it Work?

When we deploy Google Tag Manager, a trigger determines whether or not to fire our Tag and deploy the code that sends information to a tracking tool like Google Analytics.

With the auto-event trigger, we actually deploy two functionalities. One is the Listener, which picks up interactions. The second is the Filter, which determines whether or not to should turn our trigger true, which will fire our Tag and deploy the code.

Infographic flowchart showing GTM to Trigger with Listener and Filter to Tag to Google Analytics

Let’s look at an example. If you have a page that has Google Tag Manager installed, then it will automatically listen when users load a new page. However, it won’t automatically listen to clicks. 

Infographic showing mouse clicks on sample website

If you want to pick up these clicks and forward them to your tracking tool, you’ll need to deploy your auto-event tracking. To do this, you install a Listener functionality using a trigger, which will listen to all clicks happening on your website.

These get forwarded to the Filter, which then determines which clicks to evaluate. If they are evaluated as true, then GTM will fire a Tag. 

Infographic showing mouse clicks passing through trigger listener and filter to fire a Tag, which is sent to Google Analytics

Example: Create a Listener Trigger for Clicks

So let’s install our own Listener trigger with Google Tag Manager.

On our demo website’s shop, we have an “Add to Cart” button. We want to track clicks on the “Add to Cart” button with Google Tag Manager.

The first thing that we need to do is to deploy our Listener functionality through a trigger. In GTM, create a new trigger. For now, we’re just going to name it Click. For the trigger type, select the Click – All Elements option.

GTM Trigger configuration, with name and Click - All Elements highlighted

Now, eventually we will want this trigger to only track a very specific click. However, we don’t currently know what filters will define that specific “Add to Cart” button click. For now, select All Clicks and click Save.

GTM clicker trigger configuration, with All Clicks and Save button highlighted

Refresh your container and your page, then enter Preview & Debug Mode.

Now every time you click on the page, you will see a new event in your preview console. These will register as gtm.click, and each event represents a click on your page.

Determine Variables for Specific Clicks

Next, we need to evaluate these gtm.click events and see what kind of filter will just give us “Add to Cart” button clicks. To do this, we will look at the Variables tab in the preview console.

Variables are placeholders that get filled every time a new event occurs. However, all of our current variables look the same between gtm.click events. This is because these variables all relate to the event type or location, none of which change for each click.

We need a variable that reacts differently to different clicks. GTM has some built-in ones just for clicks that we can activate. In GTM, click on the Variables header in the sidebar and click Configure.

Here you’ll find different variables that we can activate. There are six variables specifically for our click trigger: Click Element, Click Classes, Click ID, Click Target, Click URL, and Click Text.

We’re not sure yet which one will help us identify our button click, so let’s activate all of these click triggers. Once they are all activated, refresh your Container.

GTM Configure Built-In Variable list with all Click variables checked

Let’s go to a product page and make several clicks around the page. This will give you some control variables to compare against your “Add to Cart” button click.

Depending on your site, clicking the “Add to Cart” button may reload the page or navigate to a new page. This would clear all of the gtm.clicks in our preview console, including our “Add to Cart” button click.

To avoid this, use Ctrl+click or ⌘+click when you click the button to open a new tab instead. If this doesn’t work, you also try the Escape key or using an extension to stop the browser from redirecting you.

Without navigating away from the page, click on the “Add to Cart” button. Your GTM preview console should now be filled with different gtm.click events. We can compare the variables of these events to see what defines our “Add to Cart” button click.

Demo website with Add to Cart button highlighted and Ctrl+click text, arrow pointing to gtm.click event in GTM Preview console

If you click on the different gtm.click events in your console, you can see all of the variables associated with each event. Some variables may be empty, but many of them should be populated. 

What we need to do right now is to figure out how our desired click differs from all the other clicks. And we do this by looking at the variables itself and figure out what is really unique about my ninth click.

So in my case, the Click Text for this gtm.click is “Add to cart.” None of my other gtm.click events share this same Click Text, so the attribute is unique to my button click. That means that this variable is a good way to filter our click interactions on this page to just “Add to Cart” button clicks.

GTM Preview console with Add to Cart gtm.click and all Variables highlighted, arrow to ‘Add to cart’ Click Text

Deploy a Variable Filter to Track Add-to-Cart Clicks

Now that we know how to filter our click interactions, let’s edit our general click trigger and turn it into a specific trigger that only fires on “Add To Cart” button clicks.

In the trigger configuration, select Some Clicks. For our filter, we want this trigger to fire when Click Text equals “Add to cart”—make sure to use the same capitalization as the original variable. Click Save.

GTM trigger configuration with name, Some Clicks, Click Text equals Add to cart, and Save button highlighted

Example: Track Add-to-Cart Button Clicks

Now that we have a trigger that recognizes our “Add to Cart” button click, we need to build a new Google Analytics event Tag that will use this trigger.

Create a new Tag and choose the Google Analytics – Universal Analytics Tag template. This time, rather than a pageview, we want our data to be sent to Google Analytics as an Event.

GTM Tag configuration with name, Tag Type, and Track Type highlighted

Event tracking lets you fill in certain parameters, such as Category, Action, Label, and Value. These are classifications on how you want to see the data later on in Google Analytics.

For this example, we’ll use a category called Click and the action Add to Cart. I want to know on which page this event occurs so that I know what product was added to the cart, so I’m going to use {{Page Path}} for the label. These double curly brackets tell GTM to dynamically fille this parameter with the page path variable from the page where the click occurs.

GTM Tag configuration with Event Tracking Parameters highlighted

For the Google Analytics settings, choose the variable that we set up earlier to send the data to your Google Analytics account. Finally, attach our “Add to Cart” button click trigger and click Save.

GTM Tag configuration with Google Analytics settings, trigger, and Save button highlighted

Testing

Let’s test our Add to Cart Tag. Refresh the Container and enter your website in Preview & Debug Mode.

To make sure that your Tag doesn’t fire falsely, click around your page on elements like titles, descriptions, and images. Your preview console will register gtm.click events, but it shouldn’t fire your Tag.

Next, click the “Add to Cart” button using Ctrl+click or ⌘+click. You should see that on this click, our Google Analytics Add to Cart Tag has fired. You can also investigate the event in your Tag Assistant by clicking on the Tag. Check that any dynamic parameters are filled correctly.

Demo website with Add to Cart Tag highlighted both in GTM Preview console and Google Tag Assistant

Finally, check that the correct information is sent to Google Analytics. Under Real-Time > Events, you should see the click event listed with your defined event category and event action.

Google Analytics Real-Time Events with Add to Cart Click event highlighted

If you click on the event, you can also view the event label, which in this case tells us what product was added to the user’s cart.

Google Analytics Real-Time Events filtered for Event Category Click with Add to Cart Event Label highlighted

Now, the real-time reporting won’t give you long-term data. If you want to analyze this later on, you can click Behavior > Events > Overview to see all the events that fired into your account.

Google Analytics Behavior Events Overview

You probably won’t see anything right away since it takes time for this to update. But if you check back later, this is where you can access your whole history of events data.

Sending Event Data to Facebook Ads

So now we have successfully built our first auto-event trigger. Remember to add anything you put on GTM into your Tag plan so that you can reference it later!

Now that we have created the button click trigger, we can reuse it to track this event in other tools. For example, let’s fire an event to Facebook Ads so we can do some remarketing and build a custom audience. Add this to your Tag plan, too.

Google Sheet Tag Plan Events tab with Button Click descriptions filled in

Facebook Ads conveniently has code for an Add to Cart event already. In the Facebook Events Manager, click Set Up > Manually Install Pixel Code Yourself > Continue and scroll down through the events until you find one called Add to Cart.

Open up the event details. Just like with our Purchase event earlier, we’ll turn off Send Event Parameters and we’ll copy this event script.

Facebook Events Manager Install Pixel Code popup  with Add to Cart event tracking script highlighted

Now we just need to create a new Tag in GTM. Since this is for Facebook Ads, we’ll make it a Custom HTML event  and paste our code into the HTML field.

GTM Facebook Ads Tag configuration with name, Tag Type, and HTML highlighted

If you don’t have another Tag with the Facebook Pixel initiation code and a higher firing priority, revisit the conversion tracking section to fix this. Otherwise, choose your Add to Cart trigger and click Save to finish.

Refresh your container, then enter your product page in Preview & Debug Mode. Test your “Add to Cart” button using Ctrl+click or ⌘+click. You should see in the GTM preview console and your Facebook Pixel Helper that our Add To Cart event has fired.

Demo website with Facebook Ads Add to Cart event Tag fired in GTM Preview console and Facebook Pixel Helper

We can also check our Tag using the Test Events tab in the Facebook Events Manager. Activate your Tag again, and you should see that Facebook Ads has received your Add to Cart event along with the Page URL.

Facebook Events Manager Test Events showing Add to Cart event tracked

Don’t forget that in order to make these updates live to all your users, you will need to submit a new Version and deploy it on your website.

GTM Versions with Version 8 summary

All right, so there you have it. This is how you can track button clicks with the help of Google Tag Manager. Using this tutorial as a starting point, you should also be able to track other interactions like form submission, scrolls, or element visibility.

Summary

That was a lot! I hope that this Google Tag Manager beginner guide was helpful to you and that you feel more confident using GTM for your own website.

Pat yourself on the back for everything that you have learned so far, but remember that your Google Tag Manager journey has only just begun!

With sufficient knowledge and practice, Google Tag Manager can dramatically augment your marketing power and strengthen your business.

Where to Learn More – 3 Ways!

1. Free GTM for Beginners Email Course

If you enjoyed this written guide, we recommend taking the full FREE Google Tag Manager for Beginners Video Course.

This free course goes into detail and shows you with over-the-shoulder tutorial videos, delivered in seven emails over seven days, with a total of just over two hours of video content.

Just one week of emails could give you the competitive edge in GTM that you need in order to take your business to the next level. Sign up today to learn the data-driven way of digital marketing!

2. Google Tag Manager Beyond the Basics Course

A slightly more advanced course that will take you to the next step in your GTM journey: Google Tag Manager Beyond the Basics.

This course has additional exercises and a demo website so that you challenge yourself by testing some implementation with GTM.

This is a perfect next step for anyone who enjoyed this guide, so check it out if you want to apply what you’ve learned and pick up some new tricks.

3. MeasureMasters Membership

Ready to really become an expert at all things data and measurement?

Join our MeasureMasters program, where we teach marketers (like you) about measuring, analyzing, and presenting your data correctly.

MeasureMasters is home to all our premium courses, live trainings, coaching, and tools that make your work easier. Check it out below!

JOIN US!

Master Data & Analytics with Measuremasters

Exclusive Courses & Workshops | Ongoing Troubleshooting | Support Resources, Tools & much more
guest
0 Comments
Inline Feedbacks
View all comments