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: May 2019
Version 1.0, May 15, 2019
Releasing May 13, 2019
New features and fixes in Adobe Analytics:
For product documentation, see Analytics Help Home.
|AppMeasurement Version 2.14.0
|Analysis Workspace: New Include Repeat Instances Flow visualization setting||The Include Repeat Instances flow setting gives you the option to include or exclude repeated instances, such as Page Reloads. Additionally, all Flow visualizations are now based on instances only.|
|Ad Hoc Analysis: Compatibility with Java 11||Ad Hoc Analysis is now compatible with Java 11. Learn how to run Ad Hoc Analysis on Java 11.|
|Data Collection: New s_ecid cookie||Added a new first-party server cookie, s_ecid, in which data collection stores the visitor’s ECID.|
Analysis Workspace Fixes
Other Analytics Fixes
|Notice||Date Added or Updated||Description|
|Upcoming change to Report Total calculations||April 16, 2019||On June 13, 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 13, 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. 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 will be 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.|
|Upcoming support changes for Date-Enabled and Numeric Classifications||February 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 June 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.
|Significantly updated the documentation on the getPercentPageViewed plug-in.||February 12, 2019||https://experiencecloud.adobe.com/resources/help/en_US/sc/implement/getPercentPageViewed.html|
|Admin > General Account Settings||February 7, 2019||* The setting Replace the last octet of IP addresses with 0 is enabled by default for any new report suites created in the London Data Center after January 2019, but only if the settings for those report suites are copied from a template listed in the Admin Console. Report suites whose settings are duplicated from other report suites inherit all settings from the selected report suite.
* The setting IP Obfuscation is no longer enabled by default for all customers with a report suite set in EMEA.
|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||Updated 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||On February 11, 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. If you are unable to connect to Adobe Analytics reporting after February11, 2019, you should upgrade your browser to the latest version.
Beginning February 20, 2019 Adobe Analytics data collection will no longer support TLS 1.0. With this change, Adobe will no longer collect 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 will no longer support TLS 1.0 encryption. Customers who access the API should verify that they will not be impacted.
|Update Adobe Report Builder due to end of support for TLS 1.0||September 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 7, 2019. After that date, prior versions of ARB no longer function.|
|Update to CSV downloads from Analysis Workspace||January 9, 2019||Starting on February 7, 2019, CSV downloads (and Copy to Clipboard) from Analysis Workspace will no longer include the thousands separator. Note: The Analysis Workspace UI will continue to show the thousands separator. Additionally, the decimal separator will continue to be included, and will adhere to the format defined under Components > Report Settings > Thousands Separator.|
|Data Feed: post_product_list column - size change||January 9, 2019||On February 7, 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.|
|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.|
|Dallas FTP server migration (ftp2.omniture.com)||October 19, 2018||On October 23, 2018, if you connect to ftp2.omniture.com via the SFTP protocol, you might be required to re-accept the SJ1 site’s host identifier. This issue applies only to October 23. See Upgrading Adobe FTP Servers.|
|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.|
|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.|
|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 (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. See Migrate Analytics user accounts for Enterprise and Federated IDs.|
|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||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 espectively. (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 Workspace.|
|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.|
|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). Note: This change does not impact reporting in Analysis Workspace or Data Warehouse. If you have data preceding these dates, expect the following: Data will not combine correctly across the pre/post January 2007 boundary. Searches will not work against data before approximately Jan. 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.|
|Update Report Builder before you migrate user IDs to the Admin Console||March 17, 2018||Important: 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.|
|Data retention: Check and set your data retention policy for Adobe Analytics||February 1, 2018||Background: 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. Learn more about the Analytics User ID Migration.|
|IP Address Obfuscation||Your company may desire to obfuscate IP address in many countries due to global privacy regulations. Audience Manager allows you to obfuscate visitor IP addresses on a global or country-by-country basis.|
|Custom Partner Integrations - Oracle Data Cloud||This page lists custom integrations between Audience Manager and data partners. Audience Manager ingests cookie and mobile ID data from the Oracle Data Cloud for Audience Marketplace via inbound data files. The custom integration specifications described in this page refer only to inbound data files that contain mobile IDs (IDFA and Android Device IDs).|
Fixes, Enhancements, and Deprecations
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 6.5, available as of April 8, 2019, is an upgrade release to the AEM 6.4 code base. Our latest updates to AEM 6.5 give you instant access to exciting improvements that drive your business forward even faster.
Cloud Manager 2019.4.0
The latest Cloud Manager release (2019.4.0 released April 18, 2019) adds a localized user interface in French, German, and Japanese. Also, deployment steps were improved.
AEM 6.4, Service Pack 4 (22.214.171.124 released April 04, 2019) is an important update that includes key customer fixes released since the general availability of AEM 6.4, April 2018.
AEM S3 Connector
AEM instances with old versions of S3 Datastore connector may become unavailable due to S3 access failures after the end of support for Signature Version 2 on June 24, 2019. As an AEM customer, Adobe recommends that you verify the version of S3 Datastore connector that you are using. If necessary, update to a recent version.
Modernizing your AEM Sites codebase
Learn how to leverage the latest AEM technology to modernize your AEM Sites codebase. Modernizing Your Existing Adobe Experience Manager Sites Codebase
AEM Rich Text Editor – Deep Dive
Learn best practices around the rich configurations and use of the Rich Text Editor in AEM.
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.
See Adobe Campaign Classic Release Notes for fixes and improvements.
For product documentation, see:
|Search Tools||(Advertisers with Google Ads accounts) Advertising Cloud can optionally upload to Google Ads all conversion data it tracks for Google Ads campaigns that use the Advertising Cloud conversion tracking service. Daily uploads include the conversion value defined using the advertiser-level attribution model. All uploaded conversions are prefixed with “Adobe_ACS_” (such as “Adobe_ACS_Subscriptions” for the conversion “Subscriptions”).
Note: The uploads won’t include conversion data uploaded to Advertising Cloud from feed files.
|Search Campaigns||The menu in Search > Campaigns > Campaigns is now hierarchical, with Campaigns under Accounts; Ad Groups under Campaigns; and Keywords (with submenu), Ads, Product Groups (Live views only), Placements (with submenu), and Auto Targets under Ad Groups.
In the Live views, Audiences and Extensions are at the same level as Accounts, with their own submenus.
This release includes the following features, changes, and enhancements:
(The issue numbers in parentheses are for internal Adobe use.)
|Feature / Enhancement||Description|
|Single Page App Visual Experience Composer (SPA VEC)||The SPA VEC includes the following enhancements to make your work quicker and more efficient:
|Automated Personalization (AP) & Auto-Target activities||You can select an experience to be used as control while creating an AP or Auto-Target activity. This feauture lets you route the entire control traffic to a specific experience, based on the traffic allocation percentage configured in the activity. You can then evaluate the performance of the personalized deliveries against the control experience. (TGT-26572)|
|Recommendations||You can use the Recommend Previously Purchased Items toggle while creating Recently Viewed Items logic. (TGT-34030)|
Refer to the Adobe Target Release Notes for the latest release information about the following products:
Magento is an e-commerce platform that provides online merchants with a flexible shopping cart system and control over the look, content and functionality of their online store. Magento is available in an open-source version and a fuller-featured commerce version.
Magento Commerce is part of Adobe Commerce Cloud and offers an eCommerce solution with enterprise power, unlimited scalability, and open-source flexibility for B2C and B2B experiences
Release notes for both our Open Source and Commerce editions can be found on the Release Information page.
Adobe Primetime is a multiscreen TV platform that helps media companies create and monetize engaging, personalized viewing experiences.