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.
Release date: July 18, 2019
Release notes for the Experience Cloud interface, including Platform core services and product administration.
Fixes and updates
cookieDomainconfig update: The library will automatically assign a top-level cookie domain when
initConfigis not set. (CORE-29223)
MCOPTOUTvalue in parent visitor versus iframe child visitor from
optIn.offto unsubscribe from events.
See Experience Cloud ID Service for cumulative release notes.
iOS and Android were updated as follows:
sessionIdin the URL query parameters.
visitorGetUrlVariablesAsyncAPIs no longer double-encode their return values. The double-encoding was causing the return values from those APIs to be flagged by certain security reviews.
Visitor.getUrlVariablesAsyncAPIs no longer double-encode their return values. The double-encoding was causing the return values from those APIs to be flagged by certain security reviews.
For product documentation, see Mobile Services.
See Experience Platform Launch (links to product help) for release notes and product documentation.
See Security bulletins and advisories for important information regarding security vulnerabilities that could affect specific versions of Adobe products.
For product documentation, see Analytics Help Home.
|Analysis Workspace – Cohort Analysis enhancements||New Cohort Analysis settings have been added:
|Analysis Workspace||In the left rail, users now have the option to Show items from last 18 months. Previously, the lookback period was a maximum of 6 months. This makes it easier to compare to pages or campaigns from last year, up to 18 months ago.|
|New Analysis Workspace template||We added a new template called “Magento: Marketing & Commerce” to Analysis Workspace. It is designed specifically for Magento e-commerce customers, but any retailer can use it to get unique insights into their commerce activities.|
|Notice||Date Added or Updated||Description|
|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 on 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.|
|Upcoming 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 will take 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 will result 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” in the October 2019 release notes.
|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.|
|End of Support for TLS 1.0||Updated January 10, 2019||As of February 11, 2019 Adobe Analytics reporting no longer supports 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. If you are unable to connect to Adobe Analytics reporting after February 11, 2019, you should upgrade your browser to the latest version.
As of February 20, 2019 Adobe Analytics data collection no longer supports TLS 1.0. With this change, Adobe no longer collects Analytics data from end users with older devices or web browsers that do not support TLS 1.1 or later. We do not expect this to have a significant impact on customer data or reporting. (If your website already does not support TLS 1.0, you will not be affected.)
Beginning April 11, 2019, the Adobe Analytics Reporting API no longer supports TLS 1.0 encryption. Customers who access the API should verify that they will not be impacted.
|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.|
Released July 15, 2019:
See AppMeasurement release history for a release history of AppMeasurement on the following platforms:
See Data Workbench release notes for the latest information.
Fixes and Enhancements
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.
New feature information for the following products:
The latest Cloud Manager release (2019.6.0) contains a new Product Update Wizard to help customers successfully run an AEM update.
The XML Documentation 3.4 solution is now available.
completerow within a table using copy and paste.
AEM 6.2 SP1-CFP20
AEM 6.2 Service Pack 1–Cumulative Fix Pack 20 (188.8.131.52), released June 6, 2019, is an important update that includes key customer fixes released since the general availability of AEM 6.2 SP1 December, 2016.
AEM 184.108.40.206, released July 3, 2019, is an important update that includes key customer fixes released since the general availability of AEM 6.3 April, 2017.
AEM 220.127.116.11, released July 3, 2019, is an important update that includes key customer fixes released since the general availability of AEM 6.4 in April, 2018.
AEM 18.104.22.168, released July 3, 2019, is an important update that includes key customer fixes released since the general availability of AEM 6.5 in April, 2019.
AEM cache invalidation update
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 release notes, see:
For product documentation, see:
See Target release notes (pre-release) for the latest release information about Target.
For information about Magento Commerce and Magento Open source release notes, see: