A broken or missing Consent Mode v2 setup can show up as shrinking audiences, weaker measurement, restricted personalisation or less useful optimisation data. These technical restrictions are not the same thing as an automatic Google Ads account suspension.

What Does Consent Mode v2 Filtering Mean?

“Filtering” is useful shorthand, but Google does not use it as a single official name for every Consent Mode restriction. Google tags change their behaviour according to the consent state sent by a site’s Consent Management Platform (CMP), while Google advertising products limit how data can be used when the relevant consent is not granted.

Consent Mode v2 connects a visitor’s banner choice with Google Tag Manager or the Google tag, Google Analytics 4 and Google Ads. The CMP collects the choice; Consent Mode communicates it. Consent Mode does not provide or collect consent by itself.

ad_user_data controls consent for sending user data to Google for advertising, while ad_personalization controls personalised advertising. Google says both must be granted for personalised advertising.

Missing consent is not a safe substitute for an explicit denied state. Google groups “not set” with “denied” for several downstream restrictions. Defaults also need to be available before Google tags use consent; if consent defaults are set after Google tags have already fired, tags may read the consent state before the default is available and Consent Mode may not be applied as intended.

What Happens When a Google Ads Setup Is Non-Compliant?

A denied consent signal is not itself evidence of non-compliance. These restrictions can also appear in a correctly configured setup when users legitimately refuse consent. Non-compliance arises when required consent is not obtained, respected or communicated correctly.

If ad_personalization is denied, Google disables personalised advertising for that traffic and remarketing products do not receive the data. If ad_user_data is denied, personal data cannot be used for online advertising. Google also limits certain click-ID-keyed conversion exports from Analytics to Ads and identifies ad_user_data as required for measurement use cases including Enhanced Conversions and tag-based conversion tracking.

That can mean smaller remarketing pools, fewer observable conversions and weaker First-party signals. Smart Bidding can use modeled conversions where modeling is available, but more of the performance picture then depends on modeling rather than direct observation. Google says modeled conversions flow into downstream reporting and bidding once the relevant eligibility requirements are met.

Policy enforcement is different. Google’s EU User Consent Policy says unresolved non-compliance can ultimately lead to limits or suspension of Google products. Google’s documented enforcement process can also affect audience functionality and conversion measurement. An incorrect Consent Mode configuration is therefore not automatically an account suspension.

What Changed for Consent Mode v2 in 2026?

On June 15, 2026, Consent Mode’s Ads settings became the single control governing the use of Google Ads cookies and IDs collected through the Google Analytics tag and SDK. Google Signals now controls the association of Analytics-sourced data with signed-in user information for behavioural reporting.

A separate change is scheduled for later in 2026. Google says ad_personalization will become the exclusive control over whether Analytics data linked to Google Ads can be used for ads personalisation. As of August 10, 2026, Google has not published the exact effective date.

Google also says the rollout of IP-address-based ads measurement and ads-personalisation solutions in the EEA, UK and Switzerland begins in August 2026. Advertisers using these capabilities still need to consider the applicable consent and disclosure requirements rather than assuming IP-based measurement sits outside the privacy framework.

The advertiser’s headquarters do not decide whether Google’s regional consent rules matter. The EU user consent Policy applies to end users in the EEA, UK and Switzerland, including when the advertiser is based elsewhere.

There is an important implementation distinction. Google currently requires advertisers using Google tags or SDKs for measurement, or audience and ads-personalisation functionality, to pass end-user consent choices for relevant EEA traffic. Google says it does not currently expect advertisers to send a verified Consent Mode or TCF signal for UK or Swiss traffic, although the broader EU user consent Policy still applies in all three regions.

Which Consent Signals Affect Google Ads?

• ad_storage controls advertising-related storage such as cookies and, in this context, the use of Google Ads cookies and IDs collected through the Google Analytics tag and SDK.
• analytics_storage controls analytics-related storage. When denied in Advanced Consent Mode, cookieless measurements can still be sent.
• ad_user_data controls consent for sending user data to Google for advertising. It matters to Enhanced Conversions, tag-based conversion tracking and some Analytics-to-Ads conversion use.
• ad_personalization controls personalised advertising. When denied, remarketing and other personalised-advertising uses do not receive that traffic.

Permission to store an advertising cookie does not automatically mean permission to send user data for ads or use it for personalisation. The signals serve different purposes and need to reflect the user’s actual choice.

Signs That Consent Mode v2 Is Configured Incorrectly

Watch for remarketing lists that stop growing, unexpected audience shrinkage, a conversion drop without a comparable decline in sales, Enhanced Conversions losing eligible user-provided data for affected traffic, or widening differences between GA4 and Google Ads. Google Ads conversion diagnostics can also show Consent Mode and modeling status.

At tag level, common faults include missing ad_user_data or ad_personalization, default consent arriving after Google tags, consent never updating after an accept action, or incorrect states surviving rejection or withdrawal.

Duplicate CMP installations, old GTM templates, incorrect trigger order and a cookie banner that is not actually communicating with Consent Mode can create similarly confusing results.

These are symptoms rather than proof. Tracking outages, attribution changes, browser restrictions and campaign changes can produce similar patterns, so the consent state itself needs to be inspected before blaming Consent Mode.

Basic vs Advanced Consent Mode — Does It Change the Impact?

Yes, mainly in how much measurement evidence remains available when a visitor does not consent.

With Basic Consent Mode, Google tags are blocked until interaction with the consent banner. If consent is not granted, no information — not even consent status — is transferred to Google. Google Ads modeling therefore relies on a more general model.

With Advanced Consent Mode, Google tags can load with denied defaults and send cookieless measurements while consent remains denied. Those signals can support advertiser-specific conversion modeling where Google’s requirements and data thresholds are met.

Those thresholds are significant. For GA4 behavioral modeling, Google currently requires at least 1,000 events per day with analytics_storage='denied' for seven days, plus at least 1,000 daily users sending events with analytics_storage='granted' for seven of the previous 28 days. Meeting those volumes still does not guarantee modeling because Google applies additional model-quality requirements.

The measurement difference can be commercially meaningful. Google currently highlights TUI as a Consent Mode case study in which the advertiser measured 7% more Google Ads conversions after implementing Consent Mode and conversion modeling. That is a case-study result, not an expected industry-wide uplift.

Advanced Consent Mode does not bypass consent or make a site GDPR compliant. The underlying consent mechanism still has to obtain whatever legally valid choice is required.

How to Fix Consent Mode v2 Problems

1. Confirm that the CMP is actually connected to Consent Mode rather than simply displaying a Cookie Banner.
2. Check explicit defaults for ad_storage, analytics_storage, ad_user_data and ad_personalization.
3. In GTM, use Consent Initialization for the CMP or consent-setting tag so consent settings are available before other triggers run.
4. Test fresh reject, accept and granular-consent journeys. Updated consent states should match the choice made in the banner.
5. Use Google Tag Assistant to inspect default and updated consent states and check which tags fired or remained blocked.
6. Check Google Ads conversion diagnostics for Consent Mode and modeling status.
7. Review regional rules, duplicate installations and old CMP/GTM templates, then publish and retest.

A correct implementation will not necessarily produce modeled conversion data immediately. Google currently requires at least 700 ad clicks over seven days for each domain-and-country grouping before Consent Mode conversion modeling can become eligible, followed by model training and additional quality checks.

A missing Consent Mode uplift figure does not necessarily mean the implementation is broken either. Google only displays Consent Mode impact results when modeled improvement reaches at least 1% for the relevant domain-and-country segment.

CookieScript’s Consent Mode validation guidance checks several of the same failure points, including whether Consent Mode is enabled, whether its GTM tag uses Consent Initialization, whether the latest template is installed and whether the required consent categories are present.

How CookieScript Helps Keep Consent Mode v2 Working

CookieScript supports Google Consent Mode v2 and provides a Google Tag Manager Community Template covering the four core consent signals. Google also lists CookieScript among CMP integrations available for advertiser consent setup and provides dedicated CookieScript setup instructions.

For advertisers, the main benefit is having the CMP and Google tagging setup work together correctly. CookieScript can communicate consent changes to Google so the consent state follows the choice made in the banner and is available to dependent Google tags.

Geo-targeted implementations need a little more care. CookieScript currently recommends placing geo-targeted banner code directly in the website <head> rather than loading it through GTM, because GTM-based location detection can be unreliable. A normal, non-geo-targeted Consent Mode implementation can still use the GTM template.

That does not remove the need for testing. Consent Mode still depends on the banner, GTM configuration and Google tags exchanging the right state at the right time.

Managing the Rest of the Consent Setup

Getting the four Google consent signals right is only part of the job. A Google Ads setup can pass its Consent Mode checks while other tracking pixels, embeds or third-party scripts still operate under separate consent rules. The wider cookie consent setup therefore needs to cover what loads outside Google, how visitor choices are stored, and what happens when those choices change.

CookieScript is a Consent Management Platform (CMP) that Google includes among the CMP partners available for Consent Mode setup. CookieScript also identifies itself as a Google-certified CMP with Gold tier status.

Beyond the Google Ads configuration covered above, relevant CookieScript tools include:

• a customizable cookie banner and automatic third-party script and cookie blocking, helping apply consent choices to advertising and tracking technologies outside Google;
• cookie scanning and automatic monthly scans, which can surface tracking technologies introduced after the original Consent Mode setup;
• visitor consent recording, providing a record of the choices users made;
• support for Global Privacy Control and IAB TCF 2.3;
• cross-domain and subdomain consent sharing for suitable multi-site setups;
• integrations for platforms including Wix, Shopify and Webflow, plus the CookieScript API for more customised implementations;
• cookie banner sharing for organisations managing consent across multiple accounts; and
• a Cookie Policy and Privacy Policy Generator for the disclosure side of the wider privacy setup.

These features address parts of the consent stack that Consent Mode itself does not. Google’s consent signals govern how Google products behave; they do not automatically block every third-party tracker, maintain a current cookie inventory, preserve consent records or manage privacy controls across an entire site.

CookieScript also provides a 14-day free trial of its Plus plan without requiring a credit card.

Consent Mode v2 Compliance Checklist

Treat Consent Mode as production infrastructure rather than a one-time tag project.

• Give one owner responsibility for the CMP, GTM and Ads/Analytics consent setup.
• Retest consent after redesigns, checkout changes, CDN changes and new marketing tags.
• Keep a change log for banner settings, GTM versions and regional rules.
• Monitor audience size, conversions and attribution for unexplained breaks.
• Re-scan for newly introduced cookies and scripts.
• Periodically test behaviour from the EEA, UK and Switzerland.

Consent Mode does not replace GDPR or ePrivacy obligations. Where consent is relied on under GDPR, European guidance requires it to be freely given, specific, informed and unambiguous. In the UK, the ICO says most commercially viable online advertising currently requires consent where information is stored on or accessed from a user’s device.

Regulatory scrutiny is not theoretical. In April 2026, the UK ICO reported that 99% of the UK’s top 1,000 websites met its cookie-banner compliance standards following focused ICO work with industry.

For international websites, the privacy picture extends beyond Europe. Depending on where visitors are located and how their data is processed, organisations may also need to account for California’s CCPA, as amended by the CPRA, Canada’s federal PIPEDA where applicable alongside relevant provincial privacy laws, China’s PIPL and Brazil’s LGPD, as well as other national and state privacy rules.

These frameworks do not impose identical consent requirements. Regional CMP settings, cookie controls and tracking configurations should therefore reflect the rules that actually apply to each audience rather than treating one Google Consent Mode v2 setup as universal compliance.

Conclusion

A broken Consent Mode v2 setup is more likely to damage advertising data than to produce an instant Google Ads ban. The immediate cost is usually lost personalisation, smaller usable audiences, weaker measurement and less complete optimisation signals.

A CMP such as CookieScript can make the setup easier to maintain, but sound consent design, correct GTM sequencing and regular testing are still essential. Consent Mode works best as part of a broader privacy and Google Ads governance process rather than as a one-time compliance checkbox.

Frequently Asked Questions

Can Google Ads stop remarketing if Consent Mode v2 is missing?

Remarketing can be restricted when Google does not receive the required consent for personalised advertising. Both ad_user_data and ad_personalization need to be granted for personalised advertising in Google advertising platforms.

Can an incorrect Consent Mode setup suspend a Google Ads account?

Not automatically. A Consent Mode configuration error is not itself an automatic suspension trigger. Separate enforcement under Google’s EU User Consent Policy can, if non-compliance remains unresolved, lead to limits or suspension of Google products, including audience and conversion-measurement functionality.

Why did my Google Ads audiences suddenly get smaller?

Consent settings are one possible cause, particularly where ad_personalization becomes denied or unavailable. Tag failures, audience eligibility changes, traffic shifts and other measurement problems should also be checked before attributing the change to Consent Mode.

What happens if ad_user_data is missing?

When the necessary consent is not granted, Google restricts advertising uses involving personal data. That can affect Enhanced Conversions-related measurement and some Analytics-to-Ads conversion flows.

Does Consent Mode v2 work when users reject cookies?

Advanced Consent Mode can send limited cookieless signals while relevant storage consent is denied and use them for modeling where Google’s eligibility requirements are met. Basic Consent Mode sends no information to Google when consent is not granted.

How can I check whether Consent Mode v2 is working properly?

Use Tag Assistant to inspect default and updated consent states, verify firing order in GTM Preview and check Google Ads conversion diagnostics. All four core consent values should be present and should update correctly after banner interaction.