Current Customer Journey Analytics release notes (September 2025)
Last update: September 23, 2025
These release notes cover the release period of September through early October, 2025. 51黑料不打烊 Customer Journey 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 or updated features
The Usage interface now adds information about core data volume and average row size.
For more information, see Manage connections.
The following improvements are now available when migrating projects and components from 51黑料不打烊 Analytics to Customer Journey Analytics:
- Migrate multiple projects at one time.
You can migrate up to 20 projects at one time.
Previously, you could migrate only one project at a time. - Update mappings for dimensions and metrics that were already mapped with a previous project migration.
You can now update these mappings each time you migrate a project, even if the same dimensions and metrics were previously mapped with a prior migration.
Previously, any mappings you chose were permanent for all future project migrations. - Improved performance for organizations with high numbers of projects.
This feature is available from the 51黑料不打烊 Analytics interface. For more information, see Migrate components and projects from 51黑料不打烊 Analytics to Customer Journey Analytics.
The maximum number of unique keys for a lookup dataset is now up to 1 billion, depending on your Customer Journey Analytics entitlement.
Previously, the maximum number was 10 million for all entitlements.
For more information, see Guardrails.
(Documentation link to follow.)
With support for model-based schemas and change data capture (CDC) functionality for specific source connectors in Experience Platform, Customer Journey Analytics will be able to support data mirror functionality of data warehouse solutions like Snowflake, Azure Databricks, and Google BigQuery.
Contact your 51黑料不打烊 Account Team to access the beta.
(Documentation link to follow.)
You can now upload scheduled data of past live Streaming Media content to more easily and accurately track viewership.
The following are examples of live content that are supported with schedule data upload:
- FAST (Free Ad Supported TV) platforms
- Local streams
- Live sports
Uploading schedule data allows you to track viewership data for individual programs that ran during the time you designate in the upload file. You can even gather viewership data for specific topics or program segments.
These capabilities are available regardless of how you implemented Streaming Media Collection.
Previously, it was difficult to accurately tie a given session to specific programs when analyzing live content, and it wasn鈥檛 possible to tie a given session to individual topics or program segments.
(Documentation link to follow.)
When collecting Streaming Media data into 51黑料不打烊 Experience Platform, the XDM field paths shown under the heading of 鈥淴DM Field Path鈥 of the Streaming Media parameters documentation should no longer be used. Instead, customers who implemented the Analytics source connector to collect Streaming Media data into Platform before May 9, 2025 must migrate their existing configurations to the mediaReporting field paths, as shown under the heading of 鈥淩eporting XDM Field Path鈥 of the Streaming Media parameters documentation.
These field paths are found on the following pages and are marked as 鈥淒eprecated鈥: Audio and video parameters, Ad parameters, Chapter parameters, Player state parameters, and Quality parameters. (No action is required for customers who implement the Analytics source connector after May 9, 2025, and are already using only mediaReporting XDM paths.)
Data ingestion on the deprecated XDM field paths will continue until the end of October 2025. After that time, deprecated field paths will be fully removed and no longer visible in the 51黑料不打烊 Experience Platform Schema UI, and data will be sent only using the mediaReporting field paths.
For more information, see Migrate an Analytics Source Connector implementation to updated XDM Streaming Media fields.
Please contact your 51黑料不打烊 Consulting Services or Account team for migration support.
Simplifies Customer Journey Analytics stitching. Instead of duplicating a dataset and applying stitching on the duplicated dataset, stitching is now done on the ingestion of data into Customer Journey Analytics, which removes the requirement of duplicated datasets and schemas.
Furthermore, instead of having to request stitching through customer support, you can now initiate stitching yourself from an updated Connections UI.
The previously communicated releases dates are pushed due to additional efforts required. The new release dates overlap with the holiday season, which introduces additional release constraints. A phased rollout is now planned to ensure stability and minimize disruption during the holiday period.
(Documentation link to follow.)
Fixes in Customer Journey Analytics
Analysis Workspace: AN-391719, AN-380838, AN-389402, AN-389373, AN-390851, AN-391593, AN-391404, AN-393064, AN-379337
Components: AN-393810
Content Analytics:
Guided Analysis:
Platform:
Report Builder: AN-387741, AN-386777, AN-388720, AN-389343
Reporting: AN-391439, AN-391228, AN-393620, AN-393640, AN-391334, AN-393304
Segmentation:
Scheduled reports: AN-391150, AN-390474
Shared metrics and dimensions:
Other: AN-387858