Consent Mode: Basic vs. Advanced—An Overview of the Differences
Management Summary
The discussion surrounding Google Consent Mode is often framed primarily from a regulatory perspective. From a technical perspective, however, there are also significant differences between implementations in Basic and Advanced Consent Mode. These differences affect the loading of Google tags, data collection, and the available modeling methods in Google Analytics 4 (GA4) and Google Ads.
In the following, both variants are classified from a technical perspective and compared with one another.
Basic and Advanced Consent Mode Explained in a Nutshell:
Basic Consent Mode
In Consent Mode Basic, Google tags remain blocked by default.
If consent is not provided, no data will be transmitted. The visit will not be tracked by web analytics. The tags will load only after the visitor has actively given consent. They will then transmit data to GA4 (Google Analytics 4) or Google Ads.
Conversion modeling in Google Ads is possible under certain conditions. These modeled conversions are based on data from users who have given their consent, as well as on historical models. To continue using advertising features, companies must enable Consent Mode.
Advanced Consent Mode
In Consent Mode Advanced, the Google tags load even before the user interacts with the cookie banner. The system immediately reports the current status.
If consent is not provided, no analytics or advertising cookies are set; however, so-called ” cookieless pings ” are sent to Google. These signals do not contain any personal data, but they provide information about interactions that have taken place. Google uses these data streams for two modeling methods:
- Behavioral Modeling estimates missing usage and event data in GA4.
- Conversion modeling fills in missing conversions in Google Ads to optimize automated bidding strategies.
Once consent is given, the standard Google tags are executed and collect the relevant analytics and advertising data.
To ensure error-free setup, we recommend performing a structured review of Consent Mode in the GA4 settings.
What are the technical differences in Consent Mode?
Both approaches exhibit fundamental differences in their technical design:
| Criterion | Basic Consent Mode | Advanced Consent Mode |
|---|---|---|
| General Requirements | Flawless implementation of Consent Mode, including the Consent Mode v2 signals (ad_storage, analytics_storage, ad_user_data, ad_personalization). | Flawless implementation of Consent Mode, including the Consent Mode v2 signals (ad_storage, analytics_storage, ad_user_data, ad_personalization). |
| Google Tag Behavior Before or Upon Rejection | Google tags are completely blocked. No data is being transmitted. | Preload Google tags As long as consent has not been given or the consent status is set to “denied,” Analytics or advertising cookies are set. Instead, the Google tags send anonymized, cookie-free pings. |
| Data Collection in the Event of Rejection | No data collection at (0% of users who declined were recorded). | Functional, anonymous signals (pings) without identifiers. |
| Data Collection with Consent | Tracking begins only after explicit opt-in. | Full tracking only after opt-in (before that, only the pings mentioned above) |
| Data Availability | Data collected exclusively from consenting users through observation and actual measurement. | A combination of actual measured data and mathematically modeled data. |
| Supported Google Tags | Blocked across all systems until consent is given. | Natively integrated. Tags dynamically adapt their behavior to the status. |
| Behavioral Modeling (GA4) | Not possible. Not available due to the lack of real-time pings. | Possible Provided that the requirements are met and the thresholds in the Google Analytics 4 property have been reached.* |
| Conversion Modeling (Google Ads) | Limited. Modeled conversions in Google Ads are based on the general model. | Possible. Advertiser-specific Conversion Modeling in Google Ads, provided the requirements are met.** |
| * The thresholds are: 1. The property must record at least 1,000 daily events with analytics_storage=’denied’ (denial) on at least 7 days. 2. At least 1,000 daily users must send events with analytics_storage=’granted’ (consent) on at least 7 of the last 28 days. **Training period for the model: at least 700 ad clicks per day, per country, and per domain group over a 7-day period. |
Google Tag Manager’s Debugging Consent Mode helps validate this seamless interaction between parameters.
Verifying the Consent Mode Implementation
Regardless of the option chosen, the implementation should be technically validated. This includes, in particular:
- Correct passing of the Consent Mode v2 parameters,
- Reviewing Consent Events in Google Tag Manager,
- Monitoring Consent Signals in Google Analytics 4.
Step-by-step instructions can be found in our previously mentioned posts on debugging Consent Mode in Google Tag Manager and on verifying Consent Mode in Google Analytics 4.
Conclusion
Basic and Advanced Consent Mode serve the same purpose but differ technically. While Basic Consent Mode blocks Google tags until consent is given, Advanced Consent Mode additionally sends cookie-less pings, thereby enabling, under the appropriate conditions, more advanced modeling methods in Google Analytics 4 and Google Ads. A clean technical implementation forms the foundation for reliable analytics and advertising data.
