Le cours ultime de Google Tag Manager 2025 : du débutant au confirmé

1. Welcome Video: Hi, guys. Welcome to my course, the Google Tag Manager Master class. All features and tools. My name is Tanoi Komadas. Just to give you a background about myself, I am a ex Google employee with 16 years of experience into PPC advertising. I've been teaching PPC ads for more than ten years now, and I teach to a lot of young professionals, PBC experts, and entrepreneurs who want to enhance their skills in this particular field. I wanted to take this opportunity to let you know what you will get to learn in this course. So we are going to start off with understanding the Google Tag Manager fundamentals, the installation, and browser setup. We'll also get to see the interface of Google Tag Manager and some best practices. Then we will see how to set up essential tags and publish them, and then we will get into understanding and improving the expand the tracking data. I will show you some advanced tracking concepts, video tracking techniques, and some advanced techniques as well, related to user ID, lookup tables, Fonten groups. I hope by the end of this course, you understand how this Google tach manager works, and you can use this very effectively for yourself and for your clients. So thank you once again, guys for enrolling into this course, and I look forward to seeing you in the class. 2. What is Google Tag Manager and Why Do You Need it: Hi, guys. Welcome to this session. In this session, we'll talk about what is a Google Tag Manager and why do we need it. Before we get into this, we just need to understand first what is a tag. A tag is a piece of code or a snippet of code. Mostly, this is going to be a Java script or a Jiff images, which are given by various third party websites. Third party websites, which will give you this tag, which we need to put on our websites specifically in order to collect data. If we are running, let's say ads or through different ads platforms like Google, Meta, Microsoft, linked in, or let's say we are setting up Google Analytics on our website, all these platforms will provide us with a tag. And now we need to place these tags on our website so that this stack can help to collect data, and that can be used for analyzing, user experience, and tracking purposes. So there can be various kinds of tags which we will have to set up on our website. So let's have a look at this. So there can be a Google tag which we use for analytics, for Google ads, tracking, for conversions. There can also be a Facebook pixel setup or a pixel code which is there, which needs to be pasted, which is used for tracking data for running Facebook ads. And similarly, there can be a Microsoft advertising tag as well, which we might put up when we're running Microsoft ads. So let's have a look at some live examples of how this will look like on a specific website. So let's say we're looking at New York Times as the newspaper. So different websites, we have the tags implemented to collect user data for various reasons. So if we just go ahead and do a view page source on such kind of a website, we can identify these codes by searching for, let's say we're looking for. So we can see here on this page, we have this particular Google Tag Manager, which is highlighted over here. So this is the code which is coming up out here. In the same manner, if you look at any technology website, let's say we're looking at tech crunch over here on this website. Here as well, if you do a view page source, we can go to the page source and we can search for any search tag as well. So here as well, you can see there is a Google Tag Manager code showing up right here. Like this, various websites will have the code set up for tracking purposes. Another example can be, let's say we are looking at a sports website, and here as well if we do a view page source, we will get to see the code in this particular manner. We can see that there are a lot of websites which will have these codes implemented primarily for the purpose of tracking data of users, which is helpful to do a lot of analysis and for running ads as well. So now, just to understand what is a Google Tag manager? This is a tool created by Google or a platform which helps to manage multiple tags on a website in a much more efficient manner. If I have a website where there are multiple tags are implemented, this tag manager can help us to manage them in a much more seamless and easier way. So what Google Tag Manager helps you with is that it removes the need to put individual codes on the website. Rather than that, what we put on the website is just a Google Tag Manager container pote. And now what we do is we have all the individual tags on our Google Tag Manager interface. So whatever changes or management we have to do, we do it on the Google Tank Manager interface, and that reflects on the website's page through the Google Tag Manager container. So this way, it becomes far more easier to deal with multiple portes for our websites. I hope this makes sense. You understand now what is this tool and how this basically works in efficiently managing multiple tags for our websites. Thank you so much guys for listening into this session, and I will see you in the next weeding. 3. Useful Chrome Plugins For Working With Google Tag Manager: Hi, guys. Welcome to this session. In this session, we wanted to see different chrome plugins, which we can use while working on Google Tag Manager. There are different types of chrome extensions which we can use for tracking and reporting purposes. Let's have a look at this. The first one, I've made a document which I will share with you in the resources section of the course, so you can easily access it from the So these are all the different types of me plug in skys. So the first one is tack assistant, Facebook pixel helper, Twitter, Pixel helper, and so on and so forth. These are all which we can easily use for different tracking and reporting purposes. So let's have a look at this. So the first one, is going to be the Google Tag assistant companion. So this is a prom extension, which basically helps the major league the Google Tag Manager, which we are trying to learn over here in this course, is what you can access from this particular prom extension. So from here, this tag assistant really helps in managing multiple ports on the website. You can also see which ports are running over here, and how you can debug as well. All those things becomes easily done through Google platform. This is one of the most extensively used tracking tool. The other one is going to be the meta Pixel helper. This is a tool which is used in case of meta ads. If you're putting up planning to run meta ads and you want to track the code, the pixel which we have set up on on the website for tracking conversions through meta ads. Then we can use this meta Pixel helper, which also does the same thing, wherein it tells us clearly whether the pixel has been placed properly on the page on the website or not, or it is not loading. We get clear information with respect to meta ad stra. The third one similarly can be used as Twitter Pixel helper, which does the same job when we're running Twitter ads, and if we want to track conversions coming through Twitter ads, then this particular chrome extension can be of great use. Similarly, we also have Microsoft ads Prom extension, which is a UIT tag helper. This does the same thing, wherein when we're running Microsoft ads, and we want to track conversions coming from it, we can place the code and then this particular prom extension can help us know whether the tag is working, firing properly or not. Is it tracking the data or not? That kind of information it will provide. So this is going to be from Microsoft advertising. Now, apart from this, there's other chrome extension, which is it like a tag explorer. Now, tag explorer is basically this extension helps to see what all tags are there on the website. So like this, I can see what all different types of tags are there on my website. Okay? If I want to pause any particular tag, I can do it from here by removing the check button from here. Okay. So this way, I can control and manage and see multiple tags which are there on the website, and I can work on them. So that's your tag explorer Chrome extension. Another one which we can use here is analytics debugger. Analytics debugger extension is used when we have set up a Google Analytics code, and we want to debug it, see if there are any errors with it. So we can see in this specific particular chrome extension, where which is going to give us all that information. And then we can make changes to it. Maybe we can pause the tag or edit the tag. All those things will be possible from this particular chrome extension. Majorly focusing on debugging Google Analytics tag. Other than that, we also have a GTM copy paste me extension. This is useful when we want to copy the GTM code from one particular account to another. If you want to do so. When let's say you you're doing it for multiple clients, you're setting up GTM for multiple clients, and you need to use the same code with different clients, then this particular rom extension can be really useful where you can simply copy the tag from one particular account and then move it to the other account. That's your GTM copy paste prom extension. And then the last one is going to be Ad Swerv Prom extension, which is used primarily to again, set up the Google GTM code on any website. We can do it from this. We can also analyze the data layers which are created in the GTM account. All those things, which you can see out here through this particular prom extension also. So these are all the prom plug ins or extensions which we can make use of. In this video in this ports, we are going to see some of them, how we can implement them, and eventually, you should be able to use them effectively for your business and for your clients. I hope this makes sense. I hope you understand all these prom extensions or plug ins for GTM and how we can make use of them. Thank you so much guys for listening into this session, and I will see you in the next video. 4. Create a Google Tag Manager Account: Hi, guys. Welcome to this session. In this session, we'll see how we can open a Google Tag Manager account. So for doing this, we're going to search for Google Tag Manager on Google, and we will see the first website out here, which you can click on, and this will bring us to the website out here. So it will ask you to log in with your Google account, so you provide your e mail ID and password, and you will reach on this particular page. So from here, we can go ahead and create a new account for our Google Tag Manager. So where we can provide certain details. So the first thing which you will have to provide out here, is going to be the name of the account. So whatever is your company's name or your client's name you can provide out here. In this manner, I can provide the name, and then we can choose the country as well. Once you do that, then we have to do the container setup. Container is basically a storage space where we're going to store all the different tags, which we will be pasting on the website. So this we also need to define out here. So we can give a container name. Now, that can be our website's URL, which we can provide here. And we are to do this for the targeted platforms. We are doing it, let's say for web pages, IOS, so all these options will be open for us. So we will be doing a tag setup for all these platforms by default. So you can provide your website URL in this particular manner. This is the website for which we are setting up the tag, and then we can select website majorly for which we want to do this, which is on desktop and mobile web pages, and then we can create. This is the terms and conditions which we need to agree to and we say accept to this, and then we can move forward from here base. Once you do this, now the account is getting created, which will then generate the code. You can see now, this is the code which needs to be past at the back end of our website. If in case, once you create the account, this pop up does not arise. Then on the home page of Google Tag Manager, you can just go to your GTM code particular label over here. If you click on it, that will bring you back to the page, and you can just copy from here, follow the instructions given out here and paste it at the back end of every page of your website. I hope it makes sense you understand now the complete process, the simple way of opening an account with Google Tag Manager. In the next video, we will see how we can paste this code at the back end of our website and activate the particular GTM code. Thank you so much, guys for listening in to this session, and I will see you in the next video. 5. The Overview of 5 Google Tag Manager Installation Methods: Hi, guys. Welcome to this session. In this session, we'll see the five different ways of installing the Google Tag Manager on different platforms. So the first one can be manual installation. So we'll see this in the coming videos, how we can install the GTM code which we got in the previous video manually on our website. That's one. The second day is going to be WordPress, so on a WordPress website, how we can do the same job if our website or our client's website is built on WordPress. Then we are going to see how the GTM code can be implemented on a shoppe file store website. Okay, how on a Shoppe file store, this can be done very easily. And then similarly, we will see if a website is built out on square space, how we can implement the GTM code on that. And then the last one is going to be the tag manager injector, which we were discussing earlier as well, which is at Swerve through which we can use this tool to also get the TM code implemented on any website. So let's have a look at these guys. In the coming videos, we'll see how these can be implemented on different websites through different platforms. Thank you so much, guys for listening into this, and I will see you in the next VD. 6. Setup Google Tag Manager on Wix: Hi, guys. Welcome to this session. In this session, we'll see how we can set up the Google Tat Manager on a ICS website, a website, which is built out on ICS. So let's have a look at this. So we saw in the previous video that once we get the particular GTM setup done, when we open the account with Google Tag Manager, we get a particular code in this particular manner, where we can install this code on every page of the website, right? From here, what we require is only the GTM code ID, which is this one, which we can copy from here, and now we can paste it at the back end of our ICs website. So let's have a look at this. This is a ICS website, which I have, on which we're going to paste this code. So currently, if you see on this particular website, This website does not have any code right now. This chrome extension helps us to check and test whether any website has any code on it or not. Right now, what we see is that this does not have any code as such. What we're going to do is we're going to set up the GTM code on this website at the back end, for which we're going to go to the Is dashboard. This is the dashboard where we have to come, and here we can specifically go to the settings page. Where we can go to marketing integrations, where we can integrate Google Tag Manager with the website. So here you can see Google Tag Manager option coming up, so you can connect over here, and you can add the Google Tag Manager ID. The one which we copied in the beginning is what we are pasting out here, and we can save it. So now you can see it says Google Tag Manager has been connected to the site, so let's have a look at this. So when we go back to our website and we refresh the page once more. So now we should be seeing the Google Tag Manager, which shows over here with a Green Smiley, the same code is out here, which means that this has been implemented successfully on the website. So this is how Google Tag Manager code gets set up on a Vicks website dise. I hope this makes sense. You understand the complete process, how to do this for a Weeks website specifically. Thank you so much, guys for listening into this session, and I will see you in the next video. 7. Setup Google Tag Manager on Wordpress: Hi, guys. Welcome to this session. In this video, we'll see how we can set up the Google Tag Manager for a WordPress website. For this, we are going to go into, again, starting from the beginning, which is once we create the Google Tag Manager account, it will generate the code for us in this manner. So we're going to take the code, the ID, the GTM ID from here, and we copy this. And now we will go to our website again. Let's say this is the website which we have and the WordPress account which we've created. In the WordPress, the easiest way to set up the GTM code is by adding a plug in. So you can go to plug ins where we can search for, let's say Google Tag Manager. And it will give you a lot of options, which we can see out here. However, out of these, the best one and the simplest one to use would be a Google Tag Manager for WordPress by Thomas Geiger. If you go to this one specifically, it will ask you to fill up the ID. You can fill up the ID over there and just save it. Once you save it, it will activate on the website, and your Google Tag Manager code will be installed on the website. This is how simple it is going to be to set up the GTM code on a WordPress website. We just need to install the right plug in, which is this one, GTM for WordPress, by Thomas Geiger. In that, it will ask you to paste the ID, the GTM ID. You just paste it and you can save it. In this manner, base, we can set up our Google Tag Manager code on a WordPress website for ourselves or for our clients. I hope this makes sense. You understand this process. Thank you so much, guys for listening into this session, and I will see you in the next video. T. 8. Setup Google Tag Manager on Shopify: Hi, guys. Welcome to this session. In this session, we'll see how we can set up the Google Tag Manager on a Shope Pi website. So let's have a look at this. To start off with, again, we'll go to the Google Tag Manager account, which we have created and we'll get the code over here. We'll have to paste both the codes on the Shope Pi website. So let's begin with the first one. This is what we are going to copy. And now we can go to our Shopify store. Let's say this is the back end of the Shop fi store. We'll have to go to the online store where we go to themes. The themes will be the website theme, and now here, we're going to go to the current theme which is being used and we'll edit the code. In edit the code, we're going to specifically look at the liquid section, and right here after the Meta tag, we are going to paste the code. You can see the Google Tag Manager code has been pasted out here, and we can save this. This is done. Now we'll go back again, and now we need to install the second code, which is this one. This needs to go after the body section of the code. Again, we're going to search for body section for which you can do a control F and you can look for body class. And now you can see right here after this, we are going to paste the second part. Here we have pasted the second part of the Google Tag Manager code, and we can save this. This is the simple way by which we can paste both the codes on our Shoppe fi website at the back end. And now this will reflect on our website, and we will be able to track our information, our conversions through Google Tag Manager on a Shoppe file store. I hope this makes sense. You understand now how we are doing this for a Shoppe fi store as well. Thank you so much, guys for listening into this session, and I will see you in the next video. 9. Setup Google Tag Manager on Squarespace: Hi, guys. Welcome to this session. In this session, we'll see how we can set up a Google Tag Manager on a square space website. So let's have a look at this. We'll start the process first by going to our Google Tag Manager account, and we can get the code from here. So we'll have to paste both the codes on the Squarespace website. So we'll going to copy the first code. And now we can go to our square space website. Let's say this is the website. We'll have to past it as a custom code. What's happening with square space is you don't have a specific integration with Google Tag Manager through square space. So we will have to add this like a custom code. For doing that, we can come to the website editor page and we can go to pages, where we can go to website tools. In website tools, we can go to code injection, where we are going to add these codes. So the first code which we have, we can put it in the header section in this particular manner. We can see the Google Tag Manager code has been pasted here. And then the second code can go in the footer section. So we can put that in the footer as well. This one specifically, we can copy, and now put it in the footer section. This way, we can add both the codes to our square space website, and Google Tag Manager will get installed here, and it will start tracking all the details for us. I hope this makes sense. You understand this now, how we can add a GTM code for a square space website. Thank you so much, guys for listening into this, and I will see you in the next video. 10. Inject Google Tag Manager Container to any Website: Hi, guys. Welcome to this session. In this session, we'll see how we can make use of a particular Cm extension to install Google Tag Manager to any website. So what we're going to use is going to be the AdWord Prom extension, which we had discussed in the previous videos as well. So let's have a look at this. So as we saw earlier also, the first thing is we log into our Google Tag Manager account, and we can come to the particular code part where we can copy the tag ID. And now, what we can do is we can install this Azer data layer inspect plus chrome extension on our chrome browser. As you can see, this is now installed over here. What we're going to do is we're going to install the Google Tag Manager code on our website, the same website, wherein we don't have any code at this moment. What we're going to do is, we're going to go to that Chrome extension once we have installed it, and we can go to advanced options where we can go to add functionality, where we're going to insert the GTM container. This is where you can paste it. Plus, you'll have to provide the website URL in the format in this manner. So now we've given the website as well and we've given the GTM container, and we can save this. Once you save it and the page reloads. So now we can see the Google Tag Manager has been installed on the website very easily. So this is another very simple way guys by which a Google Tag Manager can be set up on any website with the help of this simple extension. I hope this makes sense. You understand the complete process, how to do this. Thank you so much, guys for listening into this session, and I will see you in the next video. S. 11. GTM Interface Overview: Hi, guys. Welcome to this session. In this session, we'll see the Google Tag Manager interface and we'll understand how to use it. So once you log into your Google Tag Manager account, this is how the interface will look like. On the top left, you can see the logo and the name coming up over here, Tag Manager. And this is where your accounts website URL will show up. And now you can see there are different tabs over here. The first one is workspace. Workspace is a place where you're going to build out the container, where you're going to add the new tags which you want to place on your website. Workplace is going to be the section, where you are building out the tags, managing the tags, all that happens. Now, Google also gives you by default three workplaces to work with. So you can use the other two as well. You can have three different workspace, which you can use simultaneously. Now, this can also be helpful when you're working with a team, so you can work in your own workspace, which you have, and you have other people as well working on different workspaces. That way, a lot of collaboration can happen. This is the overview page guys where we can see all the information. So you will get to see the new tag which we can set up over here. You can give a description of this tag, which tag are you planning to install? And in the workspace changes, you will see once we create the tag, they will get listed down out here. So let's look at the second option, which is tags. Tags are going to be pieces of code or snippet of code, which we pasted on our websites. Now, this can be a Google tag, it can be a pixel meta pixel, or it can be a mi Microsoft tag, different types of Google Analytics tags, which we are pasting on the website for purely for tracking purposes, performance related tracking and reporting purposes, we do that. So you will be creating those out here in this particular section. The second piece is going to be triggers. So triggers is, when exactly do we want to fire the tag? Okay? So this is happening for an example, let's say, I'm creating a tag for an e commerce brand like Amazon. So what we want is that the tag will be pasted on the thank you page of the website, and it will trigger only when a user lands on the thank you page. And that is what will be considered as a conversion or a sale. So triggers is where you're going to define when the tags will be fired. Here you can add the thank you page to it in case if you're doing it for conversions, and it will define it to the system that it needs to fire the tag only when a user lands on the thank you page. So that's going to be the trigger section for us. The other option is variables. In variables, you can define different types of variables, which are Google specific, which are built in variables, and then there can be a user defined variables, which we can define. These variables can help us to define different types of sections of the website. Here, also, they work like a container where we can define, let's say a page URL variable which we are defining, which is for a specific website landing page. Different variables can be built out out here in this section, which will then be used in the tags, and we will be able to track specific information. The another option which we get here is folders. Folders are used for managing tags, triggers, and variables together. In separate folders, you can put them in so that you can organize them in a much better manner. This way, it becomes easier for us to manage multiple tags for a particular brand. And then comes templates. Templates are specifically community built tags and variables, and you can access this community as well, and you can use certain tags built out by these communities. Okay? So you can find a lot of pre built tags and variables here if you search the gallery, and you can use them for various reasons. As you can see, this is for the tags template, and you will have a gallery for the variables as well, which has been created, and you can use them for tracking purposes. Other than this, another important section of the interface is going to be preview and submit. Submit is where you're going to once you create the tag, you need to publish it so that it gets activated on the website. This is where we publish and we submit it. Once it is submitted, then the tag starts working on the website. We can give some information about the tag as well, the version of it as well. A that can be set up out here. The other information gather segment is pre view. Preview is where I can test the tag. I can just do a test of the tag wherein alive. It will take us to the website and it will show us whether the tag is getting fired or not. We can perform certain actions. This is like a testing of the tag which we're doing so that we can see the clear functionality of it and whether it is working properly or not. It's a very important segment. Most of the time, we're going to spend in these where you're testing our different tags to check whether it's working properly or not. In addition to this, we also have versions over here. In versions, you can see which version of the tag is being working currently on the website. Whether it's firing properly or not. So here you will see complete information given by Google, whether it is working or not. And how many tags triggers did it fire so that count will show up out. The last one is Admin, where we can see the account settings details of the Google Tag Manager, which you can see here. You can add other users from the user management segment. You can do the same thing with the container as well, where you have multiple options given out here. You can add different users who can access the container. If in case, you are not able to find the code which needs to be go on the website. You can come to this option and you can to install Google Tag Manager, and here again, you will get the options to take it from here. So these are all account settings, which we can get over here. You can also export or import your containers. If you want to move your container to a different account for those purposes, you can do this. This is how the tag manager interface is going to look like for everyone. I hope this makes sense. You understand now all the features of this. If you want to also get the code quickly, then you can just click on the GTM ID showing on the top right corner in this manner, and the code will pop out in the middle of the screen. So these are all the features guys of the Google Tag Manager Interface. I hope this makes sense. Thank you so much, guys for being with me in this session, and I will see you in the next video. 12. Best Practices & Considerations: Hi, guys. Welcome to this session. In this session, we'll see and talk about some of the Google Tag Manager best practices and considerations. So if you look at the Google Tag Manager, there are a lot of different, you can say limitations or considerations you should have while using this tool. The first being the JavaScript based tool, it is. So this particular tool, it's limited to whatever you do within the browser window, okay? So the GTM tool can only help you within the browser window, what we are working on it. If users have JavaScript disabled, then Google Tag Manager can't help and Ds cannot help with its full functionality. So that is one kind of a limitation which you have with the tool out here. The other aspect of it is the exposing data. So this being a tool, it is more like a constraint. So wherein, the tool itself will not have all your website's data itself. You will have to provide it. Okay? You will have to provide it maybe through a plug in which you add to your word press and through which you get a data, which can be integrated with Google Tag Manager. So that is how the Google Tag Manager will get the data. It will not get the data on itself. The other aspect of using GTM is related to speed. So as you can see in a Google Tag Manager, we are handling multiple tags, which goes on the page. There are triggers which we are using variables which we define. This can certainly slow down the speed of the website. It consumes a lot of the CPU, and that can have a impact on the user experience. So what we can try doing is that we can organize our tags in a much better manner where we can avoid certain tags which are not priority. Maybe we can fire them later as well. That can certainly help in fixing speed related issues. And then the last point is that at the end of the day, this is a tool which we are going to use out here. It is more dependent on us that how convenient, how compatible are we with JavaScript or TML pod. The more effective and we understand Java scrap and estimL poding, we will be able to use the GTM tool in a much more effective manner and an efficient manner. These are some of the limitations and considerations. The other aspect is the best practices. One of the best things which you can do while managing multiple tags with Google Tag Manager is removes any unused elements. If you are having a multiple tags which are being created, which are staying unused. The good practice would be that you just remove them and that can help in reducing it can increase the speed of the website. Any kind of data which you're tracking, but not using it often, then that can also be removed, maybe. That way you are increasing the speed of the website. The other aspect is version control. So as you saw that we will be creating different versions when we are building out multiple tags, triggers, and variables. So when you're publishing the version, a good idea would be that you give a clear description of this version. What this version basically do, what tags triggers it has in it. The reason is, then in the future, when you have multiple versions, you can easily revert to the one which you want to. Another aspect of it is that when you're creating these versions. We don't want it to be a case that there are a lot of tags which you create, then triggers, which you created, and then you create variables as well. After doing all that, you create the first version. What we would prefer is a systematic way of creating multiple versions. You can break down the whole process into small small steps, and after completing one particular step, a version can be created. That way, again, reverting becomes much more easier. The other aspect is user management. So when you're working with multiple clients, possibly, you will have multiple team members who will be working on those different accounts or containers. So it's a good idea that you create, give them individual access to their specific containers, to the accounts, rather than sharing your access or your logging credentials with your team members, giving them individual access is a better way of managing work. And the last is, building a plan. So before setting up any particular tag, triggers or variables for your client or for yourself, we need to make a plan around what will be the tags. What will be the triggers, which you will be defining. What will be the variables which you want? What should these tags do? Okay? What is the strategy behind why you are setting up the tags? What will be the data, which will come out of it? So we need to list this down on a piece of paper so that we have the complete picture of what is the purpose of building out this particular tag or this particular triggers for a client or for ourselves. Once you have that in place, then working on the live account would be a better way of dealing with it. I hope this makes sense. You understand now, what can be some of the best practices or habits which you can build around using Google Tag Manager in a much more efficient manner. Thank you so much, guys for listening into this session, and I will see you in the next video. 13. Naming Conventions: Hi guys. Welcome to this session. In this session, we'll discuss about the naming conventions, how we can name our Google Tag Manager account, which we are managing. There are different ways of doing it. So the first is the account name. So the account name, usually, what we would like to keep it as the company name. So if it is your own business for which you have set up your Google Tag Manager, so the account name can be your company name, or if it is for your clients, then it can be the client's company name. Okay, so that way, it will be much more better organized. If you're handling multiple clients, then a good idea would be that you create one account for every client and you can manage them separately. And the name can be given. The account name can be the client's name itself, which can be used. So that way, it is a much more better way to manage it with multiple accounts. The second is container. In the container, what we are saying is that as simple as we can keep the container name can be the website or the app name for which we are doing this. Again, depending on if it is your own business, then we're putting our own website or app name, or if it is for clients, then we put their website or app name as the container name. The third is going to be tags. Now when you start building out the tags in the container, the tag can be written in a specific format. So what I usually use it as is. The first part of it is going to be the platform and the platform feature, which we can define, what is the platform and which feature are we creating it for? And on which page it is going to get implemented. For an example, as you can see out here, Facebook pixel, the platform is Facebook, the feature I'm using is pixel setup which I'm doing, and it is going to go on the At cart page. This way, the naming of the tag remains very clear what is the purpose of that particular tag. Same way, let's say it's a Google Analytics account platform, and we're creating an event over there and which is going to go on the subscribe page, or let's say a Google Analytics page. This way, the naming of the tag can be very clear to understand. There comes triggers. When you're coming to triggers specifically, here, what I prefer doing is a case wherein we're looking at what is the particular trigger, which is going to happen and on which page. When it is going to happen. So in this case, the first part is going to be the action, page view, which means people visit the page, they view the page, and this is happening on the T thank you page. So that is when the trigger will go. The tag will fire. So this way it is very clear that what this trigger is meant to do. Similarly, let's say I create a trigger for timer, which needs to go off after 30 seconds, so it will fire after 30 seconds. This way I can build out another trigger and define it in this manner. The first part is going to be the particular action which is being going to be taken, and the second part can be when it is going to happen. Okay. Same way Link click Link click can be a trigger, which is people clicking on a link and when it is going to happen is, when a file is getting downloaded. This way, we can define our triggers as well. Other than this, when we come to variables, now variables, I prefer writing it all in lower case because of the fact that I can differentiate it from triggers and tags as well. So it becomes very clear to me that I'm looking at a particular variable which we have defined. Here as well, we can keep it very simple, where in the first part is, what is the type of variable which we are defining? And then the details of it. So for example, I'm creating a variable called Div, which has the user ID in it. I can create a variable for URL, which has query parameters in it, which has an affiliate ID in it, or I can create a cookie variable, which has referral in it. So this way, I can define different variables, which clearly signifies their purpose. And then the last one is folders. As we spoke in the previous videos as well, folders is where you can keep all your tags, figures, and variables together in different folders so that you can manage them better. You can create a folder by tag type. Let's say, you can have a separate folder for all the tags. Maybe a folder for all the Google tags. Maybe a folder, which is for the meta tags, across all our clients. So that we can do. You can create folders by tag type. You can create folders by functional groups as well. Functional groups in the sense that what are their functions? Okay? So triggers all the triggers can be here. So though they can be clapped together in a single folder. That way, also, you can do it. Or else, you can do it by team members. If you have multiple team members who are managing different types of tags for different clients, then you can have folders by the team member's name. So you will know that what all tags one particular person is managing. So these are different naming conventions which I believe we can use to organize your work in a much more efficient manner. These are my ways of finding a simpler way to do it for myself. You can also do in a similar manner or you can find out the way which you find it comfortable doing. I hope this makes sense. You understand now how naming conventions can be used to make our work easier. Thank you so much, guys for listening into this, and I will see you in the next video. 14. Trigger Types in Google Tag Manager: T. Hi, guys. Welcome to this session. In this session, we'll discuss about triggers, understanding the different types of triggers which we can make use of in the Google Tag Manager. So let's have a look at dis guys. So triggers are basically going to be conditions which are used to fire various tags. So any kind of activity which is happening on the website creates various events. So we store these events in these triggers, and this is how you can use these triggers to fire appropriate tags. So this will fire when a particular tag will be fired when these triggers or conditions are met. So let's have a look at disguise. So once we are inside the Google Tag Manager account, we can go to triggers on the left panel, and this is where you will start creating different types of triggers. So you can go to the new section where you will see various types of triggers available if you click on this trigger configuration. So now you can see these are all the options which Google provides you with. There are various types of triggers under page view. Then there are clicks based triggers, user engagement, and there are other triggers as well. Like for example, a page view trigger is the one when a particular users this gets triggered when users view a specific page. Or Links related triggers, links is a kind of a trigger where people are clicking on certain links on your website. All elements is going to be a case where people are going ahead and looking at different types of elements on the page. Maybe they're opening a particular page. They're flicking on a radio button or a drop down. So various types of elements can be there on the website, which they are doing, and which we would like to track as well. So this gets triggered in those scenarios. Similarly, in user engagement, we have something like scroll depth, which is triggered when users are scrolling through your website. So this trigger basically tracks how much percentage of the page did the scroll through vertically or horizontally. Similarly, you have form submission, which is a case when people fill up the form, that is when this particular one gets triggered. You also have other options over here, like custom event. Custom event is when we want to add any custom code on the website and trigger that, then we are making use of this. And then there's a timer trigger as well, which is used when this gets triggered when the user has spent a significant amount of time on the website, like an elapse time. So we want to track how much time users are spending on the website. So for those reasons, this particular one is triggered. So these are the different types of triggers, which you will also have to create along with your tags. So the tag will consist of the triggers as well. Okay? So when the tags will get fired when these triggers or conditions are met. I hope this makes sense. You understand how triggers work and the different types of triggers available on the platform. In the coming videos, we will see different types of use cases of them as well. Thank you so much, guys for listening into this, and I will see you in the next video. 15. Built in Variables: Hi, guys. Welcome to this session. In this session, we'll talk about variables. So variables are another segment of the Google Tag Manager, which work like placeholders for values that are populated when code is run on the website. For example, a tag manager variable named page URL will return the current page URL. Okay. Variables are used both in tags and in triggers. So in triggers, specifically, a variable is used to define filters that specify when a particular tag should fire. So we can have, for example, we can fire a trigger when the URL variable contains some kind of a STML characters. If similarly in tags, variables are used to capture dynamic values. This can be a transaction value. It can be a product ID number or a conversion tracking tag. So that is how variables are used out here. There are two types of variables which we can define here in Google Tag Manager. One is your built in variables, and the other one is your custom variables, which we can create or user defined variables. So let's have a look at built in variables. Built in variables are pre created or non customizable variables which are available here for special categories. These are predefined and created by Google itself, which you can select from. Now, these enable built in variables are will be made available throughout the tag manager whereever variable selection menus are here. So this in new containers have no user defined variables at the start, and some built in variables will be pre enabled. So you will get these built in built in variables already available when you are starting off new width variable creations. So let's have a look at this. Once you are inside the Google Tag Manager, we can go to the variable section here, and this is where you can define it. So you can see the first section is built in variables, and the second section is user defined variables. Now there are various kinds which you will see here, if you click on Configure, you will see different types of variables out here. If you want to select any of them, you just need to go ahead and select that particular variable and it gets added to the list. As you can see now. In the same manner, if you want to remove any particular one, you can just unselect and that will get removed from the list, which is there. These are the different types of variables which you can define pages related variables, page URL, which can throw a particular URL as we saw in the example. Can be used in such a scenario. The other variables are like we were talking about scroll depth in the previous video. So for scrolling related variables are also available, wherein we have scroll depth threshold depth units and directions. So this will throw details like. Scroll depth threshold would be, what percentage of the page did they scroll through 25%, 50%, 70%, 90%? Then the units as well, which we can see, and direction, whether it was horizontal or vertical. So that kind of value it will throw when if we use these variables in the tag. So this is how different types of built in variables you will get guys, which you can make use of while you're building your tanks for your business. I hope this makes sense. You understand now built in variables. In the next video, we will see user defined variables, how they work, and how we can make use of them as well. Thank you so much, guys for listening into this, and I will see you in the next video. 16. User-Defined Variables: Hi, eyes. Welcome to this session. In this session, we'll talk about the user defined variables. There can be a lot of scenarios where in Google Tag Manager provides a list of predefined variable built in variables which are given to us, which we are making use of. But there can be situation wherein they might not be useful, and you need to define certain variables yourself. In such a case, you can make use of the user defined variables option. On the same platform, you will get different types of user defined variables, which we can create out here. Let's have a look at this. So once we are inside the Google Tag Manager, we can go to variable section where we can see the second option, which is going to be user defined variables out here. So we can create a new variable. And again, here different options are available, so you can build it out in this particular manner wherein you can use it. You can have a particularly, let's say, a custom event or a first party cookie page variable, which you can create or an auto event variable can also be built out out here. So otherwise, the other option which you also get over here is the community template. So here, some of the custom variables are already pre built, which you can select from, and you can straightaway import it to make use of it in your tax. So that can also be a possibility, which you can do, wherein you can select it from the community template option, which is provided. So these are going to be the different types of user defined variables, which we can also create on the platform for various reasons. I hope this makes sense. You understand now what are user defined variables and how they are different from built in variables. And make sure you're able to use this also going forward in the different tags which you're building. Thank you so much, guys for listening into this session, and I will see you in the next VT. 17. Google Analytics 4 Setup & Publishing The First Version: Hi, guys. Welcome to this session. In this session, we'll see how we can set up the Google Analytics code with the help of the GTM setup which we have done. So for this, we're going to start off with looking at the GTM account first. So what we're going to do here is we're going to set up the code for Google Analytics. So for this, we're going to start building out a new tag first. So we're going to go to tags, and we're going to create a new tag out here. So in this, what we are going to do is we're going to select for Google Analytics. Now, as for the instructions given, we will have to use both the Google Tag and Google Analytics GA four event to set up the Google Analytics porting setup for the website. So let's start with that with Google Tag first. So here we are going to add the Tag ID specifically, for which we can go to the Analytics account, and we go to the data streams to look for the ID. Here, specifically, we can see the particular measurement ID, which we can get from here and put it out here. Once you put this, we can also put the trigger. In this trigger, we are setting up Google and Analytics, we would like to track every single page as a page view, so we can choose that as the trigger over here and we can save this. This is done now and we can do a preview as well of it by connecting our Google Ads in this, and we can see for ourselves it is getting connected, and we can see out here. Now we can check on our website once to see whether it is getting fired as well or not. In this particular place. It is going to show up out here. This is done for us, wherein we have gone ahead and created, and you can see it is firing the Google at tag over here. The other piece which we require now is going to be the second part, which is we will have to create a new tag again, where we're going to do it for the G four event tracking. This we can submit. And we can publish. Now we can see there are two tags which are showing up over here and it is showing us live out here. Now we can go back tags, and now we'll do the second part which is going to be the Google antes GA four event. Here we can give the measurement ID, and we can give it a name, let's say, in this particular manner, and this is the GA four tag which we are trying to set up. We need to add the trigger as well. In this case, the trigger also is going to be all pages which we are doing Now, this has been set up out here, and we can again see a preview of it connecting it to our website to test whether the tag is getting fired properly or not. Here we can see the J four tag is getting fired, which means that it is showing up on the website. This is good to go, and then we can publish and submit again. So now, this has been done, so we can check this out on the website as well to see for ourselves, so we can enable this and we can check it out. Also, when we are coming to this page out here, we can see the same thing inside our analytics as well, whether this is getting tracked or not. We can go to our analytics reports, and it should reflect over there as users. You can see it is tracking users now. It is showing the one user out here, which is coming through tag assistant.google.com. This is also tracking over here. This way, we are able to now, we have set up the Google Analytics code on our website with the help of, the Google Tag Manager. I hope this makes sense. You understand now how we went about it. In order to set up the analytics code, were required to set up the Google Ads tag first, and then we do the GA four event, which we have to set up as well. These two will be required to set up the analytics code on the website. I hope this makes sense. You understand the complete process. Thank you so much, guys for listening into this, and I will see you in the next video. 18. Testing & Debugging Before Publishing a New Version: Hi, guys. Welcome to this session. In this session, we'll see how we can test or debug the Google Tag Manager setup when we are putting codes on our different websites. So with this way too, before publishing the version into the Google Tag Manager system. So it's important for us to do a debugging and testing of the code, which we have set up, and we want to just see whether it's firing properly or not. So let's have a look at this. So once you have created your tags, now what we can do is we can go ahead and do a preview of it. So when we do a preview, Google will give you this option where we can provide our website URL. If you've given the website URL before also, it will automatically take it, and now it will connect to your website. So now we are going into the testing phase to see whether the tags which we've created are working out properly or not. So the first thing which the tag manager would do is going to give you this pop up where it will say that the tag assistant is connected. So now we can scroll through the page, and when you do so, a new tab has been created. A new tab has been created, which will start firing all the tags out here. So let's have a look at this. What is happening here is, based on what activities which you do on the page. If you go to different tabs, you are filling up a particular form, let's say, the tags will fill up will get fired accordingly. If I click on, let's say a particular tab in this particular manner, then we will get to see more particular tags are going to fire out here. So we get to see what all different types of tags are getting fired in this particular manner. And now if you click on any of these, you will get to see more details about it. You can see the type of the tank which we've created, the conversion ID, which we have used on it, and the firing triggers are being shown out here. This way, we get to see the data of it as well. And on the left panel, we get to see the different types of firing which happens of the code. Each of these, as you can see, has a different event code, which we can see out here. This pay, you will be able to see the debugging, which is happening. And then also, you have the option where there are other details which you get to see on the page as well. So this is going to be the tab section where the different tags will fire. Then the variables which you have defined will come up CV here specifically in this manner, so URL is this one, which we're looking at. Okay. So A those things start showing up out here. Data layer, if you have using any data layer as well, that will get defined out here, and we can see which data layer is being used. So these are all the details which we get to see. Plus, on the top now, if you see what all tags have the the system has found on the page, like there is a Google Tag Manager code, which is there. There is possibly a Google Ads code as well, which is there. This is a Google Ad, which is there. So all the tags which are there on the website is also showcased out here. So in this manner, we can test first the whole website. Tags are functions functioning properly or not. And then we can push it for publishing. We can push it for publishing, and then it can start working in a live scenario. So these are the details guys which we get to see out here. I hope this makes sense. You understand now how we are basically going ahead and debugging or testing the tags which we have created in the Google Tag Manager container for a website. Thank you so much, guys for listening into this session, and I will see you in the next week. 19. Facebook Pixel Setup: Hi, welcome to this session. In this session, we'll see how we can set up the Facebook pixel through our GTM account. Once you log into your GTM account, we can start building it out by creating a new tag. So we're going to go to tag configuration. We're going to look for a Facebook tag option out here. Now, unfortunately, Google does not give us an option for a Facebook tag to be selected from here. So in such a case, what we can do is we can go to the Meta Business Site, where we can look for Events Manager, and we can start from the process from there. So we can come to Events Manager where we can specifically look for data sources, where we can connect to web and give it a name, let's say, which will now give us two options. Facebook gives you two options of setting up the code, which is one is through connecting it with a partner, where you will see multiple platforms, so it will give you Google Tag Manager option as well, which you can select and move forward and start the process, or you can connect manually as well by selecting meta Pixel only. So when we do that, we are brought to this particular page where we get to see the metapixel code, which we can copy from here. And now we go back to our Google Tag Manager. I Google Tag Manager, we're going to go to custom HTML, and this is where we're going to paste the code. Now if you look closely to the code, the code has two parts. One part is the script part, which is this one, and the other part is the no no script part. The no script part is useful for pages where there is no Javascript. In such a case, this code can be pasted on a no Javascript page and we'll fire the pixel for us. For now, what we're going to do is we're going to cut this off and keep it aside in another document in this manner. And we'll continue with the tag creation. So now we can also give an advanced settings. We can give it a tag firing priority. A tag firing priority means that we are giving a high priority to this tag to be fired first then the other tags. So you can give it a higher number. Google will automatically give more priority to this tag and fire this first when the page loads. And then finally, we have to give the trigger, the trigger will be all pages page view because we want it to trigger when people visit the page. And this is the Facebook page tag which we have created now, and we can save it. This is one part of it. The second is now we're going to look at the other part, which is for no Java script pages. For that, we're going to create another tag, which will be we'll say custom image, and here we're going to give the image URL. From the code, if you see closely, this is the image URL, which Facebook has given us. So this is what we require, and we're going to put it in the image URL section. And for this specifically speaking, we are going to add a trigger. Now, again, this cannot be all pages, because if it is on all pages again, that every time users are visiting the page, two tags will get fired. This is specifically for those pages which does not have Djava sprint. We have to create a different trigger for this. We can define the trigger as page view again. But with a condition. This is for specific page views. Now here you're going to define the custom variable. We have to create a new variable altogether. We're going to create a new variable, which is for non Javascript page. This is going to be a custom JavaScript. And here we're going to add the function. In this particular manner. We can give it a name, let's say variable, which we can save. Now it comes over here. We will say that when this particular custom variable does not equal to. That is when this trigger fire. We can name it as non J trigger and save it. And this can be the image tag which we are talking about, which we can also save out here. Now if you see, we have created four different tags. One is for the Facebook tag, which is going to trigger when people visit the page. This is going to be the image tag when there is a no Javascript. Custom variable also created, which will define which page does not have the Java script. And this is the trigger, which will happen when people visit a non JS page. So this is done. Now we can do a preview of it. In this particular manner. From here, we can do a preview or else, what we can also do is we can now go to our website out here, and we can see the code over here primarily speaking. This is how we're going to build out all the tags, and then we're going to go ahead and implement on our website, and this is where from where it will get published. I hope this makes sense. You understand now how this is going to work out. Thank you so much guys for listening into this session, and I will see you in the next video. 20. Copy Tag and Export Container: A. Welcome to this session. In this session, we'll see how we can copy tags and export containers as well on the GTM account. Okay? So let's have a look at this once we get into the account, so there can be a lot of scenarios. So let's say you're working with multiple clients and you are setting up GTM code for multiple clients. Okay. So by now, you have a fair idea about what all codes, tags, triggers, variables, which needs to be implemented on a particular website. So what you can have is kind of a base file, which contains all the important tags, triggers, and variables. Now, this base file can be implemented on all the multiple clients accounts one by one. So you can build out this like a template base file, and this can be implemented on different websites as in when you get new clients onboarded. This process makes your work much more simplified. So if you have the base file created, which has all the important tags, triggers, and variables, we can export it first from the existing container, and then we will import it into the new container of the new client, which has boat. So let's have a look at this. What we do here is we can go to Admin, where we can first export the container. So here you can see, you have the option for exporting the container. So you can choose the version, which is where all the important tanks are created. So let's say this is the version, or you can choose the default version as well, wherein you can export it from here. Now, once you export this, now you can go to the container in which you want to past. You want to import it. So we can switch the container first. And here, we're going to import the same particular base file and attach over here. This way, now this container will be used, over here, in this particular, this will be the base file. All the tags which we're using in the previous container has been transferred to this particular container and we can start using it. This is one way which can be really useful for all of us. The second option which we have out here is going to be a case wherein you have the tags, and let's say you want to poppy the tags from one container to another. Or maybe you want to poppy the tags and make another poppies of the tag in the same container. Those things can also be done out here. For which we make use of this particular plugin called the GTM poppy paste Chrome extension, which we have, which you can add to your Chrome browser. Now with this, we can make use of it. What we do here is, first of all, you can just right click on the tag and you have to authorize the GTM poppy paste particular prom extension. In my case, I have already gone ahead and approved it, so I can straightaway get into adding it to the GTM prom extension. You can see this is the prom extension, which shows tags all our zero. What we're going to do is we're going to add it to it. Now it will get added over here, so we can see the variable has been added. Same way, I can do it for the tag as well. The tag is also added over here. Same way, I can do for the trigger Now all the three are added out here. Now, now the idea is that you have two options. You can either paste this right here, the tag and the trigger and the variable will get pasted in the same container. That can be one thing, or else, you can switch if you want to use it in a different container, you can go to that as well, and over here specifically, you can paste it. Now it will paste all the tags triggers and variables which you have copied from one container to the another one. So this can also be a good way wherein you can use multiple tags on across different containers, and then you can make use of it for setting up codes for your clients. I hope this makes sense. I hope you understand this feature as well, which is very operational usage, which can simplify our work as well when we're handling multiple clients and for whom we have to build out multiple tags and set it up for their websites. Thank you so much, guys for listening into this session, and I will see you in the next radio. 21. Google Ads Remarketing Setup: Hi, guys. Welcome to this session. In this session, we'll see how we can set up the Google Ads remarketing with the help of Google Tag Manager. So as you understand, remarketing is a concept where we try to follow users when they visit our website and they don't do business with us. In such a case, we follow these users with our ads. So now you can do so by tracking their data, their IP address, or hookies, with the help of the code, which we paste on the website. So this as well, you can set up with the help of your GTM account. So let's have a look at this guys. What we have to do is we are going to create a new code new tags for this out here. For that, we can go to tags, and we can start building out a new tag altogether, which is going to be for Google Ads. Now in Google Ad, specifically, we are looking for remarketing, so we can choose Google Ads remarketing here. And what we require now is going to be a conversion ID. For this, we'll have to go to our Google Ads account and we can get it from there. Once we are inside the Google Az account, we will have to create a remarketing list first. A remarketing list is going to be the place where we store all the IP addresses, and this is needed in order to set up the code. So we can do it for, let's say, website visitors, and we can give the name of the customers which we want to target out here. And we can create this particular segment. Once this is created, now what we require is the code for which we can go to data sources, where we will find the Google Ad tag. As you can see here, we can go to the details of it. Google will give you the tag setup instructions, how you can set it up out here. Out of these three. What we want to use is the Google Tag manager because we want to set it up through that. So we can use the third option. What you require from here is just the conversion ID. You can take the conversion ID and we can put it out here. This way, we are setting up the remarketing code. That is all we have to put out here and we can give this a name. And we can save it. In this, we need to add a trigger as well. The trigger would be that again, people who viewed that particular page, that will trigger the remarketing code so that we can add also as page view and we can save it. This way, we have now set up the remarketing tag as well on our website through our GTM account. I hope this makes sense. You understand now how we are setting up remarketing code on websites with the help of your GTM account. Thank you so much, guys for listening into this, and I will see you in the next video. 22. Troubleshooting Problems You Might Encounter: Hi, guys. Welcome to this session. In this session, we wanted to discuss different troubleshooting scenarios which you might encounter while you're working with GTM. So let's look at it. So the first one, which you can use over here is the Google Tang assistant. The Chrome extension can help you win testing all these tags. So you can use this particular chrome extension to test whether any tags are firing or not. So that can really help in troubleshooting issues, which you might see. The another problem which you might face with troubleshooting these tags can be that, uh, the Google tag manager works only when you're using the same browser, okay? Uh, the debugger tool only opens in the same browser, which is a chrome specifically browser, which we're looking at. If you're using a different browser like Firefox, then the debugger tool will not open, will not appear. So in that case, it can be an issue for us. And so we have to make sure that all this work which we are doing for ourselves or for our clients are happening on the same chrome browser. In the same browser, we are trying to investigate and implement. Same thing can happen with private windows as well. If you're using a private window in the same browser like the chrome again, there again, the debugger tool might not work. So the other reason is we want to stay in the same browser, and that is why in the normal Chrome browser only, we would like to finish and work on all the Google Tag Manager tags. You can also see that the issues can also happen if we have somehow disabled the third party cookies in the browser settings. So we need to make sure that that is not happening. So for example, when you go to settings and you go to privacy and security, here you can see third party cookies. We need to make sure that we have not blocked it. Okay? So if you have blocked it, then that can again create troubleshooting issues with Google Tag Manager. The other option which we have here is while we're working on, it can be a scenario that you're managing multiple clients. So obviously with multiple clients, we have different accounts, and you're working on different containers altogether. So we need to make sure that we're working on the correct container. This you can do by looking at the debugger tool. The debugger tool will show the container ID, the GTM ID over there as well and making sure that we are on the current container. This can certainly happen when multiple accounts we are managing. Also, sometimes it can happen that like we saw in the previous videos. Another way of setting up GTM is that we have used the POM extension add SR injector. So if you have used that, make sure we have put in the correct GTM ID. So for example, when we come to GTM add POM extension, and go to advanced options at functionality. So here we need to make sure that we are put in the correct GTM ID for which we are working on the client. Okay. So that way, we know that we're working on the correct account. The other aspect of it, which you can also look at is, if the debugger window is not working, it's not loading properly, then we have the other option is to refresh the complete website. Okay? That way, what will happen is it will remove all the cache, and we can start from scratch. So this can also help to fix any troubleshooting issues which we are facing. Another thing which can happen is sometimes we can have ad blocker added on the browser, which we need to disable out here while working on GTM. Cookies from different browsers can be there. So in such a case, we need to make sure that we have removed all these ad blockers. Okay, to clear any caches and cookies. Also, if you're working, then we remove any kind of plug ins. Sometimes there can be plug ins which you're using. Okay. So in that case, it will not open our GTM in incognito, and we will not be able to test. Okay. Also make sure that we are doing all of this in the Chrome browser because in Firefox, the deberger will not work. And then the last one is that when we're working on troubleshooting, if all these steps are not helping out, then in that case, we can reach out to the web developer team who can help us fixing in all these issues. I hope this makes sense. You understand these issues or scenarios, which you will face while troubleshooting for Google Tag Manager tags. Thank you so much, guys for listening into this session, and I will see you in the next video. 23. Time Triggered Tags Part 1: Custom Facebook Events For Remarketing: Hi, guys. Welcome to this session. In this session, we'll see how we can use time triggers to set up custom events on Facebook. So for that, we can go on the website, and we're going to start building out. So in the Google Tag Manager account, the first thing we're going to do here is to create a trigger first. So we're going to create a time trigger. So Google gives you that option to create a time or trigger over here, and you can give it a name as well. Let's say we're giving it like this, and the interval is going to be 30 seconds, which means that it will trigger an event after 30 seconds. We can give that duration in milliseconds, and we can limit it as one. Then we can give the custom variable where we can give it for the whole website, so we can choose page host name and which matches with regular expressions, and we can give it as dot star, which means it's the complete website for which we are building. And you can give it a name as well, let's say, in this manner, and we can save it. This is a trigger which we have created. Now for this, we have to create the tag. For that, we can go to tags. And we can start creating a new tag out here. Now, in this case, we need a custom event from Facebook. For that, we can go back to our events manager account, and here we can get a particular custom event, which we would need out here. We can go to the particular conversion tracking page where there are custom events provided like this one, standard event. This is what you require, which we will modify a little. We'll copy this, and we're going to create a custom STML. We had seen this earlier as well. So in this manner, we are going to put it out. Now, we don't require all of this, so we can remove all of this and just mention, let's say viewed after 30 seconds. This is all which we have to mention out here. Then we add the trigger which we created, which is time 30, and this is going to be the tag which we've created now, which we can name as time after 30 seconds. This is becoming the tag which we've created now, which will trigger a 30 seconds. This is the website on which it is going to happen. We're going to just do a preview Now it will start connecting and we just need to wait for some time for 30 seconds or you can see it is right now getting connected. And now we can see it is not yet fired because of the fact that we just have to wait for 30 seconds, and that is how this trigger will work. The intent is that when you look at these websites, right? Now this is a one page website. On a one page website, when you click on any tab, you stay on the same page. In such a case, it is difficult for analytics to understand how much time people are spending on your website, which pages are they clicking on. In such a case, we create this kind of a tag which is counting the time frame. So we The tags will fire once a user spends a certain amount of time on the page, if it's like a one page website, which we have built out. For those purposes, this is being created. Here, then you can see now the time tag has fired over here, which we can see out here, which is coming up for 30 seconds as we can see. And then afterwards, this one has also fired now, which says time after 30 seconds, which is fired as well. In this manner, with the help of this tag, we can understand how much time user spent on a one page website. I hope this makes sense. You understand now how timer tags can be created on GTM for such purposes. Thank you so much, guys for listening into this session, and I will see you in the next video. 24. Time Triggered Tags Part 2: Time on Site With Google Events: Hi, guys. Welcome to this session. In this session, we'll see how we can set up a Google Tag Manager code, which is used for tracking the time on site. Okay? So we want to track how much time users spend on the website through Google Analytics. For that, also, we can use the GTM code. So let's have a look at this and how we can define this. Once we are in the Google Tag Manager account, we can start creating a new tag. The first thing it's going to be, we're going to use a Google Analytics GA four event. Here, we can provide the measurement ID which we can get from the analytics account. If you can come to analytics account and we can take the measurement ID from here and put it out here. We can give a name to this event. We are saying time on site. And then we can give some event parameters. In event parameters, we can add an event which is going to be time, and we have to give a value. The value has to be a custom variable, which we have to fill up out here. So what we are looking for dally, a variable, which can be used for calculating the elapsed time, the time, how much time people spend on the site. So for which, ideally, there isn't any predefined ones which we can get out here. So a better option would be that we can search in the community template gallery for something like that. So let's say if you're looking for elapsed time, there is one which we can use out here, which we can use for tracking this particular same thing, which we want to do. So we're going to choose this and what we want is to convert 2 seconds, and we can name this and save it NPS has been defined over here. Now, what we need to do is have a trigger. Now the trigger, again, we need to have a trigger for time, which is going to be tracking the number of minutes seconds of it, so we're going to add a trigger like that, which can be a time based, like this. And we can give the specific interval is 20 seconds. Let's say it is going to f 20 seconds, and then we have to also define the custom variable, which we can contain over here, matches, j. This is for all the pages, we are going to give it as in this manner, and give it a name as well. And save it. Now if you see the whole thing has been set up, we have added all the details which are required over here, and we can give it a name, let's say time tag like this, and we save it. This has been created now, which we can preview. And see, we're going to do a debug of it. We'll go to the website and get connected. Right now, it is not fired. We here, as you can see, time lapse, the time tag is all here, not fired right now. Let's just wait for 20 seconds. On the website specifically, we should be able to see that happening. Once you go to the website and you can go through different parts of the website possibly. So now you can see it has fired and it has gone on the top, and it says tags fired out here. So this way, we can create the tag and when we can submit it, submit the version, and we can use this. I hope this makes sense and you understand how we can make a particular GTM code, which will be used for tracking the amount of time user spends on the website. Thank you so much, guys for listening into this session, and I will see you in the next video. 25. Scroll Distance Tracking Part 1: The Basic: Hi, guys. Welcome to this session. In this session, we'll see how we can make use of the scroll distance tracking. So this is useful in situations wherein, let's say we're writing some blog or content, and what we want to see is how much percentage of that blog people scroll and read through. So this also we can track with the help of Google Tag Manager. So let's have a look at this, how you can set this up. So for this, we're going to go inside the Google Tag Manager and we'll start building out the tags for it. So the first thing which we can do is we can build a trigger. So what we are going to create here is a specific kind of a trigger for scrolling. So we will go ahead and look at that. So Google gives us that option, which is called scroll depth. So here I can do two types of scroll depths, which I can create, which can be vertical or horizontal. Let's say we are doing it for vertical. Now, in vertical, we can also define percentages, percentages of the page which people scroll through. So we can give it a single percentage. Let's say, I just want to track how much percentage, 50% of the page is scrolled, how much, so I can do that, or I can give multiple percentages as well. And as in when people do so, it gets tracked. So we can give it in this particular manner. Now it will get tracked in all these four intervals. So this is one which we can do. Apart from that, you can set up this trigger for all pages or for some pages specifically. Maybe you have a particular blog section. In that case, you can define it for that particular page. You can do that as well, and you can give the page URL for that. So let's say your page URL contains blog. In this manner, you can define it. Or else if you want to do it for all the pages of the website, you can keep it at all pages. So this is the trigger which we are creating. Apart from this, the trigger, we also would need some variables to track this data when it actually runs. We can define some scroll variables. So Google gives us some options in that as well. Some scrolling variables are given, like scroll depth, threshold, scroll depth units, and scroll direction. These three are given, which you can also add so that we can track this as well. Let's have a look at this. This is the website for which we are doing it. Let's do a review of this. So now we are on the website and we can scroll and we can see whether this is getting tracked or not. Here now you can see the scroll depth is getting tracked. The first one, let's look at scroll depth, this one. If you look at the variables, you will see 25% was covered in this vertical. Same way when you go to the second one, it's 50% vertical, then the third one, 75% vertical. It is getting track. This is working fine, absolutely for us. Now, what we need is the tag. The tag for this, which we can also set up similarly. We're going to create a new tag altogether, which will be a Google Analytics GA four event. We can give the measurement ID of our analytics, which we can provide out here, and then give it a name, let's say, I'm giving it a name ple distance. And what we need here is an event parameter. We can add a parameter over here, which is scroll. Let's say distance, once again, and the variable. The variable can be the scroll depth threshold, which we want to set, and we want to see how much percentage is scrolled, so we can add a percentage so that it picks that value and percentage comes along with it. You can define this and then choose the trigger which we have created, we created this scroll trigger. This is now created, and we can name it, let's say scroll tag. Now this is built out and now we can preview this and see the whole thing. Now when we go to the website, we can scroll through it. Let's say till the end, we are doing it. And let's have a look at it. So we can see the scroll tag has fired over here. All the four scrolls till the end has fired. So this is the 90% one, which is also fired over here. Okay, this is 75, 25, 5025, which we can see, tag wise, the scroll tag has fired also successfully, which we can see out here, which has worked out. Okay. So this is how we can very easily create a scroll tag, which is only going to track how much percentage of the blogs or page or content. If people are scrolling through and reading. This also shows up on your analytics as well over here specifically. Now we can see the scroll distance specifically parameters showing up in this part as well on the page once we had done that, so it will reflect in your analytics account as well. I hope this makes sense. I hope you understand now how we can create a scroll distance tracking tag also through Google Tag Manager. Thank you so much, guys for listening into this, and I will see you in the next video. 26. Scroll Distance Tracking Part 2: Time Triggered: Y. Welcome to this session. In this session, we'll see another scenario of scroll distance tracking. In the previous video, we saw we could track how much when people scroll through our blogs or pages, we would like to track how much percentage of the blog or the page did this scroll through. Now, this might not be the ideal way of understanding how much they are reading the blog. A better way would be that if I can also track how much time do they spend on the blog page, in addition to that, that will be a clear picture of that. So we'll do that in this particular video and we'll see how we can implement it. So we can go back to the specific tag which we created, the scroll tag which we created in the last video, and we can come to the trigger and here we're going to add a condition. The condition can be that I want to have a particular elapse time defined over here, which is, let's say, greater than 10 seconds. Which basically means is that we want to trigger the tag only once the user has spent minimum 10 seconds on the page. This will be an ideal way of understanding how much the users are reading the content. Once you make this addition to the trigger, we can go ahead and test it out. And in that we should be able to see that. Now, Now once the page is getting loaded. Now when we scroll, it will trigger all the scroll depth tags, 25%, 50%, 70%, but the particular elapse time is not triggered till the time we don't spend that 10 seconds on the page. Once you have sp that seconds, 10 seconds, or whatever threshold you have set, then only the trigger will fire. If you see now that it has fired only after the 10 seconds. You can see it says elapse time 10 seconds, greater than ten, which we had defined out here. This is how it is going to work out for us. This way, we are having a better understanding of how much time and how much content did they really read on our pages. I hope this make sense, you understand now how we can track the amount of time spent by users on our blogs while they scrolling through it. Thank you so much, guys for listening into this, and I will see you in the next video. 27. Click Tracking Part 1: Outbound Links: Hi, guys. Welcome to this session. In this session, we'll see another situation which is click tracking. So we can also do a lot of click tracking, which we can do through GTM, which is basically tracking the different types of clicks happening on our website. So when users come to our website, they might click on different tabs or links on our website, and that we would like to track over here. So what we're looking at is a specific situation, which is outbound links, links, which if a user clicks on, they're taken outside our website to some other websites. So this is what we are going to track out here. So let's have a look at this. For this, what we can do is we can go ahead and start creating a trigger first. We're going to create a trigger, which is a click trigger, so we're going to do just links, and here we're going to go ahead and do it for specific links which are there. We're going to define that by creating a new variable. Now the new variable, which we can use here is auto event variable, wherein we're looking at the URL specifically, which is the case that the URL is outbound, and here we can give our website URL in this particular manner. And we can save this. I. And we can see that when this particular variable holds true, then this trigger should work, ideally speaking. We can say this is our bound trigger, which we have created. Now for this, we are going to create the tag. We are going to create a G event tag. Google Analytics Go event tag, we can give our measurement ID, which we can take from our account. And we can give it a name, let's say click and we can give some event parameters. We can add a parameter, let's say URL. The variable we want to use here is a click URL. This trigger when particularly outbound trigger is added to this as well, which we had created. This is becoming click t This is how we can build out this outbound click tag, and then we can use this. How it is going to work is when people are on our website, and they click on some link which takes them outside the website. That is when this particular tag will trigger. Here, the outbound click tag has been created. Okay. So this will fire when a particular link over here takes them to a different website. So this particular tag, which is right now here, will come in the tag fired section. I hope this makes sense. You understand how an outbound tag can be created, which helps to track how many people are clicking on our outbound link and going outside our website. Thank you so much, guys for listening into this session, and I will see you in the next video. 28. Conversion Tracking Part 1: Simple Google Ads Conversion Tracking: Hi, guys. Welcome to this session. In this session, we'll see how we can set up the Google Ads Conversion tracking with the help of Google Tag Manager. Let's begin, guys. So once we go into the Google Tag Manager, we can start building out the tag. By going to the tag section. So we're going to create a new tag over here, which can be a Google Ads conversion tracking. But before we do this, what we also require is a conversion linker, which we will have to create over here. So let's build this out. So conversion linker, you just need to add a trigger, which can be for all pages. So this will help us to build out the conversion tracking in the right manner. So we can name it in this particular manner. Once you create the conversion linker, now we can create the tag. So the Google Ads conversion tracking tag, and here it will require some details like conversion ID conversion label, which we will have to provide. For this, we will have to go to our Google Ads account, and from there we can generate it and use it out here. So let's have a look at this. So once you're inside your Google Ads account, you can go to the goal section in summary, where we are going to create a conversion action. So you're going to do this for the website. So we can select that and we can give our website domain, and Google will scan it and then provide the steps to create the conversion action. So we can fill up the details, and once you fill up the details, it will generate the conversion ID and the label, which we can get. So now we're going to fill up a small form which Google gives us. So here we can select the category of a type of conversion which we want to track. So in my case, in our website, we are doing a lead form submission. So from here, I can select submit lead form, and we can give it a name as well in this particular manner. And then we can give it a value. A lead, if it has a specific value or a revenue attached to it, we can do that, or else we can say, don't use a value. And then we can define the count. Count is going to be. It is going to keep track of all the unique leads which we have collected or generated, which we can take as one. These are the details which we are going to fill up on this particular page, and we can move forward. Once you save this, it will give us the instructions to set up the code, for which we are going to use today as Google Tag Manager. This is the conversion ID and the label, which we require. So we can copy it from here. And we can go back to our website and put it out there, the label as well. These are the two details which we require, after which we can come to the trigger, and we can add that trigger specifically over here ideally speaking. For the trigger again, We're going to do a page view trigger. Now, the trigger has to be for a specific page for which we are doing this. We're going to do it for some particular pages, which has a specific keyword in it, so we're going to take page URL. So on the website, which we are looking at, for which we are tracking, there is a particular form which is out here. So what we want is we want to create a trigger when people submit this particular form. So we're going to look at that URL first. Now if you see this is the page where we need to set up the code, so we can take this URLs particular keyword and use this as a trigger out here, which basically means that this will trigger only on a page which has thank you written in it. This will be the thank you page which we're creating. We can name it in that manner, and we can save it. Now the conversion tracking is created, the conversion linker is linked. We've provided all the details. The T thank you page trigger is also built out. This is our conversion tracking tag, which we have created now. Now we can review this and see how it works. It is going to get connected to our website, we'll go back to our website once. Now when it is we can see this. What we see out here is right now, the conversion linker has fired, which we had created, so it's working absolutely fine. But the conversion tracking is not yet fired because we have not yet filled up the form. So what we're going to do is we're going to fill up the form as a test. We just check whether it's firing properly or not. So now we reach the form. So let's have a look at it. So now you can see this particular tag has jumped to the tag fired section, which means that this particular tag is working absolutely fine. So in this manner now, very easily, we are able to set up the Google Ads Conversion tracking for our website through the Google Tag Manager. I hope this makes sense. You understand this complete process, how we did it. Thank you so much, guys for listening into this, and I will see you in the next video. 29. Implementing GA4 Event Tag with GTM: Hi, guys. Welcome to this session. In this session, we'll see how we can implement GA four Event tag with the help of Google Tag Manager. So let's have a look at this. So what we're going to create is a GA four Event tag, so let's go to tags, and this is where we can start the process. So we can go to tag creation. We're going to create a Google Analytics tag, so that will in a GA four event tag. Let's say this is for a particular lead form generation, which we want to create. So the first thing which is required is the measurement ID, which we have to provide here, so this you can get from your Google Analytics account. So we can go to the Analytics account Admin section in Data streams, and that is where we can get the measurement ID from here. We can popy it from here and put it out here. Now we can see it says Google Tag found in this container, so it's absolutely fine. We can give it a name as well. Let's say lead on Submit. And then we can also define the trigger for this. When will this be triggered, so we can create a new trigger for this. I will be a page view. Now, we're going to create a page view for us. Thank you page. We don't want to trigger this for all the pages on the website. On the website, specifically, if we see, we have a particular lead form out here and if we fill this up, It takes us to a thank you page. This particular part is what we require, and we use it in some pages. We'll say that the page URL, which contains thank you for that page only page view, which we want to create. If a user views this thank you page, then the tag should fire. This is a page trigger, which we are creating. We can save this. Now the trigger is also created, we have created the tag as well. This is a GA four tag which we are creating and we can save this. Now the tag is created, so we can preview. Once we preview, we can go through the page and we'll see how it is working out. This is the website which is now being created. It's connected right now. You can see right now, the the G four tag is right here. It is not firing at all, because we have not yet filled up the form. Once we now come to the form and fill it up, It should fire, because now we will be viewing the thank you page. We've reached the thank you page. Now this ideally, get fired, we can refresh the page one to see that happening. Now we can see the GA four, the tag is fired. We can see this as well. It has taken the event name as well. Lead Form Submit. This is what we had done. This was the measurement ID, which we had added. Now you can also verify this by going to analytics as well. We can go to the real time data. It should ideally show up over there as well. We can see user data out here, a real time report, let's see. It shows one active user out here. You can see the T thank you page is getting fired. It got a view over here. Event also. Out here is showing up. Let Form Summit, got a one over here. So this way, we can clearly verify that our GF event has been created now with the help of our Google Tag Manager. I hope this makes sense. You understand now the complete process, how we are doing this. Thank you so much, guys for listening into this session, and I will see you in the next video. 30. Storing Measurement ID in User-Defined Variable: Hi, eyes. Welcome to this session. In this session, we wanted to see a particular situation, which we can improve out here. You must have seen in the previous videos whenever we are creating a GA four specific event. In that, we require the measurement ID, which we need to take from the Analytics account, and then we come to our Google Tag Manager, and we put it in the tags. This process can be made in a different manner, where we can store the measurement ID in one of the user defined variables, which we can create here. So this way, you will not have to go to Google Analytics and get the measurement ID from there. So let's see guys how simply we can use the user defined variables out here. So once we are inside the Google Tag Manager, we're going to create a variable, which is a user defined variable. In this, we're going to choose a specific one, which is constant because this is going to not change. Here we can put the measurement ID. Let's go to your analytics and we can popy our measurement ID and put the v value out here. We can save this let's say we can say it as G four ID. So now this is a user defined variable, which we have created here. So going forward, whenever we are creating a GA four event or any other tags related to GA four, we can use this right here, and we can create those tags. There will not be any requirement for us to go to our analytics account and get the measurement ID from there. I hope this makes sense. You understand this simple process which can be done to simplify our work. Thank you so much, guys for listening into this session, and I will see you in the next video. 31. Tracking Clicks & Sending to GA4: Hi, guys. Welcome to this session. In this session, we'll see how we can track any type of clicks which is happening on the website with the help of Google Tag Manager and sending that data to GA four. So let's have a look at this, how we can set this up. So for this, we are going to create first a trigger, which will be a click based trigger. We can go to the triggers section where we're going to start creating this. We're going to create a click based trigger, which can be all elements. All elements is the one which tracks every kind of click which is happening on our website. So we can create this one and we can name this, let's say, click trigger. For this, we would need to also have a tag which we will fire, which can send the data to GA four. Now we're going to create a tag a GA four event tag. And we need to provide the measurement ID. Here now, you can make use of the variable, which we had created in the previous videos. Rather than going to the analytics account, you can just make use of the variable. If you remember in the previous videos, we had created a variable called GF four ID, constant, which we can now use out here, specifically, and then we can give it a name. In this, we are going to attach the click trigger in this particular manner. This is going to be the click specific tag which we are creating, which is going to go to G four, and we can save this. Now this is created with the particular trigger which we have created, so we can do a preview of this. And we can see how it is going to work. Now it is being created, so it has not fired yet. We can just scroll through it. Now if you click on certain pages, I'm clicking on this or the skills part, or let's say somewhere empty part as well. Now it has triggered. You can see this has triggered for us, and this is the event which we had name we had given the measurement ID, which I can see out here. Now, this data is getting triggered, and this will also now show up on the page as well on our analytics account. So where the data will be transferred. So we will be able to see it out here as well. Specifically, we can see all clicks is coming up here as well, which we had created as an event. So now the data is moving to analytics. So in this simple manner, guys, we are able to create a clicks based tag as well through Google Tag Manager, which is going to track all kind of clicks happening on our website. I hope this makes sense. You understand the whole process, how we went about creating it. Thank you so much guys for listening into this, and I will see you in the next video. 32. Adding Details about Clicks and Sending to GA4 Events: Hi, guys. Welcome to this session. In this session, we'll see how we can add certain details about clicks and send them to G four events. So in this, what we're going to do is we're going to add some variables so that we can get to see their values when we are triggering those particular tags, and this can be sent to GA four as well as events in which we can see the information. So let's have a look at this. So once we are inside the Google Tag Manager, what we want to do first is add certain variables for which we want to see the values. So we can add the variables, we can configure from here. Let's say we want to look at the clicks variables. These are all the variables related to clicks, which we can add here. Now they're all added in this particular manner. And now these ones. We're going to use them in our trigger, which we have created earlier. This was the tag which we had created, in which we can use them. Over here, we had created the particular measurement ID and event name. What we are going to do is we are going to add the event parameters, and we're going to add six of the six clicks related variables we had seen. Now we can add them one by one over here. These values will then fire as well. As you can see. We had filled this up, and now we can give it a name as well, so we can name in the same manner. This will show up in our specifically in G four also. Now we have added this and we can save this information. Now that we have done this, if you do a preview of this to see how it is going to look like, let's have a look at that also. Now when we see this, we have the clicks one over here, so let's click on certain sections of the website in this particular manner. Now it is firing. Now you can see the parameters are getting fired also. Over here, all of these are showing up in the click section, if we see, the variables will be here. Now we can see the variables. The click element is this one, the click ID, which is used, the click text contact. The URL, there was no particular URL, so it does not show anything. This way, the data is showing up now, so the variables are defined, and for their data, we can see. Now, the same thing will also reflect in our Go. If we go to our GFO real time data, and we see this information. Now you can see the all event section over here. If you go on all clicks. You can see all the particular event parameters which we created right now. You can see click classes, click ID, which we created, click element, text. All these are now showing up out here. So yes, after this, all the details which we added in the GTM is now passed on to G four in this particular manner, and we can see the information. I hope this makes sense. You understand now how you can add variables which can then pass the data to GA four through our Google Tag Manager. Thank you so much, guys for listening into this session, and I will see you in the next video. 33. Track Button Clicks in GA4 via GTM: Hi, guys. Welcome to this session. In this session, we'll see how we can track clicks on certain buttons on the website. Every website will have certain buttons, and if we want to track the clicks happening on them, we can do that as well throu Google Tag Manager. So let's have a look at this. For this, we can go into the account, and we can start looking at the triggers first. So we're going to create a trigger, which will be a click trigger. So we can create a new trigger from here, which is a click and we can use all elements. But now what is going to happen is, this is not for all clicks, but for certain type of clicks which are happening, specifically talking about buttons. From here, we can choose a variable which would be relevant for us. These are all going to be the built in variables which Google gives you. If you can choose from here, or you can choose any other built in variable you want to, or you can create a new variable. So let's say we're choosing click classes over here, and now we have to provide the particular variable out here. So you can go to your website and you can look at the coding of your website specifically to see what kind of variable is used on it. You can do a view page search or inspect element. And what we're going to look at is the specifically. If you look at here on the button specifically, what we're using here specifically is a button element, which shows over here, as you can see button under label or button element used here. So we can use button as the value, which we want to use. And then you can give it a name in this way. And for this now, we are going to create a tag. So we're going to use the same tag which we had used in the previous video. What we can also do is, we just want the exact same thing, so we can make a copy of this rather. And now we can say button clicks. In this we will make the changes. This is the copy. So what we re name can be button clicks. And for this, we're going to go ahead and remove this trigger specifically, which is being used. This is not the right one. What we want to use is the button click trigger which we created. Now you can go ahead and save this. This will work for us. We have created this particular tag now, which shod fire. Let's have a look at this. So this is connected. So I'm just rolling through the website now. What we will see here is that the button clicks is not fired because we have not clicked on the button yet. So let's do that. When we click on the button. Now, it has triggered out here as you can see. And if we see inside, we can see all the parameters as well showing up. Also, if you notice, if I go ahead and click on anywhere else, I'm just clicking on anywhere else. What is happening is we're getting the clicks over here. But if you see, that is not triggering the button clicks. That is just the clicks part which we had done earlier, that is getting triggered. This means that this particular setup is working absolutely fine. It is only going to trigger when we click on the actual button on the website. I hope this makes sense. You understand now how you can track clicks on your buttons on the website as well. And we can pass this data to GA four as well. Now if you go to GA four and like to see this information. We can see it in events particularly. Here, you can see button clicks coming up over here and you can see the data as well. Click classes is coming up over here. This is the URL which we'll be seeing, which is showing up in this particular manner. I hope this makes sense. You understand now how we can track clicks on buttons as well on our websites through Google Tag Manager. Thank you so much, guys for listening into this session, and I will see you in the next video. 34. Creating a Specific Page Trigger: Hi, guys. Welcome to this session. In this session, we wanted to see a different approach, which is we can create a specific tag page trigger for the same situation, which is where we are setting up, let's say a GA four event, through Google Tag Manager. So here, what we're going to do is we're going to create a specific trigger first, and we can link it to the tag, which will do the same job, which we were seeing in the previous video. So let's have a look at this. So once you're inside the Google Tag Manager, the first thing which we're going to do here is create the trigger. We're going to create the trigger, which is going to be, let's say the same thank you page trigger, which we are creating. We can create a page view, which is for a specific page, and here we can select a predefined option, which is page part contains, and then we can give the same specific keyword which is there in our thank you page URL, and we can create this particular trigger. This can be a thank you page specific trigger which we are creating. And now this trigger can be used in the tags, which we have created, so we can go to the tags, and we can choose the tag specifically. And we can attach that particular trigger out here, as you can see. And use this now to trigger and see if their leads are getting generated, tracked on Google analytics. Okay. This is another approach, which we can do wherein we can do this and create the different types of tags for specific pages for which we were creating it, and then linking it to the tags so that we can track our details. I hope this makes sense. You understand the different approach, how we can set up our Google Tag Manager codes. Thank you so much, guys for listening into this session, and I will see you in the next radio. T. 35. Capture JavaScript Errors with GTM and Send to GA4: Hi, guys. Welcome to this session. In this session, we'll see how we can capture JavaScript errors through GTM and send them to GF four. A lot of times our website is built on JavaScript, and there can be a lot of errors which might happen, and because of which it creates a bad user experience for our users. So in such a case, it makes sense to keep track of these errors and then fix them through our web developer. So in such a case, we can make use of the GTM as well to capture these errors, and then we can share it with Google Analytics, and then these can be fixed by our web developers. So let's have a look at dis guys, how we can set it up. Once we are in the Google Tag Manager, the first thing we are going to do is we're going to add certain variables related to these errors. So we can go to the variable section, and we can add these variables first related to errors. We can see under errors, there are certain variables like error message. This will show us the description of the error which has happened. Error URL will show on which page URL the error is coming, and then the line as well, error line will show which line of code has an error. These three we can add over here. And now we can create a trigger based on this. We're going to create a new trigger, which is going to be a Java script error, and we can keep it as for all JavaScript errors, which we want to track over here. We can name it as JS error trigger. And now we will use in the tag. Let's create a new tag, which is going to be a Google Analytics event tag, and we're going to add the measurement ID, so we can make use of our G four ID, which we had done earlier. And we can give this a name, let's say JS error. Now here we will have to add some event parameters, the values for it. The variables which we created for those three, we are going to use this. We can name it in that particular manner, which can be error message. Error URL, and error line. All we need to do is provide the values based on the variables which we created, error message. Error URL and error line. This we are provided. Now, we just need to add the trigger JS trigger, which we created. Now our tag is ready. Name this as JS error tag. This tag will fire when it identifies any errors JavaScript errors on the website. Now, we can't do a preview of this, but this will show up eventually once there are any errors in the JavaScript code on our website, it will fire the tag, and that will show up in analytics. So in analytics, when you go, we can go to the real time section where we go to events over here, you will see the event which we created, which is JS error error message, which we created over here, right? This particular event name will appear JS error, will appear in our analytics out here, and we will be able to see all the errors which are coming in, which can be shared with our web developer, and they can look into fixing it. This way, guys, we can make use of the Google Tag Manager again, to find out any Java script errors happening on our website. I hope this makes sense. You understand this complete process, how to set it up on the account. Thank you so much guys for listening into this, and I will see you in the next video. 36. Tracking if users are viewing a particular section, image, banner etc.: Hi, guys. Welcome to this session. In this session, we wanted to see how we can track if users are seeing a particular section of our website or image or banner or not. This also you can do through GTM, where we can set up a particular tag, which can do this task for us. Let's have a look at this. Usually, what happens is people might scroll through your website, but might not go to particular sections, important sections which we want them to visit. In such a case, we can build out a certain tag for that. For this, the first thing which we need to have is certain variables related to visibility, which we will have to add here. We can go to the variable section configure and we can go to percent visible. These two we will add over here. And then we can come to triggers. We're going to create a new trigger for this which is going to be element visibility, which we can set here, and we can give the selection method ID. We have to provide this ID, which we can get from the code from the website itself. Let's say on my website, I want to see this particular section people are visiting or not, because I want them to contact me. In such a case, I can look at the inspect element and see particularly this section primarily and look at the ID which we can use out here. If you see specifically, this is the section which is getting highlighted, this particular part in which we can get the ID from here. And put it in the section out here. Now this is going to fire one per page. Once a person comes here and spends a certain amount of time, we can go ahead and fire the tag for that. In the advanced settings, you can go ahead and give the settings as well how much time you want the person to spend on that particular section. So let's say I'm saying 10 seconds, so we can give 10,000 milliseconds out here, and we can create this visibility trigger. Once the trigger is in place, now, what we have to do is create a tag where we can create the tag, which is going to be a GA four event tag, and we can add the measurement ID, the measurement ID, G four ID. We can give it a name also like that. Let's say visibility. And we can add some event parameters, two of these parameters, which we had ed. We can the ones which we selected, the variables on screen duration. And percent visible. The other two, which we had seen specifically. Then we can name the event also in that particular manner. Percent visible. Then we can add that trigger, which we created out here. Now this is ready. We can see how this is going to work for us. We can name it in this manner visibility tag and it. Now that the tag is created, we can preview this on the page and see how it works. We can connect the website. A and now we can scroll through the website and come to that section. So once we are on this section, let's have a look at it. So right now if you see, the visibility tag has not fired. That is happening because the 10 seconds it needs to be there on the page, right? So we need to be on this page for 10 seconds, and then it will fire, and it will show up in the fired section. Once that happens, then we understand that this particular tag is working properly, and it gets all the values which we get to see out there. So now you can see the visibility tag is in the tags fired section. And if we go there, we can see the particular parameters which we are designed percent visible on screen duration is also coming up out here. This, now we can check on our analytics account as well, whether it's working properly or not, so we can refresh, and we can see real time data on analytics. We can go to the event section and see that over there. Let's go to real time. In the real time, we can see visibility. This is what we had created as an event. If we go in this, now we can see the different types of events over here. Percent visible is coming here, on screen duration is also coming here, which is also firing properly and we can see it in GA. So this is how we can set up the tag, which will help us to track whether people are watching and spending time on a particular important section of our websites. I hope this makes sense. You understand now how we can build out this tag in our GTM account. Thank you so much, guys for listening in to this session, and I will see you in the next video. 37. Introduction to Data Layer : He. Welcome to this session. In this session, we'll talk about the data layer concept in Google Tag Manager. So data layer are like a Javascript object that sits on our pages. So it is a part of your estimate code of your website, which sometimes we require. It contains all the data or information which you want to pass from your website to other applications or tools. So this is useful in different scenarios. So let's have a look at a scenario. So usually what happens is, you have a website, wherein you have listed down your product. So it has got various types of information, like name of the product, price of the product, images there, color, size, all this this there. Right? Now, when you set up a GTM tag or any other tag, let's say a dope tag or any other tags, so the GTM pulls data from these particular information, which is there on the page. Now, what happens is, in cases, sometimes when you move the information to other parts of the page, let's say, I move the size information to another part of the page, then GTM will not be able to pull that particular information. In such a scenario, we introduce a data layer. A data layer sits behind the website page, something like this. We define a data layer, which is like an object, which sits behind the page, and now we connect all the tags, GTM or a do or other tags to the data layer here, where we have we have gone ahead and defined all the information clearly. So here, the name of the product, name of the product price of the product, color size is defined clearly. So now, if even if you make changes to your front end page, let's say you move the color to other section or images to other parts of the page or size to other parts of the page, the information in the data layer remains intact. So the tag managers can easily pull the data from the data layer itself, and they can do the tracking. So this way, it really helps to go ahead and you can keep making changes to your pages while it does not affect any of your tags which you have set up through different tag managers. Let's see some examples of how this will look like. So the data layer structure is going to be something like this, wherein we introduce a script, and we need to write in this particular syntax, which is data in lower cases and layer in upper cases. This is case sensitive, so we need to write in this particular manner. Then we introduce the key value, the values which we need to define out here. We can close the script. This is the structure of the data layer, which we have to write in our est porte. Let's see this example. This is a simple example where we have written in that format. Data layer is defined. We can see the product over here, which is defined as the product price, color and size. This can be a simple example of how a data layer will be defined on a website. The other option, a complex one can be in this manner, this can be for e commerce websites, where we have multiple products, and for which we are defining all this information like name, prize, color and size. This is how data layers can be written and used on different estim codes of different businesses. Every business is going to be different, so they will be writing their data layers in a different manner. Let's see practically as well how this will look like on our website. On the website, if you have to look at data layer, you can go to Inspect Element, and here we can go to Console. We can go to the console and we can search for data layer. When we go into the data layer part, this is where you can see the data layer out here. These are the objects which we're talking about, which is numbered in this manner 012. Now if you click on any of each of these individual objects, the further you can see the information out here. Like here, we can see the particular information given out here for this object, then number one, this is another object for which the information is given here. This is how you can easily find out a data layer by going to the inspect element where we can search in console. I hope this makes sense. I hope you understand the concept of data layer and what is the use case of it? How it makes things easier for us when we're setting up GTM tax. Thank you so much, guys for listening into this session, and I will see you in the next video. 38. Using Data Layer with GTM: Hi, guys. Welcome to this session. In this session, we'll see how we can make use of the data layer in our GTM account. So once we log in to our account, we first need to create a variable. Let's go to variable section. And here we are going to define a user defined variable. So we're going to do that by going to the configure and go to new. So this will be a data layer variable, which we want to do. Now here, we will have to define the data layer variable name, which we have to provide. So for which we can go to our website and look at the variables first. We can do a inspect element. Like we saw in the previous video, we'll go to Console and go to data layer. In this particular manner, we can see the array over here. And we will find all the information. In this particular manner, there are different objects which we get to see out here. Let's say we are looking at a particular object. This one. Let's say the third object in which we need to create a variable. We have to take the exact name over here, so like we're taking this one as the name. And we can give it a name like that. And we can save it. That is the first information. Same way, we need another one so we can create another one out here. Let's say the second one, scroll threshold, and we give it a name. DL is for. And we can save it. Now you can see, we have created two data layer variables out here, which we would like to use in our Google Tag Manager. Now we can do a preview of this to see how this will work out. When we do a preview, we can add our website. Now this is fully loaded, as we can see here, and if we go to window loaded in data layer section, we will be able to see this information. 39. Custom HTML Tag - Executing HTML and JavaScript: Hi. Welcome to this session. In this session, we'll see how we can make use of a custom STML tag on a GTM account. A lot of times it happens that we might have to implement a specific code on the website or a Java script code on the website. In such a case, we can make use of the custom STML tag out here. So let's have a look at this. Once we are inside the Google Tag Manager account, we can go to the tag section where we are going to create a new tag altogether. Now this tag is going to be a custom HTML. This is where you can add your code, which can be an STMA code or a JavaScript code in this particular manner. And now you can apply this on all the pages, and we can name this as custom HTML. Once you do this, you can preview the website to have a look at it, so the code will now fire on the website, and we should be able to see the information out there. In this manner, on the website, you can be able to see the information out here. This is one way where you can apply a custom HTML. The other option if you see now in the back end, the code has fired over here, and we can see the HTML out here showing up. This means it is implemented on our page. The other option is in the same manner, you can go ahead and add a Java script code. You can add in the same place, you can add a Java code from a third party tool and implement that on your website. This way, we can add some custom codes on our website for various reasons, which might be needed for the business. I hope this makes sense. I hope you understand how custom estL codes can be implemented with the help of Google Tag Manager. Thank you so much, uys for listening into this, and I will see you in the next video. 40. Thank You!: Hi, guys. If you're watching this video, that means you've come to the end of this class, and I would like to thank you for taking up this class, and I hope this information was useful. You're able to understand how GTM works and how you can use it, implement it in your business, and for your clients. So thank you once again, guys, for checking out my class and have a great time learning ah.