Ctrlk
Analytics HelperSirdata APISemantic APIA propos de Sirdata
For the complete documentation index, see llms.txt. This page is also available as Markdown.

Video-Wall

Automatic conditioning of the main video players’ cookies (Youtube, DailyMotion, Vimeo, ...) and display of a message in the player in case of lack of consent.

How does it work ?

The video players use trackers subject to the ePrivacy directive requiring the user's consent prior to be used.

Sirdata's Video Wall conditions these videos’ playback to the user's choice:

  • When they consent, the video is accessible as usual;

  • When they refuse the processing of their data, or they don’t make any choice, the following message is displayed :

Example of message displayed when no consent is given

This allows the users to easily unlock the video if they wish to view it.

Automatic compatibility with

Rates

This service is billed monthly by volume of hits ('pageview' equivalent) per domain according to the below :

Activation & integration request

If you are already a Sirdata customer, use your Sirdata account to contact us, otherwise use our contact form.

Integration Guide: Sirdata YouTube Blocking (wyoutube.js)

This section details the implementation of the wyoutube.js script, specifically designed for blocking YouTube videos. Adhering to the loading order is essential for GDPR compliance.

Operating Principle

The wyoutube.js script is an interceptor that listens for consent signals and must be loaded before any other tag that might interact with YouTube.

YouTube-Specific Features

The role of the script is to detect attempts to load YouTube videos and apply the consent rule:

  • Without consent: The script blocks the loading of YouTube. A message is displayed in place of the video, inviting the user to provide consent to unlock the content.

  • With consent: The script allows YouTube to load the video normally.

  • Unblocking: Content unlocks instantly as soon as the choice is made, without requiring a page reload.

Implementation Method (Unique and Mandatory)

The insertion of the script must guarantee that it loads first to intercept any call to YouTube.

The YouTube blocking script must be placed directly in your site's HTML code, as high as possible within your <head> tag.

Crucial Loading Order

The script must imperatively be loaded before:

  • Your CMP (Consent Management Platform) scripts.

  • The Google Tag Manager (GTM) script.

  • Any YouTube loading script or tag.

Code structure in your <head>:

Why not use GTM for this script?

Insertion via GTM is prohibited for this script. GTM loads after the initial DOM, which is too late and would result in a "flicker" effect (the protected content appearing for a few milliseconds before being hidden).

Validation Tests

To validate your installation:

  1. Open your site in private browsing mode.

  2. Verify via your browser's "Network" tab that calls to youtube.com are not made during the initial page load.

  3. The content must remain blocked and display the consent invitation message until you interact with the consent banner.

  4. Ensure that the partner ID in the script URL (12345) is indeed the one for your Sirdata account.

PrécédentExtra-vendorlistSuivantInventory Partners

Mis à jour

Ce contenu vous a-t-il été utile ?