Check explainer
Consent Mode signal after update
Consent Mode V2 needs a gtag consent update after opt-in, otherwise Google conversion modelling stays off.
- to review
- ok
What we check
Checks whether a gtag consent update fires after "Accept".
Why it matters
Consent Mode V2 needs a gtag consent update after opt-in, otherwise Google conversion modelling stays off.
Common causes
- The CMP's Consent Mode integration is disabled, the banner only stores the decision internally.
- A custom banner replaced the standard CMP UI and simply never calls
gtag("consent","update",…). - The update fires into the void: a custom dataLayer name, or gtag is never defined on the page.
- The CMP SDK loads after GTM, the update arrives too late and the first hits of the session go out with the default.
How to fix it
Fire gtag("consent","update",{…}) in the CMP accept callback and verify in Tag Assistant.
What does a failing Consent Mode signal after update finding mean?
Consent Mode V2 needs a gtag consent update after opt-in, otherwise Google conversion modelling stays off. Fire gtag("consent","update",{…}) in the CMP accept callback and verify in Tag Assistant.
How do you fix Consent Mode signal after update?
Fire gtag("consent","update",{…}) in the CMP accept callback and verify in Tag Assistant.