AdOcean development newsletters



Release: 16-12-2019

List of issues to be addressed:
  • Important: ensure secure connection to AdOcean

Important: ensure secure connection to AdOcean

Google announced that since Chrome 80 (release scheduled for 4th February 2020), it will require that cookies accessed across sites are labeled using the “SameSite=None” and “Secure” cookie attributes. Cookies with “SameSite = None” and “Secure” will continue to be accessible across sites via secure connections. In order to comply with these requirements and retain the data about Internet users, we will add the “SameSite = None” and “Secure” attributes to cookies used by AdOcean in advance. Therefore, we need you to ensure that all your connections to AdOcean are made through the secure protocol (https).

On 16th December 2019, we will release updated versions of ado.js and aomini.js libraries that will force the secure connection to our servers. So far, requests to AdOcean where by default sent with the same protocol as the site initiating the request. After the change, https protocol will be used by default.

The changes described above will automatically be applied to implementation with the usage of ado.js or aomini.js library, such as Placement codes, Impression scripts, Iframe placement codes or Google AMP scripts.

Please ensure that:

  • Your direct requests to AdOcean, e.g. requests for in-stream video creatives (ad.xml), are also made with the secure protocol (https).
  • Your ado.js configuration does not contain the protocol attribute hardcoded to http.
  • You use tracking scripts with the secure protocol (https).
  • You use action scripts with the secure protocol (https).

If you don't adjust your direct requests to use https, they will lose the cross-site tracking functionality. As a result, we will lose the possibility of measuring reach and the part of traffic made by users in Google Chrome (and other browsers that require the "Secure" cookie attribute) will all be non-cookie traffic. That will also result in the inability to use such features as capping or retargeting for users in the affected browsers.

In order to avoid troubles with reach measurement and campaigns performance, we kindly ask you to revise and adjust your scripts until the end of January 2020. In case of any questions, do not hesitate to contact your local Tech Support.