Quick answer

Verify that the default consent state is set before relevant tags send data, that the banner updates the state when a user makes a choice, and that the choice persists and can be changed later. Test both grant and denial paths.

Consent Mode changes how supported Google tags behave based on consent signals; it does not create a consent banner or determine the legal requirements for a business. Work with the applicable privacy requirements and the site's consent-management solution.

What I would check first

List the consent categories used by the implementation, the regions where different defaults apply, the tags that depend on each category and the person responsible for maintaining the setup.

Use Tag Assistant and browser tools to inspect default state, update timing and tag behaviour. Test a fresh visit, a returning visit, a changed preference and a page transition immediately after consent is updated.

Decision framework

Separate three questions: was the visitor's choice captured, was the choice transmitted correctly, and did the downstream tag behave as intended? A banner can appear to work while the update event is late or a tag fires before the default state is set.

Do not interpret a modelled conversion as a directly observed event. Reporting can include observed and modelled information depending on the product and implementation, so document what the reports represent.

Implementation steps

Set region-appropriate defaults, connect the consent interface to the supported consent APIs, persist preferences and ensure changes are sent before navigation. When using Tag Manager, follow the consent APIs and the CMP's documented integration rather than relying on arbitrary tag sequencing.

Google's current developer guidance lists four important consent signals for web implementations: ad storage, analytics storage, ad user data and ad personalization. Confirm that the implementation and the consent banner agree on the meaning of each signal.

Common mistakes

Do not set consent defaults asynchronously after tags have started, assume the banner automatically integrates with every tag or treat Consent Mode as a substitute for a privacy review.

Do not use a successful preview as the only test. Verify behaviour on the live domain, across page transitions and after a user changes their mind. Keep a record of the expected state for each test.

Measurement and business implications

Monitor consent-state behaviour, event completeness and changes in observed reporting after implementation. Compare periods carefully and annotate the release; a reporting shift may reflect measurement behaviour rather than a real change in demand.

Use the GA4 event naming plan, conversion audit and Ads-versus-Analytics guide to keep event definitions and reporting caveats consistent.