A trigger determines when a GTM tag fires. A page view trigger fires a tag when every page loads, a click trigger fires a tag when a specific button is clicked, and a form submission trigger fires a tag when the form is successfully submitted. Setting trigger types and filter conditions well is the key to GTM quality.
A trigger combines an event type (e.g. click) and a filter condition (e.g. the CSS class of the clicked element is 'cta-button'). If you tag 'all clicks' without a filter, the tag will fire on all link/button clicks on the page, causing data contamination. Accurate filter design determines data accuracy.
GTM location: Manage all triggers in GTM (tagmanager.google.com) → Container → Trigger tab. You can see at a glance the type of each trigger, filter conditions, and number of connected tags. The four most frequently used triggers in weballin practice are page view, click (link/all elements), form submission, and custom event.
Key takeaways
- The firing point is determined by a combination of event type (page view, click, scroll, form submission, etc.) and filter conditions.
- You can restrict tag execution to only specific elements or URL patterns using regular expressions or CSS selectors.
- Exception trigger (Blocking Trigger) blocks tags from firing under certain conditions.
- Connect a dataLayer event to a tag with a custom event trigger.
- One trigger can be shared with multiple tags, reducing duplicate settings.
