when the site first loads it defaults to all consent granted (1st screenshot), but immediately after that, it resets to all consent denied
Required: Please provide a staging/production URL where we can see the issue
the second consent for the GDPR regions should not have fired since we are in the US, its granting our consents then a second later denying them.
Hey @sarah1
The state that actually applies is what carries through from Consent Initialization Event: Initialisation into later events for example Container Loaded, not every row in the Consent Default list.
Consent Pro’s GTM template registers all of your configured region defaults at init. In your setup that’s both the EU row using default denied and the Global row default granted, so Tag Assistant will show two Consent Default events. That’s expected.
Only the default that matches the visitor’s region is what gets persisted. The other row is still listed because it was registered, not because it overwrote your active consent.
If the visitor already has an fs-consent cookie state, that stored choice can also update consent after defaults are set, so the final state may come from the cookie rather than from the defaults alone.
So to debug and confirm what is persisted, please check for example what the Initialization step contains in the Consent Tab
Thanks
Hey @sarah1
This is what devs had to say concerning what you’ve shared
It looks correct, nothing wrong with those follow up screenshots
I believe they are still confused why the state is updated
For best interpretation, they need to focus on the consent states of
Event: Initialisationstep going forwardAnything before that is initial states that could be from their current consents or default region consents
They need to test against what is Current State shows from Event Number 6,7,8…going forward in their follow up screenshot.
Hope it makes sense, let me know, thanks
