Adobe Experience Cloud Release Notes - April 2020
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: April 2020
(Specific release dates my vary.)
- Analytics (Release date change - see update on April 15)
- Target (links to Target's help page)
- Primetime (links to Primetime's help page)
Looking for the help home? See Adobe Experience Cloud Documentation .
Adobe System Status
Adobe System Status provides detailed information, status updates, and email notifications about Adobe cloud products and services outage, disruption, and maintenance events. Check it out at status.adobe.com .
- Using your Adobe ID, you can subscribe to event notifications with more granularity, down to the product offering and add-on level. Furthermore in our latest release, the self-subscription process now recommends a selection of products and services based on your product entitlements. This should streamline the subscription process by reducing the number of decisions or clicks required to create your subscriptions, and most importantly, deliver more relevant notifications in your inbox. Get started at status.adobe.com/subscriptions .
New features and enhancements available today
Personalized subscriptions based on entitlements
Easier Management of Subscriptions
Experience Cloud interface
New features and fixes in the Experience Cloud interface:
- Experience Cloud Feed page was deprecated. (EXC-8505)
- Experience Cloud login page was updated to reflect new branding elements. (EXC-10747)
For product documentation, see Experience Cloud interface help .
Unified product domain
Adobe is updating the domain and interface header to unify and improve your experience across all Experience Cloud applications. These enhancements are designed to simplify your experience in small but important ways. These enhancements will not change your current workflows.
- New application URLs: experience.adobe.com/<application name> :
- All products will eventually adopt this URL pattern. Look for new URLs to become effective throughout the month.
- Browser support: Supported browsers include Microsoft Edge, Google Chrome, Firefox, Safari, and Opera (latest versions). Note: Although the Experience Cloud interface supports these browsers, individual applications might not support every browser. (For example, Analytics does not support Opera, and Target does not support Safari.)
- (Safari only) The domain change may cause cookie issues in Safari. Deselecting Prevent cross-site tracking in the Safari Privacy Preferences enables cookies across domains (and all cross-site experiences), and allows Experience Cloud to function on this new domain.
- Easier switching between your organizations or to a different application.
- Improved product help: Experience League is integrated into the product so that a help search also includes results from community forums and video content. This change simplifies access to more content and helps you get the most out of Experience Cloud. Additionally, click Help > Feedback to report issues or share your ideas with Adobe.
Release notes for the Experience Platform, including Experience Platform Launch, Journey Orchestration, Offers, People, Places, Mobile Services, and security bulletins.
Mobile Services and Mobile SDKs
Android 4.18.2 (3 April, 2020):
- In App Messaging: For security reasons, WebViews created by the SDK now set property setWhitelistingFileAccess equal to false .
iOS 4.19.2 (24 March, 2020):
- General: Fixed some leaks in Target code.
Unity 4.19.0 (10 March, 2020):
- Updated Unity Plugin to use versions 4.19.0 of iOS and 4.18.0 or Android.
- Exposed new acquisition method for Android to allow processing of a URL provided by Google Play Referrer APIs.
The Adobe Analytics April maintenance release has moved to May 21, 2020. For the latest Analytics release information, see March 2020 release notes.
- Important notices for Analytics administrators (Updated April 7, 2020)
Customer Journey Analytics
Customer Journey Analytics: Automated Dataset Backfill
This new option lets you import all historical data for a connection in Customer Journey Analytics. Learn more
Important notices for Analytics administrators
Date Added or Updated
Change to how Entries/Exits are calculated in Workspace
April 7, 2020
In Analysis Workspace, as of March 2020, we have changed how the None value interacts with Entries/Exits. Because you can now turn Nones on and off in Analysis Workspace, we apply the None value after the entry or exit, whereas (for eVars) it used to be applied before. For example, assume the first hit of a visit has no value for eVars, but the second hit does. In Reports & Analytics it will show up as Unspecified for the Entry, but in Analysis Workspace it will show up as the value on the second hit.
EOL of Conversion Level setting
March 3, 2020
The non-functioning Conversion Level setting in Admin Tools > Report Suites > General Account Settings will be removed from the interface on March 12, 2020.
EOL of Dashboard Archive
March 27, 2020
The View Archive setting under Manage Dashboards in Reports & Analytics will no longer be available as of October, 2020.
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.
New Adobe Analytics domain
Dec. 18, 2019
On January 16, 2020, Adobe Analytics began moving to a new domain - https://experience.adobe.com/analytics.
Note: This change applies to all users accessing Analytics with their Adobe ID or Enterprise ID.
End of Life - Analytics Legacy APIs
January 9, 2020
In November 2020, the following Analytics Legacy API services will reach their end-of-life and will be shutdown. Current integrations built using these services will stop working.
We have provided a Legacy API EOL FAQ to help answer your questions and provide guidance on how to proceed. API integrations that employ these services can migrate to the 1.4 Analytics REST APIs or the 2.0 Analytics APIs . Legacy OAuth accounts can migrate to an Adobe IO Analytics integration account, which can be used to access both the 1.4 Analytics APIs and 2.0 Analytics APIs.
San Jose FTP Broker Ending for London and Singapore
For customers in London and Singapore, we will no longer support brokering of data between London or Singapore and the San Jose data center ftp.omniture.com .
EOL of Ad Hoc Analysis
Aug 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 .
New Analytics tutorials
Adobe Labs (Technology Previews) allows you to engage with emerging technologies, discover valuable insights, and influence future Analytics feature development and priorities.
Improvements have been made to Experience Cloud Audience Publishing. You can now publish audiences (segments) and make them available six times faster. This reduces the current latency time from 48 hours to approximately 8 hours, and possibly faster, depending on traffic and segment size.
Multiple report suites can be analyzed in a single Workspace project by selecting report suites at the panel level. This allows you to conduct side-by-side panel analysis across different sets of data.
See Adobe Analytics Help Home for product documentation.
New features and fixes in Adobe Audience Manager:
We've added a new section to our documentation portal, which includes answers to the most frequent questions received by our Customer Support team.
- Fixed an issue causing the Duplicate Test and Duplicate Allocation Template buttons in Audience Lab not to work. (AAM-53388)
- Fixed an issue causing the Match Rate and Segment Addressable Audiences to be displayed as 0 when a destination is configured to export UUIDs. The Match Rate and Segment Addressable Audiences are now displayed as 100%. (AAM-51615)
- Fixed an issue causing trait names which contain special characters to be HTML-encoded twice. (AAM-54001)
- Fixed an issue blocking some users from switching to other Adobe Experience Cloud applications from the Audience Manager user interface. (AAM-52917)
- Fixed an issue blocking some users from creating a SHA256 data source for People-based destinations. (AAM-53525)
- Multiple accessibility improvements across the interface. (AAM-48986, AAM-49009, AAM-48984, AAM-48939, AAM-48940, AAM-48964, AAM-49032, AAM-49360)
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.
- AEM NewsletterSee the latest Adobe Experience Manager Newsletter .
- AEM as a Cloud Service - Configuring Dynamic Media Cloud ServiceA new option is available when you configure Dynamic Media Cloud Service:Selective Publish - When you select this option it means that assets are auto published for secure preview only and can be explicitly published to AEM without publishing to DMS7 for delivery in the public domain.
- Dynamic Media - Smart ImagingThe entire Smart Imaging Help topic was updated with new information, including image asset examples that depict the added Smart Imaging optimization.See Smart Imaging .
- Configuring Dynamic Media - Scene7 modeA new Sync all content option is now available on the Dynamic Media Configuration page found in Tools > Cloud Services .
- AEM Assets Brand Portal supports AEM Assets as a Cloud ServiceYou can now publish assets from AEM Assets as a Cloud Service to AEM Assets Brand Portal.
- Adobe Asset Link 2.0 releasedAdobe Asset Link 2.0 supports working with multiple AEM environments and supports AEM as a Cloud Service. AEM supports marketers' needs to configure auto-run of asset processing workflow when assets are uploaded to a folder using Adobe Asset Link.See Adobe Asset Link .
New Experience Manager tutorials
Learn about facilitating configuring, validating, and simulating Dispatcher locally.
Adobe Experience Manager (AEM) development requires a minimal set of development tooling to be installed and set up on the developer machine. These tools support the development and building of AEM Projects.
Adobe Experience Manager (AEM) can be run locally using the AEM as a Cloud Service SDK's QuickStart Jar. This allows developers to deploy to and test custom code, configuration, and content prior to committing it to source control, and deploy it to a AEM as a Cloud Service environment.
Explore the basics for navigation AEM Assets.
Explore how AEM creates and maintains asset versions.
This video walks you through the setup of the integration between AEM and Magento.
The CIF Project archetype creates a minimal Adobe Experience Manager (AEM) CIF project as a starting point for customer projects using CIF Core Components.
An introduction to OSGi, a dynamic modular architecture for Java applications that is the basis for Adobe Experience Manager.
An introduction to the [Java Content Repository (JCR) used by Adobe Experience Manager.
An introduction to Sling, an open-source RESTful web framework that is part of Adobe Experience Manager's underlying technology stack.
An introduction to the Author and Publish tiers as part of the architecture in Adobe Experience Manager.
An introduction to the capabilities and features of the dispatcher as part of the AEM architecture.
An overview of developing components with Adobe Experience Manager Sites. Includes an introduction to Dialogs, Sling Models, HTL Scripts, and Client-Side Libraries.
The AEM Project contains all of the code and configurations for an implementation. The AEM Project Archetype creates a minimal, best-practices-based Adobe Experience Manager project as a starting point for your own AEM projects.
AEM Core Components are a standard set components to be used with Adobe Experience Manager.
Learn how to install and run a local instance of Adobe Experience Manager in just a few minutes with the AEM Quickstart jar.
Additional help resources
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.
New Campaign Standard tutorials
Test your email messages using the Profile Substitution feature.
Marketo Engage is a complete applications for lead management and B2B marketers looking to transform customer experiences by engaging across every stage of complex buying journeys.
Core Marketo Engage updates
See Marketo release notes for more information.
The following features are releasing throughout the quarter:
Compose Window and Command Center updates/enhancements
Marketo Engage Success Center: Launching in February 2020. The Success Center is an in-product help center that enables you to search Product Docs and the Community, launch how-to guides, access adoption content, and more. Note: This feature will be launched as a beta in ANZ and will roll out to North America later in the quarter.
- Asset API "_method" Parameter: After September 2020, Asset API Endpoints will no longer accept _method to pass Query Parameters in a POST body to bypass URI length limitations.
- Internet Explorer Support Deprecation: Beginning with the July release on July 31, 2020, the Marketo Engage user interface will no longer be supported on Internet Explorer.
For cumulative and historical release notes, see Marketo release notes .