Use Consent Initialization deliberately

Set the initial state as early as possible. In GTM, Consent Initialization runs before standard Initialization triggers, but container order still needs testing alongside CMP and hardcoded page scripts.

Connect the CMP update

  1. Map the CMP categories to the relevant Google consent types.
  2. Send an update after the choice is stored.
  3. Handle accept, reject and partial-selection states.
  4. Restore and update the state on later page views.

Review tag-level controls

Built-in checks

Google tags understand supported consent types and adapt their behavior automatically.

Additional checks

Use extra consent requirements only when the tag truly needs blocking beyond its built-in behavior.

Test before publishing

Use GTM preview to confirm the default appears before Google tags and that each CMP action produces the expected update. Then inspect network requests and stored identifiers.

Run the public preflight audit