Analytics and Tracking

Trigger Group

Also called Combined trigger

A Google Tag Manager trigger that holds a tag back until every trigger inside it has fired.

Quick facts: Trigger Group

Category
Analytics and Tracking
Also called
Combined trigger
Level
Advanced
Affects
Tag firing logic, audience quality, debugging time
Where to see it
Google Tag Manager (Triggers), Preview mode
In this article4
  1. How a trigger group works
  2. Why it matters
  3. Where trigger groups go wrong
  4. How to use one well

How a trigger group works

A trigger group is a container for other triggers. You add two or more existing triggers to it, and the group itself only fires once every member has fired at least once during that page. Order does not matter — the group is waiting for a set of conditions to be satisfied, not for a sequence to be followed.

Once it fires, any tag attached to it runs as normal. Treat the group as something that happens once for a page rather than something that repeats, and test the behaviour yourself before building anything that depends on repeats.

Why it matters

Most triggers answer a single question: did this happen? A trigger group answers a more useful one: did all of these happen to the same person on the same page? That is the difference between recording everyone who saw a pricing page and recording only those who saw it, stayed a while and reached the bottom.

It also has a practical use in tidying up dependencies. If a tag needs both a consent decision and a form submission before it should send anything, a group states that plainly in one place, instead of hiding the logic inside a variable that the next person to open the account will not think to check.

Where trigger groups go wrong

They fail quietly, which makes them the hardest triggers to debug. If one member never fires — because a selector broke, or because that element does not exist on the template you are testing — the group never fires either, and nothing in the interface tells you which member is missing. The tag simply does nothing, on a page where everything looks correct.

They are also used where they are not needed. If all the conditions can be expressed on a single trigger, use a single trigger; a group adds a layer of indirection for no gain. And a group that mixes triggers with very different lifespans — a page view and a repeating timer, say — behaves in ways that are hard to reason about later.

How to use one well

Keep groups to two members wherever you can, and name both the group and its members after the condition they represent rather than after the tag they serve. When something stops working, open Preview mode, walk the page as a visitor would, and check each member separately before looking at the group — the answer is nearly always one member that never fired.

Use a group when the combination is genuinely the thing you want to record, and prefer a clear data layer event from the site itself when the condition is really a business event, such as a completed booking. The site knows when that has happened; a group can only infer it.

Do and do not

Do

  • Keep a group to two members where possible
  • Name each member after the condition it represents
  • Test every member separately when the group stays silent

Do not

  • Use a group where one trigger with conditions would do
  • Mix a one-off trigger with a repeating timer
  • Assume the group will fire again later in the visit

Questions people ask about this

When should I use a trigger group instead of one trigger with conditions?

Use conditions when everything you need is known at the moment the tag would fire, and a group when you need several separate things to have happened during the same page visit. Conditions are simpler to read and simpler to fix. A group earns its place only when the combination itself is the behaviour you want to record.

Why is my trigger group not firing at all?

Because one of its members has not fired. The group waits for every trigger inside it, so a single broken selector, a missing element or a condition that never matches on that template will hold the whole thing back. Nothing warns you. Open Preview mode and test each member on its own to find the one that stayed silent.

Does the order of triggers in a group matter?

No. A trigger group waits for all its members to have fired, in any order, during the page. If you need one tag to run before another, that is a different setting: tag sequencing links a pair of tags so one completes before the next begins. Groups control whether a tag runs, not when it runs relative to others.

Related terms

Found this useful?

Share it, or ask an AI to summarise it

Back to the glossary

Knowing the term is the easy part

Applying it to your own site and budget is the work. Book a call and I will tell you what actually applies to you.