Additional consent in Google Tag Manager
For tags that don't offer built-in consent, you'll have to select the correct category as additional consent and update the firing triggers for each tag.
We have provided a sample tag with your customized Google Tag Manager template where additional consent is correctly configured. Go to the tags section and locate the Sample - Additional consent tag to see how it's configured. You can safely remove this tag as it's only for demonstration purposes.
All tags using additional consent will work normally without any changes to the triggers but if you are using "Page view" triggers, the tags won't be triggered on the first page view if the user hasn't accepted the assigned cookie category. To work around that, you can add the CookieHub - Choice modified trigger as an additional firing trigger which will make sure the tag is always fired on every page.
Follow these steps to set up additional consent for your current tags:
- Go to the Tags section for your Google Tag Manager container and click the tag you would like to enable additional consent for. In this case, we'll use the Facebook Pixel tag as an example.
- Click the Tag Configuration section
- Expand Advanced Settings.
- Expand Consent Settings.
- Check the Require additional consent for tag to fire and select the cookie category that you want to assign this tag to. In this case we'll use the analytical category which is named analytics_storage in Google Tag Manager.
- Once confirmed by clicking outside the Tag Configuration section, the configuration will look like this:
- Next we'll have to modify the firing triggers. Click the Triggering section.
- Click the + icon to add a new trigger.
- Select the CookieHub - Choice modified trigger from the list.
- Now, you have two firing triggers and the tag will be fired when either of these triggers match the Google Tag Manager conditions.