a promotional graphic telling you that PCI Compliance is no longer an annual exercise and that continuous monitory must be built in

Category: Google Consent Mode

Advanced Consent Mode

Also known as: Advanced Consent Mode v2, Google Consent Mode (Advanced)

Simply put

Advanced Consent Mode is one of two configurations of Google's Consent Mode, a feature that adjusts how Google tags behave based on whether a user has granted or denied consent for cookies and data processing. In the advanced configuration, Google tags load when a page opens and send limited, non-identifying signals even when a user has not consented, allowing businesses to estimate metrics such as user engagement and conversions through modeling. It is generally positioned as an option for organizations that want more detailed measurement while still adapting to a user's consent choices.

Formal definition

Advanced Consent Mode is a configuration of Google Consent Mode (commonly discussed in its v2 form) in which Google tags are loaded on initial page load and read consent state parameters (such as analytics_storage and ad_storage) that are set by a consent mechanism, typically a consent management platform. Where consent is denied, tags do not write or read the relevant cookies but may transmit cookieless, non-identifying pings that Google uses to model unobserved conversions and engagement, in contrast to Basic Consent Mode, where tags are blocked from loading entirely until consent is granted. Importantly, Consent Mode governs how Google tags respond to a consent signal; it does not itself collect or validate consent, and the underlying obligation to obtain valid prior consent for placing or accessing information on a device (under the ePrivacy Directive and national implementations in the EU/UK) and to lawfully process any resulting personal data (under the GDPR) rests with the site operator and its CMP. Consent requirements differ across jurisdictions, and deploying Advanced Consent Mode does not by itself establish compliance; the lawfulness of transmitting signals when consent is denied depends on the specific data involved and evolving regulatory interpretation, which is outside the scope of this definition.

Why it matters

Advanced Consent Mode addresses a persistent tension for organizations operating in the EU and UK: how to measure marketing and website performance when a significant share of users decline consent for analytics and advertising cookies. By allowing Google tags to send limited, cookieless signals even when consent is denied, the advanced configuration lets businesses use modeling to estimate conversions and engagement that would otherwise go unobserved. For measurement and marketing teams, this can mean more complete reporting than an approach where tags are blocked entirely until consent is granted.

The feature also carries real compliance sensitivity, and privacy teams should treat it with care. Consent Mode governs only how Google tags respond to a consent signal; it neither collects nor validates consent. The underlying legal obligations remain with the site operator: obtaining valid prior consent for placing or accessing information on a user's device under the ePrivacy Directive and its national implementations in the EU and UK, and lawfully processing any resulting personal data under the GDPR. Deploying Advanced Consent Mode does not by itself establish compliance.

A particular point of scrutiny is the transmission of signals when a user has denied consent. Whether such transmissions are lawful depends on the specific data involved and on evolving regulatory interpretation, which differs across jurisdictions and is not settled. Organizations should therefore assess this configuration with legal counsel and their data protection function rather than assuming that its use is inherently permissible everywhere.

Who it's relevant to

Privacy and data protection officers

DPOs and privacy teams need to assess whether transmitting cookieless signals when consent is denied is defensible for their specific data flows and jurisdictions. Because the lawfulness of such transmissions depends on the data involved and on evolving regulatory interpretation, this configuration should be reviewed rather than adopted on the assumption that it is compliant by default.

Legal and compliance counsel

Counsel should evaluate Advanced Consent Mode against the layered obligations of the ePrivacy Directive and its national implementations in the EU and UK, and the GDPR, as well as differing requirements in other regimes. The tool supports adaptation to a consent signal but does not establish that valid consent was obtained or that resulting processing is lawful.

Marketing and measurement teams

Analytics and marketing teams are the primary beneficiaries of the modeled reporting that Advanced Consent Mode enables, since it can estimate conversions and engagement for users who have not consented to cookies. These teams should understand that modeled figures are estimates and should coordinate with privacy and legal functions before relying on the configuration.

Web developers and CMP implementers

Developers and those configuring consent management platforms are responsible for ensuring that consent state parameters such as analytics_storage and ad_storage are correctly set and passed to Google tags. Correct integration between the CMP and Consent Mode determines whether tag behavior actually reflects the user's choices.

Inside Advanced Consent Mode

Consent signal integration

Advanced Consent Mode adjusts how tags and scripts behave based on the consent state a user communicates through a consent management platform (CMP), passing signals that reflect whether the user has granted or denied consent for specific purposes such as analytics or advertising.

Cookieless pings and modeling

In the advanced configuration, tags typically load in a restricted state before any consent is given and may send limited, non-identifying signals (often described as cookieless pings). Where consent is denied, some platforms use statistical modeling to estimate outcomes rather than relying on data tied to the individual user. The accuracy and lawfulness of such modeling depend on how it is implemented and remain subject to evolving regulatory scrutiny.

Consent state parameters

The mechanism relies on parameters that represent distinct consent categories (for example, categories corresponding to analytics storage and advertising storage). These parameters govern whether cookies or similar identifiers may be set and whether personal data may subsequently be processed.

Two-tier relationship with legal regimes

Consent Mode operates at the intersection of two distinct regimes in EU/UK contexts: the ePrivacy rules governing the placing of, and access to, information on a user's device, and the GDPR governing any subsequent processing of personal data. The technical signal does not by itself establish a lawful basis under either regime.

Advanced versus basic implementation

In the advanced implementation, tags are loaded (in a restricted mode) before consent, whereas in a basic implementation tags are typically not loaded at all until consent is given. This distinction affects what data flows occur prior to a user's clear affirmative action.

Common questions

Answers to the questions practitioners most commonly ask about Advanced Consent Mode.

Does using Advanced Consent Mode mean I no longer need consent to run analytics or advertising cookies?

No. Advanced Consent Mode is a technical mechanism for adjusting how tags behave based on a user's consent choices; it does not remove the underlying legal obligation to obtain valid consent. In most EU jurisdictions, prior consent is generally required before placing or accessing non-essential cookies under the ePrivacy Directive as implemented nationally, and before processing any resulting personal data under the GDPR. Advanced Consent Mode operates on top of these obligations rather than replacing them, and it still relies on a consent management platform or similar tool to capture the user's choice.

If Advanced Consent Mode sends data even when a user has not consented, isn't it processing data without consent?

This is a contested and fact-sensitive area. Advanced Consent Mode may transmit signals in a form intended to be less identifying when consent is absent, rather than setting the same cookies or collecting the same data as it would with consent. Whether any such transmission still involves accessing information on the device or processing personal data, and therefore whether it requires consent under the ePrivacy rules or the GDPR, depends on the specific data involved and how it is handled. This definition does not resolve that question, and regulatory positions on such signalling continue to evolve. Organizations should assess their particular configuration with legal advice rather than assume the mechanism is exempt.

How does Advanced Consent Mode interact with a consent management platform?

Advanced Consent Mode typically depends on a consent management platform (CMP) to record the user's choices and communicate the resulting consent states to the tagging environment. The CMP handles presenting the notice and capturing the affirmative action, while Advanced Consent Mode adjusts tag behavior according to those states. The tool supports implementation of consent decisions but does not itself establish that consent was validly obtained; that remains a matter of how the CMP and notice are configured and of applicable legal requirements in the relevant jurisdiction.

What do we need to configure so that consent states are passed correctly?

In general, implementation involves ensuring that the CMP fires before tags are set, that consent categories are mapped to the correct consent states, and that those states update dynamically when a user changes their preferences. Configuration details vary by platform and by the tags in use. Because misconfiguration can cause tags to behave inconsistently with the user's actual choices, testing across consent scenarios is advisable. This definition does not cover vendor-specific setup steps, which should be taken from the relevant product documentation.

Does Advanced Consent Mode help us meet consent record-keeping obligations?

Not on its own. Record-keeping of consent is generally handled by the CMP or a separate logging function rather than by the consent-state mechanism itself. Where accountability or demonstrability of consent is expected, such as under the GDPR, organizations typically rely on their CMP's consent logs. You should confirm what your specific setup records and retains, as Advanced Consent Mode governs tag behavior rather than the maintenance of consent evidence.

Do the same configuration choices work across the EU, the UK, and US states?

Not necessarily. Consent obligations differ across regimes: many EU jurisdictions and the UK generally operate on a prior opt-in model for non-essential cookies, whereas several US state laws, such as those in California, often rely on opt-out mechanisms and may involve signals like Global Privacy Control. A single Advanced Consent Mode configuration may need to be adapted so that tag behavior aligns with the applicable rules and user rights in each region. The appropriate configuration depends on where your users are located and on facts not addressed by this definition.

Common misconceptions

Enabling Advanced Consent Mode makes a website compliant with EU cookie and privacy law.

Consent Mode is a technical tool that adjusts tag behavior based on signals it receives; it does not by itself deliver valid consent or guarantee compliance. Valid consent in most EU jurisdictions must still be freely given, specific, informed, and unambiguous, collected through a compliant CMP, and supported by appropriate records. Legal compliance depends on the overall configuration and legal judgment, not on the presence of the feature.

Because tags load before consent in the advanced setup, no data is collected until the user consents.

In the advanced configuration, tags load in a restricted state and may transmit limited, non-identifying signals (such as cookieless pings) before consent is given. Whether these pre-consent signals are permissible can be contested and may raise questions under ePrivacy rules on access to a device and under the GDPR, depending on implementation and applicable national guidance.

The same Consent Mode setup works identically everywhere.

Cookie and consent obligations differ across the EU, the UK, and individual US states such as California under the CCPA/CPRA. EU/UK contexts generally require prior opt-in consent for non-essential cookies, while several US frameworks rely on an opt-out model and may recognize signals such as Global Privacy Control. A single configuration may need to be adapted to reflect these differing legal scopes.

Best practices

Pair Advanced Consent Mode with a compliant CMP that captures freely given, specific, informed, and unambiguous consent through a clear affirmative action in EU/UK contexts, rather than treating the technical feature as a substitute for consent collection.

Map each consent category and parameter to the actual cookies, pixels, SDKs, local storage, and similar technologies in use, remembering that non-cookie technologies generally fall within the same rules.

Review what signals, including any cookieless pings, are transmitted before consent is obtained, and assess them against ePrivacy rules on device access and GDPR processing requirements before relying on the advanced implementation.

Maintain records of consent and configuration decisions to support accountability and record-keeping expectations, and log changes to tag behavior tied to consent states.

Configure and test behavior separately for different jurisdictions, distinguishing opt-in regimes (EU/UK) from opt-out regimes (such as certain US state laws) and honoring recognized signals like Global Privacy Control where applicable.

Obtain legal review of the overall setup and revisit it periodically, since regulatory positions on consent modeling and pre-consent signals continue to evolve and remain contested in some jurisdictions.