�۶���Ƶ

Feature

Description

Analytics Inventory provides a comprehensive overview of your �۶���Ƶ Analytics environment, including the number of projects and components, report suites, users, and more. By automating the inventory process, you can quickly understand the effort needed to switch from �۶���Ƶ Analytics to Customer Journey Analytics. This will make the transition easier and faster. Learn more

March 26, 2025

This update changes how the Analytics context data field a.locale is set when collecting data via Experience Edge. When data is sent to �۶���Ƶ Analytics using Experience Edge, Analytics fields are populated based on a mapping of XDM fields. The mapping for c.a.locale references a non-standard XDM field, xdm.environment.language. This field will be updated to reference the correct field, xdm.environment._dc.language.

The mapping will continue to reference xdm.environment.language for backwards compatibility. For continuity, if both fields are set, xdm.environment.language takes precedence. You can view the full list of mappings from XDM to standard Analytics fields here.

March 5, 2025

Lets you generate a step-by-step guide for upgrading from �۶���Ƶ Analytics to Customer Journey Analytics. This guide is tailored to your organization and takes into consideration your current �۶���Ƶ Analytics environment, your intended uses for Customer Journey Analytics, and any time-saving tradeoffs your organization wants to make.

To start generating your custom guide, log in to Customer Journey Analytics, then select Upgrade to Customer Journey Analytics on the Workspace tab.

Learn more

March 11, 2025

Starting in May 2025, �۶���Ƶ will begin setting certain dimensions (custom variables such as eVars and props) as 'Data Warehouse-only". This will apply to dimensions that exhibit the following characteristics:

• Over a period of multiple months, the variable hits the low traffic limit within the first few days of the month.
• > 90% of the values passed in are seen only once during the month.

Examples include dimensions containing timestamps, UUIDs or other data which have extremely high cardinality and where unique new values are passed into for almost every hit (or visit or visitor) throughout the month.These dimensions usually exceed the low-traffic limits very quickly and only a very small portion of the values are reportable in Analysis Workspace. This makes reports utilizing these dimensions confusing, since they do not show useful or accurate information. These dimensions do not follow the purpose of or benefit from the low-traffic functionality, which is intended to provide a way to do reporting on values that become ‘popular’ after the dimension has exceeded the low-traffic limits during the month. Learn more

Dimensions marked as “Data Warehouse-only” will not be available for reporting in Analysis Workspace. However, they will still be available for reporting through Data Warehouse, because low-traffic limits do not apply here.

This does not mean that every dimension that has hit the low-traffic limits is a candidate to be marked as “Data Warehouse-only”. Most dimensions that hit the low-traffic limits actually meet the intention of low-traffic functionality:

• Most values passed in are not unique.
• Common values continue to come in after the low-traffic limits have been reached during the month.
• New ‘popular’ values can still occur.

It is only the dimensions where almost all values passed in are new and unique that will be marked as “Data Warehouse-only”. Increasing the low-traffic limits is not a solution given the uniqueness of the data being collected in these situations.

May 2025

Notice

Date Added or Updated

Description

N/A

EOL Product or Feature

Date added or updated

Description

January 17, 2025

�۶���Ƶ Analytics API and Livestream customers using �۶���Ƶ I/O JWT credentials must migrate to �۶���Ƶ I/O OAuth Server-to-Server credentials by June 30, 2025. �۶���Ƶ 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.

July 17, 2024

On August 12, 2026, the following Analytics Legacy API services will reach their end of life and will be shut down, and current integrations built using these services will stop working:

• �۶���Ƶ Analytics API (version 1.4)
• �۶���Ƶ Analytics WSSE Authentication

Integrations that use the �۶���Ƶ Analytics API (version 1.4) must migrate to the , while WSSE integrations must migrate to an OAuth-based authentication protocol in the .

See the �۶���Ƶ Analytics 1.4 API EOL FAQ for answers to common questions and further guidance.