Show Menu
TOPICS×

Release Notes - September 2016

Learn about new features and fixes in the Adobe Marketing Cloud.
To receive release notes one week prior to the monthly product update, subscribe to the Adobe Priority Product Update . Release information in the Priority Product Update comes one week in advance of the release date. Please check back at release time for updates.
September 2016

Experience Cloud

Marketing Cloud 16.8.1

New features and fixes in the Adobe Marketing Cloud interface and core services.
Release date: September 15, 2016
Feature Description
Marketing Cloud Triggers
Triggers bring together Analytics and Campaign, enabling marketers to define and monitor key consumer behaviors, and then generate cross-solution communication for use in real-time decisions and personalization. For example, you can create triggers for:
  • Re-marketing for cart abandons or cart abandons with products removed.
  • Session start or session end events.
  • Any actions or sequence of actions on site, such as incomplete forms and applications.
Configuration:

Marketing Cloud ID Service

This release increments the ID service code to version 1.8.0. It includes the following features, bug fixes, and other changes.
Fixes and Improvements
Added disableThirdPartyCalls as an optional, Boolean flag you can set in the Visitor.getInstance function. When disableThirdPartyCalls= true , the ID service will not make calls to other domains. By default, disableThirdPartyCalls= false . See disableThirdPartyCalls . (MCID-51)
See Marketing Cloud ID Services product documentation.

Adobe Mobile Services

Feature Description
Android: In-App Messaging
Added a new message type that opens a deep link URI.
Android: Tracking Deep Links
Added the ability to enable tracking of 3rd party deferred deep links.
  • processAdobeDeepLink
iOS: In-App Messaging
Added a new message type that opens a deep link URI.
See Adobe Mobile Services for product documentation. To see the release notes for previous releases, expand Previous Release Notes in the left pane.

Analytics

Release date: September 15, 2016

Important Notices for Analytics Administrators

Review the following table for important Analytics notices that may affect data collection, processing, APIs, product end-of-life, and so on.
Notice Date Added or Updated Description
Schedule Traffic Spike Deadline
September 23, 2016
If you have report suites that you expect to receive increased traffic during the holiday season (particularly Black Friday, Cyber Monday, Christmas, or New Year's), please schedule traffic spikes as soon as possible.
Ad Hoc Analysis - Java 1.7.
September 15, 2016
In the upcoming October 2016 release, you must use Java 1.7 or later to launch Ad Hoc Analysis.
If you use Java version 1.6 or earlier, you will see an error message, "Unable to Launch the Application." (On the error message, you can view the Java version that you are using by clicking Details , then click the Console tab.)
Analytics API 1.3 deprecation.
September 15, 2016
Analytics APIs version 1.3 will be officially deprecated as of September 15, 2016. To prevent disruption, Adobe recommends upgrading to the latest API versions as soon as possible.
See the API Support Policy page for more information.
Analytics for Target processing time increased by 30 seconds.
August 19, 2016
To achieve a higher visitor match rate between Adobe Analytics and Adobe Target, we have increased the amount of time data is held in processing from 30 seconds to 60 seconds. This change only affects customers using the Marketing Cloud ID service, AppMeasurement for Analytics, and who have Target implemented on their pages. (AN-128584)
Legacy Alerts
August 18, 2016
Several features of existing Analytics alerts will not be included in the new Alert Manager , which will be released (as part of Analysis Workspace ) in the Fall of 2016.
Legacy Alerts Migration lists the deprecated alert features and some alert features that will be migrated to the new Alert Manager in a different form.
Data Warehouse request settings
August 18, 2016
In the September 2016 Maintenance Release, Data Warehouse will add a new request setting that will enable Data Warehouse to send empty files when there is no data in the report. This settings will be enabled by default.
AppMeasurement 1.6.3 and Visitor API 1.6.0
August 4, 2016
Version 1.6.0 of the Marketing Cloud ID service requires AppMeasurement for JavaScript version 1.6.3 or higher. If you want to upgrade to version 1.6.0 of the Marketing Cloud ID service, please make sure you are using AppMeasurement code verison 1.6.3 or higher.
AppMeasurement for Flash - Security update
April 21, 2016
Adobe has released a security update APSB16-13 for the AppMeasurement for Flash library. This update resolves an important vulnerability in the library, applicable only when debugTracking is enabled, that could be abused to conduct DOM-based XSS attacks .
Note: This issue affects AppMeasurement for Flash only when debugTracking has been enabled ( debugTracking is disabled in the default configuration). If affected, we strongly advise you to disable debugTracking immediately. Here is some sample code:
 
     public var s:AppMeasurement; 
     s = new AppMeasurement(); 
     s.debugTracking = false; // set to false or remove line 
                              // for default "disabled” behavior 


</codeblock> <p>Affected versions are <span class="term"> AppMeasurement for Flash </span> version 4.0 and earlier on all platforms. </p> <p>Note:  Due to security reasons, we will no longer be distributing an AS2 version of <i>AppMeasurement for Flash</i>. We will continue to support data collection from existing AS2-based projects. However, we highly recommend that customers upgrade their implementations to AS3 and incorporate the latest security features of <i>AppMeasurement for Flash</i>. </p> <p> <span class="term"> AppMeasurement for Flash </span> customers affected by this issue must rebuild projects with the updated library available for download from the Analytics Console <a href="https://help.adobe.com/en_US/Flex/4.0/UsingFlashBuilder/WS6f97d7caa66ef6eb1e63e3d11b6c4d0d21-7feb.html#WS6f97d7caa66ef6eb1e63e3d11b6c4d0d21-7f88" format="http" scope="external"> More… </a> (AN-121780) </p> </td> 

SiteCatalyst 14, ExcelClient, etc. end of life in September 2016
March 17, 2016
SiteCatalyst 14, ExcelClient, and a number of other legacy components will reach end-of-life in September 2016.
This means that all access to the SiteCatalyst 14 user interface and several related features will be removed. To prepare for this event, view this list of affected components, along with required user actions and suggestions on how to move forward with alternatives.
Changes to visit processing for timestamped data
March 17, 2016
In June, we will begin improving to the way visits are calculated for Timestamps Required and Timestamps Optional report suites. These changes will primarily affect data collected through Mobile SDKs and will result in lower overall visit counts going forward, in certain situations.
To see which report suites might be affected, see Timestamps Optional .
Data processing change between February and March MRs
February 18, 2016
Sometime between the February and March Maintenance Releases, the following Analytics data processing change was implemented:
Previously, when using the Product variable without having an event set, the event would default to "ProdView", set early in processing (before processing rules take effect). The event is now set after the processing rules to avoid conflicts with how mobile data processing works. This change has the following downstream effects:
  • ProdViews are no longer inflated because of hits where context data is generating events (especially in Mobile). Going forward, an event will be set at the time in data processing when the ProdView would have been set (without a set event.)
  • Any VISTA rule that has logic depending on a ProdView event being set on a hit might need to be reviewed to see if changes to the VISTA rule are needed. This is because ProdView events might be set on fewer hits than they previously were, because ProdView is set earlier in the processing pipeline. This change may or may not impact what is desired from the VISTA rule.
Elimination of hashed values in Data Feeds
February 18, 2016
In certain circumstances, hashed values ( ::hash::&lt;hash value&gt; ) may appear in data feeds for the following types of variables:
  • Merchandising eVars in post_product_list
  • List Vars (called post_mvvar1-3 , post_tnt , and post_survey )
  • Marketing Channel details. The tracking code for the Marketing Channels reports (called va_finder_detail and va_closer_detail )
A change is being implemented that eliminates hashed values over time, and replaces them with actual values.
Note: The max size of any particular value is 100 bytes or 255 bytes. For fields that support multiple values, such as post_product_list and List Vars, the max size of those fields is 64k. Therefore, if you are passing in a large number of values, some of the values may be lost as the field will be truncated at 64k.
Web Services v 1.2 API end-of-life
February 18, 2016
Version 1.2 of the Web Services API was officially deprecated on February 20, 2014. It will reach end-of-life on September 15, 2016. At that time, Adobe will remove the ability of the API servers to respond to version 1.2 API requests. Any API requests made to the https://api.omniture.com/admin/1.2 endpoint will return a 410 error. Customers have until the end-of-life date to upgrade from the version 1.2 API to the version 1.4 API to prevent an outage in their API applications.
Analytics APIs version 1.3 will be officially deprecated as of September 15, 2016. To prevent disruption, Adobe recommends upgrading to the latest API versions as soon as possible.
See the API Support Policy page for more information.

New Features in Analytics

Feature Description
Time Zone Selection for Virtual Report Suites
You can now choose a time zone when creating a virtual report suite.
If you choose one, it will be saved along with the virtual report suite. If you do not choose one, the time zone of the parent report suite is used.
When editing a virtual report suite, the time zone that it was created with displays in the drop-down selector. If the virtual report suite was created before time zone support was added, the parent report suite's time zone is displayed in the drop-down selector.
Also, if you create a virtual report suite with a time zone that differs from the parent report suite's time zone, and then copy that virtual report suite, the copied virtual report suite will reference the parent report suite's time zone unless you manually update the time zone.
Permission Changes in Analysis Workspace (AN-125014)
The following permission changes were implemented for Analysis Workspace.
Previously, you needed the following permissions to create segments or metrics in Analysis Workspace:
  • Segment creation
  • Calculated metric creation
  • Create/Curate projects in Analysis Workspace
With this release, you only need these permissions:
  • Segment creation
  • Calculated metric creation
If you want to restrict your non-admin users from creating new segments and metrics in curated Analysis Workspace projects, use the permission setting to limit the relevant group’s ability to create segments and metrics.
These permissions are accessible via Admin > User Management > Groups > [click group] > Report Access > Advanced Reporting .
Dimension name change in Segment Builder
The Full Domain dimension in the Segment Builder has been renamed to Domains to match the permission name. (AN-129355)
Data Warehouse Updates
  • New setting for delivering empty Data Warehouse files. This setting delivers empty Data Warehouse reports containing only a header row when there are no rows in the result set. (AN-126249).
  • New Date Started field set to the report suite's time zone. The start date and completed date represent the round trip time. (AN-126155)
  • Timezone overrides have been enabled for Virtual Report Suites.
Activity Map Updates
  • Activity Map now supports web sites that default their page name to their page URL. (AN-129703)
  • Activity Map now supports all calculated metric formats (decimal, time, percent, and currency) in the Links on Page report, the Bubble and Gradient overlays, and the Overlay Details panel. (AN-124059)

Analytics Fixes

Fixes were applied to the following products and services:
Product Fixes
Reports & Analytics
  • Mobile device breakdowns for reports are no longer available for certain reports. As a workaround, run the Device Report and add the relevant metric to the report. ( AN-126460)
  • Fixed a segmentation issue where segments that involved dates that were outside the date range of the report suite did not work properly. (AN-123911)
  • Fixed a segment editing error occurring if the segment owner had been deleted. Deleted segment owners now show up as Unknown User in the log. (AN-129554)
  • Fixed a dashboard issue that prevented the download of dashboards that contained fallout reportlets with non-existing checkpoints. (AN-123380)
  • Fixed an issue with editing virtual report suites - an error was thrown when no changes were made and Save was clicked. (AN-128077)
Analysis Workspace
  • Fixed an issue that prevented the Send File Now functionality to work properly. (AN-128055, AN-128057)
  • Fixed an issue that let administrators click Delete more than once when deleting a user, thereby causing Analysis Workspace projects to disappear. (AN-127911)
  • Fixed an issue that prevented curated and shared Analysis Workspace projects from showing the same data to different users. (AN-126558)
  • Fixed an issue with downloading Analysis Workspace projects in .pdf format. (AN-127277)
Data Warehouse
  • Fixed an issue that caused the time zone for date_scheduled to be incorrectly calculated. (AN-126155)
  • Segments containing literal backslashes, tabs, or newline characters in string rules are now evaluated correctly. (AN-129552)
Data Sources
  • Fixed an issue in rule builder where rule sets would not activate. (AN-127762)
AppMeasurement (Legacy and Mobile SDKs)
AppMeasurement for JavaScript
Version 1.7.0
  • Update AppMeaurement Audience Manager Module with DIL 6.5 and Additional Configurations (AN-129411)
  • Inclusion of Visitor API 1.8.0 (AN-129887)
AppMeasurement for Other Platforms
See AppMeasurement Release History the following for a release history of AppMeasurement on the following platforms:
  • JavaScript
  • iOS
  • Android
  • Flash-Flex
  • OSX
  • Windows Phone, XBOX, Silverlight, and .NET
  • BlackBerry
  • Java
  • PHP
  • Symbian
See Also: Marketing Cloud ID Service (formerly visitor ID service )
Analytics Web Services (SOAP and REST APIs)
Deprecation Notice
Version 1.2 of the Web Services API was officially deprecated on February 20, 2014. It will reach end-of-life on September 15, 2016. At that time, Adobe will remove the ability of the API servers to respond to version 1.2 API requests. Any API requests made to the https://api.omniture.com/admin/1.2 endpoint will return a 410.
Data Workbench
Feature Description
Addressable Audience 1.1 enhancement
This update improves the accuracy of segment-level addressable audience and presents the current segment-level audience reach for campaign planning and review. See Addressable Audiences .
Fixes and Enhancements
  • Fixed an issue where the Help Modal was not working on the Profile Merge Rules page. (AAM-25712)
  • Fixed an issue in Audience Lab where no warning would appear that you have not mapped all selected destinations when navigating to "Finalize" step. (AAM-25877)
  • Fixed an issue in Audience Lab where "Invalid date" would show on the Test Group Information page when no end date was specified on the Destination Mappings page. (AAM-26016)
  • Fixed an issue in Audience Lab where, in the edit baseline segment modal, # would appear instead of the baseline segment creator. (AAM-26057)
  • Fixed an issue where for Audience Lab and Profile Merge, "Adobe Audience Manager | undefined" would appear in the browser tab title. (AAM-26091)
  • Fixed an issue in the Create Test Groups flow in Audience Lab where no warning message would appear in case you left any destinations unmapped. (AAM-26109)
  • Fixed an issue when you tried to edit Destinations, an alert box would appear and the Destination could not be edited. (AAM-26191)
Improvements
  • Removed the "OK_With_Unused_Signals" error from the error list in the Onboarding Status Report. (AAM-25240)
  • In Audience Lab, we now remind you to download the CSVs before deleting any Segment Test Groups. (AAM-25581)
  • The API now returns more accurate Segment Addressable Audience numbers. (AAM-25460)
  • The Destination and Segments pages now show actual numbers instead of estimated numbers for Segment Addressable Audience. (AAM-25461)
Fixes, Enhancements, and Deprecations
  • Publish Anywhere has replaced Publisher. Get familiar with the improved features.
  • New Facebook page-level and post-level video metrics are available. View new metrics.
  • A post retweeted from within Adobe Social now appears the same as when it is retweeted natively in Twitter. For more information, see Moderate an Individual Tweet and Post a Quoted Tweet .
  • Social tags will be available in Adobe Analytics after October 1 (exact date TBD).
    • After October 1, Adobe Social users will be able to use social tags to classify outbound content and report on this content within Adobe Analytics. To get on this list for access to this new feature, please contact your Adobe Social account manager or Social Support. From there you will receive updates on next steps regarding gaining access as well as enablement assistance.
  • Fixed an issue within Post Analytics where the filter was unable to distinguish between images and links posted on LinkedIn.
  • Fixed an issue where publishing a post with an attached link would post without the link.

Target

Refer to the Adobe Target Release Notes for the latest release information about the following products:
  • Target Standard and Premium
  • Target Classic
  • Recommendations Classic

Campaign

Adobe Campaign provides an intuitive, automated way to deliver one-to-one messages across online and offline marketing channels. You can now anticipate what your clients want using experiences determined by their habits and preferences.
For product documentation, see:
Adobe Campaign Standard
Adobe Campaign V6

Experience Manager

Adobe recommends customers with on-premise deployments to deploy the latest patches to ensure higher stability, security, and performance.
Title Description
Product releases
AEM Communities Feature Packs
Communities 6.2 Feature Pack 1 and 6.1 Feature Pack 5 released on August 30, 2016. The release includes the following:
  • Adobe Social Resource Provider.
  • Social Component Framework Enhancements.
  • Bulk Moderation.
  • Turnkey Community Sites.
  • Platform updates and Samples.
Mobile 2016.11
Livefyre releases
Product maintenance releases
S3 Connector
AEM 6.1 Service Pack 2
AEM 6.1 Service Pack 2 includes the following:
  • The built-in repository (Apache Jackrabbit Oak) is now updated to version 1.2.16.
  • Improvements were made between Oak versions 1.2.7 (included in AEM 6.1 SP1) and 1.2.16 (included in SP2).
  • Removal of discrepancies and errors in the process editing presets of assets.
  • Increased responsiveness of the author modes and improved functional components in Sites, such as the carousel component.
For more information, see AEM 6.1 SP2 release notes .
AEM 6.1 Cumulative Fix Pack 1
To improve the customer experience for maintaining AEM, the hot fix delivery model for AEM is changing for AEM 6.1.
Instead of releasing hot fixes for single issues, a CFP (Cumulative Fix Pack) is planned for release every month. A CFP has the following advantages for single hot fixes:
  • Increased level of quality assurance.
  • Simplified installation experience. That is, no dependencies except the latest Service Pack.
  • It is a cumulative package. For example, CFP 3 will contain all the fixes from CFP 2 and CFP 1.
AEM hot fixes
The following new hot fixes are available:
Self-help
AEM 6.2 documentation updates
AEM Forms
Knowledgebase article
A new knowledgebase article is now available regarding a performance issue related to the usage of AEM with Java7 .
Community
AEM Community article
A new article detailing all the steps to build an e-commerce provider is now available.
Upcoming local user group meetings
Join peers in your area or, if you are traveling, join a user group meeting. Adobe Systems lists each of the events on the community calendar here .
The Seattle User Group has two upcoming meetings. See details at https://www.meetup.com/Seattle-Adobe-CQ-AEM-Meetup-Group/ .
The Melbourne Adobe Experience Manager Meetup group is hosting a code contest. The deadline to register your teams for presenting at the Adobe Marketing Cloud - Community Expo (AMCCE) is September 30, 2016. You can register at the following: https://www.surveymonkey.com/r/R596336 .
The next meeting for the Amsterdam, Netherlands AEM User Group is November 3, 2016. You can RSVP here .
Ask the AEM Community Experts webinars
The recorded August webinar titled, "AEM and eCommerce" is available to watch at the following:
RSVP for the September webinar titled "Best Practices for Experience Manager and AEM Assets" here .
AEM GEMs webinars
The last recorded GEM webinar titled "Setup and Configure AEM Dynamic Media" is available to watch at the following:
AEM GEMS webinar titled "Managing your content with the template editor of Adobe Experience Manager" is scheduled for September 14, 2016. You can RSVP here .
To access all past AEM GEM webinar recordings, slide decks, and code links, see www.adobe.com/go/gems .
adaptTo()
AEM Developer Community event hosted by Pro!Vision, September 26-28 in Berlin.
Tickets are available at the following: https://adapt.to/2016/en.html .
IMMERSE 2017
Mark your calendars for the week of May 15-19, 2017 for IMMERSE 2017.
Watch the AEM Technologist Calendar for the "Call for Presentations" and Early Bird Registrations.
Additional resources:

Recent documentation updates

Item Description Date Published
Identify, define, and monitor key consumer behaviors, and then generate cross-solution communication to re-engage visitors.
September 15, 2016
Important announcement about permission changes coming in Fall 2016.
July 21, 2016
Adobe Experience Manager 6.2
Adobe Experience Manager 6.2 is an upgrade release to the code base of Adobe Experience Manager 6.1. It provides new and enhanced functionality, key customer fixes, high priority customer enhancements and general bug fixes oriented toward product stabilization. It also includes Adobe Experience Manager 6.1 feature pack, hot fix, and service pack releases.
May 19, 2016
Getting Started with Analytics
A getting started guide for new Analytics administrators.
May 15, 2016
Marketing Cloud Integrations
A round-up of available integration topics.
May 15, 2016
Activity Map
Activity Map product documentation.
April 14, 2016
Marketing Cloud Audiences in Analytics
With the Marketing Cloud Audiences for Analytics integration in place, you can incorporate Marketing Cloud audience data such as demographic information (e.g. gender or income level), psychographic information (e.g. interests and hobbies), CRM data, and ad impression data into any Analytics workflow.
April 14, 2016
Added a product comparison table for Analytics products.
February 18, 2016
In Marketing Cloud Assets, you can store, share, and synchronize your digital assets from one central location. Marketing Cloud Assets leverages some of the features available in Adobe Experience Manager (AEM).
February 11, 2016
Added documentation for new features in Analysis Workspace.
January 21, 2016
Analytics Administrators: If you are an administrator in the Marketing Cloud, see Users and Groups for updated information about mapping Analytics groups to broader Adobe groups, and adding or bulk-adding users via the Enterprise Dashboard .
September 17, 2015
Updated Analysis Workspace product documentation with feature descriptions, tasks for creating projects, videos, and use cases.
September 17, 2015
Added product documentation and best practices for Timestamps Optional. This feature lets you integrate both timestamped and non-timestamped data in a report suite. All new report suites will be Timestamps Optional by default.
September 17, 2015
Data Workbench 6.5 Update
See Data Workbench 6.5 release notes for instructions to upgrade and a list of new features and bug fixes, including a new Associations table and chord diagram and updates to visualizations, user interface, algorithms, and export features.
September 17, 2015
Updated the Classification Rule Builder so that you add report suites and variables to a rule set when editing an existing rule set (after creating the rule set). Previously, you specified the variable and report suite while creating the rule set. This change prevents reported issues occurring with classification variables.
August 20, 2015
Profile Link works with cross-device data sources to identify and collect traits for authenticated site visitors. It includes the Profile Merge Rules feature, which lets you segment and target users accurately across multiple devices.
August 20, 2015
New Calculated Metric Builder and Calculated Metric Manager
Calculated Metrics now allow for segmented metrics, more advanced math and the ability to organize and share metrics.
June 18, 2015
Analysis Workspace (public beta)
Build data tables and drag-and-drop metrics, dimensions, segments, and multiple visualizations to a project panel.
June 18, 2015
Data Workbench 6.4
Data Workbench 6.4 release includes several new features described here .
June 18, 2015
Added Adobe Managed Certificate Program to the revamped First-Party Cookies product documentation.
The managed certificate program lets you implement a new first-party SSL certificate for first-party cookies at no additional cost.
May 22, 2015
Revamped the Adobe Mobile product documentation.
May 22, 2015
A high-level round-up what you need to do to modernize your solution implementations for core services.
March 19, 2015
If you capture enterprise customer data in a customer relationship management (CRM) database, you can upload that data into the Marketing Cloud.
March 19, 2015
Analytics Spring Release
See the New Features section in Analytics for a round-up of new documentation for the Spring 2015 Analytics release.
March 19, 2015
Analytics Classification Rules - overwrite existing values
In Admin Tools > Classification Rule Builder > &lt;rule set name&gt; , two new options enable you to select an overwrite mode:
  • Rules overwrite any existing values: (Default setting) Always overwrite existing classification keys, including classifications uploaded via the importer (SAINT).
  • Rules overwrite only unset values: Only fill in blank (unset) cells. Existing classifications will not be changed.
Previously, if a key was already classified in any column or cell, the rule would not run on that key, and the row in the table was skipped.
February 19, 2015