New features and fixes in the Adobe Experience Cloud.
Subscribe to the Adobe Priority Product Update to be notified via email about upcoming releases. New information published after the release will be marked with the publication date.
Release date: October 31, 2019
Looking for the help home? See Adobe Experience Cloud Documentation.
Release notes for Experience Cloud interface and product administration.
For product documentation, see Experience Cloud.
Release notes for the Experience Platform, Experience Platform Launch, Identity Service, and security bulletins.
See Experience Platform Launch for release notes and product documentation.
New features and fixes in Adobe Analytics:
For product documentation, see Adobe Analytics Help Home.
|Customer Journey Analytics||On November 21, 2019, Customer Journey Analytics becomes available as an add-on to Adobe Analytics.
Customer Journey Analytics allows you to bring your customer data from any channel you choose — both online and offline — into Adobe Experience Platform, and then analyze this data just as you would your existing digital data using Analysis Workspace today. Customer Journey Analytics includes the ability for you to control how you connect your online and offline data in Analysis Workspace on any common customer ID, finally allowing you to do attribution, segmentation, flow, fallout, etc. across your entire customer data set in Adobe Analytics.
Analytics Select, Prime, and Ultimate customers are eligible to purchase this add-on product. Please contact your Adobe account team for further details.
|Privacy Service API: CCPA||The California Consumer Privacy Act (CCPA) enhances privacy rights and consumer protection for residents of California, United States. This Act is set to become effective on January 1, 2020.
The CCPA provides new data privacy rights to California residents, such as the right to access and delete their personal data, to know whether their personal data is sold or disclosed (and to whom), and to refuse the sale of their personal data.
In anticipation of the CCPA, the Privacy Service will support requests to opt out from the selling of personal data.
The Privacy Service was formerly called the GDPR Service and retains all the previous functionality, now extended to support CCPA.
CCPA in Analytics
Privacy Service Overview
|Privacy Reporting: Analytics Admin Console||Enabling Privacy Reporting for Analytics adds a set of reserved variables to a report suite. The variables are designed to assist in the collection of consumer consent data at a hit level.
|Audio and Video Analytics: Privacy Support||Two new variables have been added to the Media Collection API:
These are optional variables that can be used to capture the status of a consumer’s consent at the time of the hit.
Media Collection API Documentation
The new Analytics Consent Management context data variables have been added to the Federated Analytics form. These variables are now available for use in flagging Opt Out of Sharing or Selling hits for federation.
Download Federated Form
|Notice||Date Added or Updated||Description|
|New Adobe Analytics domain||Dec. 18, 2019||On January 16, 2020, Adobe Analytics will move to new domain - https://experience.adobe.com/analytics. This change may cause cookie issues when loading Analytics in Safari. Unchecking “Prevent cross-site tracking” in the Safari Privacy Preferences will enable cookies across domains (and all cross-site experiences), and allow Analytics to function on this new Adobe Experience Cloud domain. Users can use other browsers without issue, since this only affects Safari users.|
|EOL of View Archive option||Oct. 30, 2019||Announcing the January, 2020, end-of-life date for the View Archive option in the Dashboard Manager (Components > Dashboards).|
|EOL of Enforce IP Login Restrictions option||Oct. 30, 2019||Announcing the January, 2020, end-of-life date for the IP Allowed List (Enforce IP Login Restrictions) functionality under the Admin > Company Settings > Security menu.|
|Updated handling to SameSite attribute on cookies||October 15, 2019||In August 2019, Adobe announced that it added the SameSite cookie setting to all cookies set by Analytics. An update in logic is applied where:
|End of Support for TLS 1.1||October 3, 2019||By March 31, 2020, Adobe Analytics will remove support for TLS 1.1. This change is part of our ongoing efforts to maintain the highest security standards and promote the safety of customer data.|
|San Jose FTP Broker Ending for London and Singapore||July 2020||For customers in London and Singapore, we will no longer be supporting brokering of data between London or Singapore and the San Jose data center ftp.omniture.com.
|Update to Analysis Workspace Freeform Table totals||September 12, 2019||In October 2019, freeform table total rows will begin accounting for report filters applied. To date, totals have accounted only for segmentation. With this change, dependent visualizations will update (e.g. linked Summary Number visualizations), as well as exported CSV and PDF data.|
|Upcoming change regarding
||August 30, 2019||In October or November 2019, the
|Support for Historical Timezone Offsets||August 8, 2019||Analytics will now automatically handle timezone offsets for timestamped hits. Following this change on August 8, systems that load in data for historical processing will no longer need to adjust for timezone offsets before sending in the data.|
|Classification rule builder limits||Added June 5, 2019||These limits are not new, but have been added to the documentation here.|
|New segment operator limits||Added May 31, 2019||Starting July 18, 2019, the segment operators contains any of, does not contain any of, contains all of and does not contain all of will be limited to 100 words per input field. The limit will be applied to all new and modified segments after this date. Existing segments that exceed the limit will continue to be supported, but cannot be modified or saved until the input field is reduced. These limits are being applied as part of a continued effort to improve query performance.|
|Support changes for Date-Enabled and Numeric 2 Classifications||Updated May 28, 2019||The ability to import Numeric 2 and Date-Enabled classifications has been removed from the codebase. This change took effect with the July 2019 Maintenance Release. If you have Numeric or Date-Enabled columns in your import file, those cells will be silently ignored, and any other data within that file will be imported as normal.
Existing classifications can still be exported through the standard classification workflow, and will continue to be available in reporting.
|Change to Report Total calculations||Updated July 9, 2019||On June 18, 2019, Adobe Analytics made Report Total calculations consistent across all dimensions and metrics. This resulted in a change to the totals for some reports (typically, Prop or Customer Attributes reports). Prior to this change, some Report Totals inconsistently included or excluded the Unspecified line item in the total, regardless of whether Unspecified appeared in the report.
As of June 18, 2019, Unspecified will always appear in the report total, even if it does not appear as a line item in the report. Additionally, segments using exists or does not exist logic may see different results for some dimensions after this change, specifically dimensions where Unspecified has a special name such as the “Typed/Bookmarked” line item for Referrer Type dimension or the “Other” line item for the Device Type dimension. This change will affect Analysis Workspace, Reports & Analytics, Ad Hoc Analysis, Report Builder, and the Reporting API.
Note: This Report Total calculation is now called Grand Total. See “Analysis Workspace: Update to Freeform table totals” above.
|Update to CSV downloads from Analysis Workspace||April 10, 2019||Starting on April 11, 2019, several changes were made to CSV downloads (and Copy to Clipboard) from Analysis Workspace to remove formatting from exported data.
|Upcoming change to the Analysis Workspace Debugger command||April 4, 2019||The Console command to turn on the Analysis Workspace Debugger is changing to adobeTools.debug.includeOberonXml on June 13, 2019. adobe.tools.debug.includeOberonXml will cease to function after that date.|
|Mobile browser version numbers||February 7, 2019||Starting January 8, 2019, we changed the truncation level for mobile browser version numbers from 2 to 1. From that date forward, versions only display the first two levels (e.g. Firefox 64.0.2 is now reported as Firefox 64.0).|
|End of life for Ad Hoc Analysis||January 29, 2019||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, including which versions of Java will be compatible during this period, visit Discover Workspace.
|Short Analytics report links||January 14, 2019||Any short Analytics report links that have not been visited within one year will be cleaned up and deleted starting on Thursday, January 17, 2019, on a rolling schedule.|
|Data Feed: post_product_list column - size change||January 9, 2019||On February 7, 2019, Adobe expanded the size of the post_product_list column from 64 KB to 16 MB. This change ensures 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.|
|Management changes affecting inactive Analytics 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 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.|
|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 Report Builder users download version v5.6.21 prior to February 2019. After that date, prior versions of Report Builder will no longer function.|
|Profile Merge Rules Enhancements||We released a series of enhancements for Profile Merge Rules:
|Intelligent Recommendations for Audience Marketplace Data, powered by Adobe Sensei||With Trait Recommendations, when you build or edit a segment in Segment Builder, you now get recommendations on additional traits that you can include, from Audience Marketplace data feeds that you are not subscribed to. Add the recommended traits to your segment to increase your target audience.
Additionally, we’ve redesigned the Marketplace page to make it easier for you to find similar traits and filter data feeds.
|Bulk Management Tools||We released a new version of the Bulk Management worksheet that works on MacOS and Microsoft Windows operating systems and supports Experience Cloud login.|
|HTTP Strict-Transport-Security||We added support for HTTP Strict-Transport-Security, a web security policy that protects against cookie hijacking and protocol downgrade attacks.|
As of November 2019, Audience Manager also supports sending Roku IDs, Amazon Fire TV IDs and Xbox/Microsoft IDs to Google Ad Manager and DV360 destinations, in addition to previously supported cookie, IDFA and GAID device IDs. You don’t need to change anything in your existing Google integrations.
In Audience Manager, Roku IDs, Amazon Fire TV IDs and Xbox/Microsoft IDs are called global device IDs. You can read more about these IDs and the data sources that they are associated to in the Audience Manager product documentation:
Data ingestion for the Roku, Amazon Fire TV and Xbox/Microsoft data sources works in the same way as for IDFA and GAID - an Audience Manager ID is automatically generated and linked to the DAID when ingesting data keyed off them. The new IDs are automatically sent to the existing and new Google destinations configured in your account.
For more information, please contact your Audience Manager consultant or Customer Care.
New features, fixes, and updates in Adobe Experience Manager (AEM). Adobe recommends customers with on-premise deployments to deploy the latest patches to ensure higher stability, security, and performance.
Brand Portal 6.4.5
Adobe Experience Manager Assets Brand Portal 6.4.5 is a feature release that focuses on providing Brand Portal users (external agencies/teams) with the ability to upload content to Brand Portal and publish to AEM Assets, without the need to access the author environment. This feature is called Asset Sourcing in Brand Portal, and improves customer experiences by providing a two-way mechanism for users to contribute and share assets with other globally distributed Brand Portal users.
See Release notes.
AEM Forms Automated Conversion Service
Automated Forms Conversion service helps accelerate digitization and modernization of data capture experiences through automated conversion of PDF forms to adaptive forms. The service, powered by Adobe Sensei, automatically converts your PDF forms to device-friendly, responsive, and HTML5-based adaptive forms. While leveraging the existing investments in PDF Forms and XFA, the service also applies appropriate validations, styling, and layout to adaptive form fields during conversion.
Cloud Manager 2019.10.0
The general Release Notes for Cloud Manager 2019.10.0 are now available. The notes also lists updates to deployment steps and maven project version handling.
Due to security changes within the Adobe Analytics API, it is no longer possible to use the version of Activity Map that is included within AEM. See Configuring the connection to Adobe Analytics.
You should now use the Activity Map browser plug-in for either Chrome, Firefox, or Internet Explorer as provided by Adobe Analytics.
Best practices guide for AEM Screens projects
The new Best Practices Guide for AEM Screens provides comprehensive insight and practical advice to imagine, design, and bring intentional customer experiences into your digital signage implementation. It also guides you in how to create a positive impact on your business using best practices, all while deploying a digital signage project in AEM Screens.
Headless Experience Management
Features of the Remote Content Renderer that is used for server side rendering of single page applications is now documented.
SPA and Server-side Rendering
You can extend and customize the remote content rendering service that your AEM-driven SPAs use for server-side rendering to meet your needs.
AEM Project Archetype
The AEM Project Archetype creates a minimal, best-practices-based Adobe Experience Manager project as a starting point for your own AEM projects. The properties that must be provided when using this archetype let you specify the names for all parts of this project as well as control certain optional features.
AEM Documentation Updates
Read about important documentation changes and updates for Adobe Experience Manager in the last three months.
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.
Updated on November 8, 2019, release
If you use Advertising Cloud conversion tracking and haven’t already deployed the Advertising Cloud conversion mapping tag, deploy the following code on all landing pages:
|Portfolios||When the portfolio option “Enable campaign max spend % target” is enabled, the max spend target is now never exceeded. Previously, Advertising Cloud would exceed the max spend target when doing so was optimal.|
|Search Audiences||Your audience library at Search > Audiences > Library now automatically includes an “Audience Size” column, which is populated daily from Bing Ads and Google Ads. You can optionally use the column as a data filter.|
|Integration with Adobe Analytics||Analytics now includes the dimension “Landing Type (AMO ID)” for Advertising Cloud DSP campaigns. Use this dimension to segment Analytics metrics based on how visitors landed on the site. Values include “Click Through” and “View Through.”
Note: Data for view-throughs that occurred before 31 October 2019 are shown as data for click-throughs. We therefore don’t recommend using this dimension with data prior to mid-November 2019.