Final version Stage

We decided to leave Release Candidate Stage and go for Final Version Stage. Recently we haven't found new bugs that suggest keeping Release Candidate.
So from that moment, we guarantee that the product is free of bugs and a possibility of appearing new ones is low.

New fancy tabs

Are you familiar with Google Chrome tabs? You can drag and drop them in a desired place. They work very smoothly as you might notice. If you like those tabs you will enjoy the same mechanism in our system. Edition, statistics and report tabs will behave the same as in Google Chrome

And I almost forgot! There is another fancy thing connected with tabs. From now on, when you click on the campaign name with a middle mouse button, the tab will open in the background.

Actions and Successful clicks redesign

We are working very hard to integrate with gemiusTraffic2. Our goal is to allow clients to measure conversion on sites that are measured by gemiusTraffic2. But before we will be able to add such possibility we had to redesign and unify action pages, successful clicks and successful clicks attached to specific click tag. In this release we are introducing these changes.
Thanks to that in the next release we will introduce gemiusTraffic2 integration on the conversion measuring level.
Please be aware that we have changed some of the currnet behavior of the system. For example, we have changed the name “Landing page” to Actions in the edition menu. That is why we strongly recommend getting familiar with the system before you start using this for production purposes.

And I almost forgot! There is another fancy thing connected with tabs. From now on, when you click on the campaign name with a middle mouse button, the tab will open in the background.

Actions and Successful clicks redesign

We are working very hard to integrate with gemiusTraffic2. Our goal is to allow clients to measure conversion on sites that are measured by gemiusTraffic2. But before we will be able to add such possibility we had to redesign and unify action pages, successful clicks and successful clicks attached to specific click tag. In this release we are introducing these changes.
Thanks to that in the next release we will introduce gemiusTraffic2 integration on the conversion measuring level.
Please be aware that we have changed some of the currnet behavior of the system. For example, we have changed the name “Landing page” to Actions in the edition menu. That is why we strongly recommend getting familiar with the system before you start using this for production purposes.

Date picker refactoring

We have rebuilt and redesigned a bit the date picker. The story is short. We just did it. So you will find it fresh

Ordering socio-demography statistics

We give you the possibility to order socio-demography statistics straight from the interface. The process is nice and easy and takes just a few seconds. You do not have to contact with us to do this, you can just make two clicks and that's it!

gDE2 API update

AuthorizeGtUser and LogoutGtUser operations:

• new system parameter, possible values: enum('gT1','gT2')

AddCampaignAction operation:

• new clickTagID parameter
  • acts as an optional replacement of campaignID
  • replaces gtScriptID parameter in AddCreativeClickTag and UpdateCreativeClickTag operations
  • serves to attach successful click tracking to a clickTag
• new gTidentifier parameter
  • its goal is to avoid the usage of ImportExtGtScript operation
  • serves to create an action using an external gemiusTraffic (gT) script
  • requires logging in to gT before usage

UpdateCampaignAction operation:

• new gTidentifier parameter
  • its goal is to avoid the usage of ImportExtGtScript operation
  • it lets you edit an action created with the help of an external gT script
  • requires logging in to gT before usage

GetCampaignActionsList operation:
There will be changes in the name of some result parameters. These are as follows:

• name is renamed to actionName
• gtScriptID is renamed to scriptID
• gtScriptName is renamed to extScriptName
• gtScriptAccount is renamed to extAccount and will be empty for gT4gDE actions

• sortField input values are going to be modified
  • Old version:
    enum('name','gtScriptName','gtAccount','type','creativeName','clickTagName','creationTS','modificationTS')
  • New version:
    enum('name','system','extScriptName','extProject','extAccount','type','creationTS','modificationTS')
• Following parameters will be removed (moved to new GetCampaignActionInfo operation)
  • creativeID
  • creativeName
  • clickTagID
  • clickTagName

AddCreativeClickTag and UpdateCreativeClickTag operations:

• gtScriptID parameter will be removed

GetCreativeClickTagsList operation:
There will be changes in the name of some result parameters. These are:

• gtScriptID parameter will be removed
• gtScriptName parameter will be removed
• gtScriptAccount parameter will be removed
• new actionID parameter
• new actionName parameter

DeleteCampaignAction operation:
Changes will be made to some of the query parameters of this operation:

• actionID parameter will be removed
• new actionIDs parameter

Removed API operation

ImportExtGtScript operation will be removed completely and stop functioning.

The description of the new API operations will be added to the official API documentation pages of our web site right after the release.

Please check your internal tools which use these gDE2 API operations and make necessary modifications to them accordingly. If you have any questions, please contact your local Technical Support.

api direct effect soc-dem