How am i supposed to implement Cookiebot in a CMS with concatenated scripts?

Comments

3 comments

  • Avatar
    Kenan

    Hi Patrick,

    Thanks for reaching out!

    The best option to become fully compliant is to ask Shopware if they would like to make a Cookiebot integration. Users of other systems have done it before with success.

    It is not sustainable for a regular user to change external scripts for the manual Cookiebot integration, as those changes will most likely be overwritten on updates.

    There is a developer API available here: https://www.cookiebot.com/goto/developer/

    For Typo3 you could check if the following plugin does the trick:

    https://extensions.typo3.org/extension/ns_cookiebot/

    Regards,

    Kenan

     

     

    0
    Comment actions Permalink
  • Avatar
    Patrick Biendl

    Hi Kenan,

    that's not really an option because of 5 reasons:

    1. Even if they would integrate Cookiebot, it'll take a lot of time till it will be implemented
    2. Shopware does not know what Cookies other plugins are setting, so how could they fix that/implement it?
    3. Because of 2. Shopware is currently developing an own Cookie Bar and plugins are handled like that, that they have to "register" their cookies to the Shopware Core and then Shopware can decide which Cookies to allow. But the problem is, this will take time to develop AND the plugins have to support this feature and correctly "tell" the Shopware Core their Cookies
    4. Shopware aside, this would still be no solution for TYPO3, tho.. (The Plugin isn't useful, already checked that)
    5. Even IF any of these CMS have the option to - for example - split the Javascripts so i can categorize them, then the pagespeed would be slower... the whole goal nowadays is to compress and cocatenate the website as good as you can and lower the requests needed, you even should priorize what's on the screen and load stuff that's outside the viewport later, so correctly implementing Cookiebot seems like a BIG step back in all that cases, OR it would cost A LOT of time and effort per client to "counter" this drawbacks...

    So as it seems we have three options now:
    1. Only integrate Cookiebot as "Cookie-Scanner" and the Webpages wont be compliant
    2. We take our time - a lot of time (and cost) - for every customer to integrate Cookiebot in a compliant and performant way
    3. We don't use Cookiebot at all and wait for the Shopware Plugin (or use something else)

    Greetings,
    Patrick

    0
    Comment actions Permalink
  • Avatar
    Kenan

    1. Even if they would integrate Cookiebot, it'll take a lot of time till it will be implemented

    2. Shopware does not know what Cookies other plugins are setting, so how could they fix that/implement it?

    4. Shopware aside, this would still be no solution for TYPO3, tho.. (The Plugin isn't useful, already checked that)

    5. Even IF any of these CMS have the option to - for example - split the Javascripts so i can categorize them, then the pagespeed would be slower... the whole goal nowadays is to compress and cocatenate the website as good as you can and lower the requests needed, you even should priorize what's on the screen and load stuff that's outside the viewport later, so correctly implementing Cookiebot seems like a BIG step back in all that cases, OR it would cost A LOT of time and effort per client to "counter" this drawbacks...

    When we scan a website, we discover all the tags that are tracking. This includes <script>, <img>, <iframe> etc.

    A list of the latest tags is uploaded to our CDN, and can be retieved with the following syntax:

    https://consentcdn.cookiebot.com/consentconfig/domain-group-id/domain-name/configuration.js

    Example for cookiebot.com:

    https://consentcdn.cookiebot.com/consentconfig/c99c74a8-8388-4b1a-85d7-bea3bbed4aca/cookiebot.com/configuration.js

    In theory, Shopware or any other CMS, which bundles all tags into one file, could look at that list and mark those scripts up accordingly, before bundling them. This means that all the information is available to them, the question is how to solve it technically. The final <script> tag can use the "ignore" attribute which means that autoblocking will ignore it, but the inner workings of the script could be integrated with Cookiebot, if Cookiebot is used on that site. Moreover, with the API that I linked to previously, all developer documentation is available to verify which kind of consent the visitor has given, making it possible to decide if scripts coming from different tags should be executed or not.

    3. Because of 2. Shopware is currently developing an own Cookie Bar and plugins are handled like that, that they have to "register" their cookies to the Shopware Core and then Shopware can decide which Cookies to allow. But the problem is, this will take time to develop AND the plugins have to support this feature and correctly "tell" the Shopware Core their Cookies

    It seems that your biggest concern is how much time any kind of integration will take. Unfortunately I can't comment on that, but if enough customers pressure a CMS system, eventuelly they will take it into consideration. 10-20-30 people asking for the same thing should be enough for them to at least consider it.

    I see that Shopware is open source:

    https://github.com/shopware/shopware

    With the above information, you could do a PR to their repository with the information that I have provided, to show them a PoC of how it would work. If you solve the issue once, you could use the same approach on all your customers websites.

    0
    Comment actions Permalink

Please sign in to leave a comment.