• Resolved krzysztofboxer

    (@krzychu102)


    Hi,
    I noticed a technical error in the plugin’s implementation of Consent Mode v2 regarding the integration of functional cookies.
    Currently, when a user updates their preferences, the plugin passes the “functional_storage” parameter in the gtag(“consent”, “update”, …) command. However, according to Google’s official specification, the correct parameter name should be “functionality_storage”.

    Because of this typo, Google Tag Manager does not recognize this parameter as a system-level consent type. Instead, GTM treats it as a custom, unrecognized variable. As a result, the actual, official status of “functionality_storage” in the GTM container is never updated and remains in its default/denied state, ignoring the user’s actual selection made on the banner.
    In addition, the “Consents” tab also displays: [Google Code: functional_storage]

    I’m also including a link to all consent types for confirmation:
    https://support.google.com/tagmanager/answer/10718549?hl=en
    Please update the parameter name in the plugin code 🙂
    Thank you for all your hard work on this plugin!

    Greetings, Krzysztof

Viewing 2 replies - 1 through 2 (of 2 total)
  • Thread Starter krzysztofboxer

    (@krzychu102)

    Update: This is likely only mentioned in the description under the “Consents” tab as Zarządza przechowywaniem ciasteczek dla podstawowych funkcji, takich jak logowanie. [Kod Google: functional_storage]

    However, there is another problem because the “always on” setting is not honored, and functionality_storage behaves differently depending on whether the user grants consent or not.

    Dziękuję Krzychu, widziałem, że dodałeś też na GitHubie – super!

    Thank you @krzychu102. I saw on GitHub too – awsome!

Viewing 2 replies - 1 through 2 (of 2 total)

You must be logged in to reply to this topic.