۶Ƶ

2025 ۶Ƶ Analytics release notes

Learn about the latest release updates for . Get the latest self-help documentation, tutorials, and courses on Experience League.

March 2025 mar25

Feature
Description
Rollout starts
General Availability
Analytics inventory
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
Update to Analytics context data field a.locale

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
Customer Journey Analytics upgrade guide

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
Data Warehouse-only dimensions

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

Fixes in ۶Ƶ Analytics

Activity Map: AN-361038
Admin Tools: AN-362178; AN-369483
Analytics API 1.4: AN-369615
Analysis Workspace: AN-353491; AN-363403; AN-367230; AN-367313; AN-368582; AN-369821; AN-370227;
Classifications: AN-369848; AN-370196; AN-370226; AN-370437
Data Feeds: AN-366162; AN-368906; AN-369066; AN-369087; AN-369225; AN-369798
Data Governance: AN-365157
Data Sources: AN-367550
Platform: AN-363931
Report Builder: AN-367460; AN-368975

Important notices for ۶Ƶ Analytics administrators

Notice
Date Added or Updated
Description
N/A

End-of-life (EOL) notices

EOL Product or Feature
Date added or updated
Description
Migration to ۶Ƶ I/O OAuth Server-to-Server credentials
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.

EOL for ۶Ƶ Analytics API (version 1.4)
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.

AppMeasurement

For the latest updates on AppMeasurement releases, please refer to .

February 2025 feb25

Feature
Description
Rollout starts
General Availability
Transaction ID retention period
The Transaction ID retention period of 90 days was extended to 25 months. The transactionID variable uniquely identifies a transaction so the hit can tie to data uploaded through Data Sources. Learn more here and here.
February 20, 2025
Data Feeds API reference
The for the Data Feeds API is now available.
January 30, 2025
Livestream API - Client implementation
Use the Livestream client implementation to consume Livestream data.
February 18, 2025
Update to Classifications API
You can now remove individual classification fields or keys from the server. This provides an alternative to deleting an entire classification dataset with the DELETE method.
February 18, 2025
Update to Analytics context data field a.locale

A scheduled update will change 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 will take precedence. You can view the full list of mappings from XDM to standard Analytics fields here.

March 5, 2025

Fixes in ۶Ƶ Analytics

Analysis Workspace: AN-359974; AN-366212; AN-368460
Classifications: AN-367186; AN-367328; AN-368548
Component Migration: AN-364529; AN-366398; AN-367509;
Data Feeds: AN-365685; AN-366745; AN-367256; AN-367349; AN-368363
Data Warehouse: AN-368178; AN-368331;
Mobile App: AN-367137
Platform: AN-351924; AN-365540; AN-365866; AN-366898; AN-367856; AN-367933
Report Builder: AN-366456; AN-366655;
Virtual Report Suites: AN-367411
VISTA rules: AN-365331

Important notices for ۶Ƶ Analytics administrators admin

Notice
Date Added or Updated
Description
Non-Campaign customers will lose access to Triggers
October 16, 2023
On January 30, 2025, ۶Ƶ Analytics customers that do not have an ۶Ƶ Campaign license lost access to the ability to configure and consume Triggers. Customers need to either purchase Campaign, or plan to stop using Triggers, or look into other ۶Ƶ tools that offer Triggers capabilities.

End-of-life (EOL) notices

EOL Product or Feature
Date added or updated
Description
Migration to ۶Ƶ I/O OAuth Server-to-Server credentials
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.

EOL for ۶Ƶ Analytics API (version 1.4)
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.

AppMeasurement

For the latest updates on AppMeasurement releases, please refer to .

January 2025 jan25

Feature
Description
Rollout starts
General Availability
Scheduling in the new Report Builder
Scheduling not only allows you to schedule your new Report Builder workbooks. In addition, it lets you retrieve the metadata on old scheduled tasks when you convert legacy workbooks. This way, when you convert your legacy workbooks to new workbooks and schedule them, you are sending them to the same emails and on the same cadence as the legacy workbooks. Learn more
January 22, 2025
Improvements to Reports (also known as Templates) in Analysis Workspace

Various improvements are now available for Reports (also known as Templates):

  • Now called Templates (no longer referred to as Reports).
  • Improved user experience for viewing and finding templates, including the option to view templates in a column view or a card view.
  • New, more intuitive location for Company templates (located under Workspace > Templates).
  • Previously, company templates were accessed from the dialog box when creating a project.
  • Additional pre-built templates are available.

Learn more.

Administrators can create templates and save them for others in their login company to use. Learn more

January 15, 2025
January 30, 2025
Transaction ID retention period
The Transaction ID retention period of 90 days will be extended to 25 months in February of 2025. The transactionID variable uniquely identifies a transaction so the hit can tie to data uploaded through Data Sources. (Documentation links to follow)
February 11, 2025

Fixes in ۶Ƶ Analytics

A4T: AN-355602; AN-365988
Activity Map: AN-365320
Admin Console: AN-363884
Admin Tools: AN-356747; AN-358776
Advertising Analytics: AN-355488
Analysis Workspace: AN-345318; AN-354801; AN-357052; AN-358975; AN-362886; AN-363831; AN-364124; AN-365257; AN-365319; AN-365462; AN-366194
Analytics 1.4 API: AN-358059
Classifications: AN-360049; AN-360424; AN-360745; AN-362208; AN-362345; AN-362560; AN-362576; AN-362633; AN-362653; AN-362762; AN-362815; AN-362881; AN-362885; AN-362973; AN-363343; AN-363558; AN-363860; AN-364239; AN-364480; AN-364451; AN-364528; AN-364548; AN-364552; AN-364585; AN-364598; AN-364643; AN-364715; AN-364912; AN-364997; AN-365081; AN-365189; AN-365197; AN-365203; AN-365431; AN-365647; AN-365794; AN-366546
Component Migration: AN-362236; AN-365429
Contribution Analysis: AN-360146
Data Feeds: AN-356997; AN-362470; AN-362498; AN-362775; AN-363323; AN-363413; AN-363569; AN-364063; AN-364142; AN-364294; AN-364298; AN-364325; AN-364367; AN-364594; AN-364995; AN-365127; AN-365272; AN-365519; AN-365760; AN-366152;
Data Repair API: AN-362773; AN-362874
Data Sources: AN-360745; AN-362202; AN-364566
Data Warehouse: AN-361447; AN-362616; AN-364524; AN-365108
Mobile App: AN-362856; AN-365270
Overage Alerts: AN-355594; AN-364547
Platform: AN-358914; AN-360205; AN-362990; AN-364550; AN-365454; AN-365485
Report Builder: AN-363478; AN-364433; AN-365610
Reporting Activity Manager: AN-362440
Segmentation: AN-359921
VISTA rules: AN-362927

Important notices for ۶Ƶ Analytics administrators

Notice
Date Added or Updated
Description
Non-Campaign customers will lose access to Triggers
October 16, 2023
On January 30, 2025, ۶Ƶ Analytics customers that do not have an ۶Ƶ Campaign license lost access to the ability to configure and consume Triggers. Customers need to either purchase Campaign, or plan to stop using Triggers, or look into other ۶Ƶ tools that offer Triggers capabilities.

End-of-life (EOL) notices

EOL Product or Feature
Date added or updated
Description
Migration to ۶Ƶ I/O OAuth Server-to-Server credentials
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.

EOL for ۶Ƶ Analytics API (version 1.4)
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.

AppMeasurement

For the latest updates on AppMeasurement releases, please refer to .

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