Show Menu
TOPICS×

Release Notes - June 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.

Experience Cloud and Core Services

Release notes for the Experience Cloud interface and core services. Includes Mobile Services, Launch, by Adobe, Dynamic Tag Management, GDPR API, and Experience Cloud ID Service.

Experience Cloud Interface

New features and fixes in the Adobe Experience Cloud interface, including Assets, Feed, Notifications, and the People core service.
Fixes
  • Enabled a link to GDPR access for Administrators. (CORE-11731)
  • Updated Beta Feedback feature to restrict file types that can be attached to feedback. (CORE-10474)
  • Fixed an issue with deleting audiences from Audience Library. (CORE-12792)
  • Fixed an issue that resulted in a blank screen while accessing Workspace links using Federated IDs. (CORE-11620)

Experience Cloud ID Service

Visitor API 3.0 or higher is required for customers using the Experience Cloud ID Service. Adobe recommends upgrading to the latest Visitor API version whenever associated code libraries are updated ( at.js, AppMeasurement.js, and so forth.)
See Experience Cloud ID Services product documentation.

Launch, by Adobe

Launch release notes are updated regularly at https://docs.adobelaunch.com/getting-started/release-notes .

Experience Cloud Mobile SDKs

Fixes in Version 4.16.0
  • Added a new API that will return a string that contains Visitor ID Service-related URL variables . (iOS - AMSDK-6246 and Android - AMSDK-6247)
  • At privacy opt-out, a request is now sent to Audience Manager to remove the user from all activation and reporting. (iOS - AMSDK-6249 and Android - AMSDK-6252)

Analytics

Release date: June 14, 2018

New Features in Adobe Analytics

Enhancements and new features released in Adobe Analytics.
Product Feature Name Description
Analysis Workspace
Previously, when a dimension was dropped on a column, we showed the top 5 values for non-time dimensions (and 15 for time dimensions) and kept those values static (i.e., the 5 values picked never changed).
From now on, by default, we show dynamic values instead of static ones, with the option to turn them into static values. Other things to note:
  • Click (i) on dynamic dimension and you will see the ranking (top 1 of 5) and dimension type.
  • As your data updates, the dynamic dimension columns will update to show the current 5/15 dimension items.
  • A dynamic dimension column that is copied or moved will become static.
  • When hovering a static dimension column you will see a lock icon, indicating that the dimension is static.
New Workspace Features modal
Similar to the Tips of the Day introduced last month, this modal shows new Workspace features the first time you log in to Workspace after a new release.
Adobe Analytics Admin
Analytics usage logs now track when someone opens a project in Analysis Workspace (in addition to the existing tracking of create, update, unshare and delete actions.) This allows for better visibility into who is using Workspace, and how often.
Transfer Assets now allows for the transfer of scheduled projects to another user.
Adobe Analytics Components and Tools
Two rule options were added to the Alert Builder that offer you a choice to be notified of either only higher or only lower anomalies (but not both).
Segment Builder + Alert Builder: Incompatible Components
When defining a segment or an alert, an “ incompatible components” message will appear if not all the components (metrics/dimensions/segments) in the segment or alert are compatible with the currently selected report suite.

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).
Product Fix or Update
Analysis Workspace
  • Fixed an issue that occurred when Freeform panels were not loading due to too many columns. We now display an error message indicating the reason for the error. (AN-162360)
  • Fixed an issue that occurred when setting a project as a group of users’ landing page. (AN-162291)
  • Fixed an issue with Locked Selection not working (in some situations) for Selected Positions in an Area Stacked visualization. (AN-162213)
  • Fixed an issue that caused (in some situations) percentages to change unaccountably in the Summary Changes visualization. (AN-161364)
  • Fixed an issue with the “Percent Change” calculated metric sometimes not working properly when creating a metric from a selection. (AN-161356)
  • Fixed an issue that occurred when changing the date range for a panel and the date range for the 2nd- and 3rd-level breakdowns in that panel not changing. (AN-160019)
  • Fixed a localization issue that caused metrics labels to display in English instead of the localized language. (AN-156651)
Other Analytics Issues
  • Fixed an issue that prevented a user deletion from showing up in the audit log. We are now showing Company Change events as part of the Admin Console. (AN-161461)
  • Fixed a Segment Builder issue where an inner container could not be moved out of its parent container. (AN-162497)
  • Fixed an issue that caused Data Warehouse-specific dimensions to disappear from the Segment Builder. (AN-162359)
  • Fixed an issue with some old classifications permissions (such as Classification Importer and Classification Rule Builder) still working - they are now disabled. (AN-159451)
  • Fixed an issue that caused Analytics for [!DNL Target] classifications to show “unknown” values when switching report suites. (AN-156702)
  • Fixed an issue with incorrect User IDs getting logged in access logs. (AN-162176)
  • Fixed an issue with creating segments that included rules based on metrics with decimal points. The segment builder rounded the decimal points off and did not include decimal points. (AN-162520)
  • Fixed an issue with Analytics segments not publishing properly to [!DNL Audience Manager]. (AN-162536)
  • Fixed issues with some Java 8x/7x versions not being compatible with the latest Ad Hoc Analysis JNLP file. (AN-162401)
  • Fixed an issue that occurred when transferring assets from the new User Management interface - if the user whose assets were transferred had alerts, those alerts were not displayed. (AN-160674)
  • Fixed an issue with being unable to log in to Analytics. (AN-160959)
  • Web Services: Fixed a reported error in API when Channel value type is set to evar (AN-159233)
  • Web Services: Fixed an issue with variable updating in ReportSuite.SaveClassification API method. (AN-159389)
Data Workbench

Analytics - Developer, Administration, Data Collection, and Implementation

Fixes and updates applied to Analytics administration tools, including implementation and developer (Web Services and SDKs).
Fixes
Product / Feature Update
OAuth Revokation
An endpoint was added to the API Gateway that allows Analytics clients to revoke OAuth access tokens and refresh tokens per the standard defined here: https://tools.ietf.org/html/rfc7009
See Adding revokation endpoint for documentation.
AppMeasurement (Legacy and Mobile SDKs)
AppMeasurement for JavaScript
Note: Visitor API 3.0 or higher is required for customers using the Experience Cloud ID Service. Adobe recommends upgrading to the latest Visitor API version whenever associated code libraries are updated ( at.js , AppMeasurement.js , and so forth.)
AppMeasurement for Other Platforms
See AppMeasurement Release History the following 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

Important Notices for Analytics Administrators

Review the following table for important Analytics notices that may affect data collection, processing, APIs, product end-of-life, and so on.
Notice Date Added or Updated Description
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.
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.
Update Adobe Report Builder due to end of support for TLS 1.0
May 10, 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 September 13, 2018. After that date, prior versions of ARB will not be supported.
Changes to linear allocation models in Calculated Metrics
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.
Ad Hoc Analysis
April 12, 2018
As of July 2018, Ad Hoc Analysis will support only Java 8 or higher. Due to security fixes not supported in older versions of Java, we will reject connections from Java 7 and will no longer provide access to versions that run on Java 7.
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.
Ad Hoc Analysis: Changes to JNLP file
May 8, 2018
Changes were made to the Ad Hoc Analysis JNLP file that require you to download a new version of this file with the May Maintenance Release. Failure to do so will result in a Java error when starting Ad Hoc Analysis, and will prevent you from launching the application.
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.
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.
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 [!UICONTROL 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.
End of Support for TLS 1.0
May 4, 2018
  • Starting July 19, 2018, 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 July 19, you should upgrade your browser to the latest version .
  • Starting September 13, 2018, 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 September 13, 2018, 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.
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.
Code Manager - Legacy H Code
February 8, 2018
Downloading legacy JavaScript (H code) from the Code Manager is no longer supported.
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.
Notice for API Methods affected by the migration to the Admin Console.
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 .
Bot Rules
Sept. 21, 2017
We recommend defining no more than 500 bot rules per report suite.
The user interface allows for 500 rules to be manually defined. After this limit is reached, rules need to be managed in bulk through the Import File and Export Bot Rules options.
Calendar Events: Displaying top 20 most recent events
September 21, 2017
To ensure optimal reporting performance, the 20 most recent calendar events will be displayed on trended and overtime graphs.
geo_zip
August 23, 2017
As of August 22, Adobe Analytics started determining geo_zip on all hits received during data collection. This update increases data accuracy, particularly for mobile devices. Previously, the geo_zip was set once per visit. Now, geo_zip can correctly change during a visitor's visit. The geo_zip field is not used in reporting, but surfaces in Data Feeds.
Geo Segmentation
August 21, 2017
On August 22, Adobe Analytics enabled Geo Segmentation reports for all customers. This change is in anticipation of the upcoming removal of the geo segmentation settings in the Admin Console.

Audience Manager

Item Description
In June 2018, Adobe is deprecating support for the TLS 1.0 protocol. Adobe Audience Manager functionality will not work for your end users that use browsers which only support TLS 1.0. We have collected for you a list of browsers, versions, and TLS support.
Fixes, Enhancements, and Deprecations
  • The Audience Manager User Interface moves to a top-level site navigation, replacing the left sidebar navigation you were used to. We hope you'll enjoy the extra space.
  • This release includes an API optimization. Customers were experiencing latency with the get_children method in the Folders API. (AAM-37237)
  • We fixed a bug in Segment Builder where the information modal would return an incorrect status for expression validity. For example, for incorrect expressions, the modal would show "Success" and for correct expressions, the modal would read "Error". (AAM-36980)

Target

Refer to the Adobe Target Release Notes for the latest release information about the following products:
  • Target Standard and Premium
  • Recommendations Classic

Primetime

Adobe Primetime is a multiscreen TV platform that helps media companies create and monetize engaging, personalized viewing experiences.

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.
For product documentation, see:

Experience Manager

AEM release notes

Adobe recommends customers with on-premise deployments to deploy the latest patches to ensure higher stability, security, and performance.
Title Description
Product releases
AEM Desktop App 1.9
Improved user experience with resumable uploads, better indication of the status of background operations, and pre-fetching of linked files (for InDesign assets, for example).
Cloud Manager
Cloud Manager, part of Adobe Managed Cloud Services, lets organizations self-manage Experience Manager in the cloud. It includes a continuous integration and continuous delivery (CI/CD) framework. This framework lets IT teams and implementation partners speed the delivery of customizations or updates, and improve production availability by enforcing quality gates as part of every custom code deployment.
Find more details in the Cloud Manager documentation .
Product maintenance
AEM 6.3 Service Pack 2-Cumulative Fix Pack 1
AEM 6.3 SP2-CFP1 (6.3.2.1), released May 10, 2018, is an important update that includes key customer fixes released since the general availability AEM 6.3, April 2017.
AEM 6.3 Feature Pack 22818
This Feature Pack delivers updates to Content Fragments, the JSON Exporter, and Core Components, to achieve feature parity with AEM 6.4.
GDPR Readiness
Documentation for GDPR Readiness with AEM.
Analytics Activity Map Updates
Activity Map functionality for published pages as part of the page editor.
Self-Help
AEM Maintenance Roadmap
Cloud Manager Documentation
GDPR Readiness
GDPR Readiness with AEM documentation is available.
Package Validation Updates
Updated How to Work With Packages documentation with more details about the new package validation feature including the ability to validate ACLs.
Community
Adobe IMMERSE
Adobe IMMERSE June 12-15, 2018 is the annual global conference for developers who build solutions on Adobe Experience Manager.
Adobe IMMERSE also has additional sessions this year on Adobe Cloud Platform, Adobe I/O, Adobe Sensei, ColdFusion, and FrameMaker. Register and use discount code He7B52 to get your ticket for $15.00 and unlimited access to 90+ sessions live and on-demand.
Need help getting approval to attend? Download the IMMERSE'18 Justification Letter here . Edit the letter based on your situation, then send it to your boss.
Local User Groups
Check out the Adobe Experience Manager / Adobe Cloud User Groups here ; make sure you join our virtual group to get access to upcoming webinars and news here .
AEM GEMS Webinars
AEM GEMS on-demand sessions are available here . There are more than 70 in-depth how to sessions on best practices and new innovations from Adobe.
Ask the AEM Community Expert on-demand sessions are available here . Get in-depth on topics discussed in the Experience League and the HelpX Forum from Adobe and the greater community experts.

Advertising Cloud

Updated: June 6, 2018, for June 9 release
Feature Description
Integration with Adobe Analytics
You can now create Google AdWords remarketing lists (RLSAs) from shared Analytics segments. Previously, the advertiser also had to have Adobe Audience Manager . To be eligible, an advertiser must implement the Adobe Experience Cloud ID service, provide its IMS Org ID, and deploy a tag on its websites.
Search Bulksheets
(Google AdWords accounts) Bulksheets now support remarketing list (RLSA) targets for campaigns.
The Download Bulksheet dialog for AdWords campaigns includes the optional entity section "Campaign RLSA Target," with the fields "Campaign Name," "Bid Adjustment," "Ad Group Name," "Audience," "Target Type" (with the value inclusion ), "RLSA Target Status" and "Adobe Rec Bid Adjustment."
Search Campaigns
The Keywords view now has two sub-views: Keywords and Negatives. The Negatives sub-view allows you to create and delete campaign-level and ad group-level negative keywords.
You can now edit and delete custom metrics from your default and custom views and from the column configuration settings.
You can now drag and drop columns in your custom and default views. To save your changes, you must save the view.
Constraints Beta
You can now create and edit incremental bidding constraints.
Advertising Cloud help is available in the product under the Help ? menu.