Integrating a TCF 2.0 CMP
It is possible for a broadcaster to use a TCF 2.0 (https://iabeurope.eu/tcf-2-0/) compliant Consent Management Platform to handle the listener's cookie consent. The consent dialog for the CMP will be displayed the first time the listener opens the player.
We hold consent values on a domain by domain basis, although cookie values (e.g. presets) travel around with the listener. This means that if a listener switches to a different station from another broadcaster, the CMP values will not be used in the new station.
When the broadcaster uses a CMP, we show the specific cookie consent form from that CMP, which allows the listener more control over which cookies are permitted within the player. Not only can the listener control which Radioplayer cookies are allowed (required, functional, performance) but they can also control their consent for third parties such as advertising platforms.
When a CMP has been integrated, the web player will pass the user's specific consents onto any ad providers that are used in the player. This consent only applies to this player; so when a listener moves to another station, that is not using a CMP, then we revert back to the existing Radioplayer cookie consents.
For details on how we manage consent in ad providers, see the monetisation section.
We have successfully integrated the player with usercentrics (https://usercentrics.com/), however any TCF 2.0 compliant CMP should work as they all use to the same standard API.
If you would like to use another TCF 2.0 compliant CMP, follow the pattern of implementation shown below.
Steps to implement
We assume that as a broadcaster, you have already signed up to a CMP and have an account with them. This step is necessary for them to store a users consent values.
Utilising a CMP will necessitate altering the generated console that you will have downloaded from Radioplayer Cloud.
- Add the CMP's scripts to the downloaded player HTML. You may need to contact your CMP to check whether they have any rules or restrictions on this - for instance Usercentrics asks that it is placed immediately after the opening tag. You will need to include your unique settingsId, so that the CMP provider can identify your settings.
<script
id="usercentrics-cmp"
data-settings-id="XXXXXX"
src="https://app.usercentrics.eu/browser-ui/latest/bundle.js"
data-tcf-enabled
></script>
-
By hand, add an extra key to the console JSON configuration to provide the player with a few key details on the CMP you are using. This will allow the player to display the consent interface when the user clicks on "Manage my cookie settings" from the menu. The key name is "CMP" and sample attribute values of this key are shown in the table below.
Note that you will need to get the values to enter into the JSON object from your CMPs documentation.
Property | Description |
---|---|
windowObject | The name of the object your CMP creates within the global window object. |
openFunction | The name of the function within the windowObject that opens the interface. |
manageCookieSettingsSubtext | A string to replace the sub text next to "Manage my cookie settings", by default it reads "(via Radioplayer.co.uk)" - this should be changed to via 'x' |
For example, for usercentrics, the CMP value in the JSON will look like this:
"cmp": {"windowObject": "UC_UI", "openFunction": "showFirstLayer", "manageCookieSettingsSubtext": "via usercentrics"}