From our analytics team, we've encountered incorrect behavior with the Google Consent Mode tag in Tealium. We've configured the tag, and as an addition to the tag, we've created an extension that populates the "ad_storage" and "analytics_storage" variables.
When a user enters our site and has their initial interaction with our modal, the tag behaves correctly (initializing Google Consent Mode with its "default" function, as per the documentation). However, when the user changes their consents, what we expect from the GCM tag is to trigger the "update" function, but it doesn't; it triggers the "default" function again.
This causes GCM to initialize once more. Consequently, Google to not validate this solution.
Have you encountered something similar? Are you familiar with this issue?