Review third-party tags in a tag manager
A tag manager can contain both Google tags with built-in consent behavior and other tags that need separate controls. Enabling Google Consent Mode is not a blanket consent configuration for the entire container.
Keep the Passiro main script in the installation position documented by Passiro, before dependent scripts. Inventory the container’s tags and review which consent types each checks. For custom templates, use the tag manager’s documented consent APIs; do not add an improvised Custom HTML consent-default tag that conflicts with the CMP.
Test no-choice and rejected sessions in a defined opt-in region. Check each relevant tag’s trigger, consent requirements and actual requests. Accept the required category and verify that the tag can run. Then withdraw optional consent and test the next relevant event and reload.
Basic mode can prevent the container from loading before consent. Advanced behavior that allows an eligible Google loader does not authorize unrelated tags inside the container.
Acceptance: every optional integration has an intentional consent rule and passes the relevant scenarios. Do not invent a Passiro community template, custom event name or data-layer contract. Add platform-specific setup instructions only after the supported integration has been verified.