Consent Mode is an application programming interface (API) that carries a user's cookie consent decision from a website's consent banner to Google's measurement and advertising tags, which then change what they collect and store. It exists because two things are true at once in Europe: the ePrivacy Directive requires prior consent before storing or reading information on a device, and Google's advertising products were built on the assumption that an identifier persists across page views. Consent Mode reconciles the two. It does not display a banner, collect consent, or store a record of it. It transmits the outcome and adjusts tag behaviour accordingly.

That distinction locates responsibility. The banner, the legal basis, and the proof of consent belong to the site operator or its consent management platform (CMP). Consent Mode is the wire between that software and Google's servers.

Consent Mode defines seven consent types. Four govern advertising and analytics: ad_storage (cookies or device identifiers used for advertising), analytics_storage (the equivalent for analytics), ad_user_data (whether personal data may be sent to Google for advertising), and ad_personalization (whether that data may be used for personalised advertising). Three others cover functionality, personalisation, and security storage, and are rarely wired to Google tags in practice. Each type carries one of two states, granted or denied.

Implementation follows a fixed sequence. A default state is declared before any Google tag executes, normally with everything denied. The user interacts with the banner, and the CMP issues an update call carrying the new states. Sequence is the failure point: an update sent before the default, or a default declared after the tag has already run, produces a signal Google's systems cannot read as consent.

Those states compress into HTTP request parameters. The gcs parameter, inherited from the first version, uses the format G1xy, where the trailing digits represent ad_storage and analytics_storage as 1 for granted and 0 for denied. G111 indicates consent for both, G100 neither. The gcd parameter, added with version two, encodes all four advertising and analytics signals plus information about how each state was reached, using letter codes rather than binary digits. Google's developer documentation confirms gcd is sent on every request to Google services whether or not Consent Mode is active, and warns that these fields are subject to change. Google does not publish the letter mapping; independent measurement documentation has reverse-engineered it, with p understood to mean denied by default and never updated, and r denied by default then granted. A dma parameter carries Digital Markets Act context, and dma_cps encodes consent to specific Google services.

Two implementation patterns exist, and the gap between them is the most consequential decision in the framework.

In basic Consent Mode, Google tags do not load until the user interacts with the banner. Nothing reaches Google beforehand, not even the default consent status. If the user declines, nothing is sent at any point, and conversion modelling for that account falls back to a general model built from other advertisers.

In advanced Consent Mode, tags load with the page. While consent is denied, they send what Google calls measurements without cookies, commonly described as cookieless pings. Google's documentation lists three kinds: consent state pings from each page, key event pings marking a conversion, and Analytics pings. The payload includes timestamp, user agent, referrer, a boolean for consent state, a random number generated per page load, and an indication of whether the page or a prior page carried ad-click information such as a GCLID or DCLID. Because the account contributes its own data, modelling switches from the general model to an advertiser-specific one.

When ad_storage is denied, Google's tags write no new advertising cookies, read none that exist, route requests through an alternative domain such as pagead2.googlesyndication.com to avoid sending previously set third-party cookies in headers, and truncate IP addresses at collection. A separate setting, ads_data_redaction, strips ad-click identifiers from the pings themselves.

The commercial argument for Consent Mode rests on modelling. Google Ads uses the pings to estimate conversions that were not observed, presents them in the standard conversions column, and feeds them into automated bidding. Eligibility is not automatic: Google's documentation sets a threshold of 700 ad clicks over a seven-day period, per country and domain grouping, alongside a correctly implemented Consent Mode or Transparency and Consent Framework integration. Accounts below that volume receive no modelled conversions at all.

Recovery-rate claims vary and read as vendor estimates rather than audited figures. Iubenda's guide, covered in PPC Land's analysis of the European cookie consent landscape, puts recovery above 70% of ad-click-to-conversion journeys lost to refusals. Practitioner audits circulating in 2026 cite 15% to 40%. Modelling accuracy degrades as the non-consenting share of traffic rises, and refusal rates differ sharply by market.

Google launched Consent Mode in beta on 3 September 2020, limited to a small number of European advertisers and covering tags for Google Ads, Floodlight from Campaign Manager and Display & Video 360, and Google Analytics. PPC Land's account of the beta recorded Google Tag Manager product manager Scott Herman's description of the design: tags that adjust rather than disappear, measuring conversions at a more aggregate level when consent is absent. Five CMPs supported it at launch. Modelled conversions reached Google Ads reporting and bidding in April 2021.

The second version arrived in late 2023, and the driver was regulatory. The Digital Markets Act designated Google a gatekeeper, and gatekeepers carry direct responsibility for the lawfulness of consent underlying personalised advertising. Two parameters were added to the API, splitting what had been a single storage permission into separate questions about transmission and use. Google paired the change with an expanded CMP partner programme and a March 2024 deadline, after which accounts without v2 signals lost personalised advertising and remarketing for European traffic.

Tooling followed. Google Tag Manager gained a consent mode override setting in August 2024, applying a denied default per region without site code changes. Tag Diagnostics was folded into the Analytics consent settings hub in June 2025, reporting the share of traffic and conversions attributable to EEA users. Google's own CMP added Consent Mode supportin March 2025 through two account-level flags. Enforcement arrived on 21 July 2025, when Google began disabling personalisation, remarketing, and conversion tracking for advertisers in the European Economic Area and United Kingdom that were not passing compliant signals.

Consent Mode stopped being a compliance artefact once enforcement had teeth. PPC Land documented a case reported by Mike Teasdale, founder and planning director at Harvest Digital, in which a client's Google Ads conversions fell 90% overnight after the July 2025 enforcement. Nothing had changed in the account. The banner was collecting choices and failing to transmit them. Roughly 40% of the attribution data proved recoverable once signals were restored; the rest was gone permanently, and any bidding model trained during the gap had learned from an incomplete record.

The failure mode is silent by construction. No error surfaces in the interface. Bidding strategies dependent on conversion volume optimise against a smaller signal, and cost per acquisition drifts upward before anyone connects it to the tag layer.

The unresolved question is whether advanced Consent Mode is lawful in Europe. Google's position is that cookieless pings contain no identifiers and fall outside the consent requirement. Several data protection specialists disagree. Brian Clifton, a measurement and privacy strategist, has argued that GDPR frames privacy in terms of personal data rather than the technology used to collect it, and that the pings should be blocked until consent is given. Piwik PRO, a competing analytics vendor, notes that the request still carries an IP address. German advisory firm DataGuard considers the advanced variant non-compliant.

Academic work has added detail. A study of Google Tag Manager published on arXiv examined Consent Mode v2 traffic and found data actively transmitted through cookieless pings that Google's documentation characterised as passively collected browser metadata.

No regulator has ruled definitively either way, leaving the choice between basic and advanced as a risk assessment rather than a settled question. Guidance in strict-enforcement jurisdictions, notably Germany, France, and the Netherlands, tends toward basic mode or regional overrides. A second criticism, aired in PPC Land's coverage of the Google Signals change, holds that consolidating controls into a signal the publisher must implement shifts compliance burden downward while the platform retains the structural benefit. Modelling itself remains opaque: advertisers cannot audit the estimates or see the underlying non-consented data.

Consent management platform. A CMP renders the banner, records the choice, and blocks scripts. Consent Mode transmits the result to Google. A site can run a CMP without Consent Mode, and the signals then never reach Google's tags, which is precisely the failure documented in the Harvest Digital case.

Transparency and Consent Framework. IAB Europe's TCF is an industry standard producing a TC String consumed by hundreds of vendors, and is mandatory for publishers serving Google ads in Europe. Consent Mode is proprietary to Google and used mainly by advertisers. Google mandated migration to TCF v2.3 by February 2026. The two coexist and are configured separately.

Google Signals. An Analytics admin setting governing whether data is associated with signed-in Google accounts. Until June 2026 it also acted as a second gate on advertising data. It is not a consent signal and never was.

Microsoft Consent Mode. Microsoft Advertising introduced its own framework for Universal Event Tracking, also keyed to a parameter named ad_storage, with a May 2025 deadline. The name and the parameter are shared; the implementations are not interchangeable.

On 15 June 2026, Google removed Google Signals from its role as co-controller of advertising data collection. For any Analytics property linked to a Google Ads account, ad_storage became the sole authority over whether advertising cookies and device identifiers are collected. PPC Land covered the announcement when Google published it on 16 April 2026, and examined its practical scope in May: organisations already running a certified CMP were largely unaffected, while sites that had used a disabled Signals toggle as a privacy backstop lost it without any action of their own.

Two further consolidations were announced without dates. Ads personalisation, currently controlled at account, property, link, and event level inside Analytics, is to be governed exclusively by ad_personalization, and IP addresses collected by the Google tag and SDK are to be encrypted and routed to the linked Ads account under Ads settings. As of August 2026, Google has confirmed both for later in 2026 without publishing a schedule.

A parallel track runs the other way. In December 2025, data transmission controls surfaced in Google tag settings, letting advertisers transmit limited advertising data or block it entirely when consent is denied. Simo Ahava, co-founder at Simmer, described the feature as a basic Consent Mode style control layered on top of an advanced setup.

• 25 May 2018: GDPR takes effect across the European Union
• 3 September 2020: Google launches Consent Mode in beta for a limited set of European advertisers
• April 2021: Modelled conversions from Consent Mode become available in Google Ads reporting and bidding
• 2 May 2023: The Digital Markets Act becomes applicable, designating Google a gatekeeper
• November 2023: Google announces Consent Mode v2, adding ad_user_data and ad_personalization
• March 2024: Consent Mode v2 becomes mandatory for personalised advertising and remarketing on EEA and UK traffic
• August 2024: Google Tag Manager introduces the consent mode override setting
• March 2025: Google's own CMP adds Consent Mode support for European regulations messages
• June 2025: Tag Diagnostics is integrated into the Google Analytics consent settings hub
• 21 July 2025: Google begins disabling personalisation, remarketing, and conversion tracking for non-compliant EEA and UK advertisers
• December 2025: Data transmission controls appear in Google tag settings
• 16 April 2026: Google publishes the Analytics data controls announcement
• 15 June 2026: Google Signals loses authority over advertising data; ad_storage becomes the sole control

• What is Consent Mode? - The original beta explainer, including supported tags, the ping payload, and the five launch CMPs.
• Google launches Consent Mode to enable conversions without cookies - Coverage of the rollout across Google Tag Manager and the global site tag.
• Google updates Consent Mode with two new parameters - The v2 parameter additions and the March 2024 deadline.
• New updates to Consent Mode from Google - EU User Consent Policy enforcement and the expanded CMP partner programme.
• Google Tag Manager introduces new Consent Mode Override Setting - Region-specific denied defaults without code changes.
• Google's CMP launches support for consent mode - Account-level flags letting Google's own CMP feed consent choices across its products.
• Google strengthens consent monitoring tools with diagnostic integration - Tag Diagnostics in the Analytics consent hub and EEA traffic share reporting.
• Consent Mode V2 enforcement is silently breaking Google Ads conversions - The Harvest Digital case and the mechanics of silent attribution loss.
• Google strips Analytics of ad data authority in June 2026 consent overhaul - The April 2026 announcement and its technical scope.
• Google Signals loses ad data control on June 15 - what it really means - Which configurations were actually exposed by the Signals change.
• Ex-Google analyst says Signals change benefits Google, not advertisers - Criticism of the consolidation and the resulting compliance burden.
• Google's hidden data controls let advertisers block tag tracking - The December 2025 data transmission controls.
• Microsoft Advertising mandates user consent signals by May 2025 - Microsoft's separate Consent Mode for Universal Event Tracking.
• Google mandates TCF v2.3 migration by February 2026 - The publisher-side consent framework running in parallel.
• Cookie consent in Europe is changing - what marketers need to know - Recovery-rate claims and the wider European enforcement picture.
• Every advertiser in EEA needs a Consent Management Platform (CMP) - Background on the CMP category Consent Mode depends on.

Who: Google built and maintains Consent Mode. Advertisers and publishers using Google Ads, Google Analytics, Floodlight, or Google Tag Manager implement it, usually through a certified consent management platform. Microsoft operates a separate framework under the same name.

What: An API that transmits granted or denied states for up to seven consent types to Google tags and SDKs, altering what they store and send, and generating the cookieless signals that feed conversion and behavioural modelling.

When: Beta from 3 September 2020, modelled conversions from April 2021, version two from late 2023, mandatory for European personalised advertising from March 2024, enforced from 21 July 2025, and the sole control over advertising data from linked Analytics properties since 15 June 2026.

Where: Technically global, since the parameters are sent on every request. Commercially decisive in the European Economic Area, the United Kingdom, and Switzerland, where the EU User Consent Policy applies and non-compliance disables measurement and remarketing.

Why: European law requires consent before storing or reading data on a device, while Google's advertising and bidding systems depend on persistent identifiers. Consent Mode preserves partial measurement across the gap, using aggregate estimation in place of observed conversions, and in doing so places the accuracy of a website's consent banner directly upstream of its campaign performance.