SEO Moz is one of the best SEO themed blogs out there. We’re going to share some of our favorite blogs of theirs in the coming month or so because they have such great info it needs to be shared with our readers as well. This post indexing came on May 24th written by Dana DiTomaso and the rest of this great post can be found here. Enjoy reading!
Agencies, are you set up for ongoing Google Tag Manager success? GTM isn’t the easiest tool in the world to work with, but if you know how to use it, it can make your life much easier. Make your future self happier and more productive by setting up your GTM containers the right way today. Dana DiTomaso shares more tips and hints in this edition of Whiteboard Friday.
Click on the whiteboard image above to open a high resolution version in a new tab!
Hi, Moz fans. My name is Dana DiTomaso. I am President and partner at Kick Point, which is a digital marketing agency based in Edmonton, Alberta. Today I’m going to be talking to you about Google Tag Manager and what your default container in Google Tag Manager should contain. I think if you’re in SEO, there are certainly a lot of things Google Tag Manager can do for you.
But if you’ve kind of said to yourself, “You know, Google Tag Manager is not the easiest thing to work with,” which is fair, it is not, and it used to be a lot worse, but the newer versions are pretty good, then you might have been a little intimidated by going in there and doing stuff. But I really recommend that you include these things by default because later you is going to be really happy that current you put this stuff in. So I’m going to go through what’s in Kick Point’s default Google Tag Manager container, and then hopefully you can take some of this and apply it to your own stuff.
Agencies, if you are watching, you are going to want to create a default container and use it again and again, trust me.
So we’re going to start with how this stuff is laid out. So what we have are tags and then triggers. The way that this works is the tag is sort of the thing that’s going to happen when a trigger occurs.
So tags that we have in our default container are the conversion linker, which is used to help conversions with Safari.
If you don’t know a lot about this, I recommend looking up some of the restrictions with Safari tracking and ITP. I think they’re at 2.2 at the time I’m recording this. So I recommend checking that out. But this conversion linker will help you get around that. It’s a default tag in Tag Manager, so you just add the conversion linker. There’s a nice article on Google about what it does and how it all works.
Then we need to track a number of events. You can certainly track these things as custom dimensions or custom metrics if that floats your boat. I mean that’s up to you. If you are familiar with using custom dimensions and custom metrics, then I assume you probably know how to do this. But if you’re just getting started with Tag Manager, just start with events and then you can roll your way up to being an expert after a while.
So under events, we always track external links, so anything that points out to a domain that isn’t yours.
The way that we track this is we’re looking at every single link that’s clicked and if it does not contain our client’s domain name, then we record it as an external link, and that’s an event that we record. Now remember, and I’ve seen accidents with this where someone doesn’t put in your client’s domain and then it tracks every single click to a different page on your client’s website as an external link. That’s bad.
When you transfer from HTTP to HTTPS, if you don’t update Google Tag Manager, it will start recording links incorrectly. Also bad. But what this is really useful for are things like when you link out to other websites, as you should when you’re writing articles, telling people to find out more information. Or you can track clicks out to your different social properties and see if people are actually clicking on that Facebook icon that you stuck in the header of your website.
The next thing to track are PDF downloads.
Now there’s a limitation to this, of course, in that if people google something and your PDF comes out and then they click on it directly from Google, of course that’s not going to show up in your Analytics. That can show up in Search Console, but you’re not going to get it in Analytics. So just keep that in mind. This is if someone clicks to your PDF from a specific page on your website. Again, you’re decorating the link to say if this link contains a PDF, then I want to have this.
Then we also track scroll tracking. Now scroll tracking is when people scroll down the site, you can track and fire an event at say 25%, 50%, 75%, and 100% of the way down the page. Now the thing is with this is that your mileage is going to vary. You will probably pick different percentages. By default, in all of our containers we put 25%, 50%, 75%, and 100%. Based on the client, we might change this.
An advanced, sort of level up tactic would be to pick specific elements and then when they enter the viewport, then you can fire an event. So let’s say, for example, you have a really important call to action and because different devices are different sizes, it’s going to be a different percentage of the way down the page when it shows up, but you want to see if people got to that main CTA. Then you would want to add an event that would show whether or not that CTA was shown in the viewport.
If you google Google Tag Manager and tracking things in the viewport, there are some great articlesout there on how to do it. It’s not that difficult to set up.
Then also form submits. Of course, you’re going to want to customize this. But by default put form submits in your container, because I guarantee that when someone is making your container let’s say for a brand-new website, they will forget about tracking form submits unless you put it in your default container and they look at it and say, “Oh, right, I have to edit that.” So always put form submits in there.