Current Adobe Analytics release notes (April 2024)

Last update: April 17, 2024

These release notes cover the release period of April 17, 2024 through May. Adobe Analytics releases operate on a continuous delivery model which allows for a more scalable, phased approach to feature deployment. Accordingly, these release notes get updated several times a month. Please check them regularly.

New features or enhancements features

Feature
Description
Rollout starts
General Availability
Streaming Media: Send Roku data to Adobe Experience Platform Edge Network
Now when installing Media Analytics with Experience Platform Edge, you can use the Adobe Experience Platform Roku SDK to send Streaming Media data to Adobe Experience Platform.
April 12, 2024
Improved workflow for Web SDK migration

Datastreams now automatically map fields from the Web SDK data object straight to Adobe Analytics. Data object mapping is similar to XDM object mapping, but does not require an XDM schema. This improved workflow provides the following benefits:

  • It delays the requirement to use a schema until you are ready to send data to Adobe Experience Platform. If a schema was required at this stage of an implementation migration, you would be forced to use a schema based on Adobe Analytics fields. Adobe Experience Platform services, such as Customer Journey Analytics, don’t have a concept of props or eVars. An Analytics-focused schema can introduce difficulties if your organization wants to use its own schema in the future.
  • After making implementation changes to the Web SDK, your organization is in a better position to migrate from Adobe Analytics to Customer Journey Analytics. If you send data to Adobe Analytics using the Web SDK, you do not need to make additional implementation changes to send data to Adobe Experience Platform. Instead, you can use data prep to map data object fields to your XDM schema.

See Migrate from the Adobe Analytics tag extension to the Web SDK tag extension and Migrate from AppMeasurement to the Web SDK for more information.

April 2024
Permissions enhancement for project-only Workspace components
Previously, if a user (User A) shared a project with another user (User B), and gave User B edit access to the project, User B would be able to edit the project. However, User B would not be able to edit Quick Segments embedded in the project. That limitation is now removed - User B can edit Quick Segments and other project-only components that are embedded in the shared project.
April 17, 2024
Use the same cloud accounts for Data Feeds, Data Warehouse, and Classification sets

Cloud accounts and locations that you create can now be used for exporting data (with Data Feeds and Data Warehouse) and importing data (with Classification sets).

Changes when configuring accounts: Users can Configure cloud import and export accounts and Configure cloud import and export locations that can be used for any of the following purposes:

  • Importing data with Classification sets
  • Exporting data with Data Feeds
  • Exporting data with Data Warehouse.

Changes when managing accounts and locations from the Locations page: Users can use the Locations page (under Components > Locations) to view and manage all the accounts and locations that they create, regardless of where they were created.

Previously, the Locations page applied only to accounts that were created for importing data with Classification sets.

Changes when managing locations from Data Warehouse or Classification sets

When managing locations within a given application area (Data Warehouse or Classification sets), only the locations that were created in that specific application area are available. For example, when viewing the Data Warehouse application area, only Data Warehouse locations are available. All accounts are still available in each application area, regardless of the application area where they were created. Previously, all accounts and locations were available in each application area, regardless of the application area where they were created. This is still true when viewing the Data Feeds application area.

April 17, 2024
Administrators can manage all locations and accounts in their organization

A new option on the Locations tab (on the Components > Locations page) allows Administrators to view and manage all locations in the organization.

A new option on the Location accounts tab (on the Components > Locations page) allows Administrators to view and manage all accounts in the organization.

Previously, administrators could view and manage only the locations and accounts that they created.

April 17, 2024
Increase in default low-traffic thresholds

In mid April 2024, Adobe will begin increasing the default report suite low-traffic thresholds as follows: low-traffic thresholds This will impact only variables which are currently set below the new thresholds. These changes will be made incrementally, and we expect the work to be complete by the end of May. As these increases are rolled out, you may notice changes for high-cardinality variables:

  • More dimension values may be available for reporting.
  • Segments and calculated metrics may include more data.
  • Virtual report suites based on segments may include more data.
  • Classification exports may include more data.
Mid April, 2024
May 31, 2024
Activity Map uses fewer server calls for Web SDK

Currently, Activity Map link events are counted as their own events and incur extra cost.

This enhancement takes some link events and packages them into the next hit, similar to how events are handled by AppMeasurement.

May 31, 2024

Fixes in Adobe Analytics

  • Fixed the following Classifications issues: AN-343439; AN-343503; AN-343504; AN-343986; AN-344262; AN-344564; AN-345204; AN-345234
  • Fixed the following Classifications Rule Builder issues: AN-341488; AN-342501; AN-345751
  • Fixed the following Intelligent Alerts issue: AN-343466;
  • Fixed the following Segmentation issue: AN-342313
  • Fixed the following Data Warehouse issue: AN-344292
  • Fixed the following Data Feeds issues: AN-339545; AN-340092; AN-342124; AN-342862; AN-343737; AN-344035; AN-344329; AN-344703; AN-344721; AN-344940; AN-345180; AN-345196; AN-345225; AN-345236; AN-345326; AN-345631; AN-345659
  • Fixed the following Data Sources issue: AN-343541
  • Fixed the following Analysis Workspace issues: AN-336303; AN-336472; AN-338422; AN-338556; AN-339718; AN-340147; AN-340301; AN-340421; AN-340951; AN-341172; AN-342905; AN-342909; AN-343448; AN-343570; AN-344050; AN-344182; AN-344763; AN-344768;
  • Fixed the following Analytics Admin issues: AN-342519; AN-342523; AN-343623; AN-343882; AN-344237; AN-344829; AN-345235;
  • Fixed the following A4T issues: AN-341619; AN-344402
  • Fixed the following Mobile App issue: AN-342010

Other Analytics fixes

AN-336099; AN-337474; AN-337993; AN-339718; AN-339901; AN-340014; AN-341356; AN-343021; AN-343102; AN-343353; AN-343416; AN-340014; AN-344037; AN-344525; AN-345737

Important notices for Adobe Analytics administrators admin

Notice
Date Added or Updated
Description
13-month expiration of saved cust_visids
March 20, 2024
An upcoming release of the Analytics Hit processing engine, targeted for April or May, will start enforcing a 13-month expiration of saved cust_visids. If the report suite has “Enable Visitor Stitching” enabled, this setting is used for finding the cust_visid for a visid_high/visid_low value with no cust_visid on the hit. Currently, there is no expiration of the mapping of a cust_visid for a visid_high/visid_low. With this release, if 13 months or more have passed since visid_high/visid_low has had a cust_visid on a hit, the mapping will expire.
Adobe API object member additions
January 17, 2024
Adobe may add optional request and response members (name/value pairs) to existing API objects at any time and without notice or changes in versioning. Adobe recommends that you refer to the API documentation of any third-party tool you integrate with our APIs so that such additions are ignored in processing, if not understood. If implemented properly, such additions are non-breaking changes for your implementation. Adobe will not remove parameters or add required parameters without first providing standard notification through release notes.

End-of-life (EOL) notices eol

EOL Product or Feature
Date added or updated
Description
Migration to Adobe I/O OAuth Server-to-Server credentials
May 11, 2023

Adobe Analytics API and Livestream customers using Adobe I/O JWT credentials must migrate to Adobe I/O OAuth Server-to-Server credentials by January 1, 2025. Adobe I/O will not allow new JWT credentials to be created beginning May 1, 2024. Customers using JWT must create a new OAuth Server-to-Server credential or migrate their existing JWT credential to an OAuth Server-to-Server credential. Customers must also update their client applications to use the new OAuth Server-to-Server credentials.

AppMeasurement

For the latest updates on AppMeasurement releases (Version 2.26.0), please refer to AppMeasurement for JavaScript release notes.

recommendation-more-help
69b719ed-622a-4df7-a307-14caa7222de3