The best part is that it can be fully automated to run on a regular cadence, it can send notifications if something doesn’t follow rules you set up in the beginning, and it eliminates careless human errors. Technology Governance will check for your TMS container on every page, verify that your data layer variables are present with data in the right format, and check for any other vendors and their variables. This approach is best if you have a complicated website or multiple digital properties that you want to validate regularly. This approach, however, is still best reserved for spot-checking your Google Tag Manager implementation as it has limitations in terms of scalability, testing under various authenticated states, and differentiating between tags that are firing within or outside of your TMS.Ī solution like ObservePoint’s Technology Governance is the most comprehensive and automated way to test Google Tag Manager, monitor other vendor tags, and verify your data layer. Using a tag debugger is much simpler than using your developer tools to manually scan each page.
Click on the Data Layer to see variables.“Data Layer” should now be an item in your report. Add the data layer object name in the box.Click the TagDebugger extension logo in your Chrome browser.You can also verify that the data layer is present and the variables are populating correctly: Then you can verify that the container tag for GTM or other vendor tags are present.Type in “Google” or your other vendor’s name. Click on the filter button in the Tag Name column.See the tool capturing network requests.After you’ve installed the extension, to check for tags: You can access it by going to the TagDebugger page and adding it to Chrome.
#TAG MANAGER FREE#
ObservePoint’s TagDebugger is a free Chrome extension which will allow you to check for your container tag, vendor tags, and the data layer more easily. Using a browser extension tag debugger is a more efficient way to test Google Tag Manager and other vendor implementations. Let’s take a look now at the next testing method, which is a little less prone to human error. Both of these are concerns if you’re trying to stay compliant with regional privacy laws and only fire tags for users who have opted in. You also won’t be able to tell what’s firing inside or outside of your TMS. Physically click around, type, and look for things.Īnother downside to this approach is that you can’t easily test GTM under various states, for example, as an authenticated user vs. It’s also prone to human error because you have to 1. This approach works and lets you see everything you need to look for, but using the developer tools to test your tags can get a bit tedious if you’re trying to check a lot of tags or check tags frequently. You can also use the Console tab in your dev tools to inspect the data layer object. If you can’t find a tag, you would have to go back to GTM and check your triggering rules.
#TAG MANAGER MANUAL#
The most manual way to test your GTM implementation is to go to the Network tab in your browser’s developer tools and find the container and vendor tags. You can use any of these, but each of them have their pros and cons: Now, there are three different techniques to test your GTM implementation. Are the various vendor tags firing as expected?.Is the data layer present and populated correctly?.The three basic questions you want to answer when testing a tag management system are: In this article, we’ll go over the aspects you should test after you make changes to a tag manager and three ways to do it. When you make updates to your Google Tag Manager implementation, you’ll want to test your tags to make sure the changes worked as expected and didn’t negatively affect existing tracking.
0 kommentar(er)
