Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Support Richard

    (@rvcybot)

    Hi Jaime,

    I wasn’t aware that adding ?dnt=1 disables cookies.
    Theoretically, this indeed works and the iframe doesn’t set cookies, our scanner won’t flag the iframe as a source of cookies, and won’t attempt to block it.

    Should this not be the case though, and you prefer to use that setting and want to override Cookiebot’s “judgement”, you can add the following attribute to the iframe: data-cookieconsent=”ignore”.
    Be careful when using this attribute though! Any element with it can set cookies without consent and using it arbitrarily on scripts can cause reference errors.

    Thread Starter jmslbam

    (@jmslbam)

    Cookiebot doesn’t rapports the cookie, so that’s ok.

    I will remove vimeo from the blocking “regex” so that all other video will be blocked.

    # data-cookieconsent=”ignore”
    Thank you for the tip, but that won’t be necessary when remove vimeo.com from the regex.

    #Youtube no-cookie url.
    Wouldn’t this be also the case with the Youtube no-cookie https://www.youtube-nocookie.com/embed/sRrqF8eXs38

    # Default behaviour
    And wouldn’t this then be default behaviour for Vimeo and the No-cookie video’s within Cookiebot Autoembed blokkage functionality?

    Because now video’s are being blocked when it’s not necessary.

    Hope it makes sense and you can confirm the above reasoning.

    Plugin Support Richard

    (@rvcybot)

    Hi Jaime,

    Regarding YouTube no-cookie, despite the name suggesting the opposite, that still sets cookies. However, if you can disable cookies by adding a parameter, the scanner should recognize that no cookies are set, and won’t flag them or attempt to block the resource.

    You can always “ignore” the resource, but please make sure that you don’t accidentally set cookies without consent.

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Do Not Track and Youtube No Cookie vs. Autocorrect Embeds’ is closed to new replies.