Adobe Experience Cloud Release Notes - October 2018
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.
Latest update: October 12, 2018
- Analytics (Updated October 12, 2018 )
October 11, 2018
New Features in Adobe Analytics
Enhancements and new features released in Adobe Analytics.
Panel dropdown management
We made a few changes to the management of panel dropdowns, which were introduced in the September MR. When you right-click the dropdown, you can now
- Delete a dropdown (this option is always present.)
- Delete a label (if a label is showing.)
- Add a label (if no label is showing.)
Links in panel and visualization tooltips
We have added links to pertinent videos and documentation to panel and visualization tooltips.
The new Analytics API uses the Adobe I/O gateway to make it easy to use alongside any other Adobe APIs. The API extends the same level of customization to the API that customers are accustomed to in Analysis Workspace. It is truly RESTful, making it much easier for developers to interact with the API.
The current scope of this API is reporting-only; the Admin API will continue to use API 1.4 until a future release.
Support for special characters in user names
Experience Cloud logins let you use a number of special characters - Analytics now supports all characters allowed in Experience Cloud user names.
Analytics help resources
Analytics - Fixes and Updates
Fixes and minor updates applied to Adobe Analytics interface tools and components (Analysis Workspace, Reports & Analytics, Report Builder, and so on).
- Fixed an issue with Workspace projects not loading properly. (AN-169531, AN-169486)
- Fixed a performance issue that caused significant delays with opening Workspace projects. (AN-168790)
- Fixed an issue with the Donut visualization that prevented users from editing its label. (AN-168722)
- Fixed an issue with Line Graph visualizations not rendering properly in some situations. (AN-168199)
Other Analytics Issues
- Segmentation : Fixed segmentation issues that caused problems with reporting and with the transfer of assets. (AN-167075, AN-169096, AN-168860, AN-169292)
- Admin : Fixed an issue with errors that occurred when sharing calculated metrics templates. Going forward, you can no longer share those templates. (AN-168655)
- Admin : Fixed an issue that caused problems when using specials character in Analytics user names. Experience Cloud logins let you use a number of special characters. Now Analytics supports all characters allowed in Experience Cloud user names. (AN-168014)
- Admin : Fixed an issue with users getting logged out of Analytics. If you copied and pasted an image from the browser to, Excel (for example) we would log you out as a security precaution. This is no longer the case. (AN-166710)
- Admin : Fixed a post-migration issue around Report Builder permissions. (AN-168329)
- Reports & Analytics : After a data center migration, the shortened URL in dashboard email's Link to Report feature was pre-populated with the wrong login company. No data from that login company was visible or compromised. (AN-166881)
- Reports & Analytics : Fixed an issue with some charts being greyed out in HTML scheduled reports. (AN-168636)
See Data Workbench Release Notes for cumulative release information.
Important Notices for Analytics Administrators
Updated October 12, 2018
Review the following table for important Analytics notices that may affect data collection, processing, APIs, product end-of-life, and so on.
Dallas FTP server migration ( ftp2.omniture.com )
On October 17, 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 17.
End of support for Internet Explorer 11
Adobe will end support for Internet Explorer 11 within Adobe Analytics on November 13, 2018, in accordance with Microsoft's own end of support for this version. Please switch to Microsoft Edge or another supported browser as soon as possible.
Data Feed: post\_product\_list column - size change
In January 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.
End of life for Ad Hoc Analysis
Date added: 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.
End of Support for TLS 1.0
Date added: Sept. 7, 2018
- To minimize customer impact, we are delaying Adobe Analytics Reporting’s end of support for TLS 1.0 encryption. Starting in February, 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. Because the Analytics reporting interface already requires a modern web browser, we do not anticipate issues. If you are unable to connect to Adobe Analytics reporting after February 2019, you should upgrade your browser to the latest version .
- Starting February 2019, 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.
- 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.
- Starting February 2019, Adobe Analytics Data Collection will no longer support TLS 1.0. With this change, we will no longer collect Analytics data from end users with older devices or web browsers that do not support TLS 1.1 or later.Note: If your web site does not support TLS 1.0, you will not be impacted by the collection change.
Update Adobe Report Builder due to end of support for TLS 1.0
Date added: Sept. 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 2019. After that date, prior versions of ARB will no longer function .
New help for the Analytics user migration
Date added: May 10, 2018
We updated the Analytics user ID migration help with information about migrating Enterprise and Federated IDs to the Admin Console.
Upcoming removal of Account Activity Report
Date added: 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
Date added: May 10, 2018
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 respectively. (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
Date added: 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
Date added: 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.
Update Report Builder before you migrate user IDs to the Admin Console
Date added: 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.
See Analytics User Migration to the Admin Console for migration information.
Back-end changes that affect reporting
Date added: 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
Date added: 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
Date added: 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.
Code Manager - Legacy H Code
Date added: February 8, 2018
Data retention: Check and set your data retention policy for Adobe Analytics
Date added: February 1, 2018
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.
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
Date added: 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.
Notice for API Methods affected by the migration to the Admin Console.
Date added: September 21, 2017
Adobe will phase out the Permissions and Company.GetLoginKey API methods as part of our effort to migrate user access and management to the Admin Console.
All Analytics companies that currently use these methods will receive a pre-migration notification beginning March 31, 2018 . After receiving this notification, administrators will have 30 days before their migration starts, and these methods will cease to work for your company.
To prepare for this event, view the list of affected APIs, and learn what Adobe recommends, see Analytics Administration API 1.4 .
Filter segment test groups by status.
You can now filter segment test groups by their status, from the segment test group list. The available statuses are:
This option is also available in the Segment Test Group API , through the groupStatus query parameter.
Fixes, Enhancements, and Deprecations
- Added pagination to the segment test group list page (AAM-39399).
- Fixed an issue causing duplicate segment mappings to be saved in some cases, when clicking the Save button repeatedly in a short time interval (AAM-38687).
- Fixed an issue causing the Identity Management System to incorrectly switch between organization accounts (AAM-40727).
- Fixed an issue causing trait population of segments to be displayed as Undefined or Not Available when switching between Code View and Basic View (AAM-39975).
- Fixed an issue causing the Create and Save buttons in the Create Model section to be displayed incorrectly for accounts with large number of data sources (AAM-38644).
- Added visual loading indicators to the Limits and Profile Merge Rules pages (AAM-39879).
Refer to the Adobe Target Release Notes for the latest release information about the following products:
- Target Standard and Premium
- Recommendations Classic
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 product documentation, see:
- Cloud Manager 2018.7.0This Cloud Manager release provides key improvements around autoscaling, code quality analysis, detailed view of your environments and performance testing. Release Notes .
Adobe Stock integration with AEM
Integration with Adobe Stock gives AEM users the ability to do the following:
- Extend search results to Adobe Stock directly in the AEM user interface.
- Preview Adobe Stock assets.
- Save and license Adobe Stock assets into AEM without leaving the familiar AEM user interface.
Licensed and saved assets become available as regular assets that are managed in AEM.
See the following documentation: https://helpx.adobe.com/experience-manager/6-4/assets/using/aem-assets-adobe-stock.html
- AEM 6.3 Service Pack 3AEM 6.3 SP3 (220.127.116.11), released September 12, 2018, is an important update that includes key customer fixes released since the general availability of AEM 6.3, April 2017.
- AEM 6.4 Service Pack 2AEM 6.4 SP2 (18.104.22.168), released October 3, 2018, is an important update that includes key customer fixes released since the general availability of AEM 6.4, April 2018.
- AEM ScreensTo use Dynamic Embedded Sequence, you assign a channel by Channel Role.Using Dynamic Embedded Sequence lets the user follow a hierarchy where changes and updates made to one channel is propagated to other one in relation. It follows a parent-child hierarchy and also includes assets such as images or videos.
- AEM Cloud ManagerAutoscaling is enabled via horizontal scale-out of Dispatcher/Publish segments on the production environment to support a sudden increase in load, volume, access, and other defined monitored metrics. Follow the Release Notes for 2018.7.0 for more information.
Where do you go to get insights from Adobe Experience Manager Experts on best practices for designing, developing, and deploying digital experiences?
Adobe Systems wants you-our enterprise developers-enabled on the latest version of Adobe Experience Manager. Doing so can help you meet your marketing origination goals to gain and retain customers through digital experiences. We also know that taking time away from the office for training is challenging for many. You have options, however, to learn at your own pace, including where and when it works best for you.
See our calendar of upcoming events , including the following resources:
- Adobe IMMERSEOur annual virtual enterprise developer conference was held in June; the 2018 live sessions are complete. However, you did not miss out! You can still hear helpful tips and tricks, get introduced to aspects of Adobe Experience Manager, and learn about the Adobe Cloud platform.You can purchase your On-Demand Pass for unlimited access to 90+ sessions. Go here and use discount code He7B52 .
- AEM GEMs WebinarsThis webinar series provides an avenue for community experts to learn from Adobe Engineers, Product Managers, and other subject matter experts. Among other things, you learn best practices and tips when working with various aspects of Adobe Experience Manager.Sessions occur each Wednesday, 08:00 Pacific Time/17:00 Central European Summer Time.See upcoming sessions or watch previously recorded sessions here .
- Ask the AEM Community Expert WebinarsThis monthly webinar series provides insights into topics that were recently discussed in our Experience League | AEM HelpX Forum .Sessions occur the last or second to last Tuesday of each month, 08:00 Pacific Time/17:00 Central European Summer Time.See upcoming sessions or watch previously recorded sessions here .Still need help? Join the AEM Community, introduce yourself and post your question here .
Updated: October 11, 2018, for October 13 release
The filter dialog was redesigned to require fewer clicks.
(Google Ads and Bing Ads) The AdWords Audience Target Report was renamed AdWords/Bing Ads Audience Target Report and now includes data for Google Ads remarketing list and in-market audience targets and Bing Ads remarketing list targets. Cost, click,and revenue data are available for remarketing list targets; cost and click data are available for in-market audience targets. Note: Google Ads doesn't provide the means to track revenue data for in-market audiences.
Advertising Cloud help is available in the product under the Help ? menu.