Study first
Review the ideas behind the questions
Review how GTM reads consent choices before you decide whether a tag is blocked, consent-aware, or configured incorrectly.
Set consent before tags evaluate
Consent mode depends on a clear default state and timely updates when the user makes or changes a choice.
- Consent mode needs default consent settings before measurement commands send data.
- Consent updates should happen on the page where the user makes the choice and before page navigation when possible.
- Consent mode v2 adds ad_user_data and ad_personalization alongside ad_storage and analytics_storage for advertising use cases.
Separate built-in and additional checks
GTM has different consent behavior for Google tags with built-in checks and tags that need extra consent rules.
- Google tags that support consent mode adjust their behavior based on consent state.
- Additional consent checks can be used for tags that do not have built-in consent checks.
- Using extra blocking controls on consent-aware Google tags can prevent consent mode from working as intended.
Audit consent settings across the container
Consent bugs are often container-review problems, not just single-tag problems.
- Consent Overview can show whether tags are not configured or have consent settings applied.
- Previewing changes helps confirm that tags respond to consent state before publishing.
- Old exception triggers or extra consent checks on Google tags should be reviewed when consent-mode data looks incomplete.