Triggers and tag firing options in Google Tag Manager
CookieHub offers various triggers that you can use in Google Tag Manager and since each use case might be different, a different set of triggers may be required for each tag.
Configurations that may affect triggering:
| Option | Service | Details |
| Regional consent type | CookieHub | When multiple regions are being used in CookieHub, a asynchronous request is made detect the user's country. While this request is being performed, Google Tag Manager may already have evaluated triggers for tags and if additional consent checks are specified, depending on the triggers, they may not be evaluated again automatically once the country has been detected. When multiple regions are specified and implied consent is used, this setting may affect all firing triggers. |
| Firing triggers | Google Tag Manager | CookieHub offers various firing triggers that can be used standalone or in combination with other triggers to fire tags based on user interaction with the CookieHub dialog. |
| Trigger exceptions | Google Tag Manager | All CookieHub triggers can be used as exceptions to prevent loading tag when certain conditions are true. |
| Additional consent checks | Google Tag Manager | When additional consent checks are configured for a tag the configured consent category must be either explicitly or implicitly allowed before the tag is triggered. If multiple categories are specified for a tag in additional consent checks, all of them must be allowed. Please note that additional consent checks rely on firing triggers and Google Tag Manager will not re-evaluate tags automatically when Google consent mode signals are updated. |
| Tag firing options | Google Tag Manager | It's important to understand how tag firing options affect the triggering of tags in Google Tag Manager, especially for tags configured with additional consent as this setting will affect how often the tag is evaluated with the firing and exception triggers and if the tag can trigger multiple times or not. |
CookieHub triggers
| Trigger | Triggered when? |
| CookieHub - Loaded | Triggered once per page when CookieHub has been fully loaded and the country of the client has been detected. For first time users, the CookieHub dialog will be shown and depending on the consent type specified, the cookie categories may or may not be allowed at this time. |
| CookieHub - Consent Update | Triggered every time Google Consent mode signals are sent. It's triggered after every interaction with the CookieHub dialog (Allow all, Deny all or Save settings). Additionally, it's triggered on each page load after CookieHub has determined the current consent settings for the user, either stored consent settings or the default settings based on consent type configured and country detected. |
| CookieHub - Choice Modified | Triggered on every user interaction with the CookieHub dialog (Allow all, Deny all or Save settings). |
| CookieHub - Allowed Necessary | Triggered when the necessary cookie category is allowed, either due to manual user interaction with the CookieHub or dialog or based on default settings or stored cookie consent settings. |
| CookieHub - Allowed Preferences | Triggered when the preferences cookie category is allowed, either due to manual user interaction with the CookieHub or dialog or based on default settings or stored cookie consent settings. |
| CookieHub - Allowed Analytics | Triggered when the analytics cookie category is allowed, either due to manual user interaction with the CookieHub or dialog or based on default settings or stored cookie consent settings. |
| CookieHub - Allowed Marketing | Triggered when the marketing cookie category is allowed, either due to manual user interaction with the CookieHub or dialog or based on default settings or stored cookie consent settings. |
Tag Firing Options
| Option | Intended functionality | Known issues |
| Once per page | Tag will only fire once on each page load, meaning that once any trigger combination matches, it's not evaluated again. | The trigger evaluation does not include additional consent checks so if the consent group isn't allowed at the time the trigger combination matched, the tag won't be fired in this page load even though the user would manually interact with the CookieHub dialog. |
| Once per event (default) | Tag will fire every time the trigger combination matches. | Depending on the trigger setup, using this option may cause multiple instances of a tag to be loaded. |
| Unlimited | Tags will fire whenever triggers tell it to. (This option is only used with tag sequencing.) | See Once per event |
What triggers and settings should I use?
For tags with built-in consent mode support, including Google Analytics, Conversion Linker, Floodlight, Google Ads Conversion Tracking and Remarketing you don't have to use special CookieHub triggers as these tags will respect Google Consent mode and re-evaluate triggers when Google Consent mode signal is received.
For other tags that require additional consent, you can in most cases simply use the CookieHub - Consent Update firing trigger but you can find reference table below:
| Firing option | Triggers | |
| Tag should be fired once on load | Once per page | CookieHub - Allowed [category] |
| Tag can be fired multiple times (either on load or CookieHub dialog interaction) | Once per event | CookieHub - Consent Update |
| Tag should not be triggered on user interaction instead of page load | Once per event | No specific CookieHub events required. Use the event that should trigger the tag. |
Why can't I use CookieHub - Consent Update for all tags?
The Consent Update event is always triggered when CookieHub signals any update to the Google Consent mode settings. When the default consent mode settings are pushed, the Consent Update event is triggered but at that time, the default consent settings are used which are usually to deny all cookie categories. If the firing option is set to Once per page, the tag won't fire again causing these tags to not load at all.