Skip to main content

Comments

4 comments

  • Official comment
    Uzair Suleman

    Hi Erich,

    Yes, you are right that one embedded youtube video is not blocked and the iframe is loading prior consent.

    This is happening because YouTube changes its trackers frequently which causes this issue.

    Therefore we suggest you that either mark up the iframe (by adding a manual mark up) or adding a placeholder informing the customer that they need to give consent to view the video.

    You can do this by following our instructions in this article: Iframe cookie consent with YouTube example

    Best wishes,

    Cookiebot Support

  • rabiasher

    If all cookies are being rejected despite using Cookiebot, it's likely due to YouTube's cookies, which are not managed directly by Cookiebot. Check the YouTube embed settings and ensure they comply with your cookie consent strategy.

    0
  • james

    It seems like you're facing an issue with cookie blocking on a specific webpage, and you're questioning why only one embedded YouTube video on the left is blocked despite using Cookiebot for consent management. The behavior you're experiencing might be due to various reasons, and here are some possibilities:

    1. YouTube's Embedding Policies: YouTube might have specific policies related to embedding videos, and they could be utilizing cookies or other tracking technologies. Even though you are blocking cookies using Cookiebot, the YouTube video might still be using other methods for tracking.

    2. Additional Embedded Content: Check if there are other embedded elements on the page (besides the YouTube video) that might be making additional requests or using cookies. These elements could be influencing the behavior you're observing.

    3. Cookiebot Configuration: Ensure that the Cookiebot configuration for your website is set up correctly. Check if there are any specific settings or exemptions that might affect how cookies are handled for embedded content.

    4. Browser Settings: The behavior might also be influenced by the privacy settings or cookie policies of the web browser being used. Users can configure their browsers to block certain types of content, and this could affect the loading of embedded elements.

    5. YouTube's Privacy-Enhanced Mode: YouTube offers a privacy-enhanced mode for embedded videos that reduces the use of cookies. If privacy is a significant concern, consider using YouTube's privacy-enhanced mode in addition to Cookiebot.

    6. Content Security Policy (CSP): The webpage might have a Content Security Policy in place that restricts certain types of content or requests. Check if the CSP is configured to block specific resources.

    To troubleshoot the issue further, you can use browser developer tools to inspect network requests, check for any console errors, and analyze the behavior of the embedded elements. Additionally, reviewing the documentation for both Cookiebot and YouTube's embedding policies may provide more insights.

    If the issue persists, you may want to reach out to the support or community forums of Cookiebot for specific guidance tailored to your setup.

    0
  • CarX Street

    Hello,

    It seems that despite having the Cookiebot script in place for cookie consent on your page, you're experiencing an issue where only one embedded YouTube video on the left is blocked when all cookies are rejected.

    There could be a few reasons for this behavior:

    1. Cookie Categorization: Check if the cookies associated with the YouTube video are categorized separately from others. Some cookie consent tools allow you to categorize cookies, and users might be rejecting only specific categories.

    2. Embedded Content Policies: Different embedded content, like YouTube videos, may have their own privacy policies and cookie usage. Users might be allowing cookies for essential functionalities but blocking those associated specifically with the YouTube video.

    3. Dynamic Content Loading: If the YouTube video is loaded dynamically or through scripts after the initial page load, it might be outside the scope of the initial Cookiebot script. Ensure that the consent mechanism extends to dynamically loaded content as well.

    0

Please sign in to leave a comment.