Google Consent Mode

A simple example

A visitor rejects optional categories in the consent interface. The technical setup must communicate that choice in time for the affected tags to follow the intended behaviour.

What the implementation must coordinate

The visitor’s choice, the consent platform and the measurement tags need to agree. Google’s implementation guide requires consent defaults before relevant configuration or events, followed by updates when the choice changes. Timing matters: an update after navigation can arrive too late for the event you intended to control.

Make the design explicit

Record which consent states apply to each region, which tags depend on them and how choices persist. Decide the implementation mode and behavior with the people responsible for privacy and measurement. A banner being visible does not demonstrate that the tags obey it.

Test visitor choices

• New visitor before making a choice.
• Accepting the offered categories.
• Rejecting optional categories.
• Changing an earlier choice.
• Returning after a saved preference.
• Moving between relevant checkout and website domains.

Keep technical and legal reviews separate

A passing tag test establishes observed behavior under those conditions. It does not establish a lawful basis for every use of data in every market. EU and UK requirements need separate, current review for the specific implementation; a generic Consent Mode switch cannot settle that question.

Coordinate the technical and privacy decisions

A consent interface, a consent signal and a tracking destination are separate parts of the journey. A visitor’s choice needs to be reflected in the implementation the business has approved. A banner that appears on screen is not enough evidence that the expected state reached each tag. Conversely, a tag diagnostic cannot decide whether the wording of the banner meets the business’s obligations.

For a practical review, create a test matrix that describes the expected behaviour before a choice, after acceptance, after rejection and after a later change. Include the domains and checkout paths actually used by customers. Record observed behaviour and resolve differences with the technical and privacy owners. Google Consent Mode is a technical feature; it is not a substitute for reviewing consent requirements. Avoid treating modelled reporting as a complete replacement for directly observed transactions.

• Agree expected states and data handling with the appropriate owners before deployment.
• Test new and returning visits across the customer journey.
• Keep the implementation record current when the banner or tagging setup changes.

Use the consent testing checklist →