Google Consent Mode v2 Explained: Signals, Modes, Limits

Google Consent Mode v2 is a mechanism that passes a visitor’s consent choices to Google tags so they behave accordingly. It works with a consent banner and does not replace one, and it covers Google’s tags only. It is not a legal basis by itself.

General information, not legal advice. Check Google’s current documentation and your regulator.

The four signals

Signal	Controls	Added in
ad_storage	Storage for advertising	v1
analytics_storage	Storage for analytics	v1
ad_user_data	Whether user data may be sent to Google for ads	v2
ad_personalization	Whether data may be used for personalised ads	v2

These details match the summary in BusinessMCP’s consent mode guide, which cites Google’s own consent mode overview. Implementation uses a default call before tags load and an update call once the visitor chooses.

Basic versus advanced

Basic mode blocks Google tags until consent is granted, so declining visitors are invisible to them. Advanced mode loads tags with defaults denied and sends cookieless pings, which enable more detailed conversion modeling. Whether advanced mode is acceptable depends on jurisdiction, so involve counsel. The guide itself says that assessment depends on where your visitors are.

Key takeaway: Consent Mode controls how Google tags behave. It does not tell you whether your own analytics, replay or ad tools need consent, and it does not make a banner legal.

What modeling means

When visitors decline, Google may estimate missing conversions. Those figures are modeled, not observed. The guide notes behavioral modeling in GA4 requires minimum traffic and event thresholds that smaller sites may not reach, and modeled data cannot be reconciled visitor by visitor. Treat modeled numbers as estimates and keep them labelled as such in reports.

What it does not cover

Consent Mode is scoped to Google’s tags. A separate cookieless, first-party analytics tool is outside it, and its legal treatment depends on what it stores and processes. That is the subject of GDPR-compliant web analytics and analytics without a cookie banner.

Is it required?

Google asks advertisers with EEA and UK audiences to send v2 signals for ad personalization and remarketing since March 2024, according to the guide’s FAQ, which clarifies this is contractual rather than a legal mandate. If you do not use Google Ads features that depend on those signals, your obligations differ. Verify with Google’s current documentation, since policies evolve.

Implementation outline

1. Choose a consent platform that supports Consent Mode.
2. Set default consent states to denied for the regions that need it, before Google tags load.
3. Send an update call when the visitor accepts or declines.
4. Test in a private window: decline first, then check which Google requests fire.
5. Repeat with acceptance and confirm tags upgrade.
6. Document your choice of mode and the reasoning.

Make declining as easy as accepting. The UK ICO stresses “reject all” prominence, as quoted in the guide, and its cookies guidance is the primary source to read.

Common mistakes

• Setting defaults after tags load, so the first hit goes out ungoverned.
• Treating Consent Mode as a substitute for a banner.
• Assuming modeled conversions equal measured ones.
• Forgetting non-Google scripts that set their own identifiers.
• Not retesting after site or CMP updates.

Alternatives to a heavy Google stack

If Google’s ad features matter little to you, a cookieless tool can replace the analytics part and shrink the consent surface. BusinessMCP’s web analytics page says no banner is required for its script itself while noting that other tools may still need consent, and its script supports gate-all or split consent. Read Google Analytics alternatives before you decide. Whatever you pick, keep a record of what each script does and review it when your tools change.

A short worked scenario

A European online shop uses Google Ads and GA4 and runs a consent banner. Visitors who accept send full signals, and Google tags work as usual. Visitors who decline send denied signals. In basic mode, Google tags do not load for them, so their visits and conversions are not seen by Google at all. In advanced mode, tags load with denied defaults and send cookieless pings, from which Google may model some conversions.

The shop’s marketer sees a gap in reported conversions after introducing the banner, partly because fewer people are tracked and partly because modeling fills in only some of it. The honest framing for management is: reported Google conversions are lower and partly estimated; actual orders from the shop’s own database are the reference. Reconciling the two monthly protects you from budget decisions based on a shrinking, modeled number.

Pairing Consent Mode with a cookieless tool

Some teams keep Google tags for advertising and add a cookieless tool for reporting. That gives a measured, unmodeled view of traffic for the entire audience, including visitors who declined advertising cookies, while Consent Mode governs only the advertising stack. BusinessMCP’s web analytics is one example of such a tool, with its own consent attributes for gating identification and recordings. Check that each tool’s legal basis is documented. See also analytics without a cookie banner and the GA4 migration plan if you are reducing reliance on Google.

Keeping it working

Consent setups break quietly. A banner update, a new tag in a tag manager or a theme change can alter the order in which scripts load, and the default consent call may end up firing late. Schedule a quarterly test: open a private window, decline everything, and watch the network tab for Google requests. Repeat with acceptance. Record the result with a date and the tool versions.

Also keep a short written note about why you chose basic or advanced mode, who approved it and when it will be reviewed. Regulators and customers rarely ask for the technical detail first; they ask whether you thought about it. A dated page that answers that question is worth the ten minutes it takes to write, and it saves a long search through old tickets the day someone asks.

Finally, brief your marketing team. If they add a new advertising platform tag without telling whoever owns consent, the setup you tested last quarter is no longer the setup that runs today.