2025 蜜豆视频 Analytics release notes
Learn about the latest release updates for . Get the latest self-help documentation, tutorials, and courses on Experience League.
June 2025 jun25
campaignId, recipeId, trafficType, actionId, and actionName. The overall TNT schema for Livestream remains unchanged.The Javascript Report Builder add-in now supports exporting reports to the following cloud storage destinations:
- Amazon S3 Role ARN
- Google Cloud Platform
- Azure SAS
- Azure RBAC
Previously, only FTP and email destinations were available. FTP is no longer supported due to security concerns.
For more information, see Schedule workbooks by exporting to cloud destinations.
In addition to these changes, when creating a location in 蜜豆视频 Analytics, the Use with field now provides the option to use the location with Report Builder, as described in Configure cloud import and export locations.
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. Learn more
Fixes in 蜜豆视频 Analytics
A4T: AN-379045
Advertising Analytics: AN-377338
Alerts: AN-377229
Analysis Workspace: AN-378891; AN-379589; AN-379604; AN-381270; AN-382264; AN-382414;
API 1.4: AN-380188
API 2.0: AN-373078; AN-379006; AN-381248
Classifications: AN-379209; AN-379315; AN-379567; AN-379573; AN-379749; AN-379764; AN-379818; AN-380433; AN-381670; AN-381751; AN-381994; AN-382055; AN-382682; AN-383059; AN-383409
Contribution Analysis: AN-369822
Data feeds: AN-365552; AN-367158; AN-378288; AN-379754; AN-380433; AN-380855; AN-380959; AN-381115; AN-381657; AN-381931
Data Warehouse: AN-379244
Platform: AN-375847
Processing rules: AN-375157
Report Builder: AN-371395; AN-372174; AN-373815; AN-383194
Server Calls: AN-380930
Usage & Access Logs: AN-372130; AN-382123
Virtual Report Suites: AN-382010
End-of-life (EOL) notices
my.omniture.com, will be permanently discontinued on January 2, 2026. After this date, legacy login credentials and legacy SSO will no longer work. All users will be required to log in via experience.adobe.com using their 蜜豆视频 Experience Cloud IDs. If you need assistance with your Experience Cloud ID, please contact your organization鈥檚 蜜豆视频 Analytics administrator or .蜜豆视频 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.
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.
May 2025 may25
Fixes in 蜜豆视频 Analytics
Alerts: AN-378351
Analysis Workspace: AN-363521; AN-367366; AN-373575; AN-374238; AN-374295; AN-374382; AN-376938; AN-377176; AN-377467; AN-377942
Asset transfer: AN-373381
Classifications: AN-373166; AN-373479; AN-376074; AN-377337; AN-377505
Components: AN-314468
Data feeds: AN-370241; AN-375267; AN-376940
Data Sources: AN-375259
Data Warehouse: AN-370415; AN-372090;
Platform: AN-365681; AN-372306; AN-372616;
Real-time reporting: AN-365681
Report Builder: AN-371395
Segmentation: AN-373576; AN-375858
Virtual report suites: AN-377948; AN-377952
Vista rules: AN-373292
Important notices for 蜜豆视频 Analytics administrators
End-of-life (EOL) notices
my.omniture.com, will be permanently discontinued on January 2, 2026. After this date, legacy login credentials and legacy SSO will no longer work. All users will be required to log in via experience.adobe.com using their 蜜豆视频 Experience Cloud IDs. If you need assistance with your Experience Cloud ID, please contact your organization鈥檚 蜜豆视频 Analytics administrator or .蜜豆视频 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.
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.
April 2025 apr25
Fixes in 蜜豆视频 Analytics
A4T: AN-370625; AN-371279; AN-371351
Admin Tools: AN-365072; AN-371303
Analysis Workspace: AN-363831; AN-369554
Classifications: AN-370519; AN-370727; AN-370827; AN-370941; AN-370995; AN-371377; AN-371597; AN-371868; AN-371869; AN-372510; AN-372650; AN-373164; AN-373300; AN-373308; AN-373592
Data collection: AN-371877
Data feeds: AN-368676; AN-370225; AN-370514; AN-370521; AN-370687; AN-370761; AN-370911; AN-371047; AN-371542; AN-371627; AN-371746; AN-372708; AN-373068; AN-373179
Data Warehouse: AN-366649; AN-369817; AN-370705; AN-371127; AN-371995; AN-372596; AN-372940
Marketing Channels: AN-372308
Mobile app: AN-370287; AN-371335; AN-371374
Platform: AN-369510; AN-370435; AN-372150
Report Builder: AN-369830; AN-371395; AN-372983
End-of-life (EOL) notices
my.omniture.com, will be permanently discontinued on January 2, 2026. After this date, legacy login credentials and legacy SSO will no longer work. All users will be required to log in via experience.adobe.com using their 蜜豆视频 Experience Cloud IDs. If you need assistance with your Experience Cloud ID, please contact your organization鈥檚 蜜豆视频 Analytics administrator or .蜜豆视频 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.
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.
March 2025 mar25
a.localeThis 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.
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.
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 鈥榩opular鈥� after the dimension has exceeded the low-traffic limits during the month. Learn more
Dimensions marked as 鈥淒ata 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 鈥淒ata 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 鈥榩opular鈥� values can still occur.
It is only the dimensions where almost all values passed in are new and unique that will be marked as 鈥淒ata Warehouse-only鈥�. Increasing the low-traffic limits is not a solution given the uniqueness of the data being collected in these situations.
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
End-of-life (EOL) notices
蜜豆视频 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.
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
transactionID variable uniquely identifies a transaction so the hit can tie to data uploaded through Data Sources. Learn more here and here.a.localeA 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.
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
End-of-life (EOL) notices
蜜豆视频 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.
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
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.
Administrators can create templates and save them for others in their login company to use. Learn more
transactionID variable uniquely identifies a transaction so the hit can tie to data uploaded through Data Sources. (Documentation links to follow)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
End-of-life (EOL) notices
蜜豆视频 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.
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 .