Architecture
Google Consent Mode v2: Basic vs Advanced
See what loads before a visitor decides, how measurement differs and which questions settle the implementation choice.
In brief
The modes differ primarily in pre-consent tag behavior. Select one deliberately and test the network, not just the banner.
Basic mode
Google tags are blocked until the visitor grants relevant consent. Before that choice, no Google tag data is sent. After permission, permitted tags load and use the granted state. This is the clearest path when you require no Google requests before consent.
If your requirement is no Analytics requests before permission, follow the GA4 prior-blocking procedure and verify the network trace.
- Prior blocking must cover the real script and request paths.
- Google's modeling options differ from Advanced mode; verify reporting expectations with your analytics team.
Advanced mode
Google tags load with a denied default and can send cookieless pings before permission. After a granted update, they can use the granted behavior. Denied does not mean no network traffic in this mode.
Review the mode with your privacy owner for each region and purpose. Google's technical description is not a legal conclusion for your site.
What both modes need
Both modes need the four v2 signals, a valid default before tags, a same-page update after the banner choice and correct mapping of analytics versus advertising. Both also need separate controls for vendors that do not support Google's consent commands.
Compare a real first visit
Use a fresh profile and inspect Network and Storage before touching the banner. In Basic mode expect Google tags to be absent. In Advanced mode expect tags to load with denied state and potentially limited pings. Then accept analytics only and verify advertising remains denied.
- Do not infer Basic mode from a banner that merely covers the page.
- Do not infer Advanced mode from a GA4 report; inspect the actual request sequence.
Make the decision explicit
Write down which Google products run, whether any Google request is permitted before permission, who approved that behavior, and how it will be tested. Revisit the decision when you add Ads, remarketing or new regions.
Try it
Choose a mode to investigate
Agree on pre-consent behavior with your privacy owner first. The technical mode should implement that decision.
Continue with a related guide
Primary sources
Reviewed 15 October 2026. Validate product interfaces and requirements for your own implementation.
Check the implementation on your site
Consentory helps teams inspect trackers, configure prior blocking and document consent choices. The guides above give you a test plan before rollout.