Category: Google Consent Mode

Basic Consent Mode

Also known as: Basic Google Consent Mode, Basic Consent Mode v2

Simply put

Basic Consent Mode is one of two ways to set up Google's consent mode, a feature that adjusts how Google tags behave based on whether a visitor has given consent. In this basic version, Google tags are held back and do not load or send any data until the visitor grants the relevant consent. This differs from the advanced version, which loads tags earlier but limits what they send before consent is given.

Formal definition

Basic Consent Mode is an implementation of Google's consent mode in which Google tags are blocked from firing entirely until the user grants the relevant consent signals (for example, analytics or advertising consent). Unlike Advanced Consent Mode, no tags load and no data (including anonymized or 'cookieless' pings) is transmitted to Google prior to consent; data is collected only from users who have consented. Basic Consent Mode requires minimal customization of Google Tags and is typically integrated with a consent management platform (CMP) that communicates the user's consent state. As a technical mechanism for controlling tag behavior, it is a tool that supports consent-based data collection but does not by itself determine or guarantee compliance with legal requirements. Whether prior consent is required before tags fire depends on the applicable legal regime: in most EU/UK jurisdictions the ePrivacy rules generally require prior consent for placing or accessing non-essential cookies and similar technologies, and the GDPR governs any resulting processing of personal data, whereas some US state frameworks rely on opt-out rather than opt-in. This definition does not address advanced consent mode behavior, the specific consent signal parameters used by Google, or the sufficiency of any given configuration under a particular data protection authority's guidance.

Why it matters

For organizations operating under EU and UK rules, the point at which a Google tag fires can carry real legal significance. In most EU/UK jurisdictions, the ePrivacy rules generally require prior consent before placing or accessing non-essential cookies and similar technologies, and the GDPR governs any personal data processed as a result. Because Basic Consent Mode withholds all Google tags until the relevant consent is granted, and transmits no data (including anonymized pings) to Google beforehand, it aligns with a strict interpretation of prior-consent obligations. This makes it a configuration that privacy and compliance teams frequently consider when they want data collection to begin only after an affirmative user action.

The distinction between Basic and Advanced Consent Mode matters because the two behave differently before consent is given. Advanced Consent Mode loads tags earlier and can send limited signals to Google prior to consent, whereas Basic Consent Mode sends nothing until consent is granted. Teams weighing these options are effectively balancing measurement continuity against a more conservative approach to pre-consent data flows. Choosing Basic Consent Mode means accepting that no data is collected from users who do not consent, which affects the completeness of analytics and advertising datasets.

It is important to stress that implementing Basic Consent Mode is a technical mechanism, not a compliance determination. The mode controls tag behavior, but whether a given setup meets legal requirements depends on the applicable regime, the underlying consent collection (which must generally be freely given, specific, informed, and unambiguous under the GDPR), and evolving guidance from data protection authorities. Some US state frameworks rely on opt-out rather than opt-in, so the same configuration may not map cleanly across jurisdictions. Basic Consent Mode supports consent-based data collection but does not by itself guarantee compliance.

Who it's relevant to

Privacy and data protection officers

Those responsible for cookie and tracking compliance may consider Basic Consent Mode where they want a conservative approach in which no Google tags fire and no data reaches Google before consent is granted. They should assess whether the configuration, together with the underlying consent collection, meets the standards applicable in their jurisdiction, recognizing that the mode itself does not determine compliance.

Web developers and analytics implementers

Developers integrating consent mode need to understand that Basic Consent Mode requires minimal customization of Google Tags and is typically wired to a CMP that communicates the consent state. They handle the technical work of ensuring tags remain blocked until the relevant consent signals are granted.

Marketing and measurement teams

Teams relying on Google analytics and advertising data should understand that Basic Consent Mode collects data only from consented users and sends nothing before consent, which affects dataset completeness compared with Advanced Consent Mode. This trade-off is relevant when planning measurement strategy.

Legal counsel and compliance advisors

Counsel advising on ePrivacy and GDPR obligations in the EU and UK, or on opt-out frameworks in some US states, may evaluate Basic Consent Mode as a tool supporting consent-based data collection. They should note that whether prior consent is legally required, and whether a specific configuration satisfies it, depends on the applicable regime and evolving regulatory guidance.

Inside Basic Consent Mode

Consent Mode (general concept)

A mechanism, associated primarily with Google's tag ecosystem, that adjusts how tags behave based on the consent choices a user has communicated, typically via a consent management platform (CMP). It relies on consent signals or 'consent states' passed to tags rather than simply firing or blocking them outright.

Basic implementation

In the 'Basic' variant, tags are generally prevented from loading until the user grants consent. Where consent is denied, the relevant tags do not fire and, as a result, no measurement data is sent for those users. This differs from the 'Advanced' variant, which may load tags in a limited state and send cookieless signals before a consent decision is made.

Consent signal parameters

Consent Mode works with named consent states (for example, parameters covering analytics storage and advertising storage) that reflect whether the user has consented to particular processing purposes. These signals are typically set based on choices captured through a CMP.

Relationship to the CMP

Consent Mode is a tag-behaviour layer that depends on an upstream consent decision. The CMP or consent banner is responsible for obtaining and recording consent; Consent Mode reacts to the outcome. It does not itself collect valid consent.

Legal context (device access vs. data processing)

Because the Basic variant blocks tags before consent, it is intended to align with the requirement, under the ePrivacy Directive and its national implementations in most EU jurisdictions, that information generally not be placed on or read from a user's device without prior consent. Separately, any subsequent processing of personal data must have its own basis under the GDPR; the two obligations are distinct.

Common questions

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

Does Basic Consent Mode mean cookies are still set before a user gives consent?

No. In Basic Consent Mode, the relevant Google tags are typically prevented from loading until the user makes a consent choice, so associated cookies are generally not set beforehand. This differs from Advanced Consent Mode, where tags load in a restricted state and send cookieless pings prior to a decision. Because Basic mode blocks the tags themselves until consent is granted, it can align more closely with the prior-consent expectation under the ePrivacy rules as implemented in most EU jurisdictions. However, whether any given configuration is compliant depends on how it is deployed and on the guidance of the relevant data protection authority, so this should not be treated as a guarantee of lawfulness.

Is enabling Consent Mode enough to make my site compliant on its own?

No. Consent Mode is a technical signaling mechanism that adjusts how Google tags behave based on a consent state; it is not itself a consent management platform and does not collect, present, or record consent. You still need a valid consent mechanism, appropriate disclosures, and consent record-keeping, and in the EU that consent must generally be freely given, specific, informed, and unambiguous. Consent Mode can support a compliance program but does not replace legal judgment or the underlying obligations, which vary between the EU, the UK, and individual US states.

How does Basic Consent Mode receive the consent signal from my CMP?

Basic Consent Mode relies on consent states (such as those governing analytics and advertising storage) being passed to Google tags, typically by a consent management platform that updates those states after the user makes a choice. In a Basic configuration, tags are generally held back until an appropriate signal is received. The precise integration depends on your CMP, your tag management setup, and how the default and updated states are configured, so you should verify the wiring in your specific implementation rather than assuming default behavior.

What happens to measurement data when a user declines consent under Basic Consent Mode?

Because Basic Consent Mode generally prevents the affected Google tags from loading when consent is declined, no tag-based data is sent for those users, which can reduce measurement completeness compared with Advanced mode. Some Google products offer modeling to estimate unmeasured activity, but the availability and behavior of such features depend on the product and configuration, and any modeling should be assessed for its own privacy implications. You should confirm what data is and is not collected in your setup rather than assuming a particular outcome.

Should I set default consent states to denied when implementing Basic Consent Mode?

In EU-facing implementations, a common approach is to set default consent states to denied until the user provides consent, so that tags are not activated beforehand, consistent with prior-consent expectations in most EU jurisdictions. Requirements differ under other frameworks, such as certain US state laws that rely on opt-out rather than opt-in, so the appropriate default may vary by the geography of your users. The correct configuration depends on which regimes apply to you, and legal input is advisable where the scope is unclear.

How can I verify that Basic Consent Mode is behaving as intended after deployment?

Verification typically involves testing that tags and associated cookies are withheld before a consent choice and that they load only after consent is granted, using browser developer tools, tag debugging utilities, or network inspection. You should also confirm that your CMP is passing the intended consent states and that these are logged as part of your consent record-keeping. Because tools support but do not replace compliance judgment, testing should be paired with a review of whether the observed behavior meets the standards applicable in your jurisdiction.

Common misconceptions

Enabling Basic Consent Mode makes a website compliant with EU cookie and data protection law.

Consent Mode is a technical tool that adjusts tag behaviour; it does not by itself deliver valid consent, an adequate consent banner, or a lawful basis under the GDPR. Compliance also depends on how consent is obtained, informed, and recorded, and on legal judgment specific to the relevant jurisdiction. No tool guarantees compliance.

Basic and Advanced Consent Mode behave the same way when consent is denied.

They differ. In the Basic variant, tags are generally blocked from loading until consent is granted, so no data is sent where consent is absent. The Advanced variant may load tags in a limited state and transmit cookieless signals before or without full consent, which raises different considerations regarding device access and data processing.

Because Basic Consent Mode blocks tags before consent, no further privacy analysis is needed.

Blocking device access before consent addresses one part of the ePrivacy requirement, but the handling of any personal data still requires its own analysis under the GDPR. Requirements also vary between the EU, the UK, and individual US states, where opt-out models may apply, so the appropriate configuration is fact- and jurisdiction-dependent.

Best practices

Treat Basic Consent Mode as a complement to, not a replacement for, a properly configured CMP that obtains freely given, specific, informed, and unambiguous consent through a clear affirmative action in EU jurisdictions.

Confirm that tags governed by Consent Mode are genuinely prevented from placing or reading information on the user's device before consent is granted, since this device-access step is governed by the ePrivacy Directive and its national implementations.

Separately assess the lawful basis and transparency obligations for any personal data processed after consent, recognising that ePrivacy and GDPR obligations are distinct and must each be satisfied.

Map the consent signals (such as analytics and advertising storage states) to the corresponding cookie or tracking categories, and verify that essential or strictly necessary technologies are handled appropriately versus those that typically require prior consent.

Validate the actual runtime behaviour through testing to ensure the deployed configuration matches the intended Basic behaviour, rather than assuming the setting alone is sufficient.

Adapt the configuration to the geographic scope of your audience, since consent requirements differ across the EU, the UK, and individual US states, and obtain legal review for contested or fact-specific questions.