Show Menu
TOPICS×

Adobe Experience Cloud Release Notes

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: August 8, 2019

Experience Cloud and Experience Platform

Release notes for the Experience Platform, Experience Cloud interface, product administration, Experience Platform Launch, Identity Service, and security bulletins.

Experience Cloud interface

  • Fixed a critical issue in Experience Cloud login that led to session logout for some users. (MCUI-6908)
  • Updated Experience Cloud login to improve performance and reduce latency. (MCUI-6854, MCUI-6869, MCUI-6883)
  • Updated interface cosmetically. (MCUI-6861, MCUI-6911, MCUI-6862)
  • Fixed an issue with Experience Cloud Triggers that led to incorrect interpretation of Like clause in the Trigger definition. (MCUI-6611)
For product documentation, see Experience Cloud .

Experience Platform Launch

See Experience Platform Launch for release notes and product documentation.

Analytics

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

New features, enhancements, and fixes in Adobe Analytics

Feature
Description
Support for SameSite cookie settings
The SameSite cookie setting will be added to all cookies set by Analytics. This change allows you to be compliant with the Chrome changes requiring the SameSite cookie field. Analytics cookies will default to none . If you have exclusively used a 1st-party domain (e.g. stats.domain.com) you can have Adobe ClientCare set it to lax for 1st-party collection domains.
Workspace: Increase item limit for dropdown filter from 50 to 200
We increased the limit of items that can be placed in a dropdown filter from 50 to 200. This enhancement accommodates a variety of use cases, such as adding all countries (195) to a filter, or all US states and provinces (52).
A4T Activity Impressions and Activity Conversions enabled for Attribution IQ
We have enabled two Analytics for Target (A4T) metrics for Attribution IQ: Activity Impressions and Activity Conversion. Previously, in Analysis Workspace, these metrics were inflated compared to Reports & Analytics. With this change, users can now apply a "same touch" attribution model, which will bring Analysis Workspace in line with Reports & Analytics.

Fixes

  • Fixed an issue with the text display in real-time reports when in full-screen mode. (AN-183168)
  • ( Updated August 20, 2019 ) Data collection now rejects redirect URLs that contain "@" signs to prevent attackers from redirecting to malicious sites via whitelisted domains.
  • ( Updated August 20, 2019 ) Visitor Migration is now disabled for all hits coming from browsers which do not support the SameSite Cookie attribute, and if the hit contains a 3rd-party cookie.
  • ( Updated August 20, 2019 ) Fixed an issue where first hits were not sent the s_vi cookie for a new visitor.

Important notices for Analytics administrators

Notice
Date Added or Updated
Description
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.
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.
Upcoming change to Report Total calculations
Updated July 9, 2019
On June 18, 2019 , Adobe Analytics will make 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.
Update to CSV downloads from Analysis Workspace
April 10, 2019
Starting on April 11, 2019, several changes were made to CSV downloads (and #) from Analysis Workspace to remove formatting from exported data.
  • The thousands separator is no longer included. The decimal separator will continue to be included, and will adhere to the format defined under Components > Report Settings > Thousands Separator . Note: Numeric values that use a comma as the decimal separator will continue to be quoted in the exported CSV.
  • No currency symbols will be shown.
  • No percent symbols will be shown. Percentages will be in decimal form. E.g., 75% will be represented as 0.75.
  • Time will be shown in seconds.
  • Cohort tables will show raw values only; percentages will be removed.
  • If a number is invalid, an empty cell will be displayed.
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.
  • 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.
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.

AppMeasurement

AppMeasurement 2.16.0 releases on August 8, 2019.
Feature
Description
sendBeacon support for exit links
Implemented sendBeacon support in AppMeasurement for exit links. This will improve exit link tracking and will likely result in increased traffic.
ECID/fid values
ECID/fid values are now cached on the first hit even though OptIn settings change.
DIL 9.3
Updated Audience Management Module to DIL 9.3
Scroll reach tracking
Exposed switch in s.ActivityMap.trackScrollReach to turn scroll reach tracking on or off.
Visitor ID Service 4.4.0
Upgraded AppMeasurement to use Visitor ID Service 4.4.0.

Fixes

  • Fixed a bug in AppMeasurement queuing that occurred before isReadyToTrack was true.
See AppMeasurement release history 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

Audience Manager

Fixes and Improvements
  • The Administration tab now only appears to user accounts with administrative privileges (AAM-48557).
  • The List Users API now returns full user details (AAM-48662).
  • You can now resize the trait folder list (AAM-48800).
  • Multiple UI accessibility optimizations (AAM-48865, AAM-48933).
  • Loading optimizations for the Administration and Data Sources pages (AAM-48514).

Experience Manager

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.

Product end-of-life

Digital Publishing Suite Classic (DPSC) will end-of-life on August 31, 2019. For more information, see the Digital Publishing Suite Classic End-of-Life FAQ .

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.

Adobe Campaign Standard

Feature
Description
External API Activity (Public Beta)
For deeper personalization, External API Activity allows you to bring data from external systems into a workflow via a REST API call. The REST endpoints can be a customer management system, Adobe I/O Runtime or Adobe Experience Cloud REST endpoint (e.g. Data Platform, Target, Analytics, Campaign). This capability is currently in public beta. For more information, refer to the detailed documentation and the how-to video .
Report on workflow segment
This feature allows marketers to break down their delivery performance by segment code. When you create a workflow and use a segmentation activity to assign segments to the delivery population, these segments can now go into the same delivery. This allows you to display the opens/clicks statistics based on multiple segments within a single delivery. For more information, refer to the detailed documentation and the how-to video .

Adobe Campaign Classic

Adobe Campaign Control Panel

New Control Panel capabilities include the ability to add URLs that Campaign Classic connects to for data/file transfers.
Please note that Control Panel is available for both Adobe Campaign Classic and Adobe Campaign Standard customers hosted on AWS. No upgrades are required to access Control Panel.

Additional resources

Advertising Cloud

Updated: August 9, 2019, for August 10 release
  • (Advertisers with the Advertising Cloud conversion tracking service) With Apple's Intelligent Tracking Prevention (ITP) 2.2, which was released in May, Advertising Cloud conversion-tracking cookies are automatically deleted from Apple Safari browsers after 24 hours. Advertising Cloud has a new ITP solution, however, that enables you to track conversions that occur within Safari for more than 24 hours after the original click. The solution uses local storage and iframe technology. Contact your Advertising Cloud Search account manager for the implementation instructions.
  • In Search > Advanced (ACM), you can now configure campaign-level final URL suffixes for Google text ad and shopping ad templates.
  • Advertisers with Google Ads accounts that are eligible for Customer Match can now do the following:
    • Create a Google Ads customer match audience using user IDs from an Adobe audience segment. To see this feature, the advertiser account must be configured to allow it.
    • Create a Google Ads customer match audience by uploading a customer data file. The file can consist of contact information (email addresses, mailing addresses, or telephone numbers), user IDs, or mobile device IDs. Some types of contact information must be hashed using the SHA-256 algorithm.
    • Update any Google customer match audience except audiences created from an Adobe audience. You can upload data to add, to delete, or to replace all existing data for the audience. All contact information must be hashed using the SHA-256 algorithm.
  • The Audiences > Targets and Audiences > Exclusions views include a "Type" column.