Consent Mode signal after update

Consent Mode V2 needs a gtag consent update after opt-in, otherwise Google conversion modelling stays off.

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.

The fix

Fire gtag("consent","update",{…}) in the CMP accept callback and verify in Tag Assistant.

Matching template

Consent Mode Audit Checklist

Seven layers, each with a check, a failure signal and an owner. Covers this finding and the six around it.

Get the checklist →

Check it yourself first

The Tracking Check tests this point along with all the others, in seconds.

Start the Tracking Check →

Asked often

What does a failing "Consent Mode signal after update" check 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 a failing "Consent Mode signal after update" check?

Fire gtag("consent","update",{…}) in the CMP accept callback and verify in Tag Assistant.

The fix, delivered

Wired up in days, not sprints.

Findings from the Tracking Check go into a ranked sequence with effort estimates in the Audit Sprint, every module with an acceptance criterion.

To the service Request an Audit Sprint