Article
Google Tag Manager Custom Event Trigger Explained
analyticsmania.com
Quoted on this wiki
Every place a page here uses this source, in the order the words come in it.
Before you ask a developer for adataLayer.push(), you should always try to use GTM’s built-in triggers first. Here’s a simple decision framework: “Can the interaction be tracked with a URL? Yes:(e.g., a “Thank You” page visit). Use the page view trigger and filter by thePage URL.” Is the interaction a standard click on a link or button? Yes:Use the built-in click triggers (All ElementsorJust Links). In GTM preview mode, click the element and inspect the available click variables (likeClick Classes,Click ID, orClick Text) to find a unique and stable condition for your trigger.
Well, I cannot say that the aforementioned statement is a lie. But I can’t say that it’s 100% true, either. There is no black and white. “You can track many web interactions without the developer’s input, and that’s awesome!” Why is this the best method? A developer can trigger the dataLayer.push from the website’s backend code at the precise moment a successful action occurs. This eliminates the guesswork and fragility of trying to listen for changes in the website’s front-end, making sure your tracking is more accurate and less likely to break during a site redesign.
If you spot a non-standard interaction that cannot be tracked with ready-made tracking solutions (like GTM Recipes), work side-by-side with a developer: “Explain to them which interaction you wish to track and what additional data you are expecting.” Give them a little piece of Data Layer event code.