Skip to content

consent settings being reverted when setting multiple regions (default command) #2

@agohorel

Description

@agohorel

Hello, I'm seeing some unexpected behavior when using this template with multiple regions configured under the default command. What I'm trying to do is establish a default setting for the US region, and a global default anywhere else. To test this, I've configured the US rule to default everything to granted, and the region-less default to denied across the board.

Screenshot 2023-05-19 at 11 53 24 AM

My understanding is that the more specific region should override the less specific one. What I'm seeing in the consent tab of the GTM tag assistant is the values being overridden initially, but then they seem to revert back.

Initial consent call:
Screenshot 2023-05-19 at 11 55 25 AM

Second call:
Screenshot 2023-05-19 at 11 56 03 AM

At this point I would expect the newer (and more region-specific) consent settings to persist, however every subsequent event (until updates triggered by user interaction via the CMP) takes the values from the initial consent call:
Screenshot 2023-05-19 at 11 57 44 AM

For context, I am physically based in the US. I have also tried sanity checking by setting the non-US region to Australia, but I get the same undesired behavior.

Is there something about the way GTM preview mode works, with respect to regions, that would prevent consent mode from picking up the US value over the region-less one?

Any advice is greatly appreciated!

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions