Why is Advanced Consent Mode not active in my setup?

Advanced consent mode is only active if Google tags load before the user interacts with the banner, set a default consent state and then receive an update from the banner. If the banner blocks the tags until consent is given, you are running basic consent mode, and users who decline send no signals at all. Even with a correct setup, conversion modeling in Google Ads and behavioral modeling in GA4 only start once Google’s data thresholds are met.

Two questions are often mixed up: is consent mode implemented in its advanced form, and is modeling already running? The first is a setup issue, the second also depends on data volume.

What is the difference between basic and advanced consent mode?

• Basic consent mode. Google tags are blocked until the user interacts with the banner. If the user declines, no data is sent to Google, not even the consent state. Conversion modeling in Google Ads then relies on a general model.
• Advanced consent mode. Google tags load when the page opens and set the default consent state, usually denied. If the user declines, the tags send cookieless pings. Google describes this as enabling better, advertiser-specific modeling.

Why is advanced consent mode not active?

1. The banner blocks the Google tag. Many consent tools or Tag Manager triggers only fire the Google tag after consent. That is basic consent mode by definition, regardless of any consent mode setting in the banner.
2. No default state before the first tag. The command gtag(‘consent’, ‘default’, …) or the matching consent mode template in Tag Manager must run before any Google tag. If it comes later, the first hits are sent without a consent state.
3. Parameters missing. Consent mode v2 uses four parameters: ad_storage, ad_user_data, ad_personalization and analytics_storage. If the banner only sets the older two, Google Ads features that depend on ad_user_data and ad_personalization lose data.
4. No update after the choice. The banner must send gtag(‘consent’, ‘update’, …) when the user makes a choice. If the banner loads asynchronously, wait_for_update in the default command gives it time before tags fire.
5. Thresholds not reached. According to Google, conversion modeling in Google Ads requires 700 ad clicks over a 7-day period per country and domain grouping. Behavioral modeling in GA4 has its own minimums for consented and non-consented traffic.

How do I check the setup?

1. Open the website in Tag Assistant in a new private window without making a choice. The first event must already show a default state with all four parameters.
2. Decline in the banner. With advanced consent mode, requests to Google still appear in the browser’s Network tab, but without cookies. If nothing is sent, the tag is blocked.
3. Accept in a second private window and check that an update to granted follows before the page view or conversion is sent.
4. In Tag Manager, check the consent settings of each tag. Google tags have built-in consent checks; third-party tags may need additional consent requirements.
5. Optionally, set url_passthrough to keep click information in the URL when cookies are not allowed. ads_data_redaction further reduces the ad data sent when ad_storage is denied; use it deliberately, not by default.

Let the Google tag load on every page, set the default state for all four parameters before it, and have the banner send only the update. Then verify with Tag Assistant that declined visits still send cookieless pings.

Sources

• Google for Developers: Consent mode overview
• Google for Developers: Set up consent mode on websites
• Google Ads Help: About consent mode modeling
• Analytics Help: Behavioral modeling for consent mode

Want to know whether your consent mode really runs in advanced mode? We check banner, Tag Manager and Google tags and make sure every consent and every declined visit is handled correctly. Book a free intro call or read more about our tracking agency.