Customizing CookieHub Triggers

CookieHub offers various triggers that you can integrate into Google Tag Manager to control when your tags fire. Each use case may require different triggers to ensure tags are fired based on user interactions with the CookieHub dialog. Several factors and configurations can impact how these triggers work. Here's a breakdown of these configurations and the available triggers:

Configurations Affecting TriggersCopy Anchor Link

1. Regional Consent Type (CookieHub): When multiple regions are specified in CookieHub, an asynchronous request is made to detect the user's country. Google Tag Manager may have already evaluated triggers for tags, and if additional consent checks are required, they may not be automatically re-evaluated once the user's country is detected. This setting can affect all firing triggers when multiple regions are specified and implied consent is used.
2. Firing Triggers (Google Tag Manager): CookieHub provides various firing triggers, which can be used independently or in combination with other triggers to fire tags based on user interactions with the CookieHub dialog.
3. Trigger Exceptions (Google Tag Manager): All CookieHub triggers can also be used as exceptions to prevent loading a tag when specific conditions are met.
4. Additional Consent Checks (Google Tag Manager): When additional consent checks are configured for a tag, the specified consent category must be either explicitly or implicitly allowed before the tag is triggered. If multiple categories are specified, all of them must be allowed.
5. Tag Firing Options (Google Tag Manager): These options determine how tags are evaluated with firing and exception triggers and whether a tag can trigger multiple times.

CookieHub TriggersCopy Anchor Link

• CookieHub - Loaded: Triggered once per page when CookieHub is fully loaded and the user's country is detected. For first-time users, the CookieHub dialog is shown, and depending on the consent type, cookie categories may or may not be allowed at this time.
• CookieHub - Consent Update: Triggered every time consent mode signals are sent. It's activated after every interaction with the CookieHub dialog (Allow all, Deny all, or Save settings). It's also triggered on each page load after CookieHub has determined the current consent settings for the user.
• CookieHub - Choice Modified: Triggered on every user interaction with the CookieHub dialog (Allow all, Deny all, or Save settings).
• CookieHub - Allowed Necessary, Preferences, Analytics, Marketing: Triggered when the corresponding cookie category is allowed. This can occur due to manual user interaction with the CookieHub, dialog settings, or based on default settings or stored consent preferences.

Tag Firing OptionsCopy Anchor Link

• Once per page: The tag fires once on each page load, and if the consent group isn't allowed at the time the trigger combination matches, the tag won't be fired in that page load.
• Once per event (default): The tag fires every time the trigger combination matches. Depending on the setup, using this option may cause multiple instances of a tag to load.
• Unlimited: Tags fire whenever triggers indicate, primarily used with tag sequencing.

Choosing the Right TriggersCopy Anchor Link

• Built-in consent mode Support: For tags with built-in consent mode support (e.g., Google Analytics, Conversion Linker, Floodlight, Google Ads Conversion Tracking, and Remarketing), special CookieHub triggers may not be needed. These tags respect consent mode and re-evaluate triggers when consent mode signals are received.
• Additional Consent Tags: For tags requiring additional consent, you can often use the "CookieHub - Consent Update" firing trigger. However, specific trigger combinations may be more suitable, depending on your requirements.
• Consider Firing Options: Be aware of how tag firing options affect trigger evaluations, especially for tags configured with additional consent. The chosen option can impact how often the tag is evaluated.

Please note that the "CookieHub - Consent Update" event is always triggered when CookieHub signals any update to consent mode settings. Be cautious when using "Once per page" with tags that depend on Consent Update, as the tag may not fire again, potentially causing these tags not to load at all.