BookmarkSubscribeRSS Feed
BenGrubbs
SAS Employee

What's new for 12 September 2017

 

  • Values can now be removed without error from the Placement Key field when editing placements.
  • Corrected an issue where modifying a flight via the API would inadvertently remove the flight's assigned product if it was not explicitly defined in the API request.
  • When a tag had stacked values and the tag was referenced by a token in the creative, the "next" value from the stack was used for the token substitution rather than the one actually used during ad selection.
  • Events can now be compared in targets. This allows events to be compared using targeting operators such as equals, greater than, etc. For example, it is possible to target visitors that have logged event A a greater or equal number of times than event B. When creating an event target, select the "Select another event" button to use this functionality.
  • Campaign revenue stats have been removed from the Edit and View Campaign pages due to latency in generating the statistics. Revenue data should be retrieved through operational or BI reports.

 

What's coming up in the next release

 

  • Tag values can now be created with display names. Display names are used in cases where tag values may be alphanumeric strings (e.g. audience segment values). Using a display name still retains the tag value as defined, but uses a user-defined string when displaying the tag value in the UX. When creating a tag value, a display name is entered as: "tag_value|display_name". The display name is used in all areas of the UX, but the actual tag value is used for ad serving purposes.
  • Added API support for tag value display names.