Show Menu

Adobe Experience Cloud release notes - November 2018

New features and fixes in the Adobe Experience Cloud.
Subscribe to the Adobe Priority Product Update to be notified via email about upcoming releases. You will receive the notice three to five business days in advance of the release. New information published after the release will be marked with the publication date.
November 2018
Latest update: December 4, 2018

Adobe Cloud Platform

Release notes for the Experience Cloud interface and platform core services. Includes Mobile Services, Launch, by Adobe, Dynamic Tag Management, GDPR API, and Experience Cloud ID Service.

Dynamic Tag Management

Adobe plans to sunset Dynamic Tag Management by the end of 2020.
  • 2019-07-01: Starting in July of next year, DTM will no longer allow the creation of new properties. This will have no impact on existing properties.
  • 2020-07-01: DTM properties will enter a read-only mode. You will not be able to create or edit tools, rules, or data elements. You will no longer be able to publish to DTM environments. This will have no impact on previously published libraries.
  • 2020-12-31: End of support. Servers will be decommissioned, documentation will go offline, and communities will be removed. This will have no impact on previously published libraries.
For more information, see DTM Plans for a Sunset .

Analytics Cloud


New features and fixes in Adobe Analytics:
For product documentation, see Analytics Help Home .

Analysis Workspace

(Implemented September 2018.) Changes were made to which components administrators and non-administrators can see in curated Workspace projects and curated virtual reports suites (VRSs). Previously, anyone could see non-curated components when clicking Show all Components . The updated curation experience allows for more fine-grained control over which components are visible.
Adobe Analytics and General Data Protection Regulation (GDPR)
Analytics supports a new method for passing the legacy Analytics visitor ID to a GDPR request (see AAID ). Also, Analytics now supports deleting (anonymizing) the Purchase ID value as part of a delete request.
Prompted by the EU cookie compliance regulation , data controllers (Analytics customers) now have the option to restrict pre-consent data to Adobe Analytics, and prevent it from being server-side forwarded to Adobe Audience Manager (AAM). A new implementation context variable lets you flag hits where consent has not been received. The variable, when set, prevents these hits from being sent to AAM until consent has been received.

Media Analytics SDK for iOS & Android (formerly VHL SDK)

Adobe Analytics for Audio
Connects a listener's streaming audio engagement with their full digital behavior. You can understand who's listening where, when, and how often, and evaluate user behavior in a commonly fragmented audio marketplace. This feature enables businesses to measure the reach of their listeners, measure the popularity of their content, and provides insight into how to keep users engaged based on their behaviors and look-alike modeling. Measure 10-second audio content and 1-second streaming ads with our best-in-class SDKs, to evaluate both quality of experience (stall, errors, time to start) and content plus ad KPIs.
Maintaining Ad Breaks
Enhanced Ad tracking in scenarios where if a player has entered an ad break, and no calls are sent for a certain period of time, the SDK logic will default back to content playback, even if the player is still in an ad break state. During a pre-roll ad, this may result in a content start firing before the ad break is complete. In Media 2.2 SDK, buffer calls will be sent between ads within an ad break when there is a long delay between ads.
SDK Name Change
Starting with the 2.2 release, the Video Heartbeat Library (VHL) SDKs are renamed to Media SDK. The Media 2.2 SDK is fully backwards compatible with the VHL 2.X SDK series. The name change does not represent a functional break, simply a change in naming convention.

Analytics Fixes and Updates

Analysis Workspace
Fixed an issue where in Create metric from selection and Compare attribution models , the Percent Change calculated metric was incorrect. (AN-170471)
Other Analytics Fixes
  • Calculated Metrics: Fixed an issue related to copying calculated metric parameters. (AN-169648)
  • Calculated Metrics: Fixed a localization issue in the calculated metric preview. (AN-165086)

Data Workbench

See Data Workbench release notes for the latest information.

Important Notices for Analytics administrators

Management changes to inactive Adobe Live Stream endpoints
December 20, 2018
Starting on February 1, 2019, Live Stream endpoints with no active consumer connections for 90 days may be disabled. You can reach out to Adobe Customer Care to inquire about your Live Stream endpoints and, if necessary, have them re-enabled. In addition, please ensure your consumer processes maintain a persistent connection, as intended by the design of the service, and that they are implemented to reconnect when the connection is disconnected or interrupted.
Dallas FTP server migration (
October 19, 2018
On October 23, 2018, if you connect to via the SFTP protocol, you might be required to re-accept the SJ1 site's host identifier. This issue applies only to October 23.
Update to Mobile Device dimension
October 16, 2018
On September 26, Adobe updated its device lookup to Device Atlas's 2.1 API. This caused more detailed devices (e.g. Apple iPhone 7, Apple iPhone 8 Plus, etc.) to appear in the Mobile Device dimension for some browsers. This new level of device detail should be used directionally as is does not extend to all devices and browser types at this time.
End of support for Internet Explorer 11
Sept. 12, 2018
Adobe will end support for Internet Explorer 11 within Adobe Analytics on November 13, 2018. Please switch to Microsoft Edge or another supported browser as soon as possible.
Data Feed: post_product_list column - size change
Sept. 12, 2018
In January 2019, Adobe plans to expand the size of the post_product_list column from 64 KB to 16 MB. This change is intended to ensure that merchandising eVar values added to post_product_list during processing do not cause truncation of product and revenue values.
If you have processes that ingest post_product_list values, please ensure those processes can handle values up to 16 MB in length, or will truncate the value at 16 KB to avoid data ingestion failures.
End of life for Ad Hoc Analysis
August 9, 2018
On August 6, 2018, Adobe announced the intention to end-of-life Ad Hoc Analysis. An end-of-life date will be shared once available. For more information, visit Discover Workspace .
We will not modify Ad Hoc Analysis to support Java 9+ from this point forward. If you upgrade to Java 9+, Ad Hoc Analysis will cease to function. Only Java 8 will be supported.
End of Support for TLS 1.0
Sept. 7, 2018
To minimize customer impact, we are delaying Adobe Analytics Reporting’s end of support for TLS 1.0 encryption. Starting in February, 2019, Adobe Analytics Reporting will no longer support TLS (Transport Layer Security) 1.0 encryption. This change is part of our ongoing efforts to maintain the highest security standards and promote the safety of customer data. Because the Analytics reporting interface already requires a modern web browser, we do not anticipate issues. If you are unable to connect to Adobe Analytics reporting after February 2019, you should upgrade your browser to the latest version .
Starting February 2019, Adobe Analytics Reporting API will no longer support TLS 1.0 encryption. Customers who access the API should verify that they will not be impacted.
  • API clients using Java 7 with default settings will need modifications to support TLS 1.2 . (Refer to “Changing default TLS protocol version for client end points: TLS 1.0 to TLS 1.2”.)
  • API clients using Java 8 should not be impacted because the default setting is TLS 1.2.
  • API clients using other frameworks will need to contact their vendors for details on TLS 1.2 support.
Starting February 2019, Adobe Analytics Data Collection will no longer support TLS 1.0. With this change, we will no longer collect Analytics data from end users with older devices or web browsers that do not support TLS 1.1 or later.
Note: If your web site does not support TLS 1.0, you will not be impacted by the collection change.
Update Adobe Report Builder due to end of support for TLS 1.0
Sept. 7, 2018
Due to the end of support for TLS 1.0, we recommended that Adobe Report Builder (ARB) users download ARB v5.6.21 prior to February 2019. After that date, prior versions of ARB will no longer function.
New help for the Analytics user migration
May 10, 2018
We updated the Analytics user ID migration help with information about migrating Enterprise and Federated IDs to the Admin Console.
Upcoming removal of Account Activity Report
May 10, 2018
The Account Activity Report will be replaced by the Server Call Usage feature in the Adobe Analytics Summer Release. The Account Activity Report will be permanently removed on August 9, 2018. To view summary data about report suite traffic after August 9, 2018, use the Server Call Usage feature.
Changes to linear allocation models in Calculated Metrics
May 10, 2018 (Effective July 19, 2018)
On July 19th, Adobe Analytics will revise the way allocation models in calculated metrics are evaluated. As part of this change, calculated metrics that use a non-default allocation model will be migrated to new and improved attribution models.
Marketing Channel Last Touch and Marketing Channel First Touch allocation models will be migrated to new Last Touch and First Touch attribution models respectively. (Marketing Channels are not being deprecated, only the two allocation models that appear in calculated metrics).
Additionally, we will correct the way linear allocation is calculated. If you use calculated metrics with linear allocation models, the reports may change slightly to reflect the new, corrected attribution model.
This change to calculated metrics will be reflected in Analysis Workspace, Reports & Analytics, the Reporting API, Report Builder, and Ad Hoc Analysis.
See the Calculated Metrics documentation for more information about this change.
Anomaly Detection and Contribution Analysis functionality removed from Reports & Analytics
April 10, 2018
Anomaly Detection and Contribution Analysis have been removed from the Reports & Analytics feature set and are now available only via Analysis Workspace .
Adobe Analytics Select and Foundation customers have access only to “daily-granularity” Anomaly Detection in Analysis Workspace help.
Adobe no longer issuing 3rd-party s_vi cookies for Safari
April 05, 2018
On March 20, 2018, Adobe stopped issuing third-party s_vi cookies for the Safari browser. This change does not impact customers using first-party data collection cookies. This change also removes the visit and visitor inflation experienced by some customers, resulting from Safari ITP.
Update Report Builder before you migrate user IDs to the Admin Console
March 17, 2018
Update your installation of Report Builder to the latest version. This update is a pre-requisite for running the Analytics user ID migration to the Admin Console, beginning in April 2018.
See Analytics User Migration to the Admin Console for migration information.
Back-end changes that affect reporting
April 11, 2018
A change to the (back-end) lookup mechanism is going to impact reporting in several ways. Please be aware that these changes went into effect around the end of February, 2018:
  • Page renaming will no longer be allowed. Going forward, you will need to use classifications to rename pages. Until the May 10, 2018 release, the system will continue to process the renamed pages as they are currently configured. Adobe is asking all customers to migrate to classifications by that date. After the May release, existing renames will no longer be honored and can change, retroactively, without notice.
  • The URL replacement methodology is different. Previously, Adobe Analytics would store (mostly) the first URL associated with each page name each month. Going forward, we will store the most recent URL for each page name.
  • (Updated April 11, 2018) Category reports for roll-ups and current data in Reports & Analytics are no longer provided. Deprecating category roll-up reports in the Web Service API is effective with the May 10, 2018, Adobe Analytics maintenance release.
  • There is no longer any support for page/prop data from before approximately January 2007 (in some cases, 2006). This only impacts pages, props and page events (i.e. custom links, exit links, download links). (This change does not impact reporting in Analysis Workspace or Data Warehouse.)
If you have data preceding these dates, data will not combine correctly across the pre/post January 2007 boundary, and searches will not work against data before approximately January, 2007.
Upcoming support changes for Date-Enabled and Numeric Classifications
May 7, 2018
In the May 10, 2018 Maintenance release, we will begin limiting the functionality of date-enabled and numeric classifications. These classification types will be removed from the Admin and Classification Importer interfaces.
From that date on, no new date-enabled and numeric classifications can be added. Existing classifications can still be managed (uploaded to, deleted) through the standard classification workflow, and will continue to be available in reporting.
Upcoming support changes for Marketing Channel Cost and Budget
February 28, 2018
In the April maintenance release, we will remove Marketing Channel Cost and Budget from the Admin > Marketing Channel menu. No new cost and budget data can be added. Existing cost and budget data will continue to be available in reporting, but cannot be updated.
Code Manager - Legacy H Code
February 8, 2018
Downloading legacy JavaScript (H code) from the Code Manager is no longer supported.
Data retention: Check and set your data retention policy for Adobe Analytics
February 1, 2018
The European Union’s General Data Protection Regulation (GDPR), which applies as from May 25, 2018, provides that Adobe, in its role as your data processor, must take appropriate measures to assist its customers in fulfilling access, deletion, and other requests from individuals. Applying appropriate, secure, and timely deletion policies is an important part of complying with this obligation. As a result, Adobe would like to work with you to implement a data retention policy before GDPR takes effect on May 25, 2018.
What to expect
Unless you already have an Adobe Analytics data retention policy in place, Adobe will begin applying data retention as currently specified in customer contracts for Adobe Analytics, unless other arrangements are made.
Most Adobe Analytics contracts state that Adobe may delete data after 25 months. Once a data retention policy is in place for your organization, it is enforced on a rolling monthly basis. Data retention for longer periods than 25 months is available for an additional fee. Data retention periods for shorter periods can also be configured by contacting Customer Care.
You will soon receive an email with additional details for your organization.
Data retention impacts all methods for accessing historical Adobe Analytics data, including but not limited to Reports & Analytics, Analysis Workspace, Report Builder, the Web Services Reporting APIs, data warehouse, and data feeds.
Next steps
Identify stakeholders within your organization responsible for making decisions about data retention. Your organization is best placed to know the appropriate period for which Adobe Analytics data should be retained.
Contact your Adobe Customer Success Manager if you have questions regarding data retention for Adobe Analytics.
User account linking
October 26, 2017
Analytics users no longer need to manually link their accounts between the Experience Cloud and Analytics. Users can contact their Admin Console administrator to request Analytics access.
The Analytics user ID migration enables administrators to easily migrate user accounts from Analytics User Management to the Adobe Admin Console. After your users are migrated, they will have access to the purchased solutions and core services available in the Experience Cloud.

Audience Manager

New features and fixes in Adobe Audience Manager.
See Segment Mapping Rules for more information on the set of rules that IRIS follows when sending segments to destinations. Go to IRIS > Segment Mapping Rules .
With Trait Exclusions, you can remove traits from modeling. This way, extremely common traits such as site visitor traits don't bias your model. This new capability also enables you to remove traits from third-party data feeds.
Audience Lab Advanced Functionality - Duplicate Allocation Template and Test Segment Holdout
We released two features to increase your productivity when using Audience Lab. Learn how to get started with them in Audience Lab Advanced Functionality .
Fixes, enhancements, and deprecations
We updated the name of the Outbound History Report to Outbound File History Report. The previous name caused some customers to think the report would show outbound data for HTTP destinations. In fact, the report covers files delivered to S3 or FTP locations.
Known issues
  • The latest version of Safari includes Intelligent Tracking Prevention (ITP) 2.0 tools. This affects Addressable Audience metrics for your Safari users and data collection using the h_referer signal. Read about Safari traffic as a Cause of Low Match Rates for Addressable Audiences and data collection using the h_ prefix .
  • The release of Trait Exclusions in Algorithmic Modeling introduced an issue for customers using Role-Based Access Controls . When creating a new model, if you only select data sources that you have access to, you can see their corresponding traits in the Exclusions window. However, if you select any other data sources than the ones you have access to, in addition to the ones that you have access to, you will see a blank list. Unselect the data sources that you don't have access to in order to see the traits. (AAM-42380)
Documentation Updates

Marketing Cloud

Experience Manager

New features, fixes, and updates in Adobe Experience Manager. Adobe recommends customers with on-premise deployments to deploy the latest patches to ensure higher stability, security, and performance.

Product releases

  • AEM Dispatcher 4.3.1
Adobe strongly recommends using the latest version of AEM Dispatcher to avail the latest functionality, the most recent bug fixes, and the best possible performance.

Self help

  • Configuring AEM Assets integration with Experience Cloud and Creative Cloud
The documentation for configuring the AEM Assets integration with Experience Cloud and Creative Cloud has been updated. If you use this integration, Adobe recommends that you update the configuration to point to instead.


  • Experience League: Fast-track your Adobe Experience Cloud Expertise
Learning any new software can be challenging. Even after the initial training, there may be a lot to learn and you may not know where to start or who to ask for help.
When it comes to learning Adobe Experience Cloud , you can expect a different experience. Unlike any other guided learning program out there, our Experience League enablement program is uniquely tailored to your individual needs—and it's free for everyone. Experience League just launched Business Essentials for most of the solutions in Experience Cloud (two for AEM). It is also coming up with Implementation essentials very soon.
For more information see the following: .


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


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.

Adobe Campaign Classic 18.10

Availability: November 5, 2018
Push notification improvements
A number of enhancements has been implemented for push notifications in Adobe Campaign:
  • Track silent notifications in iOS
  • Implement feedback on registration calls in iOS
  • Improve iOS delivery preparation speed
As a part of GCM depreciation by Google, Android V2 connector now allows connections only to the FCM server.
SQL Data Management activity
A new data management workflow activity has been added. The SQL Data Management activity lets you write or copy-paste your own SQL scripts to create and populate work tables (FDA only).
Workflow monitoring
With the new Adobe Campaign Workflow HeatMap, the platform administrators have a quick graphical representation of all the concurrent workflows, which allows them to monitor the load on the instance and plan workflows accordingly.
For product documentation, see: