An overlooked and relatively under-documented feature of Google Tag Manager (GTM) is the ability to adjust the trigger type of a pageview trigger. The reason why this capability goes unnoticed to many is because the functionality is not as intuitive as the other custom trigger settings available and it is uncommon to have a lot cases that require varying pageview load scopes. While these reasons alone will make the common user avoid exploring deeper into the functionality, a recent issue I ran into related to this feature changed my perception and made me realize that every user should understand this
In the first installment of this two part series, we created our first Google Tag Manager event listener to track all outbound link clicks. In part two, we are going to test this setup and make sure that our trigger logic fires tags with the correct outbound link information. Preview and Debug mode To kick off this process, enter Preview and Debug mode. Preview and Debug mode is Google Tag Manager's default testing console that tracks all on-page events and the tags, triggers and variables that are being triggered with each event. Brief interruption: For information on this tool, as
One of the most important, yet commonly overlooked portions of the Google Tag Manager (GTM) creation process is debugging. It is the final step before your hard work tracking data points pays off and the last thing that anyone wants to invest time in. Commonly referred to as quality assurance or QA’ing, this step in the tagging process requires repetitive mundane tasks to ensure that every possible user experience scenario is tested for and data consistency is validated. Hate it or not, the quality of your effort in this step will make or break your reporting and data quality.
Connor Phillips is a Senior Marketing Analyst located in New York City. He enjoys digging into data and making data-driven marketing decisions. In his spare time he bartends, works on coding and loves to run.