Development Newsletters
Release: 21-09-2016
List of new features and major fixes for this release:
- Changes in the user settings
- Password change for new users
- Soc-dem attributes in Soc-dem ranking
- gDE API changes
Note: Please remember to change your password in the gemiusDirectEffect interface. Access to the accounts for which passwords will not be changed till Friday, September 23, will be blocked.
Changes in the user settings
We would like to introduce a few more changes related to the recent update to our security management system explained in the previous deployment (Release: 07-09-2016). To make password recovery easier for all users, we have made some changes in the user settings.
E-mail address field required in user settings
In order to facilitate password recovery for all accounts, providing an e-mail address will be obligatory while creating a new account or updating an already existing one.
Password change for new users
We will also introduce a change in the password recovery form for all new users. After creating a new account, an e-mail with an activation link will be sent to the e-mail address provided in the user settings and the user will be asked to set a password to the newly created account with the use of the password recovery form.
Soc-dem attributes in Soc-dem ranking
We are pleased to inform that we introduce three new intersections in the soc-dem Basis of ranking:
- Feature x Placements
- Feature x Creatives
- Feature x Placements x Creatives
Figure: Basis of ranking in the soc-dem view
Thanks to these changes, more detailed statistics for soc-dem features available in a campaign will be presented in a more friendly way directly in the gemiusDirectEffect interface.
gDE API changes
In the next deployment (on 5 October), we will introduce a few changes in the gDE API. To ease your work with the gDE API, the GetRealUsersStats command will be removed and all its functionalities will be moved to the GetBasicStats command.
We will also remove the possibility to access the gDE API through http:// protocol. Starting from the next deployment, it will be available only through a safe https:// connection.
In case of any questions please contact your local Tech Support office.