Trigger
Data & TrackingAlso: Event Trigger · Tag Trigger · Automation Trigger
Quick definition
A trigger is the condition that tells a tag or automated action to fire. In tag management, a trigger watches for a specific event, like a page view, button click or form submission, and fires the associated tag when that condition is met. In marketing automation, a trigger starts a workflow when a contact does something or meets a criteria.
How it varies across Australia
Most Australian businesses using a tag manager have far more triggers configured than they actively maintain. Trigger bloat, where old or duplicate triggers fire alongside newer ones, is one of the most common causes of conversion over-counting and inflated attribution data.
See data and tracking scores across Australian industries →The two contexts where triggers live
Tells a tag when to fire. Watches for browser events like clicks, scroll depth, page views or custom data layer events.
Starts a workflow in a CRM or email platform. Examples: a contact filling a form, a deal reaching a stage, or a customer going quiet for 30 days.
What it actually means
Think of a trigger like a motion sensor connected to a light. The light doesn't turn on until the sensor detects movement. The sensor is the trigger. The light turning on is the tag firing, the conversion event logging, or the email sending.
In Google Tag Manager (GTM), a trigger is a rule you set up that watches the browser for a specific behaviour. When a visitor clicks the checkout button, that click can trigger the purchase conversion tag to fire, which sends the conversion event to your Google Ads or Meta Ads account. Without a correctly configured trigger, the tag never fires and the conversion never records.
In marketing automation platforms like HubSpot, Klaviyo or ActiveCampaign, a trigger starts a workflow. A contact submitting a lead form triggers a welcome sequence. A customer who hasn't opened an email in 90 days triggers a re-engagement flow. A deal sitting in the proposal stage for more than two weeks triggers an internal sales alert.
The trigger is the logic layer that connects observed behaviour to your marketing and tracking response. Attribution, conversion tracking, CRM automation and even retargeting audiences all depend on triggers being set up correctly and firing only when they should.
A trigger is the thing that decides when everything else happens. Get it wrong and your data, your automations and your attribution all drift quietly off course.
How it shows up
Triggers show up in Google Tag Manager as the middle layer between variables and tags. Every tag in GTM has at least one firing trigger and, optionally, one or more exception triggers that prevent it from firing.
In automation platforms, triggers appear as the entry point of every workflow. The trigger defines who enters the workflow and under what conditions. Change the trigger and you change the entire population the workflow reaches.
When triggers are misconfigured, the symptoms show up downstream. Inflated conversion counts in Google Ads. CRM contacts stuck in workflows they should have exited. Retargeting audiences that include people who already converted. Debugging data quality problems almost always starts by checking whether the relevant trigger is firing correctly and only when it should.
The Australian context
Australian businesses using tag managers alongside consent management platforms face a specific trigger challenge. Under the Privacy Act and ACMA's consent requirements, tags that set cookies or collect personal data should only fire after consent is granted. A trigger that ignores consent state fires the tag on every visit regardless, which creates compliance exposure.
Configuring consent-conditional triggers, where the tag fires only after a positive consent signal from the consent management platform, is now standard practice for Australian businesses. Getting this wrong is not just a data-quality issue.
Where people get this wrong
Related terms
Common questions
What is a trigger in Google Tag Manager?
In Google Tag Manager (GTM), a trigger is a rule that watches the browser for a specific event and tells a tag to fire when that event happens. Common trigger types include page views, click events, form submissions and custom data layer events. Every tag needs at least one trigger or it never fires.
How is a trigger different from a tag?
The tag is what does something, like sending a conversion to Google Ads or loading a pixel. The trigger is the condition that tells the tag when to do it. One tag can have multiple triggers, and one trigger can fire multiple tags. They work together but serve different functions.
What causes a trigger to misfire?
The most common causes are over-broad conditions (a page view trigger that matches too many URLs), duplicate triggers running at the same time, and triggers that were never paused after the original campaign ended. A GTM audit looking at all active triggers is usually the fastest path to diagnosing conversion over-counting.
Do triggers affect my compliance with Australian privacy rules?
Yes. Tags that set cookies or collect personal data should only fire after a visitor gives consent. If your triggers are not connected to your consent management platform, those tags fire regardless of consent state. This is a compliance risk under the Privacy Act and relevant to ACMA's consent requirements for direct marketing.
Debrief
Get the next one
No spam. No fluff. Just the next article, straight to your inbox.
Keep exploring
About New Rebellion
New Rebellion is a marketing intelligence consultancy. We build tools, score Australian businesses on how their marketing actually performs, and publish Debrief every day. This dictionary is part of how we work in the open.
How we think →