Last updated: 2026-04-06
Reference
Global Triggers¶
Global Triggers are reusable trigger configurations that combine events, conditions, and exceptions into a single definition. Define a trigger pattern once and reference it across multiple rules.
When to Use Global Triggers¶
Global Triggers are useful when:
- Multiple rules share the same trigger logic -- e.g., "fire on all product pages with analytics consent"
- You want centralized trigger maintenance -- update the trigger definition in one place
- You need consistent trigger behavior -- ensure the same conditions apply uniformly
How Global Triggers Work¶
A Global Trigger encapsulates:
- Event -- what initiates evaluation (e.g., Page View, custom event)
- Conditions -- requirements that must be met (e.g., URL pattern, consent status)
- Exceptions -- circumstances that prevent firing (e.g., internal traffic, specific pages)
When a rule references a Global Trigger, it uses the trigger's full event + condition + exception logic. The rule only needs to define its own actions.
Creating a Global Trigger¶
- Navigate to Tag Manager > Global Triggers
- Click Create Global Trigger
- Name the trigger descriptively (e.g., "All Pages with Marketing Consent")
- Configure the Event (e.g., Page View)
- Add Conditions (e.g.,
CMP.marketingequalstrue) - Add Exceptions if needed (e.g., exclude
/admin/*pages) - Save
Using Global Triggers in Rules¶
When creating or editing a rule:
- In the Trigger section, select Use Global Trigger
- Choose the Global Trigger from the list
- The rule inherits the trigger's event, conditions, and exceptions
- Configure the rule's actions as usual
Global Triggers vs Local Triggers¶
| Aspect | Local Triggers | Global Triggers |
|---|---|---|
| Scope | Single rule only | Shared across multiple rules |
| Maintenance | Edit per rule | Edit once, applies everywhere |
| Complexity | Defined inline | Defined separately and referenced |
Common Global Trigger Patterns¶
| Trigger Name | Event | Conditions | Use Case |
|---|---|---|---|
| All Pages | Page View | None | Basic page tracking |
| Pages with Analytics Consent | Page View | CMP.analytics = true | Third-party analytics |
| Pages with Marketing Consent | Page View | CMP.marketing = true | Marketing pixels |
| Product Pages | Page View | URL contains /product/ | E-commerce tracking |
| Checkout Flow | Page View | URL contains /checkout/ | Conversion tracking |
Best Practices¶
- Name triggers descriptively -- the name should explain when the trigger fires
- Use Global Triggers for widely-shared patterns -- if only one rule uses a trigger, keep it local
- Review before editing -- changes to a Global Trigger affect all rules that reference it
- Document trigger logic -- especially for complex condition combinations
Continue to Platform Extensions for extending Tag Manager with custom functionality.