Test Google Consent Mode before and after visitor choices

Before starting, confirm that a real Google tag or Tag Manager container is installed, record whether Passiro uses Basic or Advanced mode, and choose a defined opt-in test region. Without a Google integration, you can review configuration but cannot claim an end-to-end tag test.

View full size

Use separate fresh sessions for the following scenarios:

• No choice: check the intended default for analytics_storage, ad_storage, ad_user_data and ad_personalization before dependent tags run.
• Reject: the optional consent signals for this opt-in scenario should remain denied.
• Analytics-only choice: check that advertising signals do not become granted merely because analytics was accepted. Verify the actual category mapping in your integration.
• Accept all: inspect the consent update and the behavior of the relevant tags.
• Withdraw: reopen settings, reject optional use, save, reload and confirm the updated state persists.

Use Tag Assistant to inspect consent defaults, updates and affected tags. In Basic mode it may connect only after the blocked tag can load; that successful connection does not replace a fresh pre-consent test. In Advanced mode, cookieless Google requests can occur with denied consent. Inspect storage as well as requests.

Acceptance: save a test record for each scenario with the mode, region, browser and observed signals. Investigate conflicting defaults or late updates rather than adding a second consent-default script.