۶Ƶ

2024 ۶Ƶ Analytics release notes

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

October 2024

Feature
Description
Rollout starts
General Availability
New Report Builder for ۶Ƶ Analytics
The new Report Builder application brings updated features to ۶Ƶ Analytics, such as improved performance, streamlined user interface, 2.0 API support and support for Microsoft Excel on Mac, Windows, and web browsers. [Documentation link to follow]
October 16, 2024

Fixes in ۶Ƶ Analytics

Analysis Workspace: AN-343611; AN-355870; AN-357100; AN-358364; AN-358756; AN-359269
Analytics Mobile App: AN-354085
Classifications: AN-353074; AN-357533; AN-358308; AN-358350; AN-358732; AN-358925; AN-359249
Cross-Device Analytics: AN-357968
Data Feeds: AN-358489; AN-358542
Data Warehouse: AN-352181; AN-356701; AN-356802; AN-356804; AN-359162

Important notices for ۶Ƶ Analytics administrators

Notice
Date Added or Updated
Description
Additional implementation detail XDM fields automatically mapped
September 11, 2024
When using the ۶Ƶ Experience Platform Edge Network to send data to ۶Ƶ Analytics, the XDM fields xdm.implementationdetails.name and xdm.implementationdetails.environment now always map to context data variables c.a.x.implementationdetails.name and c.a.x.implementationdetails.environment. Previously, some scenarios prevented these values from populating. Please adjust any relevant processing rules to accommodate the availability of these values.

End-of-life (EOL) notices

EOL Product or Feature
Date added or updated
Description
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.

Migration to ۶Ƶ I/O OAuth Server-to-Server credentials
May 11, 2023

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

September 2024

Feature
Description
Rollout starts
General Availability
Additional information in the “Used in” column in the calculated metric manager and segment manager

The “Used in” column in the calculated metric manager and segment manager contains the following new reporting areas:

  • Report Builder: Shows the number of calculated metrics or segments that are being used in the Report Builder.
  • Ad hoc components: Shows the number of ad hoc calculated metrics or ad hoc segments that are being used in projects. These ad hoc calculated metrics and segments (otherwise known as “quick calculated metrics” and “quick segments”) can be used only in the project where they were created, so they are reported separately from the “Project” reporting area in the “Used in” column.
Sept 11, 2024
Activity Map v3 extension
The Activity Map v3 extension is now available. If you have the v2 extension installed, uninstall it before installing the v3 extension. Navigate to Tools > Activity Map to obtain the latest version of the extension.
Sept 3, 2024

Fixes in ۶Ƶ Analytics

A4T: AN-355736
Activity Map: AN-353779
Analysis Workspace: AN-348485; AN-349693; AN-357247
Analytics Mobile App: AN-352645
Classifications: AN-355636; AN-355651; AN-355753; AN-356005; AN-356439; AN-356540; AN-356577; AN-356622
Cross-Device Analytics: AN-355138
Data Feeds: AN-356258; AN-357133
Data Warehouse: AN-339292; AN-353807
Export Locations: AN-356912
Privacy API: AN-352420
Report Builder: AN-352555; AN-354316
Scheduled projects: AN-355971
Segmentation: AN-352095;
Target reporting: AN-355748

Other fixes: AN-349698; AN-349880; AN-354860; AN-355355; AN-356289;

Important notices for ۶Ƶ Analytics administrators

Notice
Date Added or Updated
Description
13-month expiration of saved cust_visids
August 20, 2024
The August 20, 2024, release of the Analytics Hit processing engine enforces 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. Previously, there was 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 expires.
Additional implementation detail XDM fields automatically mapped
September 11, 2024
When using the ۶Ƶ Experience Platform Edge Network to send data to ۶Ƶ Analytics, the XDM fields xdm.implementationdetails.name and xdm.implementationdetails.environment now always map to context data variables c.a.x.implementationdetails.name and c.a.x.implementationdetails.environment. Previously, some scenarios prevented these values from populating. Please adjust any relevant processing rules to accommodate the availability of these values.

End-of-life (EOL) notices

EOL Product or Feature
Date added or updated
Description
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.

Migration to ۶Ƶ I/O OAuth Server-to-Server credentials
May 11, 2023

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

AppMeasurement

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

August 2024 aug24

Feature
Description
Rollout starts
General Availability
Web SDK improvements for link tracking

Several notable improvements are available in the latest version of the Web SDK around link tracking, which directly benefits Activity Map. These new features are available in both the Web SDK JavaScript library and the Web SDK tag extension.

  • Event grouping: When a visitor clicks an internal link, you can choose to group event data on the next page instead of triggering a separate event call for link tracking. This improvement reduces the number of events that the Web SDK uses against your contractual limit.
  • Filter click properties: A new callback that replaces OnBeforeLinkClickSend. You can use this callback to filter or obfuscate link-related data before sending it to ۶Ƶ.

See clickCollection in the Web SDK user guide for more information.

Open Beta started July 10, 2024
July 18, 2024

Fixes in ۶Ƶ Analytics

  • Fixed an issue where multiple unknown values were displayed in Workspace (AN-353632)
  • Fixed an issue where the notification email did not send after adding new customers or new Analytics product profiles in the Admin console (AN-350930)

Other Analytics fixes

AN-354361; AN-354248; AN-354211; AN-354324; AN-351532; AN-349808; AN-347831; AN-353777; AN-354092; AN-354064; AN-354202; AN-354006; AN-354097; AN-352548; AN-353819; AN-353818; AN-353628; AN-353747; AN-353527; AN-353490; AN-352647; AN-352656; AN-351274; AN-352135; AN-351519; AN-344906; AN-353697; AN-354499; AN-354402; AN-354062; AN-353905; AN-353932; AN-354142; AN-354194; AN-354182; AN-353758; AN-353039; AN-353612; AN-350799; AN-354414; AN-354636; AN-354249; AN-353637; AN-350949; AN-349402; AN-355103; AN-354174; AN-353823; AN-354819; AN-354215; AN-354219; AN-354040; AN-354763; AN-354597; AN-354478; AN-354528; AN-354335

Important notices for ۶Ƶ Analytics administrators

Notice
Date Added or Updated
Description
13-month expiration of saved cust_visids
August 20, 2024
The August 20, 2024, release of the Analytics Hit processing engine enforces 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. Previously, there was 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 expires.

End-of-life (EOL) notices

EOL Product or Feature
Date added or updated
Description
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.

Migration to ۶Ƶ I/O OAuth Server-to-Server credentials
May 11, 2023

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

AppMeasurement

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

July 2024 july24

Feature
Description
Rollout starts
General Availability
Web SDK improvements for link tracking

Several notable improvements are available in the latest version of the Web SDK around link tracking, which directly benefits Activity Map. These new features are available in both the Web SDK JavaScript library and the Web SDK tag extension.

  • Event grouping: When a visitor clicks an internal link, you can choose to group event data on the next page instead of triggering a separate event call for link tracking. This improvement reduces the number of events that the Web SDK uses against your contractual limit.
  • Filter click properties: A new callback that replaces OnBeforeLinkClickSend. You can use this callback to filter or obfuscate link-related data before sending it to ۶Ƶ.

See clickCollection in the Web SDK user guide for more information.

Open Beta started July 10, 2024
July 18, 2024

Fixes in ۶Ƶ Analytics

  • Fixed an issue that prevented users from logging in to the Analytics UI (AN-352953)
  • Fixed an issue that prevented users from logging in to the Analytics mobile app (AN-352463)
  • Fixed an issue that prevented downloading the project as a PDF (AN-352680)
  • Fixed an issue where classifications were not being imported (AN-352178)

Other Analytics fixes

AN-352905; AN-352902; AN-352693; AN-352659; AN-352619;
AN-352577; AN-352575; AN-352572; AN-352571; AN-352549; AN-352501; AN-352499; AN-352478; AN-352466; AN-352437; AN-352378; AN-352355; AN-352341; AN-352318; AN-352297; AN-352272; AN-352267; AN-352263; AN-352088; AN-352019; AN-352018; AN-351978; AN-351908; AN-351809; AN-351750; AN-351689; AN-351624; AN-351564; AN-351524; AN-351507; AN-351416; AN-351414; AN-351405; AN-351299; AN-351283; AN-351231; AN-350710; AN-349912; AN-349786; AN-348300; AN-348061; AN-347865; AN-347676; AN-347478; AN-343611; AN-343114; AN-334124

Important notices for ۶Ƶ Analytics administrators

Notice
Date Added or Updated
Description
13-month expiration of saved cust_visids
May 22, 2024
An upcoming release of the Analytics Hit processing engine, targeted for July 2024, 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 expires.

End-of-life (EOL) notices

EOL Product or Feature
Date added or updated
Description
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.

Migration to ۶Ƶ I/O OAuth Server-to-Server credentials
May 11, 2023

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

June 2024 june24

Feature
Description
Rollout starts
General Availability
Select multiple fields in a drop-down filter

When multiple fields have been added to a drop-down filter, users can now select more than one field at a time. The panel is filtered to include any of the selected fields.

Previously, users could select only one field at a time in a drop-dow filter.

For more information, see Static drop-down segments in Panels overview.

View a video demonstration of this feature.

June 19, 2024
Table of contents for Workspace projects

A new table of contents is now available for projects. The table of contents provides links that enable users to quickly jump to panels and visualizations within the project. The table of contents can be enabled for individual projects or for all projects for a given user.

For more information, see Project table of contents.

View a video demonstration of this feature.

June 19, 2024
Create hyperlinks for dimension items in a freeform table

You can create hyperlinks for one or more dimension items to make them clickable within a freeform table in Analysis Workspace.

You can create hyperlinks for dimension items that have URL values, or you can create custom URLs for dimension items that have non-URL values.

You can create dynamic custom URLs for multiple dimension items by using variables. Variables can reference the value of a dimension item or they can reference the breakdown dimension.

For more information, see Create hyperlinks for dimensions in a freeform table.

View a video demonstration of this feature.

June 19, 2024
Administrator settings to control the accounts and locations that are used for export and import

A new “Admin settings” tab in the Locations manager gives administrators control over whether users can create and edit accounts and locations. These settings apply when users configure cloud import and export accounts and configure cloud import and export locations.

Administrators can also limit the types of accounts (Google Cloud Platform, Azure RBAC, Amazon S3, and so forth) that users can create and use.

Previously, any user could create, edit, and use accounts and locations for any type of account.

June 12, 2024
June 20, 2024
Share accounts and locations that are used for export and import

Users can now make the accounts and locations they create available to all users in their organization. Only account and location owners and system administrators can edit and delete accounts and locations.

Previously, accounts and locations could be used only by the user who created them.

These settings are available when users configure cloud import and export accounts and configure cloud import and export locations.

June 12, 2024
June 20, 2024
New Data Sources API Guide
The endpoints provide methods to create, view, delete, and upload to Data Sources accounts.
Available now
New methods in the Classifications API Guide

Two new methods for retrieving file partitions were added to the Classifications API Guide.

Available now

Fixes in ۶Ƶ Analytics

  • Fixed the following Classifications issues: AN-347682; AN-348396; AN-348625; AN-348668; AN-348926; AN-348936; AN-349040; AN-349191; AN-349195; AN-349443; AN-349697; AN-349758; AN-349862; AN-350051; AN-350054; AN-350208; AN-350497; AN-350525; AN-351067
  • Fixed the following Data Warehouse issues: AN-346862; AN-349409; AN-349926; AN-350629; AN-350996
  • Fixed the following Data Feeds issues: AN-346727; AN-348282; AN-348334; AN-348725; AN-348726; AN-348823; AN-349081; AN-349207; AN-349307; AN-349539; AN-349710; AN-349729; AN-349742; AN-349878; AN-349943; AN-350527;
  • Fixed the following Data Sources issue: AN-350038
  • Fixed the following Analysis Workspace issues: AN-342953; AN-346346; AN-349590; AN-349717; AN-350057; AN-350697; AN-350904
  • Fixed the following Report Builder issues: AN-348903; AN-350691
  • Fixed the following A4T issues: AN-347690; AN-350853

Other Analytics fixes

AN-346470; AN-346850; AN-347227; AN-348145; AN-348564; AN-349001; AN-349008; AN-349211; AN-349719; AN-350523;

Important notices for ۶Ƶ Analytics administrators

Notice
Date Added or Updated
Description
13-month expiration of saved cust_visids
May 22, 2024
An upcoming release of the Analytics Hit processing engine, targeted for July 2024, 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 expires.
ISO region updates
May 10, 2024
۶Ƶ will perform 2024 ISO region updates on June 7, 2024. Expect to see minor geo information (region) updates following this release.

End-of-life (EOL) notices eol

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

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

May 2024 may24

Feature
Description
Rollout starts
General Availability
New documentation for upgrading from ۶Ƶ Analytics to Customer Journey Analytics

For organizations upgrading from ۶Ƶ Analytics to Customer Journey Analytics, there are multiple upgrade options and many considerations to keep in mind based on an organization’s current ۶Ƶ Analytics implementation and long-term goals. New documentation resources are now available to help you better understand:

  • The various upgrade paths that exist
  • Which upgrade paths are available based on an organization’s current ۶Ƶ Analytics implementation
  • The advantages and disadvantages of each upgrade path
  • Step-by-step guidance for each upgrade path
  • Considerations for handling historical data

Get started with the upgrade to Customer Journey Analytics

Available now
Set contextData fields via XDM
Customers sending data to ۶Ƶ Analytics via the Experience Edge Network can set context data values directly either in XDM or in the ‘data’ portions of the payload.
Available now
Analytics Real-time Reporting 2.0 API
The new Real-time Reporting API 2.0 in ۶Ƶ Analytics improves customer integration and provides rapid reporting results. These results can be used programmatically to work with basic, trended, and breakdown reports.
May 30, 2024
The Streaming Media Collection: Send web data to ۶Ƶ Experience Platform Edge Network with the Web SDK

You can now use the ۶Ƶ Experience Platform Web SDK to send streaming media web data to ۶Ƶ Experience Platform Edge Network. This enhancement allows you to build more personalized campaigns and provide more personalized content, resulting in more tracking data to report on.

This change provides a unified collection method for web implementations across all Platform solutions, such as Customer Journey Analytics, ۶Ƶ Real-time CDP, ۶Ƶ Journey Optimizer, and Event Forwarding. Previously, the only way to send streaming media web data to Edge Network was by using the Media Edge API.

Learn more

May 29, 2024
Increase in default low-traffic thresholds

In mid April 2024, ۶Ƶ 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
Administrator settings to control the accounts and locations that are used for export and import

A new “Admin settings” tab in the Locations manager gives administrators control over whether users can create and edit accounts and locations. These settings apply when users configure cloud import and export accounts and configure cloud import and export locations.

Administrators can also limit the types of accounts (Google Cloud Platform, Azure RBAC, Amazon S3, and so forth) that users can create and use.

Previously, any user could create, edit, and use accounts and locations for any type of account.

(Updated documentation link to follow)

June 12, 2024
June 30, 2024
Share accounts and locations that are used for export and import

Users can now make the accounts and locations they create available to all users in their organization. Only account and location owners and system administrators can edit and delete accounts and locations.

Previously, accounts and locations could be used only by the user who created them.

These settings are available when users configure cloud import and export accounts and configure cloud import and export locations.

(Updated documentation link to follow)

June 12, 2024
June 30, 2024
Activity Map to use 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.

(Updated documentation link to follow)

Open Beta starts June 19, 2024
TBD

Fixes in ۶Ƶ Analytics

  • Fixed the following Classifications issues: AN-343186; AN-344711; AN-344856; AN-345094; AN-345179; AN-346265; AN-345288; AN-346339; AN-346560; AN-347572; AN-347681; AN-347768; AN-348024
  • Fixed the following Data Warehouse issues: AN-346789; AN-347031; AN-347568;
  • Fixed the following Data Feeds issues: AN-343616; AN-345831; AN-345988; AN-346124; AN-346232; AN-346972; AN-347680; AN-347755; AN-347954
  • Fixed the following Data Sources issue: AN-347890;
  • Fixed the following Analysis Workspace issues: AN-321503; AN-343103; AN-343471; AN-345171; AN-345223; AN-345912; AN-346026; AN-346330; AN-346839; AN-347679
  • Fixed the following A4T issue: AN-345118;

Other Analytics fixes

AN-327749; AN-332949; AN-342881; AN-343171; AN-343708; AN-344034; AN-345559; AN-346023; AN-346230; AN-346330; AN-346469; AN-346606; AN-346750; AN-346973; AN-347026; AN-347110; AN-347439;

Important notices for ۶Ƶ Analytics administrators

Notice
Date Added or Updated
Description
13-month expiration of saved cust_visids
May 22, 2024
An upcoming release of the Analytics Hit processing engine, targeted for July 2024, 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 expires.
ISO region updates
May 10, 2024
۶Ƶ will perform 2024 ISO region updates on June 7, 2024. Expect to see minor geo information (region) updates following this release.

End-of-life (EOL) notices

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

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

April 2024 apr24

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

Datastreams now automatically map fields from the Web SDK data object straight to ۶Ƶ 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 ۶Ƶ Experience Platform. If a schema was required at this stage of an implementation migration, you would be forced to use a schema based on ۶Ƶ Analytics fields. ۶Ƶ 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 ۶Ƶ Analytics to Customer Journey Analytics. If you send data to ۶Ƶ Analytics using the Web SDK, you do not need to make additional implementation changes to send data to ۶Ƶ Experience Platform. Instead, you can use data prep to map data object fields to your XDM schema.

See Migrate from the ۶Ƶ 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, ۶Ƶ 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 ۶Ƶ 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 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 ۶Ƶ Analytics administrators

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.
۶Ƶ API object member additions
January 17, 2024
۶Ƶ may add optional request and response members (name/value pairs) to existing API objects at any time and without notice or changes in versioning. ۶Ƶ 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. ۶Ƶ will not remove parameters or add required parameters without first providing standard notification through release notes.

End-of-life (EOL) notices

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

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

AppMeasurement

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

March 2024 mar24

Feature
Description
Rollout starts
General Availability
Change to deletion protocol for Workspace projects
Previously, deleted projects were never purged from the system. We will now start purging deleted projects after 180 days. During the 180 days after deletion, users can still access a deleted project via the Web interface if they have a URL to the project.
March 14, 2024
AppMeasurement update
AppMeasurement release v2.26.0 is available.
March 4, 2024
New column available on the Projects landing page

The Last used column is now available when viewing the Projects tab on the ۶Ƶ Analytics landing page.

This information can help you determine whether a project is valuable to users in your organization by showing the date and time when the project was last opened.

Previously, the Last used column was available only in the Calculated metrics manager, Segments manager, and Alerts manager.

March 13, 2024
Analytics support for consent flags required by Google for DMA

Due to new European privacy regulations, Google requires that data collected in Europe that was sent to them must indicate whether two particular kinds of consent were granted.  Starting March 6th, Google will no longer accept event data that does not indicate that the relevant consent was granted. ۶Ƶ Analytics has released support for capturing this data via a new adConsent variable. You can see the new variable listed in the Privacy Reporting UI. If you would like to activate this and already have privacy enabled for the previous consent variables, you will need to enable privacy again.

The Ad Platform Consent dimension displays whether consent is collected to send data to third-party advertising providers like Google.

March 13, 2024

Fixes in ۶Ƶ Analytics

  • Fixed the following Classifications issues: AN-335632; AN-337559; AN-340164; AN-340370; AN-341089; AN-341211; AN-341284; AN-341469; AN-341481; AN-341760; AN-341778; AN-342144; AN-342258; AN-342338, AN-342400
  • Fixed the following Classifications Rule Builder issues: AN-340921; AN-341269; AN-341292; AN-341467; AN-341666; AN-342145; AN-342329
  • Fixed the following Alerts issue: AN-340736
  • Fixed the following Segmentation issue: AN-336242
  • Fixed the following Data Warehouse issues: AN-335354; AN-339446; AN-339774; AN-340221; AN-340599; AN-341277; AN-342009; AN-342088; AN-342592
  • Fixed the following Data Feeds issues: AN-335508; AN-340887; AN-341050; AN-341208; AN-341403; AN-341479; AN-341524; AN-341661; AN-342000; AN-342125; AN-342256; AN-342301; AN-342410; AN-342502; AN-342525
  • Fixed the following Report Builder issue: AN-340540
  • Fixed the following Analysis Workspace issues: AN-295889; AN-330981; AN-338818; AN-339730; AN-341114; AN-341520;

Other Analytics fixes

AN-312198; AN-338009; AN-339549; AN-333970; AN-334790; AN-336461; AN-336572; AN-339549; AN-341119; AN-341246; AN-341268; AN-341272; AN-341475; AN-341547; AN-341558; AN-341680; AN-342017;

Important notices for ۶Ƶ Analytics administrators

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.
۶Ƶ API object member additions
January 17, 2024
۶Ƶ may add optional request and response members (name/value pairs) to existing API objects at any time and without notice or changes in versioning. ۶Ƶ 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. ۶Ƶ will not remove parameters or add required parameters without first providing standard notification through release notes.
getPageLoadTime plug-in deprecated
January 10, 2024
This plug-in is no longer supported. Its code uses the interface, which is deprecated on most modern browsers. Work on an updated plug-in has started.

End-of-life (EOL) notices

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

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

AppMeasurement

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

February 2024 feb24

Feature
Description
Rollout starts
General Availability
AppMeasurement update
AppMeasurement release v2.26.0 is available.
March 4, 2024
Data Warehouse updates

The following Data Warehouse improvements are now available:

  • When creating a Data Warehouse request, users can now make requests available to all users in the organization by enabling the new toggle called Make available to users in your organization.

    For more information, see Data Warehouse request general settings.

  • When creating or managing Data Warehouse report destinations, system administrators can now show accounts and locations that were created by users in the organization by enabling the toggle called Show all destinations.

    For more information, see Configure a report destination for a Data Warehouse request.

N/A
January 10, 2024
Updates to Key Metrics Summary visualization
When using the Key Metric Summary visualization, the Comparison date range can now automatically update, depending on whether the Comparison date range option you choose is relative to the primary date range or fixed. Learn more.
N/A
January 17, 2024
Data Warehouse API documentation
Please refer to the for more information. Go to Select a definition and select Data Warehouse APIs.
February 19, 2024
Activity Map for Web SDK without extra cost
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.
March 6, 2024
Increase in default low-traffic thresholds

In mid April 2024, ۶Ƶ 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
End of May, 2024

Fixes in ۶Ƶ Analytics

  • Fixed the following Classifications issues: AN-319515; AN-337559; AN-338149; AN-338702; AN-338769; AN-338891; AN-339327; AN-339649; AN-339668; AN-339669; AN-339776; AN-339822; AN-340017; AN-340202; AN-340476;
  • Fixed the following Classifications Rule Builder issues: AN-338385; AN-338399; AN-338592; AN-338810; AN-338893; AN-339431; AN-339894; AN-339933; AN-340201; AN-340309;
  • Fixed the following A4T issues: AN-334830; AN-336194; AN-338309; AN-338650;
  • Fixed the following Data Collection issue: AN-339323
  • Fixed the following Data Warehouse issues: AN-335542; AN-331425; AN-337215; AN-338445; AN-338643; AN-338651; AN-339461; AN-340066; AN-340207; AN-340460
  • Fixed the following Data Feeds issues: AN-335952; AN-338653; AN-339508; AN-339681; AN-340418
  • Fixed the following Data Sources issues: AN-338648
  • Fixed the following Analysis Workspace issues: AN-326509; AN-336186; AN-336190; AN-336309; AN-337922; AN-338094; AN-338323; AN-338556; AN-339600; AN-340445

Other Analytics fixes

AN-328239; AN-332908; AN-335449; AN-335517; AN-336075; AN-336100; AN-336128; AN-338088; AN-338270; AN-338393; AN-338494; AN-339326; AN-339742; AN-339883; AN-340419;

Important notices for ۶Ƶ Analytics administrators admin

Notice
Date Added or Updated
Description
۶Ƶ API object member additions
January 17, 2024
۶Ƶ may add optional request and response members (name/value pairs) to existing API objects at any time and without notice or changes in versioning. ۶Ƶ 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. ۶Ƶ will not remove parameters or add required parameters without first providing standard notification through release notes.
getPageLoadTime plug-in deprecated
January 10, 2024
This plug-in is no longer supported. Its code uses the interface, which is deprecated on most modern browsers. Work on an updated plug-in has started.

End-of-life (EOL) notices

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

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

AppMeasurement

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

January 2024 jan24

Feature
Description
Rollout starts
General Availability
Data Warehouse updates

The following Data Warehouse improvements are now available:

  • When creating a Data Warehouse request, users can now make requests available to all users in the organization by enabling the new toggle called Make available to users in your organization.

    For more information, see Data Warehouse request general settings.

  • When creating or managing Data Warehouse report destinations, system administrators can now show accounts and locations that were created by users in the organization by enabling the toggle called Show all destinations.

    For more information, see Configure a report destination for a Data Warehouse request.

N/A
January 10, 2024
Updates to Key Metrics Summary visualization
When using the Key Metric Summary visualization, the Comparison date range can now automatically update, depending on whether the Comparison date range option you choose is relative to the primary date range or fixed. Learn more.
N/A
January 17, 2024

Fixes in ۶Ƶ Analytics

  • Fixed the following Classifications issues: AN-314821; AN-326839; AN-332079; AN-332704; AN-332812; AN-332902; AN-332975; AN-333300; AN-333023; AN-333033; AN-333174; AN-333910; AN-334097; AN-334208; AN-334373; AN-334439; AN-334698; AN-334838; AN-334848; AN-334987; AN-335046; AN-335082; AN-335202; AN-335203; AN-335254; AN-335322; AN-335552; AN-335591; AN-335603; AN-335610; AN-335617; AN-335699; AN-335891; AN-335901; AN-336063; AN-336072; AN-336193; AN-336479; AN-336684; AN-336801; AN-337370; AN-337398
  • Fixed the following Classifications Rule Builder issues: AN-332390; AN-332573; AN-332718; AN-332927; AN-333248; AN-333953; AN-334647; AN-334736; AN-334910; AN-335642; AN-335683; AN-335811; AN-336033; AN-336569; AN-336852; AN-336875; AN-336902; AN-337190;
  • Fixed the following A4T issues: AN-334564; AN-336178;
  • Fixed the following Server Call Usage issues: AN-332568; AN-333105; AN-333167; AN-333983; AN-334209; AN-334278
  • Fixed the following Data Warehouse issues: AN-333010; AN-333076; AN-330227; AN-331580; AN-333350; AN-334291; AN-334283; AN-334287; AN-334301; AN-334385; AN-334453; AN-334977; AN-335079; AN-335171; AN-335245; AN-335426; AN-335680; AN-335818; AN-336087; AN-337308;
  • Fixed the following Data Feeds issues: AN-332241; AN-332366; AN-332617; AN-332654; AN-332702; AN-332723; AN-333014; AN-333166; AN-334037; AN-334125; AN-334211; AN-334216; AN-334235; AN-334976; AN-335158; AN-335368; AN-335408; AN-335468; AN-335471; AN-335528; AN-335596; AN-335662; AN-335733; AN-335883; AN-335894; AN-335968; AN-336098; AN-336192; AN-336243; AN-336659; AN-336977; AN-337117; AN-337219; AN-337262; AN-337393; AN-337462; AN-337854
  • Fixed the following Report Builder issues: AN-335246; AN-336311;
  • Fixed the following Analysis Workspace issues: AN-323760; AN-324191; AN-324913; AN-330126; AN-332808; AN-333168; AN-333382; AN-334839; AN-336040; AN-337043;

Other fixes

AN-323975; AN-325383; AN-325809; AN-326787; AN-331611; AN-331818; AN-332124; AN-332272; AN-332911; AN-333070; AN-333302; AN-333377; AN-333904; AN-333928; AN-333968; AN-334056; AN-334099; AN-334191; AN-334207; AN-334776; AN-335206; AN-335294; AN-335320; AN-335394; AN-335443; AN-335967; AN-336099; AN-337452; AN-337463

Important notices for ۶Ƶ Analytics administrators

Notice
Date Added or Updated
Description
۶Ƶ API object member additions
January 17, 2024
۶Ƶ may add optional request and response members (name/value pairs) to existing API objects without notice or changes in versioning. Such additions should be non-breaking changes for your implementation. ۶Ƶ 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. ۶Ƶ will not remove parameters or add required parameters without first providing standard notification through release notes.
getPageLoadTime plug-in deprecated
January 10, 2024
This plug-in is no longer supported. Its code uses the interface, which is deprecated on most modern browsers. Work on an updated plug-in has started.

End-of-life (EOL) notices

EOL Product or Feature
Date added or updated
Description
EOL for Reports & Analytics
January 10, 2024

Effective January 17, 2024, ۶Ƶ discontinued Reports & Analytics and its accompanying reports and features. The reports, visualizations, and underlying technology that power Reports & Analytics no longer met ۶Ƶ’s technology standards. Most Reports & Analytics features are available in Analysis Workspace. Since the release of Analysis Workspace in 2015, Reports & Analytics functionality and capabilities have been moved to Analysis Workspace and a threshold of workflow parity has been reached. explains the end-of-life process.

On January 17, 2024, ۶Ƶ terminated many of the associated Reports & Analytics features, including:

  • Scheduled reports
  • Data extracts
  • DL reports
  • Legacy dashboards
  • Custom reports
  • Custom conversion reports
  • Publishing widgets
  • Pathfinder report
  • Full paths report
  • Roll-up report suites
  • ASI report suites

After January 17, 2024, any scheduled reports using these features are no longer sent. In addition, you can no longer schedule future reports using these features as of January 17, 2024.

EOL of Publishing Lists feature
January 10, 2024
As part of the EOL of Reports & Analytics, Publishing Lists reached end-of-life on January 17, 2024. You can no longer create new or access existing Publishing Lists to send or schedule Analysis Workspace projects.
EOL for Data Workbench
January 2, 2024
۶Ƶ end-of-lifed Data Workbench effective December 31, 2023. See Data Workbench end-of-life announcement for details. Contact your organization’s ۶Ƶ Account Manager with any questions.
Migration to ۶Ƶ I/O OAuth Server-to-Server credentials
May 11, 2023

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

AppMeasurement

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

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