How to Gate GTM Tags with Native Consent Settings

Edited

In Google Tag Manager, a tag’s triggers decide when it would fire, and its consent settings decide whether it’s allowed to. With the Captain Compliance CMP tag supplying the consent state, gating a tag is a matter of telling GTM which consent categories it requires. This article covers choosing the right setting for each kind of tag, applying it one tag at a time or in bulk, and verifying the result.

Requirement

The Captain Compliance CMP tag must be installed and firing on Consent Initialization. It sets the Google Consent Mode defaults before other tags evaluate their consent settings and sends updates when the visitor’s state changes. Without it, every tag sees consent as granted.

The three settings

Each tag has a Consent Settings section (under Advanced Settings) with an Additional Consent Checks option:

  • Not set. The tag hasn’t been reviewed. GTM applies no enforcement to it, so it fires regardless of consent. Treat this as a to-do state, never a final one.

  • No additional consent required. The tag either has consent checks built in (Google tags) or doesn’t need consent (strictly necessary). GTM applies no extra gating.

  • Require additional consent for tag to fire. The tag runs only if every category you list is granted. Use this for tags with no built-in checks.

Which setting for which tag

Tag

Setting

Google Analytics 4, Google Ads, Floodlight, the Google tag, Conversion Linker

No additional consent required. Their built-in checks handle consent (advanced Consent Mode). To run basic Consent Mode instead, see below.

Microsoft Advertising UET

No additional consent required (built-in checks).

Captain Compliance CMP tag

No additional consent required.

Strictly necessary tags: site functionality, security, the consent banner itself

No additional consent required.

Performance tools without built-in checks: Hotjar, Clarity, Quantum Metric, Funnelytics, session replay

Require: analytics_storage

Advertising tags without built-in checks: Meta, TikTok, Reddit, Pinterest, Snap, LinkedIn, affiliate and retargeting pixels

Require: ad_storage, ad_user_data, ad_personalization

Functionality and personalization tools: chat widgets, recommendation engines, A/B testing that stores preferences

Require: functionality_storage, personalization_storage

Custom HTML tags

Require the categories matching what the script does. If it does nothing that needs consent, mark it No additional consent required rather than leaving it Not set.

The categories map to Captain Compliance’s banner categories: Performance is analytics_storage; Targeting is the three ad signals; Functionality is functionality_storage and personalization_storage.

Basic or advanced Consent Mode for Google tags

This section explains how to set each mode. For help choosing one, see How to Choose Between Basic and Advanced Google Consent Mode.

Google tags support two modes, chosen per tag:

  • Advanced: leave the tag at No additional consent required. It fires on every page; while consent is denied it sends cookieless pings that Google uses for modeling, and it behaves normally once consent is granted.

  • Basic: set Require additional consent and list the category that matches the tag: analytics_storage for GA4, the three ad signals for Google Ads and Floodlight. The tag then doesn’t fire at all until that category is granted, with no pings sent while denied.

A Google tag in advanced mode lists its built-in checks and needs no additional consent:

A Google tag in GTM showing its built-in consent checks and No additional consent required

Pick one mode and apply it consistently across your Google tags. Mixing the two makes behavior hard to reason about and to test.

Configure a single tag

  1. Open the tag and expand Advanced Settings, then Consent Settings.

  2. Choose the Additional Consent Checks option.

  3. If you chose Require additional consent, add each required category.

  4. Save.

The Consent Settings section of a GTM tag set to require analytics_storage

Configure tags in bulk with Consent Overview

  1. Go to Admin > Container Settings and turn on Enable consent overview.

The Enable consent overview setting in GTM Container Settings

  1. On the Tags page, click the shield icon. Tags are grouped into Consent Not Configured and Consent Configured.

GTM Consent Overview with the Consent Not Configured and Consent Configured groups

  1. Select a group of tags with the same requirement, click the shield edit icon, choose the setting and categories, and save.

Editing consent settings for the selected tags in GTM Consent Overview

  1. Repeat until Consent Not Configured is empty.

A practical order: all Google and strictly necessary tags first (No additional consent required), then third-party performance tags, then advertising tags, then functionality tags, then whatever’s left one by one.

How and when the check happens

GTM evaluates a tag’s consent requirement once, at the moment its trigger fires. If the required categories are granted, the tag runs; if not, it’s blocked for that event and is not retried when consent arrives later on the same page.

This matters for tags that fire early. A tag on All Pages or Initialization is evaluated before the banner has delivered the visitor’s state, so in an opt-in region it’s blocked even if the visitor then clicks Allow, and in an opt-out region it can be blocked on a visitor’s first page view. Move those tags onto the CC - Consent Ready trigger, which fires once the state is known. The CC - Consent Ready article explains how.

Verifying in Preview

In Tag Assistant:

  • Google tags appear as fired even when consent is denied. In advanced mode that’s the cookieless ping, which is expected. Validate by checking the request, not the firing status.

  • Tags with Require additional consent show as not fired while their categories are denied, and as fired once they’re granted and their trigger fires.

  • The Consent tab on any event shows the state of each category at that moment.

Run the full scenario set, default load, GPC, allow and reject from an opt-out and an opt-in region, before publishing. The testing article lists what to expect.

Common mistakes

  • Leaving tags at Not set. They fire without any enforcement. Clear the Consent Not Configured list.

  • Putting Google tags on a Consent Initialization trigger. They then run before the CMP tag has set defaults. Use Initialization or later.

  • Catch-all custom event triggers. A trigger whose event name matches .+ fires on every event, including Consent Initialization, before stored choices or GPC have been applied. Use ^(?!gtm\.init_consent$|gtm\.init$).+ or give the tag specific triggers.

  • Forgetting that denial isn’t retried. Early-firing tags need CC - Consent Ready, not just a consent setting.

When to use trigger-based gating instead

Native consent settings decide whether a tag may run; they can’t make it run at a new moment. If you need a tag to fire the instant a visitor clicks Allow, without a page reload, or to react to consent changes in more detail, use custom triggers built on the Captain Compliance consent events. The trigger-based gating article covers that approach. For most containers, native settings plus CC - Consent Ready are enough.

Related articles