Consent Mode adjusts the behaviour of Google tags according to the user’s choice on cookies and storage. For Google Ads, properly implemented, it allows aggregate measurement and conversion modelling when consent is declined, respecting privacy. It requires testing and verification, because configuration errors are common.
The essentials in a definition
Consent Mode is Google’s mechanism to adjust tags to the user’s consent choice. It applies in Google Ads and GA4, depends on a valid consent platform, follows the developer documentation and does not replace compliance with the GDPR.
What it does and does not do
Consent Mode communicates to Google the consent state for purposes such as advertising and analytics. With consent, tags work normally; without it, they adjust behaviour and may send limited signals, from which, under certain conditions, the platform models conversions. It does not replace consent nor change the legal obligation under the GDPR.
Options, signals and requirements change; always confirm current documentation.
Configure and test
Use a compatible consent-management platform, set the default state (denied, in the EU), send updates when the user chooses and confirm tags respect the state. Test in preview mode and with network-inspection tools to see the parameters sent, in each scenario (accept, decline, change choice).
Also check integration with GA4 to keep consistency.
Consent communicated, verified and measured
- Configure the consent platform
- Test all scenarios
- Track consent and modelling
- Audit after every change
Impact on conversions
When there is refusal, direct measurement falls; modelling can reduce the gap but does not eliminate it, and depends on volume and conditions. Track consent percentage, observed and modelled conversions, and compare with your own data (orders, leads) to see the real difference.
Do not compare periods before and after implementation without considering the fall in observable data.
Consent is not a technical detail: it is the basis of legitimate measurement.
Continuous verification
Review the configuration after changes to the site, banner or tags. Document the default state, purposes and regional rules. Run periodic tests and keep the banner clear and easy to use, to obtain informed and free consent.
Include the check in quarterly audits.
Decision table
| Scenario | Expected behaviour | Check |
|---|---|---|
| Consent granted | Tags work normally | Correct consent parameters |
| Consent declined | Limited signals, no disallowed storage | No disallowed cookies |
| Choice changed | State updated | Tags react to the change |
| No choice | Default state denied, in the EU | Tags do not fire improperly |
Common mistakes to avoid
- Implementing without testing. Common errors go unnoticed.
- Comparing before and after without context. The fall in observable data looks like a loss of performance.
- An unclear banner. Consent stops being valid.
How to measure the result
Track consent rate, observed and modelled conversions, and the difference from orders.
Limits and exceptions
Legal requirements vary by country and change, and this content is not legal advice. Modelling is an estimate. Measurement with consent declined has limits that technology does not eliminate.
Illustrative example
Illustrative example: a store audits the configuration and finds an old tag firing before the choice. It fixes it, tests the four scenarios and tracks consent rate and observed and modelled conversions. It compares with orders and starts to interpret the fall as part of the effect of refusal.
In practice: checkpoints
Document the consent platform, the default states and the regions in which each rule applies, and keep a test script that anyone can run after changes. Compare observed and modelled conversions each month, record the consent rate and note changes in banner text or design that may affect it. Keep consent logs as required, review the privacy policy together with the configuration and train the team to avoid adding tags that bypass the consent platform.
Frequently asked questions
Does Consent Mode remove the need for a banner?
No; the banner and consent collection are still necessary.
Does modelling recover all conversions?
No; it narrows the gap, subject to conditions and volume.
How do I test?
With tag preview and parameter inspection in each scenario.
How often should I audit?
Quarterly and after any change to the banner or tags.
Can I increase the consent rate?
With a clear, honest banner, without manipulative practices.
Implement Consent Mode with the correct default state, test all scenarios and interpret conversions with modelling and your database.
Sources and recommended reading
- Google for Developers: set up consent mode
- Analytics Help: consent mode
- General Data Protection Regulation (GDPR)
Last editorial review: October 2026. Informational content; always confirm current conditions in the official sources before deciding.