All Collections
Campaign Analytics
Adding cookie consent to your campaign
Adding cookie consent to your campaign

Get consent from participants to use tracking and other cookies

Niklas Cuthbert Mehlsen avatar
Written by Niklas Cuthbert Mehlsen
Updated over a week ago

Connecting with a cookie consent provider gives your players the option to accept different kinds of cookies when they access your campaign's live URL.

By default, Playable campaigns set some statistical and functional cookies. See the full list here: Cookies set on Playable campaigns.

You currently have three options for adding cookie consent to your campaigns:

  1. Integrate Playable's built-in cookie consent banner

  2. Link to your account with with an external cookie consent provider

  3. Add cookie consent via SDK

Option 1: Add Playable's Cookie Consent

Playable has a cookie consent banner that you can add to your campaign. The banner prompts visitors to accept functional, statistic, and marketing cookies.

To add this cookie consent to your campaign, go to Integrations > Misc. > Cookie Consent 2.0 and click configure.

In the integration settings, you can define:

  • the position of the banner (top or bottom of the screen)

  • the design (colors, fonts, button styles)

  • a link to where users can read more about the campaign's cookies

  • all of the text in the banner (headline, buttons, labels)

Option 2: Link to a third party cookie consent provider

If you use Cookieinformation or Cookiebot, you can connect them to your Playable account.

Go to Account Settings > Global administration > General and scroll down to find the Cookie consent settings.

1. Select your provider

Turn on the cookie consent provider setting and select your provider from the drop-down menu.

2. Add the script

Insert a script from your chosen provider under Account Settings > Developer > Scripts.

The script will look something like this, depending on your provider:

<script id="CookieConsent" src="https://policy.app.cookieinformation.com/uc.js" data-culture="DA" type="text/javascript"></script>

3. Whitelist Playable in your provider's account

Log into your account with the cookie consent provider and whitelist your Playable domain, whether it is your default Playable subdomain or a custom domain you have set up.

Option 3: Add cookie consent via SDK

If you don't use one of the cookie consent providers we integrate with, you can manually implement SDK for consent providers to only set cookies when consent is given.

To get started using our SDK, you first need to enable Playable cookies. To limit the cookies that are set on campaigns, you then have to add the following line under Account Settings > Developer > Scripts:

Insert into the <head>-tag on all campaigns

<script>window.cookieWait = true;</script>

This will notify Playable that cookies shouldn't be set unless consent has been given, so the platform will wait to set any cookies until it gets consent. This is done by calling a series of JavaScript functions to either grant or reject consent.

Here is a description of the series of functions and variants that is available for you to manipulate the consent:

  1. window.cookieAccept(); Accepts all cookie categories.

  2. window.cookieAccept('functional'); Accepts only functional cookies. Available categories are: 'functional', 'statistic' & 'marketing'.

  3. window.cookieReject(); Rejects all cookie categories.

  4. window.cookieReject('functional') Rejects only functional cookies.

Using the above JavaScript functions, you can control consent and manually implement your own consent provider, which will be integrated with cookies set by Playable.

Note: Cookies added via scripts

You can add your own scripts that may set marketing and other cookies. Scripts can be added globally, on individual campaigns, or via integrations.

If you set cookies via script, you may have to take some extra steps to ensure that your chosen cookie consent provider correctly recognizes them.

Scripts added manually

added globally or on a campaign

  • You should wrap the script in a control to prevent it from firing before the needed cookies are accepted. Otherwise, Playable can not know what kinds of cookies are set by the script.

  • If cookies are enabled but no consent provider is selected, the script will fire automatically.

  • If a consent provider is selected, and the script is wrapped in a control, the script will fire after the necessary cookies are accepted.

Scripts added via a campaign integration

for example: Facebook pixel

  • The platform will wrap the script in a control that identifies what kind of cookie it is (marketing, statistics, etc.).

  • If cookies are disabled, the script will not fire.

  • If cookies are enabled but no consent provider is selected, the script will fire automatically.

  • If a consent provider is selected, the script will fire after the needed cookies are accepted.

Scripts added via Google Tag Manager

  • You need to control in GTM what kind of script is being set so that they can be blocked or fired based on what the user accepts.

FYI: Disabling Playable cookies

If you want to disable cookies set by Playable, you can do so under Account Settings > Global Administration > General.

Note this will have an impact on the way your campaign statistics work, among other things. It will not have any impact on cookies that are set by additional scripts that you have added, unless these scripts are added via an integration.

Did this answer your question?