Displaying ads on specific Slaves only

From now on it is possible to force Master script to download ads only for those Slaves that are present on the given website (even if there's more Slaves defined in the interface).

To make it work you just need to add one additional parameter to Master script called slaveIds. Values of this parameter are simply slave IDs.

This way you can avoid problems with impression attempts being counted for slaves that are not present on the website (which causes overestimation in your inventory) or where ad is not displayed due to exclusion with ad picked for not implemented slave.

"Replace [TIMESTAMP]" button

From now on we give you possibility to add new button to your creatives which will automatically change all occurrences of [TIMESTAMP] / [timestamp] to <%%TIMESTAMP%%> macro. It is located at the very bottom of creative's parameters, in Tools section.

To enable this functionality - please contact with your local tech support.

Removing user's data / First party OPT-OUT

User has possibility to remove from ao-fpgad cookie private data like:

• information about seen ads;
• user ID;
• date of the last update of the above data;

It doesn't remove below information:

• if browser supports 3rd party cookies;
• date of the last check of 3rd party cookie support in browser;

To remove data on publisher's side you need to execute below JS:

This script is available from ado.js level so wherever you need to execute it you also need to put ado.js there, with the same settings as in the place where ads, with first party capping option enabled, are being displayed. Please find example implementation below:

To remove data on user's side you need to follow below steps:

• Open the website pointed out by publisher, where ad with first party capping option enabled is being emitted.
• Open Developer Tools in your browser.
• Open Console tab.
• Type "ado.removeUserData()" and click ENTER
  

First party OPT-OUT

The difference between OPT-OUT and removing data is that in case of OPT-OUT new cookie won't be created and ao-fpgad cookie is deleted but new "technical" cookie AO-OPT-OUT with value: 1 and lifetime of 5 years is created, which will inform our scripts to not create cookies with user's information.

Similar to removing user's data there are two ways (publisher / user side). You need to apply to above's intstructions with only difference that instead of ado.removeUserData() you need to use ado.disableUserData().

Passing GDPR information to AdOcean

We've been recieving a number of questions, why the AdOcean sets cookie despite negative consent given by the user.

Thus we'd like to kindly remind You, if the GDPR applies in your country you have to pass that information to AdOcean. By default AdOcean assumes the GDPR does not apply and user has given a positive consent, meaning the cookie will be given regardless of users consent.

There are 3 options:

• Set parameters gdprApplies and gdprConsent inside placement configuration;
• Use CMP compatible with IAB (1.1 or 2.0). The placement code will automatically pull the gdprApplies and gdprConsent values from the CMP.
• Set consent = true or false inside the placement configuration

Placement configuration:

Where params take values:

• consent: true or false - if we have user consent for data processing;
• gdprApplies: true or false - value informing whether the GDPR applies;
• gdprConsent: "consent-string" - a consent string in a format declared by the IAB, in ver. 1.1 or 2.0
  

adocean creatives macros