
May 6, 2021
16 Most common Google Tag Manager mistakes
Updated: May 6th, 2021. We’ve all been there: you open Google Tag Manager, set up tags, triggers and variables properly (at least you thought so), but that new implementation doesn’t work. You read that super awesome 5-step tutorial few more times, but it doesn’t help.
You feel stuck, irritated and decide it’s enough GTM for today. The next day you open GTM, take a fresh look and realize you did a stupid and obvious mistake (which could have been fixed in a blink of an eye). I’ve been there. Too many times. That’s why I’m sharing a list of the most common Google Tag Manager mistakes I’ve committed or I have noticed that others are doing them. Let’s hope this blog post will save you some time and energy.

Table of Contents
Here is the list of common Google Tag Manager mistakes that are covered in this blog post:
- Viewing the wrong Google tag manager account
- The container is not published
- Using Data Layer variable before its respective dataLayer.push occurs
- Not using preview and debug console properly
- Not using other debugging tools
- Not checking Google analytics real-time reports
- Not removing old Google Analytics implementation (completely)
- Not using the GA Settings Variable
- Using dataLayer = []; and putting it after GTM snippet
- Using too many auto-event listeners
- Typos (duh…)
- Not cooperating with developers
- Not Using Regex in order to reduce the number of conditions/triggers
- Publishing all the changes at once
- Tracking forms with Click Trigger
- Not having a proper naming convention
- Final words
MISTAKE #1 – Viewing the wrong Google tag manager container
This mistake is popular among newbies and/or multi-taskers. The problem of “GTM Preview and Debug mode is not working” might be caused by a distraction and the wrong GTM account/container.
If you track multiple websites and/or have access to multiple Tag Manager accounts, you might be using the snippet from another account and/or container (by accident, of course). Double-check whether ID in your GTM account is the same as in the Javascript snippet that is hardcoded on a site.
MISTAKE #2 – Container is not published
So you’ve started working on a new project, set up all triggers, variables, tags, etc., but you get way too little data (as if only your browser is being tracked. But what about all those other visitors?). This has probably happened because you didn’t publish the container.
Once you do a significant portion of changes in your GTM container, TEST it and then go Live by pressing the Submit button in the top-right corner of the GTM interface (+ complete all the steps that you will be asked).
Another tip – right after you (or your developer) adds a GTM snippet to a new website, publish a version of the empty container (with default settings).
If an unpublished GTM container’s snippet is placed on a website, you’ll get a 404 error (GET http://www.googletagmanager.com/gtm.js?id=GTM-XXXXXX) in the browser’s Javascript console (learn more about that here). This isn’t a big problem, but if your developers are tracking Javascript errors with particular tools (e.g. TrackJS), they’ll see those 404 errors in reports. This will create an unwanted noise for them (yes, I know they can use filters, but simply publishing an empty container won’t hurt anybody 🙂 ).
MISTAKE #3 – Using Data Layer variable before its respective dataLayer.push occurs
Here’s another common mistake. You have a tag that fires on the Container Loaded event. The tag is using a data layer variable, that accesses the page_category key from the data layer.
So every time a page_view event is fired, you also send the page_category to, say, Google Analytics 4.
But here’s the problem. page_data dataLayer.push (that contains the page_category) occurs only after DOM Ready. This means that on Container Loaded, page_category is not available yet, therefore, you will always send undefined with the GA4 tag.
It’s important to understand this. You can use a certain Data Layer variable only after that particular data is available in the Data Layer. What options do you have in this case?
- Either fire a tag on that particular dataLayer.push that contains the page_category key
- Or ask a developer to activate that dataLayer.push code before the GTM container snippet is loaded

MISTAKE #4 – Not using preview and debug console properly
When an event is selected in the left column of the Preview and Debug console, the Tags tab will show the tags present during that event. They are split into Tags that fired and Tags that did not.
This is the place where you should look for the answer to Why didn’t this tag fire? A tag will be fired only if all conditions of a single trigger are met. A red X icon indicates which conditions weren’t satisfied. Use them as clues and find out how you can fix the trigger.
I apologize a bit for the outdated screenshot of the preview mode. But in my defense, that does not change the essence here 🙂
If you want to learn more about proper debugging in GTM, feel free to read this guide.
MISTAKE #5 – Not using other debugging tools
GA debugger and Data Layer Inspector are among the most popular debugging tools you should be aware of. Both of these are free Google Chrome extensions that will make your life much easier.
Data Layer Inspector is like a Swiss army knife that adds additional information to the browser’s console, also allows you to temporarily inject the GTM container on any site, debug other analytics tools (including server-side setup), etc. Learn more here.
As for GA debugger, when it comes to Enhanced E-commerce tracking, GA debugger is irreplaceable for me (together with the GTM/GA debug). When enabled, it displays all data that is passed to Google Analytics, thus I can troubleshoot much faster.
In fact, I have prepared a comprehensive list of Chrome extensions and tools for GTM. Take a look at this list here.
Also, a bunch of debugging tips is explained here.
MISTAKE #6 – Not checking realtime reports or GA4 DebugView
I’ve seen a lot of beginners not checking their GA real-time reports or GA4 DebugView once they have implemented Google Analytics tracking via GTM. They had a false perception that once the GA tag fired (according to the Preview and Debug console), their task was completed.
But that was very far from the truth because in some cases, they were accidentally sending data to the wrong Google Analytics property. Constantly checking real-time reports prevents this issue. And in other cases, they were not seeing data at all (because of filter misconfiguration in GA).
If on the other hand, you are checking GA real-time reports but they are just not working, read this guide.
If you are working with Google Analytics 4, then the DebugView is your friend. If you want to learn more, take a look here.
Lastly, other tools that you want to implement (e.g. Facebook Pixel) can also offer real-time debugging features. Always use them.
MISTAKE #7 – Not removing hardcoded tracking codes (completely)
If you have decided to migrate from hardcoded Google Analytics (or some other tool) to a more flexible implementation via Google Tag Manager, beware: the process won’t be easy. This warning does not apply to small websites with basic tracking – just simply add GTM container snippet, publish Google Analytics tag (or some other tool’s tag) and simultaneously remove hardcoded tracking codes from a website.
But if you’re thinking about migrating a larger website with more complex tracking, a lot of things can go wrong. My e-book for Google Tag Manager beginners covers some points related to migration.
The most common issue (from my experience) was not removing all hardcoded link tracking events which caused data duplication. Some of those hardcoded events were simply missed by the developer.

MISTAKE #8 – Not using the GA Settings Variable in Universal Analytics
If you have ever tried to use Google Tag Manager, you’ve probably noticed that for every Universal Analytics tag, you need to set parameters/settings individually, e.g. Tracking ID, cookie settings, Cross-domain tracking parameters, etc.
Back in the old days, this was super difficult to manage. You had to create a bunch of Constant (or other types of) variables and manually set in every GA tag.
Eventually, things have gotten much easier with the help of a Google Analytics Settings Variable. This is a central place where your GA settings are kept. Whenever you want to create a Universal Analytics tag, you just reuse the same GA Settings Variable that contains parameters like Tracking ID, etc.
To learn more, read this guide.
MISTAKE #9 – Using dataLayer = []; and putting it after GTM snippet
Data Layer is a fundamental ingredient of a successful Google Tag Manager implementation. A data layer is an array that contains all of the information that you want to pass to Google Tag Manager. Few examples of what data can be passed to dataLayer:
- User’s pricing plan
- User’s registration country, etc.
What can you do with that data? Anything you like!
For example, you can pass the user’s pricing plan as a custom dimension to Google Analytics. However, there’s one catch (and if developers make this mistake, your entire GTM event tracking will break).
If a developer adds custom information to the Data Layer like this (I mean dataLayer = xxxxxx):
var dataLayer = [{ 'pricingPlan' : 'premium', 'registrationCountry' : 'Lithuania' }];
…and places this code snipper below the Google Tag Manager container JavaScript code, the Data Layer will be broken.
No new events will be visible in the Preview and Debug mode. In other words – things will go wrong.
So it’s important that dataLayer’s snippet (as shown below) would be placed above the GTM container snippet (according to Google’s recommendation):
<script> dataLayer = [{ 'pricingPlan': 'Premium', 'registrationCountry': 'United Kingdom' }]; </script> <!-- Google Tag Manager --> ... <!-- End Google Tag Manager -->
Even a better option (MUCH MUCH BETTER) is to command dataLayer with dataLayer.push method. If you need any particular data to be passed to the dataLayer, ask your developer to use the dataLayer.push method instead (see the example below).
window.dataLayer = window.dataLayer || []; dataLayer.push({ 'pricingPlan': 'Premium', 'registrationCountry': 'United Kingdom' });
Are you a little tired? If yes, then bookmark this blog post about common Google Tag Manager mistakes and come back later. If not, let’s roll!
MISTAKE #10 – Not monitoring page performance after adding additional codes/tags to GTM
When you started using Google Tag Manager, you probably saw statements like “Google Tag Manager optimizes page loading speed”.
The reality is — “it depends”. I have done a bunch of tests and saw some improvement when you compare hardcoded tracking snippets (added directly to the website) vs tags added to GTM.
Nevertheless, every added code piece to a website negatively impacts page loading speed. So if you add a bunch of different pixels, like Facebook Pixel, GA3, GA4, Reddit Pixel, Quora Pixel, Linkedin insight tag, and a bunch of other stuff, your page loading time will increase by A LOT.
So after you add some new tags, it is a very good practice to take a look at your page speed. Actually, you should run several tests before adding the codes and then compare them to what happens after you publish your changes.
I have published an article about GTM vs Pagespeed, so take a look there.
MISTAKE #11 – Typos (duh…)
I’ll be quick here. When a tag doesn’t fire, always check for typos in:
- Trigger’s conditions. If you’re using regular expressions in your conditions, double-check whether you need standard regex or ignore case option.
- Names of variables. This usually happens with Data Layer variables for me.
Also, keep in mind that the majority of fields in GTM are case-sensitive (or maybe all of them? I’m not sure.). This means that the S letter is not the same as the s.

MISTAKE #12 – Not cooperating with developers
A lot of marketers and digital analysts started using Google Tag Manager (probably) because they believed the promise that they will not need to rely on developers anymore. Ever.
The reality is quite the opposite. Even though Google Tag Manager greatly increases flexibility and the agility of marketing teams, developers might still be needed. Especially, when you have to deal with more complex setups or projects.
Google Analytics Ecommerce implementation is a good example. If you’re working on a custom e-commerce platform, you WILL need to work with developers and ask them to push the transaction/product/checkout/etc. data to the Data Layer.
Trying to implement everything on your own (and scrape the website for some data) will result in fragile setups that can easily break.
Another thing – ask a developer to quickly review the custom JavaScript code you found online and now plan to implement via Custom HTML tag. I’ve seen way too many cases when marketing teams added some unknown script and temporarily broke some features (or the entire frontend) of a website.
The end result of this? The marketing team lost access to publish GTM container changes. Marketing/analytics teams and developers should be friends, not enemies.
MISTAKE #13 – Not Using Regex in order to reduce the number of conditions/triggers
What happens when you want to add multiple conditions to fire one tag? Usually, people create either multiple conditions in a trigger or assign multiple triggers to the same tag.
Technically, this will work, but there is a more optimal way to do that, regular expressions (RegEx).
Instead of having, say, multiple “contains” conditions, you can match different data with just one Regular Expression. If you want to have multiple conditions connected with “OR”, you’ll have to either create separate triggers and assign them to the same tag, or you can use just one trigger with a regular expression.
Aleksandrs Pasters has explained how you can utilize regex in GTM. You should definitely check it out. Also, I constantly use Regex 101 online validator to check whether my regular expressions are configured correctly.
If you want to learn more about all the possible options on how to create “OR” conditions in Google Tag Manager, read this guide.
MISTAKE #14 – Publishing all the changes at once
When you work on a bunch of new tracking features for a week and then publish all of them at once, I call this “big bang” deployment.
And this is not a good thing. If something goes wrong with your newly published container version, you will have to revert the entire version (including things that were working).
The rule of thumb that I follow: work with smaller portions. If you implement X tracking functionality, publish it. Then start working on another one. In that case, if something goes wrong with your latest version, your previous smaller batches that you published will still be live and work fine.
MISTAKE #15 – Tracking forms with Click Trigger
This mistake is popular among beginners who tried and failed to use a built-in Form Submission trigger in GTM. What they do not know, is that the Form Submission trigger sucks and does not work with the majority of online forms. At least that’s what I’ve experienced.
And what do beginners do after the built-in trigger form does not work? Apparently, they choose a Click trigger as plan B, which is a super bad idea. Why? Because click trigger tracks all clicks of a Submit button (not only successful submissions)
If a visitor tries to submit the form but accidentally leaves a required field empty, the click trigger will be activated anyway. As a result, you’ll have way too many form submissions/conversions which are false positives.
Solution? There is a bunch of other techniques on how to track forms with Google Tag Manager. Just try one of them.
MISTAKE #16 – Not having a proper naming convention in place
Working in a GTM container that has a lot of tags/triggers/variables but as no decent naming convention is a real hell. Imagine that you see a tag called “contact”.
Contact what?
Is that a form submission of the contact form? Is that a click on a “contact us” link. Is that something else?
If you have 10 or 20 tags, even the most terrible naming of your GTM assets can cause no problem. But when you deal with 100+ items, you will waste more time.
But you don’t always know whether the new GTM container that you have just created will eventually become massive. So start using proper naming conventions from day 1.
I have published a guide about GTM and GA conventions that you might find useful.
Common Google Tag Manager Mistakes: Final words
In short, we all do mistakes. If I got a penny for every mistake I’ve made… I’d probably have two pennies right now.
Just kidding! I’d be a millionaire. Mistakes teach us valuable lessons, that’s why I wanted to share this list with you. Hopefully, you’ll manage to avoid them.
Remember, it’s much cheaper to learn from the mistakes made by others.
Do you know other common Google Tag Manager mistakes?
Have you come across any other common Google Tag Manager mistakes? I’d really like to hear them and add them to this list. You can contact me via Twitter, LinkedIn, o just simply post a comment below.

69 COMMENTS
Thanks a lot for this post!
I have question regarding a situation I just encountered. Please forgive my excessive laymen:
I have pasted the SAME GTM snippet, to various domains, each of which has it's own Google Analytics tracking ID.
I created a click event tag, linking it to only one GA Tracking ID (Website A), thinking that only events from that website would be triggered. Websites A, B and C were once properties in the same GA Account (they're from the same series of GA tracking ID numbers), but now are spread among three accounts. Website D is from a completely separate Account.
The Events ended up triggering in all websites, but all the data merged in Website A's GA account. The rest didn't record any Events.
Secondly, Website B's GA account registered sessions from all the other websites, effectively doubling my total sessions in Website B3s account.
Website's C and D did not record any Events or extra sessions.
Any idea of what might've happened here?
Hey, honestly, that sounds like playing with matches. I'd say that your triggers are misconfigured somewhere but there might be many other reasons.
My personal best practice approach - use different GTM containers in different websites IF those websites have different structures/functionality.
For example, in a company I'm working in, we have one container for website, one for blog, on for the main product, etc. They are all very different in structure, content, features, so it's more logical for me have different tags, triggers, Google analytics tags, etc.
In addition to that, all those different GTM containers are using the same GA tracking ID.
Hi,
I get a [javascript][/javascript] at the footer of all pages ever since I integrated the tag manager snippet. Everything works fine but I cannot get rid of this annoying text at the bottom of all pages. Any ideas?
Thanks,
Peter
Hi, Looks like one of your Custom HTML tags is injecting that text. Try disabling them one by one and see it if helps. You can do this check with help of GTM Preview and Debug mode.
Hi,
I already installed tag manager. However, the click classes can't detect :'(
And how i can get the publish button...I can't find out where it is.
Hey,
Does that element have a CSS class that you're trying to track?
If you're not seeing publish button, then it looks like you don't have a full access to the container. Someone share with you only limited access.
Cheers
Hi Julius,
We just started setting up GTM and already have a GA account. I created a Tag for our Youtube page which aligned with a goal (conversion) set in GA. I ran preview mode and confirmed that the tag is tracking in GTM and afterwards published to the Live site. However, I was looking in Real-time reports and it appears to not be tracking in GA. Why would that be?
Side note: I did remove all of GA and have since placed it back in until I can figure out a solution.
Thanks,
Brandon
Hi, maybe this will help https://www.analyticsmania.com/post/google-analytics-real-time-reports-not-working/
For multi-location companies, can you load more than one Google tag manager onto a site?
Yes, but they will use the same dataLayer, therefore conflicts might happen.
Hi Julus,
This is probably a dumb question, but when I click through my site, the GTM code appears but the entire page then reloads and it refreshes the debug console - thus erasing the event triggers.
What am I doing wrong? This is happening on the past 2 sites.
Hey, don't worry. This behavior is expected. When you refresh the page, he preview and debug mode refreshes as well. You're not doing anything wrong!
Hi Julius,
One question after analise a GTM from a client.
It's possible to use a unique GTM in multiples URLS tottaly different one from other? Off course every one has a different GA.
Ex:
www.url-1.com
www.url-2.com.br
www.url-3.net
www.url-4.org
Thanks in advance.
Junior
Yes, that is totally fine.
Hi Julius,
those are very interesting tips, but I think I have a different kind of problem.
We run our local environment in a different URL than the production site, after changing our hosts file. And I cannot make GTM work with this setup (at least not the debug & preview mode), because seems like it doesn't understand it's the same thing.
It's like if 'analyticsmania.com' was your public URL, but you type 'am.com' to open it in your local server.
Is it possible to use GTM like this?
Thanks in advance!
Yes, it is possible. Preview and debug mode is using 3rd party cookies, therefore it does not care about different domains.
What does the js console show when you try to enable preview and debug mode in the local environment?
Are you sure that developers have added the gtm code snippet to the local environment? You can check that with the Tag Assistant chrome extension.
After struggling for 2 days I could make it work by disabling a chrome extension (DuckDuckGo Privacy Essentials). I tested a few times and every time it was disabled the debug mode worked fine.
Followed a tip from a comment on one of your other posts: https://www.analyticsmania.com/post/google-tag-manager-preview-mode-not-working/#comment-6524
Thanks Omkar and Julius!
I went through and checked the list and it appears I haven't made these mistakes with my Tag Manager. I'm having a problem when that when I go in to my Google Analytics page I'm only able to see Real time data. It will accurately show when tags are fired such as the page views and clicks on particular links I have on my site. The problem is that I can only see the real time data and the option to see "Events (Last 30 min)." I set up my tag manager and analytics page a day and a half ago. Is this why it's not holding any data yet? It seems like I'm doing it right I just can't tell if I will be able to see the Behavior information.
Thank you!
This is not ok. My guess would be that you have enabled a particilar segment in your GA reports and because of it you don't see any data in behavior.
Thank you for your reply. I looked into it and changed some things as mentioned. But I think I found out what my rookie mistake was! For some reason the date range for the reports was showing yesterday and the previous days before that. As mentioned I just setup my analytics yesterday. I didn't have the current date selected in the upper right hand corner on my report page. I changed it to today's date and ta-da! my data appeared!! An embarrassing noob mistake.
Thanks again for helping and your quick reply! Your info was really helpful.
Hi Julius,
We've always had google analytics goals set up and now that we're using GTM a question came up.
As we set up GTM and triggers, will this affect the GA goals?
If you send events using the same category/action/label, then your GA goals will not be affected.
Hi
what is "Only fire this tag in published containers" GTM?
thanks
Hey, here's a quote from Google's help:
"If firing a particular tag results in a fee being charged, you can avoid firing it in testing environments (e.g., during previewing and debugging). Instead, when applicable, Google Tag Manager will tell you when the tag would have fired. For the most accurate testing, leave this option unchecked."
Hope that helps.
I did not understand
Would you please say your own deduction?
thanks
Let's say that you have a particular tag which costs you money to fire (because maybe you're paying that tool a fee per submission, etc.).
You don't want to actually fire that tag on testing or development environment because you don't want to spend money on fake submissions of your employees.
So what you do is that you enable this checkbox. When it's enabled, the tag (in testing environments) will be displayed in the Preview and Debug mode as "fired", but it won't send the actual data to that 3rd party tool, therefore, you won't spend money on fake submissions.
hi. I have a problem. After I installed google analytic by google tag manager, every time I enter my website and click something, google analytics include my clicks. How can i solve this problem?
Hey, are you sure you haven't implement click tracking via GTM? If that's not the case, I'd say that your website has some hardcoded click tracking or some plugin which does that automatically.
Before I install Google Analytics by GTM, I did not had this problem. I have installed Google Analytics by GTM on two of my website and I have the same problem. You have never had this problem?
I do not know what you mean by click tracking via GTM. I have just done the same process that all website teach us about installing GA by GTM.
How can I find that my website has some hardcoded click tracking or plugin?
Thank you for your help.
Could you explain then, what you mean by saying "you installed GA by GTM"? How did you do that?
If there is a plugin, you could check in your content management system's list of plugins. Or contact a developer who developed that website.
To find out if you have hardcoded click tracking is to temporarily remove GTM code and check GA reports again. If you see the clicks, then you probably some hardcoded click tracking. There are other ways to check but they are more technical and require a deeper dive into the source code, so I'll skip them this time.
Hi Julius,
My All variable always show Undefined as like click ID variable is undefined.
When i select Form Submission trigger and then i select all Form but my trigger is not show in Debug mode left Side this gtm.formSubmit?
I am new In GTM.
Hi, Click variables will return some value only if:
1. You click some element and you have enabled at least one click trigger
2. AND that clicked element has some attribute like ID, Class, etc.
Form trigger does not support all forms. Here's a guide explaining various form tracking techniques
No need to worry about being new in GTM. We've all been there. Just continue reading/learning and you'll be good.
If you're in a hurry, my GTM course will save you time learning GTM and will show you many shortcuts.
I m facing issues with my data counts. Some time the stats of event tracking matches with back-end data .. but some some I see huge difference. I want to make sure every tag must fire its pixel / GA events on triggers . Is there any method where I cam make browser or code to make sure every applicable GTM pixel firing appropriately.
It's next to impossible to guarantee that your tracking data will be 100% accurate compared to the backend data (due to browser nuances, JavaScript isn't very reliable too, visitors might be using blocking extensions, etc.). it is acceptable to have 5-10% discrepancy (depending on a project).
But if you have a larger discrepancy, you need to thoroughly test your implementation. Here's a guide with various tools/ideas.
Hi Julius,
I have a question on how I see reporting/metrics of GTM Tags in GA. I use Pardot, Salesforce, GTM, and GA. When I have a marketing campaign, for example, CES 2019, this is my workflow:
1) Create a campaign in Pardot and copy the tracking code
2) Go into GTM and create a new Tag (custom HTML) so I can incorporate the Pardot tracking code. Trigger “all page views”.
I then distribute the landing page with the CES 2019 campaign on LinkedIn, our blog, Twitter, and Facebook. I should mention we have the universal GA tag set up with our site, and I have Twitter and Facebook linked.
Where Google Analytics should I see reporting on the GTM Tag? I would like to see in GA which distribution source had more views. In GA, Behavior/Events tab is empty. Do I need to only use the featured Google Analytics Tag for something to populate in Events?
Thanks in advance!
Hi, I'm not familiar with the Pardot but I guess that the custom HTML tag's data will be visible somewhere in Pardot, not GA. If you want to see some attribution data in GA regarding CES campaign, you should tag all your campaign links on FB, Linkedin, etc. with UTM parameters. Read more about them here https://www.annielytics.com/guides/definitive-guide-campaign-tagging-google-analytics/
Hi Julius,
I'm new to GTM. My employer is separating from our agency and I am taking over the marketing. How do I transfer the GTM without duplicating or losing data? I think the agency may not have used best practice - create a GTM for our company and add their agency as a user. If they added my client's Hubspot website (which they created) to their GTM account, is there a way to remove their GTM without losing data and add a new one that I create?
Can you explain the situation a bit clearer? So there is an agency, then you as their client and then you have some additional clients?
It does not matter who created the container, they can be removed from it in GTM. So why don't you just take over the container that was created for you by the agency? Ask them to make you the admin and then remove them.
Hi Julius,
I've set up some Google Ads Conversion Tracking tags, and they're firing with the correct triggers, but nothing seems to be tracking in Google Ads. I've got the correct conversion ID and Labels assigned to the tags, and I've published the latest version on GTM (including a conversion linker tag on all pages), but nothing is coming through when i check conversion actions on Google Ads. Google Tags assistant is also telling me nothing is wrong. Is there something I'm missing?
Cheers,
Chris
Just by firing those tags, nothing will be displayed in Google Ads. You need to actually click your live ad, then fire the conversion tag and only then you'll see the conversion in your GAds reports (with some delay).
Hi Julius,
I am new to GTM and in project also. GTM is added for e-commerce project. My Code is working absolutely fine on stage environment. Decided to deploy same code on live environment. There I am getting issue, On live environment Only "page view Requests" tab is showing and "Events" tab is not showing up on Google Tag Assistant. Because of this we are not able to do any tracking.
Will it take 2-3 days time? Or if in 2- 3 days problem will be still there, then what will be the solution for this?
Thanks
Achla
There's no need to wait 2-3 days. Make sure you have published your container changes to the live environment too. If you are using GTM environments feature, you need to choose to which environment you're publishing your changes.
If you're using a totally different container for the live site, you need to copy your changes from the test container to live container.
Hi,
The data layer for page view is firing after the page view event. How could I push this along with page view so that when my tag fires on page view event I get the data layer to info to use.
could you please recommend something.
You need to ask a developer to activate that dataLayer.push (with your custom data) before even Google Tag Manager container is loaded. In other words, that dataLayer.push code should be placed above Google Tag Manager container snippet.
Hi,
I have an analytics account and tag manager account.
Let us say, I have added Google Analytics Snippet to my website. (The GA will start reporting the date)
And,
I want to use the tag manager account only to collect the triggers/events. I will just create a variable for my GA ID and I will use this variable to create different tags.
My question.
Now I will have 2 snippets.
1 is for GA.
1 is for Tag Manager. (There is no tag with the track type: page view tag added )
In the above case: Can I use both the GA and Tag manager snippets on the site?
Or,
It's mandatory to add page view tag on the tag manager and use only Tag manager snippet for tracking GA report and Events report.
Please guide me. Hope I will receive an email once you reply to this.
You can have pageview hardcoded in site's code, it will work fine. But in the long run, you'll need to migrate fully to GTM anyway (because once you need to make a custom configuration to the pageview, you will not be able to do that via GTM and will have to modify your hardcoded snippet)
Hello, I have question about the GTM container id.
I added GTM Snippet to my website ( head and opening body script)
And download the WASP to check if the GTM installed correctly or not.
but my GTM container id which I can see at GTM manager page and GTM id of my website what I can see through the WASP is not matched.
For example, correct GTM id is GTM-MK00000 and I added the snippet which include GTM-MK00000 to my website at the correct position. but when I check container id of my website through WASP, it shows that GTM Container (gtm): 2ou1m0.
I'm not sure what is problem...
please help
WASP is too difficult for beginners. Use Tag Assistant and you'll be fine.
I already installed tag manager.
I can't find out where it is publish button.
If you don't see the button, this means that don't have full access to the container (not enough permissions). Ask your coworker or client to give you "publish" permission. Or create a new container.
I'm curious about your Rule #13. Have you done any tests that show regex is faster than multiple more simple trigger rules?
Rule 13 is not about speed. It's about easy of tag management.
Speedwise - 10 triggers vs one trigger with regex will not make a big difference.
Hi Julius,
I have a question regarding the Click buttons that appear on the left side of the debug mode.
I recently added a new GTM container to our website, while all our pageview tags are working fine but when I make clicks on the website (in debug mode) I don’t see the ‘Click’ getting recorded on the left side of the GTM debug window. Can you please advise what could be the reason behind it?
You need to create a click trigger in gtm
Thank you, Julius.
I wasn't referring to a specific tag that is dependent on a click. Rather, when you have the website in debug mode, wherever you click on the website a corresponding click gets recorded in the debug window. So, that part is not happening. And without that I am not able to determine the click variables associated with the click, to thereafter use in a click trigger.
As I have said, you must have at least one click trigger in a container to start seeing click events. With or without a tag. So just create a trigger.
Thank you once again, Julius.
I wasn't aware that without a click trigger (with or without a tag), the click doesn't record in the debug mode.
I am able to see the clicks now.
Yes, this one of the fundamental things that many GTM usres don't realize and that I focus a lot in my GTM course for beginners.
Hi Julius, how are you? Thanks for sharing this post with us!
I set-up my GTM with basically three conversions: Contact Form, WhatsAppbutton and click email. But I found that some users, use in the same session CF and WhatsApp to contact with us, triggering 2 conversions when actually is one.
Is there a way to stop triggering one of them to avoid counting two times?
Thanks!!
Here is one which has given me a migraine, and it's silly.
I was trying to track a click event on a tag. Nothing was showing in up vars in tagman on the click event; they were blank. I couldn't understand it.
Every now and then, they would pass though, I'd try again, and they wouldn't show up the next time. It was driving me insane.
I looked more closely and see there is a tag wrapping the text inside the button, and most of the time, that is what I (the user) was actually pressing!! It was showing up sometimes because I would press the button on the outer edges, missing the span.
I added the class trigger name to both the span and the button... done!
Hi Julius,
Im using GTM & Universal Analytics to track conversion from Google ads.
I setup goals in analytics of 6 types which is Destination, Duration, Pages, Events, & Smart Goal.
Do I need to create a trigger in GTM for the 6 of them?
Thank you so much!
Hi Julius,
Thanks a lot for your amazing content on Google Analytics, it is always most helpful - both articles and videos! I've learned so much from you over the past few months.
I was wondering if you could give me a piece of advice, please... I am fairly new to GA/GTM and am stuck in a situation where both Gtag and Gtm snippets had been installed on a website and I cannot possibly get developers remove the old GA tracking as it's not on the priority list (I realise it's bad practice).
I tried using GTM without firing a Pageview tag (as 'in theory' gtag should cover that basic data collection) however now I'm seeing thousands of users with only a handful of pageviews. Could this be caused by using both snippets at the same time? Or is that a deeper issue with tracking that I need to investigate? Prior to publishing event tags (but gtm container published) the numbers looked fine.
Thank you!!
Hi, gtag base tag alone should not be the problem. Further investigation required.
Thanks for getting back to me! That's some relief on my end, but going to keep digging deeper.
Thanks again!
Thanks for getting back to me! That's some relief on my end, but going to keep digging deeper.
Thanks again!
hi julius :)
I have a question:
Is Google Tag Manager required for the site?
thank you dude
Hi, Julius, I read all of the above mention mistakes about the google tag manager but did not find a solution. I am trying to track button clicks but can not add variable configuration. Can you please tell me how I can resolve this issue?
Hello, I am working on Vue application.
I have configured gtm in html file,and pushing the random data into datal ayer using event key in one of my vue component.
in this way the data is getting populated after container loaded.
but is there any way to push the data before the gtm snippet code in html file?
I am not a developer. You should find a way to activate GTM container snippet after the dataLayer is initiated.