{"id":34869,"date":"2021-01-26T07:00:36","date_gmt":"2021-01-26T15:00:36","guid":{"rendered":"https:\/\/www.eigene-homepage-erstellen.net\/?p=34869"},"modified":"2020-12-22T12:27:00","modified_gmt":"2020-12-22T20:27:00","slug":"common-google-tag-manager-mistakes","status":"publish","type":"post","link":"https:\/\/www.eigene-homepage-erstellen.net\/blog\/analytics\/common-google-tag-manager-mistakes.htm","title":{"rendered":"Tips for Troubleshooting Google Tag Manager Mistakes"},"content":{"rendered":"\n

Updated on January 26, 2021, to include additional tips.<\/em><\/p>\n

I don’t think I’ll ever stop making mistakes in Google Tag Manager (GTM), which means I’ll continuously improve my tracking abilities from the lessons I’ll learn. Thankfully, there are multiple tools we can test through before publishing to the site. The ability to do so has honestly made me a little too fearless at how creative I get with my tracking configurations.<\/p>\n

Although not comprehensive, this post is meant to guide you through some common mistakes to check through when troubleshooting your GTM configurations. I’ll also provide some tips to allow you to use GTM more efficiently.<\/p>\n

Tools for Testing Google Tag Manager Tags<\/h2>\n
First, I’ll briefly touch on a few tools I use to test tags in Google Tag Manager. I typically use a combination of a few, depending on what I’m testing. I’ll also share a few tips for some advanced tracking across each of these tools.<\/p>\n
Besides GTM Preview Mode, there are a few other tools that you should use in tandem to have better visibility into how hits get parsed. Having the debugger open is most useful for identifying the exact values, events, and registered criteria. For example, it can tell you whether a form submission event gets sent, the exact click ID, the dataLayer values pushed, etc. However, it doesn’t necessarily show you how data will be consumed by the end platforms at a granular level (especially outside of Google Analytics).<\/p>\n
Remember to take advantage of other extensions as well to see how hits register in their respective platforms, such as the Facebook Pixel Helper<\/a>, Twitter Pixel Helper<\/a>, and the Google Analytics Debugger<\/a> (which is especially useful for viewing detailed eCommerce hits in the console).<\/p>\n
Validate Hits in the DOM<\/h3>\n
The Document Object Model (DOM) has plenty of useful reports to use while testing: checking cookie values in the Application panel, identifying element attributes in the Elements panel, returning dataLayer values, and discovering errors in the console testing tags before publishing in the Network panel. For this post, we’re only very briefly touching on the Network and Application panels.<\/p>\n
The Network panel shows you what tags would fire with your current configuration in GTM, even before publishing. The difference is that those tags may not send 200 status codes. Enable debugging in GTM, right-click on the page, hit “Inspect,” and navigate to “Network” at the top of the DOM to view every hit sent out from the page. Once you’ve tested the action, you can enter “collect” into the search bar to filter for GA hits or a part of the pixel that you’re testing (for example, “Linkedin”) to see what hits were sent.<\/p>\n