Configure Consent Requirements for Your Tags

After installing the TrueVault CMP template, configure each tag in Google Tag Manager (GTM) to require the consent signals that match how the tag uses data.

This step is necessary even if your organization uses an informational banner or does not display a banner in some regions. TrueVault can still use consent signals to enforce an opt-out choice.

Choose your banner behavior

In the TrueVault app, open Privacy Center → Website Consent and configure the banner behavior for each region where your site operates:

• GDPR: Denies non-essential consent by default and uses the GDPR-specific experience for applicable EEA, UK, and Swiss visitors.
• Informational: Displays a notice but does not ask the visitor to choose consent purposes.
• Opt-out: Allows consent by default and lets the visitor withdraw it.
• Opt-in: Denies non-essential consent by default until the visitor grants it.

See Compare Consent Banner Variants for the differences between their default states and visitor controls. The correct configuration depends on your organization's practices and legal requirements. TrueVault applies the regional configuration; GTM enforces the tag requirements you set below.

Previously set cookies are not automatically deleted. TrueVault enforces consent by preventing tags from firing — via the consent signals described below — not by scanning the browser for cookies or deleting them. When a visitor declines consent, GTM can prevent the corresponding tags from running again, but browser security restrictions prevent a CMP from reliably deleting cookies set by other domains. If your organization wants already-set cookies removed when a visitor opts out, your own site code must clear them (for example, in a consentChanged listener). If preventing those cookies from being set in the first place is important to your organization, use an opt-in configuration so consent-gated tags do not run before the visitor grants consent.

Match tags to consent signals

Review the vendors shown in the Consent Management section of your organization's Developer Instructions. For each corresponding tag in GTM, require the signal that matches its purpose:

Tag purpose	Consent signal
Advertising or marketing	ad_storage
Analytics or measurement	analytics_storage
Personalization	personalization_storage
Functional features	functionality_storage
Security	security_storage
Selling, sharing, or targeted advertising subject to an opt-out	tv_not_opted_out

A tag can require more than one signal. For example, an advertising vendor identified as selling or sharing data may need both ad_storage and tv_not_opted_out.

Some Google tag templates display Built-In Consent Checks. These checks describe how the product responds to consent signals; they do not necessarily prevent every network request. Review the Google Analytics and Google Consent Mode v2 guides before adding extra requirements to Google tags.

Configure tags individually

Use this method when you have only a few tags to update or when each tag needs different consent requirements.

1. In the GTM workspace, select Tags.
2. Open the tag you want to configure, then select Tag Configuration.
3. Open Advanced Settings → Consent Settings.
4. Under Additional Consent Checks, select Require additional consent for tag to fire.
5. Click Add required consent and select each signal the tag requires.
6. Save the tag.

Repeat these steps for each tag listed in your Developer Instructions and for any other tag that processes visitor data.

Configure multiple tags with Consent Overview

Consent Overview makes it easier to review and update tags in bulk.

Enable Consent Overview

1. In GTM, select Admin → Container Settings.
2. Select Enable Consent Overview.
3. Save the container settings.

Return to Workspace → Tags, then select the shield icon to open Consent Overview.

Apply requirements in bulk

1. Select the tags that have the same purpose and require the same consent signal.
2. Click Edit Consent Settings (the shield-and-cog icon).
3. Under Additional consent settings, add the appropriate signal.
4. Save the changes.

Review tags in smaller groups when they have different purposes. Do not apply one signal to every tag simply because they belong to the same vendor.

Save and continue the setup

Save the tag changes in your workspace. Before you publish the container, complete both of the following:

1. Configure US and Canada opt-outs for tags involved in selling, sharing, or targeted advertising.
2. Add the Consent Changed event so applicable page-level tags respond when a visitor updates their choices.

You will test the complete configuration before publishing it.