How to Choose Between Basic and Advanced Google Consent Mode
Google Consent Mode has two implementations, basic and advanced. Both pass a visitor’s choice to Google tags. They differ in what Google tags do while consent is denied, and that difference affects both measurement and legal risk. This article compares the two and explains how to set each with Captain Compliance.
The difference
Basic | Advanced | |
|---|---|---|
When Google tags load | Only after the visitor’s consent state allows them | On every page, whatever the consent state |
While consent is denied | Nothing is sent to Google | Google tags send cookieless pings, without cookies or advertising identifiers |
Modeling in Google’s reports | Limited, because Google receives nothing from visitors who have not consented | Google uses the pings to model conversions and behavior |
A network capture before a choice or after Reject | Shows no requests to Google | Shows requests to Google |
Why it matters for defensibility
Privacy claims and regulator inquiries often start from a recording of a site’s network traffic. The question is what left the browser before the visitor agreed, or after the visitor refused. See How to Avoid Network-Traffic-Based Privacy Litigation.
In advanced mode, the answer includes requests to Google. The requests carry no cookies, but like any web request they reveal the visitor’s IP address, the page address, and browser details. You need to be ready to explain why those requests are acceptable.
In basic mode, the answer is that nothing went to Google. That is easier to show and easier to defend.
U.S. wiretapping-style claims focus on third parties that receive a visitor’s communications without consent. European opt-in rules focus on what happens before consent. Advanced mode leaves more to argue about under both.
Advanced mode is not unlawful in itself. Google documents both modes, and many organizations use advanced mode with their counsel’s approval. The choice is a matter of risk tolerance.
What basic mode costs
In opt-out regions, little. Captain Compliance sets the default to granted there, so Google tags run from the first page view. Basic mode only stops data from visitors who reject, turn on Do Not Sell or Share, or send a Global Privacy Control signal.
In opt-in regions, more. You receive nothing from visitors who reject or never choose, and Google has no pings to model from.
Basic mode withholds data in exactly the cases where sending it is hardest to defend.
Set each mode with Captain Compliance
Captain Compliance sends the same Consent Mode signals in both modes. The mode depends on how your Google tags are set up.
Advanced: leave Google tags on their usual triggers, with only their built-in consent checks.
Basic: on each Google tag, add the matching consent type as an additional consent requirement, such as
analytics_storagefor Google Analytics andad_storagefor Google Ads. The tag then does not fire until that type is granted. See How to Gate GTM Tags with Native Consent Settings.Tags that fire very early need one more step in either mode. See How to Fire Early-Loading Tags After Consent with CC - Consent Ready.
You can mix the two, for example basic for advertising tags and advanced for analytics.
Without Google Tag Manager, basic mode means that the Google script does not load until consent. See How Captain Compliance Works with Google Consent Mode and How to Block Scripts Before Consent with Auto Blocking and Strict Mode.
How to decide
Choose basic if defensibility comes first: your sector or region sees active litigation, you want the simplest account of what your site sends, or your counsel requires that nothing is sent before consent.
Choose advanced if modeled measurement is essential and your counsel has accepted cookieless pings.
Write down the decision, who made it, and why. A recorded reason is easier to defend than an unexamined default.
This article describes product behavior and common considerations. It is not legal advice. Confirm your approach with your own counsel.
Check which mode is running
Open your site in a private or incognito browser window, and open the browser’s developer tools on the Network tab.
In a region where consent starts as denied, or after you select Reject, filter the requests for
google.In basic mode, there are no requests to Google Analytics or Google Ads. In advanced mode, there are requests that include
gcs=G100, which marks consent as denied.
For a full test plan, see How to Test Your GTM Consent Setup.
