Consent Mode in TAG
Steps to configure the "Consent Mode" in TagCommander.
Last updated
Was this helpful?
Steps to configure the "Consent Mode" in TagCommander.
Last updated
Was this helpful?
Commanders Act provides a tag template to manage the "Consent Mode" in TagCommander. This seamless integration takes advantage of our TrustCommander OnSite API.
Summarizing all recommended steps:
Access your Commanders Act account.
Add our tag template.
Configure your tag and rules.
Configure your third-party vendor tags in GTM.
Test and deploy your container(s).
From the "INTEGRATIONS" side menu, expand(1)"Sources" and select (2)"Web containers".
Select a "Web" container and, from the step (3)"SELECT" (or "EDIT"), click on (4)"Add Tag(s)".
Search for the tag "gtag - Google Consent Mode with TRUST (BETA)" to add it and proceed with its configuration.
You can now configure your tag and check the (5) "Tag Implementation guide" for more details.
See (6) each field for detailed information on how you can map these fields with your datalayer.
Under "RULES", select (7) "Do Not Include In Privacy Scope" as privacy category or select a category that is always ON.
If your website adopts virtual pages, you need to add a trigger for when these pages are loaded. This can be done under the top section "TRIGGER(S)".
You can skip the following steps, completing your configuration, if you don't have any third-party vendor tags hosted in GTM.
To ensure that the consent is correctly managed by GTM with third-party vendor tags, we strongly recommend to enable reactive events by configuring the related fields.
While Google native product tags, such as "Google Analytics" or "Google Ads" ones, work out of the box, third-party vendor tags, hosted in GTM, require additional settings to properly operate with the user consent. First, open your tag configuration and check under the (8) "Advanced Settings" → (9)"Consent Settings" if a consent type (E.g. "ad_storage") is already preconfigured: if not, you need to add it by selecting the option (10) "Require additional consent for tag to fire" and (11) input the consent type(s) you want to include.
Then, you need to configure its triggers and this is where we're going to use our reactive events we prepared in the previous section (Configure your tag and rules). Locate the "Triggering" area in your tag configuration and add a Trigger Group.
In the trigger group add (12)any preexisting triggers and (13)a trigger named as your configured reactive event.
The latter has to be configured as a (14)"Custom Event" with the same (15)"Event Name" you used in the previous section (Configure your tag and rules) and it has to fire on (16)"All Custom Events".
This completes your configuration. You can now start the testing phase, leading to the final deployment in production. Learn more on how you can configure and run tests with your tags in GTM by checking the section "Consent configuration" in the "Help Center".
