How Captain Compliance Works with Google Consent Mode

Edited

Captain Compliance is the source of truth for a visitor’s consent. Google Consent Mode v2 is how that consent reaches Google tags, and Google Tag Manager is where it’s enforced for everything else. This article explains the mapping between the two and the settings that control the pre-consent defaults.

The division of labor

  • Captain Compliance records the visitor’s choices per category and stores them.

  • The Captain Compliance CMP tag in GTM translates those choices into Google Consent Mode signals: it sets the default state for the visitor’s region at Consent Initialization and sends an update whenever a stored preference is found or the visitor makes a choice.

  • Google tags read those signals through their built-in consent checks and adjust their behavior accordingly.

  • All other tags are gated by GTM’s per-tag consent settings, which read the same signals.

Category mapping

Captain Compliance category

Google Consent Mode signals

Strictly Necessary

security_storage (always granted)

Functionality

functionality_storage, personalization_storage

Performance

analytics_storage

Targeting

ad_storage, ad_user_data, ad_personalization

personalization_storage follows the Functionality choice because it covers site preferences such as recommendations and saved settings. ad_personalization is the advertising signal and stays with Targeting.

Pre-consent defaults

Before a visitor makes a choice, each signal is either granted or denied by default. Which one depends on the consent model that applies to the visitor’s region.

  • Opt-out model (permission by default): non-essential categories are granted until the visitor opts out. Typical for US states.

  • Opt-in model (permission first): non-essential categories are denied until the visitor opts in. Typical for the EU, UK and Quebec.

With the recommended consent scope in the CMP tag (“Use my Captain Compliance regions”), these defaults come from the region configurations in your dashboard. In the app, select Consent banner, select your domain, and open each configuration’s Playground. In the Cookie settings scene, the category toggles under Categories set whether each category is granted or denied before the visitor chooses: toggles on for an opt-out region, off for an opt-in region. See How to Create Regional Consent Banner Configurations.

Strictly Necessary is always granted and has no toggle.

If you’d rather define regions in GTM, the CMP tag’s other consent scopes let you list regions by ISO code or apply one model everywhere. Those use Google’s region matching rather than Captain Compliance’s, so keep the lists aligned with your banner configuration.

Google Consent Mode options on the Captain Compliance CMP tag in GTM

Basic and advanced Consent Mode

Google Consent Mode can run in two ways, and the choice is made per Google tag in GTM:

  • Advanced. Google tags load on every page regardless of consent. While consent is denied they send cookieless pings with no identifiers, which Google uses for conversion and behavioral modeling. Once consent is granted they operate normally. This is the default behavior of Google tags with built-in consent checks and no additional consent requirement.

  • Basic. Google tags don’t fire at all until consent is granted. No pings, no modeling, nothing sent while denied. You get this by adding the relevant category as an additional consent requirement on the Google tag.

Either is a valid implementation. Advanced gives Google more data for modeling; basic gives the stricter “nothing until consent” behavior some organizations prefer. The tag-gating article explains how to set each.

For help choosing between them, and what each one means for legal risk, see How to Choose Between Basic and Advanced Google Consent Mode.

Consent events

The banner pushes two events to the data layer that GTM can use.

captainComplianceConsent carries the visitor’s state: the active model and whether each category is granted. It’s pushed when a stored preference is loaded and again whenever the visitor changes it. The CMP tag reads it to send Consent Mode updates, and the same state is written to the cc_consent_preference cookie as a fallback.

captainComplianceConsentReady is pushed once the banner has resolved the visitor’s effective state for the page, taking the regional default, any stored preference and GPC into account. It’s the event to use for tags that must not run before that point; the CC - Consent Ready article covers it.

Global Privacy Control

When a visitor’s browser sends GPC, Captain Compliance treats it as a rejection of all non-essential categories, wherever the visitor is. The CMP tag applies a denied default at Consent Initialization using the CaptainGPCSignalDetected variable, and the banner reports the signal in its events and cookie so later updates stay denied while it’s present.

Verifying the signals

In GTM Preview, select an event in Tag Assistant and open the Consent tab. It shows the state of each signal at that event, with the Consent Default and Consent Update entries in the event list marking when the CMP tag set them.

Expect Google tags to show as fired even while consent is denied: in advanced mode that’s the cookieless ping, not a failure. Check what was sent, not whether the tag fired. Tags gated by additional consent requirements show as not fired while denied. For the full set of scenarios to run, see the testing article.

Without GTM

The same signals work with a direct gtag.js installation. Call the consent default before the gtag snippet and send updates from the captainComplianceConsent event using the mapping above. GTM is still recommended, since it enforces consent for non-Google tags as well.

Related articles