Opens in a new tab
Home/Blog/Consent Mode v2 on WordPress: the four signals

Consent Mode v2 on WordPress: the four signals

Privacy & CompliancePhillip StemannNovember 11, 2026

Last updated: November 18, 2026

Title card: Consent Mode v2 on WordPress: the four signals
In this article
Key takeaways
  • Consent Mode is a way to tell Google tags what the visitor has agreed to. It has four signals: ad_storage, analytics_storage, ad_user_data and ad_personalization. Each is granted or denied.
  • Order is everything. The default command must run before any Google tag, and the update command runs after the visitor chooses. Out of order, Google says, defaults will not work.
  • Basic and advanced differ in when tags load. In Google’s words, basic blocks tags until the visitor interacts with the banner and sends nothing before that. Advanced loads tags on page open with defaults set to denied, and sends the consent state and cookieless pings while consent is denied.
  • GA4 behavioral modeling needs the advanced implementation, plus data thresholds: 1,000 events a day with analytics_storage denied for at least 7 days, and 1,000 daily users with it granted on at least 7 of the previous 28 days.
  • Consent Mode does not collect consent, does not make a banner lawful and is not legal advice. It passes a decision to Google tags. Whether the decision was validly obtained is a question for your regulator and your counsel.

Most WordPress sites get Consent Mode by installing a banner plugin and ticking a box. The box can be ticked while the signals are wrong, late or missing. This post explains the four signals, what default and update mean, how basic and advanced differ in Google’s own wording, what each choice means for GA4 and Google Ads, how the common WordPress consent plugins expose it, and how to test it. It is the hub of our privacy and browsers series.

One boundary up front: this is a technical explainer. It is not legal advice, and nothing here says that any setup is or is not compliant. Where the law matters, I point to the people who decide it.

What Consent Mode is, and what it is not

Google’s Tag Manager Help describes consent mode as something that “allows you to adjust how your Google tags behave based on the visitor’s interaction with the consent banner on your website.” Two parts of that sentence matter. There has to be a banner (a consent management platform, or CMP) that records the visitor’s choice, and the tags have to be told about it.

Consent Mode is the second part only: you declare a state, and Google tags change what they read, write and send. It does not show a banner or store a record of consent. That is the CMP’s job and, behind it, a legal decision.

The four signals

Google’s consent guide for the tag platform lists four consent types, each set to granted or denied.

Four cards: ad_storage covers advertising cookies and IDs, analytics_storage covers first-party analytics cookies, ad_user_data covers sending advertising-related user data to Google, ad_personalization covers personalized ads. The last two were added in Consent Mode v2.
The four signals and what each one is about. Wording condensed from Google’s consent guide and Ads Help.
Signal What Google says it does Practical effect
ad_storage Controls cookie storage for advertising. Google Ads Help says it “controls the usage of Google Ads cookies and IDs from the Google Analytics tag and Firebase SDK in Google Ads.” When denied, the Analytics help page says no advertising cookies are written or read.
analytics_storage Controls cookie storage for analytics measurement. When denied, GA4 “will not read or write first-party analytics cookies” and sends cookieless pings instead (Analytics Help).
ad_user_data Sets consent for sending user data related to advertising to Google. Added in version 2.
ad_personalization Sets consent for personalized advertising. Added in version 2.

The first two are about storage on the visitor’s device. The last two are about what is done with the data once Google has it. Google’s Tag Manager Help page says advertisers must collect consent from end users based in the EEA and share the consent signals with Google to keep using tags for measurement, ad personalization and remarketing.

Google’s docs list further types (functionality_storage, personalization_storage, security_storage) that some plugins also set; this post focuses on the four above.

Default and update

You use two commands. default declares the state before the visitor has chosen. update changes it after they do. This is the example in Google’s guide:

// 1. Before any Google tag
gtag('consent', 'default', {
  'ad_storage': 'denied',
  'ad_user_data': 'denied',
  'ad_personalization': 'denied',
  'analytics_storage': 'denied'
});

// 2. After the visitor makes a choice
gtag('consent', 'update', {
  'ad_user_data': 'granted',
  'ad_personalization': 'granted',
  'ad_storage': 'granted',
  'analytics_storage': 'granted'
});

Signals are granted independently. A visitor who accepts statistics but refuses marketing should produce an update with only analytics_storage granted. Plugins map banner categories to signals, and that mapping is where many bugs live.

Timeline of five steps: default command runs first, Google tag loads or waits, wait_for_update holds tags for a number of milliseconds, the visitor's choice or a stored choice is read, then the update command changes the state.
From default to update. The order is the part people get wrong.

Order of operations

Google’s guide is blunt about this: “If your consent code is called out of order, consent defaults won’t work.” The sequence is: load the consent solution so the default is set, load the Google tag, then call update after user interaction. Tag Manager Help adds that if Google tags load before the visitor has interacted, “Google won’t be able to verify user consent choices and this may lead to loss in data.”

wait_for_update

Many consent tools load asynchronously and read a stored choice from a cookie or local storage. If the Google tag fires before that finishes, it sees only the default. wait_for_update tells tags to wait a number of milliseconds for an update before they send anything:

Add 'wait_for_update': 500 to the default call (Google’s example value) and tags wait up to half a second for an update.

One plugin below documents a default of 2000, so the value trades waiting for slow consent tools against delaying measurement.

Region-specific defaults

The default command accepts a region list of ISO 3166-2 codes such as 'ES' or 'US-AK', for example 'region': ['ES', 'DK']. Google says the most specific setting wins, so a subdivision overrides its country. Which regions need a denied default is a legal question; technically it is just a list.

URL passthrough and ads data redaction

Google’s guide also documents url_passthrough (passes ad click and session information through URL parameters when cookies are denied) and ads_data_redaction (redacts ad identifiers when ad_storage is denied). Whether to enable them is for your privacy adviser to decide.

Basic versus advanced

This is the part people mix up, so here is Google’s wording. On Google’s About consent mode page, basic consent mode is: tags “blocked until user interaction with a consent banner”, with “no data is sent before a user consents – not even the default consent status.” Advanced consent mode: tags “load with defaults set to denied, unless configured otherwise”, and “when consent is denied, consent state and cookieless pings are sent. When consent is granted, cookies are written and all measurement data is sent.”

The tag platform’s overview puts the definitions this way: in basic, you “prevent Google tags from loading until a user interacts with a consent banner”; in advanced, “Google tags load when a user opens the website or app.”

Two-column comparison of basic and advanced consent mode: tag loading, behavior when consent is denied, behavior when granted, and the conversion modelling type used by Google Ads.
Basic versus advanced, restricted to what Google’s pages state.

Two clarifications:

  • The documented difference is when tags load and what is transmitted while consent is denied. Whether a cookieless ping is acceptable for your site is a legal question this article cannot answer.
  • Advanced does not mean cookies are set before consent. Google states that with advanced, cookies are written when consent is granted. While consent is denied, the tags send consent state and cookieless pings.

What a cookieless ping contains is documented in Analytics Help: functional information (timestamp, user agent on web, referrer) and coarse information (Boolean consent state, whether an ad click identifier such as GCLID or DCLID is present, random numbers generated per page load, and the consent platform’s developer ID). Google says Analytics does not store or log IP addresses. That is Google’s statement; a regulator may ask different questions.

What it means for GA4 and Google Ads

GA4

With analytics_storage denied, GA4 does not read or write its first-party analytics cookies and sends cookieless pings. In advanced mode, Google can use those pings for behavioral modeling, which uses machine learning to estimate the behavior of users who declined analytics cookies from similar users who consented. The eligibility page sets these data requirements:

  • at least 1,000 events per day with analytics_storage='denied' for at least 7 days, and
  • at least 1,000 daily users sending events with analytics_storage='granted' for at least 7 of the previous 28 days.

The same page requires the advanced implementation: tags loaded before the consent dialog appears, and Google tags loading in all cases. It adds that meeting the thresholds does not guarantee eligibility, because the model applies further quality criteria. To see modeled data in reports, the reporting identity must be set to “Blended”.

In practice: on basic mode, or below those volumes, expect declined consent to remain a gap. Report it as a gap rather than scaling numbers up by hand.

Google Ads

Ads Help lists the conversion modeling difference in the same comparison table: a general model (less detailed modeling) under basic, and an advertiser-specific model (more detailed modeling) under advanced. Ads Help says ad_storage controls whether Google Ads cookies and IDs from the Analytics tag are used. The Tag Manager page states the signals need to reach Google for remarketing and personalization to continue for EEA users. I found no Google page with figures for how much modeling recovers, so I quote none.

If you send conversions from the server to Google Ads, for instance as offline conversions, the browser-side consent signals do not travel with those requests by themselves. See whether server-side tracking bypasses consent and Google Ads offline conversions for WordPress.

How WordPress consent plugins implement it

Everything below comes from each vendor’s own documentation, fetched in October 2026. I list what each page states, not which tool is best.

Tool What its documentation says
Complianz Offers basic and advanced modes. Before interaction only security_storage and functionality_storage are set to granted; the four signals are managed. Works with Google Tag Manager (container ID in the wizard) or direct gtag with a GA4 tag ID. With Google Site Kit, only advanced consent mode is available.
CookieYes Enable “Support GCM” for basic. Also enable “Allow Google tags to fire before consent” for advanced. Maps ad_storage, ad_user_data and ad_personalization to its Advertisement category and analytics_storage to Analytics. Default region “ALL”, customizable with ISO 3166-2 codes. “Wait for update” defaults to 2000 ms.
Real Cookie Banner Activated under Cookies > Settings > Google Consent Mode. Supports the seven standard consent types, sends them through gtag.js and, when enabled, to Google Tag Manager. With geo-restriction on, it transmits per-country treatment. It says it is not a certified Google CMP partner, because certification would require things it declines to do, such as loading services through GTM before consent.
Borlabs Cookie Install the Google Analytics or Google Ads package and enable Consent Mode there; basic consent mode is enabled when you install the package. For more complex setups it recommends Google Tag Manager. The page does not list signal defaults or region settings.
Cookiebot The plugin page says Cookiebot is certified by Google and supports Consent Mode v2, and that you enable Consent Mode in the Cookiebot admin without custom code. Cookiebot’s support-center pages returned an error when I fetched them, so I am not describing its basic or advanced options.
Site Kit by Google Not a banner. Consent mode is enabled under Site Kit > Settings > Admin Settings and needs the WP Consent API plugin plus a separate consent plugin that shows the banner. By default Site Kit updates consent for the statistics and marketing categories. The documentation names the EEA, Switzerland and the UK as the default regions.

Two patterns in that table are worth noticing. First, “basic” and “advanced” often come down to one toggle about whether Google tags may fire before consent, so reading the toggle label matters more than reading the plugin’s marketing page. Second, if a plugin loads your Google tag itself (Site Kit, a Borlabs package) it controls the order; a second tag pasted into the theme breaks that.

Checklist of eight checks for a WordPress consent setup: default before tags, region defaults agreed with an advisor, all four signals, deliberate basic or advanced, update on every choice, wait_for_update, no stale cached state, and testing in Tag Assistant and the Network tab.
An implementation checklist you can run against any consent plugin.

What to test, and how

Tag Assistant

Google’s verification guide uses Tag Assistant. Enter your site’s URL, then check the Summary for the earliest and latest Consent events. Under API calls, confirm that ad_storage, ad_personalization, ad_user_data and analytics_storage were set. The Output tab’s Consent section shows “On-page Default” and “On-page Update” columns. The two questions to answer are whether the default is set before any tags fire and whether the update follows each choice.

Network tab

Google’s pages that I fetched do not document the gcs and gcd request parameters, so treat what follows as third-party, not official. Simo Ahava’s write-up and Consent Mode HQ describe gcs as G1xy, where x and y are 1 (granted) or 0 (denied) for ad storage and analytics storage. gcd is a longer code that carries the consent states. Consent Mode HQ warns that gcs cannot show ad_user_data or ad_personalization, so G100 can sit next to granted v2 signals. Look for them on requests to /g/collect or /ccm/.

A repeatable test, in a clean private window each time:

  1. Open the site with DevTools Network open and “Preserve log” on. Do not touch the banner. Note the first Google requests and their gcs/gcd values. In basic mode there should be none yet; in advanced there should be pings with denied states.
  2. Reject everything. Confirm no _ga cookie appears in Application > Cookies.
  3. Clear site data, reload, accept everything. Confirm the update fires and cookies appear.
  4. Accept only statistics. Confirm analytics is granted and ads signals stay denied.
  5. Reload as a returning visitor; the stored choice should apply without a flash of the default state.
  6. Repeat in Safari and a mobile browser (our Safari ITP post explains why cookie lifetimes differ).

Common mistakes

  • The default is set after the tags fire.
  • Only two signals. An older setup omits ad_user_data and ad_personalization. Google says certified CMP providers update automatically; with a self-maintained banner you update it yourself.
  • Cached banner and cached state. A page cache that stores HTML with a rendered consent state can serve one visitor’s choice to the next. Read the choice client-side from the visitor’s own storage, and test logged out in a private window after purging the cache.
  • Two tags, two defaults. Pick one owner for the Google tag and the default.
  • Counting on modeling without checking eligibility. Basic mode, or traffic below the thresholds, means no GA4 behavioral modeling.

What Consent Mode does not do

Consent Mode controls how Google tags behave. It does not:

  • Make you compliant. Google’s EU user consent policy applies to users in the EEA, the UK and Switzerland and asks organizations to obtain legally valid consent for cookies or other local storage where legally required, and for the collection, sharing and use of personal data for ad personalization. It also asks for records of consent, clear instructions for revoking consent and identification of the parties that receive data. A signal passed to a tag does not discharge those obligations.
  • Control tags that are not Google’s. Meta, TikTok, LinkedIn and other scripts need blocking or their own consent handling. The Google signals do not do that for them.
  • Cover server-side sends. If your server forwards a purchase to an ad platform, the decision to send it is made in your code, not in the browser. See Does server-side tracking bypass consent?.
  • Replace a legal view. Which analytics need consent, which defaults apply in which country and whether cookieless pings are acceptable differ by jurisdiction and change over time. Ask your national data protection authority’s guidance and your own counsel. See GDPR and WordPress analytics in Denmark and whether you need a cookie banner for regulator sources; neither replaces advice.

I deliberately left out an effective date for the Google requirement. The pages I fetched from Google for this article do not state one, so I am not asserting one. Check the current wording on Google’s help page yourself.

Frequently asked questions

Do I need Consent Mode if my site has a cookie banner?

A banner collects the choice; Consent Mode passes it to Google tags. Google’s Tag Manager Help says advertisers need to collect consent from EEA end users and share the signals with Google to keep using tags for measurement, personalization and remarketing. Whether you need it depends on whether you use Google tags and advertising features for those visitors.

Is advanced mode better than basic?

It depends on what you need and what your advisers accept. Advanced sends cookieless pings while consent is denied and is required for GA4 behavioral modeling. Basic sends nothing before consent. Neither one answers the legal question.

What happens if I do not set a default?

Google’s guide says defaults will not work if the code is called out of order, and that tags loading before a visitor interacts can leave Google unable to verify the choice. Set the default first and verify it in Tag Assistant.

Related reading

Traculo forwards events from its servers to GA4, Google Ads, Meta and other platforms, and shows a delivery log for each event, which is useful when you need to see what was actually sent. It does not make a consent decision for you; that stays with your banner and your advisers. You can read how it works on the server-side event tracking page, or look at your traffic by browser and country in Traculo’s website analytics, free up to 2,000 events a month.

ShareLinkedInXEmail

About the author

Track what matters, without the guesswork

Traculo gives WordPress sites analytics, funnels and server-side event forwarding in one dashboard. Start on the free plan with 10,000 events a month.

Try Traculo free

Related articles

Title card: Do you need a cookie banner for WordPress analytics?
Privacy & ComplianceNovember 20, 2026

Do you need a cookie banner for WordPress analytics?

Whether WordPress analytics needs a cookie banner depends on what you store and your country's rules. CNIL, Denmark, Ireland, Germany compared.

Read more
Title card: GDPR and WordPress analytics: the Danish picture
Privacy & ComplianceNovember 18, 2026

GDPR and WordPress analytics: the Danish picture

What Datatilsynet, DIGST, the CNIL and the EU-US Data Privacy Framework say about WordPress analytics in Denmark, as of October 2026. Not legal advice.

Read more
Title card: How much data do ad blockers cost a WordPress site?
Privacy & ComplianceNovember 16, 2026

How much data do ad blockers cost a WordPress site?

What ad blockers actually block, what the public numbers show, and how to measure your own analytics loss on WordPress using logs, GA4 and Search Console.

Read more