{"id":100074,"date":"2025-02-20T20:14:52","date_gmt":"2025-02-20T20:14:52","guid":{"rendered":"https:\/\/peraltafinancing.com\/analytics\/trigger-groups-in-google-tag-manager\/"},"modified":"2025-02-20T20:14:52","modified_gmt":"2025-02-20T20:14:52","slug":"trigger-groups-in-google-tag-manager","status":"publish","type":"post","link":"https:\/\/fivemor.com\/?p=100074","title":{"rendered":"Trigger Groups In Google Tag Manager"},"content":{"rendered":"


\n<\/p>\n

\n

Trigger Group<\/strong><\/a> is the newest trigger<\/a> type you can add to a tag in Google Tag Manager<\/a>. It allows you to establish dependencies between multiple triggers, not firing the tag until every trigger in the group has fired at least once<\/strong>.<\/p>\n

\n

<\/p>\n

\"Trigger<\/p>\n

<\/a><\/p>\n<\/div>\n

This establishes an interesting new paradigm in Google Tag Manager, because until now it wasn\u2019t possible to create triggers that relied on earlier<\/em> values of a given key (event<\/code> in this case). With the Trigger Group, information about triggers that have fired on the page is persisted internally in GTM, and once the triggers configured in the Trigger Group have all signalled completion, the Trigger Group will fire any tag it\u2019s attached to.<\/p>\n


\n X<\/span><\/p>\n

\n
\n The Simmer Newsletter<\/strong>\n <\/p>\n

\n Subscribe to the Simmer newsletter<\/a> to get the latest news and content from Simo Ahava into your email inbox!\n <\/p>\n

<\/span><\/p>\n

How to create a Trigger Group<\/h2>\n

You\u2019ll find the new Trigger Group<\/strong> within the trigger workflow. So, in the Google Tag Manager UI, select Triggers<\/strong>, then NEW<\/strong>, and finally click the \u201cChoose a trigger type to begin setup\u201d option.<\/p>\n

\n

<\/p>\n

\"Create<\/p>\n

<\/a><\/p>\n<\/div>\n

In the overlay that opens, select the Trigger Group<\/strong> option.<\/p>\n

\n

<\/p>\n

\"Trigger<\/p>\n

<\/a><\/p>\n<\/div>\n

Now you should see the configuration screen.<\/p>\n

\n

<\/p>\n

\"Trigger<\/p>\n

<\/a><\/p>\n<\/div>\n

Trigger Groups have a very simple<\/strong> operational logic.<\/p>\n

    \n
  1. \n

    Click the Choose a trigger<\/strong> (or the blue plus) button in the middle of the configuration screen.<\/p>\n<\/li>\n

  2. \n

    Choose one or more existing triggers from the overlay that opens.<\/p>\n<\/li>\n<\/ol>\n

    Every single trigger you add to the Trigger Group will need to fire on the page<\/strong> as many times as it appears in the Trigger Group for the group itself to fire any tag to which it is attached.<\/p>\n

    Note that you can add a trigger more than once<\/strong>. By adding a trigger more than once into the group, that particular trigger must fire as many times as it has been added to the group for the Trigger Group to work.<\/p>\n

    The order of triggers in the group is inconsequential<\/strong>. The Trigger Group will fire as soon as all the included triggers have fired once, regardless of order<\/em>.<\/p>\n

    Once you\u2019re done adding triggers, you can also add additional firing conditions by selecting Some Conditions<\/strong> from the \u201cThis trigger fires on\u201d selection. Any condition you add here will need to pass in addition to the triggers of the group firing.<\/p>\n

    When you\u2019re done, you can add the Trigger Group to your tags. The Trigger Group works just like a regular trigger in that as soon as its conditions are met (i.e. all the triggers in the group have fired), the tag itself will fire.<\/p>\n

    Following the example of another recent article<\/a> of mine, you can create a Trigger Group with a Scroll Depth trigger<\/a> and a Timer trigger<\/a>. The Trigger Group will not fire until both the Scroll Depth trigger and the Timer trigger have fired, meaning you can defer your tag from firing until the user has scrolled a sufficient amount and spent some time on the page.<\/p>\n

    In this example, I have a Scroll Depth trigger which fires at 50<\/code> percent scrolled, and a Timer trigger which fires at 30 seconds of dwell time on the page.<\/p>\n

    \n

    <\/p>\n

    \"Engagement<\/p>\n

    <\/a><\/p>\n<\/div>\n

    The Trigger Group combines the Timer and the Scroll Depth trigger into a decent engagement tracker.<\/p>\n

    Example 2: Wait for the All Pages trigger to fire first<\/h2>\n

    This example should ring true if you want to establish a running order between two triggers (and, as a consequence, the tags that these triggers fire). A classic example is waiting for the Page View tag in Google Analytics<\/a> to fire before any Event tag.<\/p>\n

    \n

    Even though it\u2019s a bit of a myth<\/a> that collecting events before pageviews is somehow detrimental to analytics (GA is more than capable of stitching together a session where the entrance hit was not a pageview), the exercise is still illuminating.<\/p>\n<\/blockquote>\n

    In this Trigger Group, we have the actual<\/em> trigger we want to fire the tag with as well as the All Pages<\/strong> trigger. The idea being that the event trigger itself will do nothing until the All Pages trigger has also fired.<\/p>\n

    \n

    <\/p>\n

    \"Wait<\/p>\n

    <\/a><\/p>\n<\/div>\n

    Remember that you can\u2019t establish order<\/strong> in a Trigger Group. The Trigger Group will fire as soon as all the triggers listed within have fired – regardless of order. So the underlying assumption here is that the Event – nonIdle<\/strong> trigger will never fire before the All Pages<\/strong> trigger.<\/p>\n

    It might be more reasonable to use tag sequencing<\/a> in most cases where you want to establish a sequence of items firing, but especially when you have a large amount of tags depending on a very similar dependency, it might be easiest to use a Trigger Group instead.<\/p>\n