Important: ensure secure connection to gemiusDirectEffect

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 gDE in advance. Therefore, we need you to ensure that all your connections to gemiusDirectEffect are made through the secure protocol (https).

From 18th December 2019, we will by default set the secure protocol on all new placements in your gDE campaigns. Consequently, all types of scripts for new placements will by default explicitly contain the secure protocol (https).

Please ensure that:

• All your campaigns that end later than on 31st January 2020 are scripted with the secure protocol (https). Revise both your display scripts and tracking scripts and adjust them if necessary. If scripts contain insecure protocol (http) or no protocol at all (//), modify the script to explicitly use the secure protocol (https).
• Your direct requests to gDE, e.g. requests for in-stream video creatives (ad.xml), are made with the secure protocol (https).
• Your action scripts contain the secure protocol (https).

If you don't adjust your scripts and direct requests to use https, they will lose the cross-site tracking functionality. Consequently, 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 calculate Real Users and Demography statistics, as well as all indicators based on cookies, such as: unique cookies, primary/secondary clicks, unique interactions, post-click/post-view actions, etc.

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.

New parameters in Slash HTML5 template

This week we present you new possibilities of Slash HTML5 creative template. Please find below a list of new parameters:

• Initial position - percentage value specifying the initial position of the division line between left and right element, e.g. 70% means that the left element will take 70% of the creative area.
• Click and drag mode - when enabled, user needs to click and drag the division line in order to move it and reveal the other part of the Slash creative. Otherwise, the division line follows the mouse cursor.
• Separate target_url parameters for left and right element - allow to open a different landing page depending on which element of the creative is clicked. Works only with the click and drag mode (as otherwise mouse cursor is always on the division line and it is impossible to click a specific part of the creative). If click and drag mode is not enabled, target_url from the left element will be used for the entire creative.
• Separate clicktag overlay parameters for left and right element - creates a transparent layer above the frame with the HTML5 creative, causing that clicks will open the landing page without passing events to the frame.

direct effect slash html5