Consent Management

BeOp in the TCF vendors list#

In order to be available on CMPs and to be sure having the consent of users in order to use cookies to improve their experience, BeOp has registered in the IAB TCF vendors list. The identifier of BeOp is 666, what a number!

The BeOp content server is able to deliver ads that contains some tracking elements from 3rd parties like Google, Facebook, etc... In order to protect user rights, if your website has a CMP, please add BeOp identifier in your partners list in order to be able to catch the TCF signal concerning BeOp and others data processors.

info

BeOp uses 1st party cookies in order to :

✅ improve the user experience by saving the current progress in a multiple questions widget
✅ maintain a counter of "How many times this user has seen this ads" in order to reduce the advertising pressure on that web user

BeOp does not use 1st party cookies in order to :

❌ follow and retarget users
❌ do user oriented statistics

These features are simply not available on BeOp platform

🤫 BeOp does not use 3rd party cookies ! 🤫

Currently, BeOp can be operated in a totally consentless mode, meaning that if users do not consent, we can still display contents (sponsored or not) without saving the progress or maintain the counter for ad capping.

For Prebid adapter installation#

The Prebid adapter uses all the features that are coming with in the Prebid script. Just add BeOp in your vendor list and the full experienced will be preserved with or without consent.

For Javascript SDK installation#

The Javascript SDK is allowing you to benefits from advertising, editorial, marketing or data oriented contents from the BeOp content server.

Running a TCF compliant CMP#

If you are a European/Californian editor, or want to be compliant with European/Californian laws in terms of data protection, you must have a way to collect consents from users, also called a CMP (Consent Management Platform). If your CMP is a fully IAB TCF compliant CMP, just add BeOp in your partners list, then try to load a page with the BeOp SDK without giving a consent:

Have a look into the cookies explorer of your site domain (reminder, BeOp is only using 1st party cookies) in the developers console

If you can't find a beopid cookie, that means your CMP is well loaded before BeOp SDK, all clear ✅
If you can find a beopid cookie, that means your CMP did not load before BeOp SDK, we have an issue here ❌

In that case, BeOp has implemented a specific param to put in the SDK configuration : waitForTCF

<script>
  window.beOpAsyncInit = function () {
    BeOpSDK.init({
      account: "YOUR_ACCOUNT_ID",
      waitForTCF: true,
    });
    BeOpSDK.watch();
  };
</script>
<script async src="https://widget.beop.io/sdk.js"></script>

warning

Adding the waitForTCF param to the BeOP SDK config interrupts the SDK until it receives a TCF signal !!!

Only add this param if you are certain that the CMP is installed on ALL PAGES that include a BeOp SDK

Other ways to manage consents#

If you have your full custom consent management, or if you want to authorize BeOp to work on your exclusive decision to access end user local storage, another param can be set on the BeOp SDK config: canAccessStorage

<script>
  window.beOpAsyncInit = function () {
    BeOpSDK.init({
      account: "YOUR_ACCOUNT_ID",
      canAccessStorage: true, //or false
    });
    BeOpSDK.watch();
  };
</script>
<script async src="https://widget.beop.io/sdk.js"></script>

By doing that setup, you are saying to the BeOp SDK whether it can access user local storage in order to put or not the beopid cookie on your 1st party domain

true means that BeOp can access the user local storage
false means that it can't

Thanks to that setup, you can manage the consent by yourself and initialize BeOp as you want.