Analytics Cloud - Product Changelog に戻る
- 2025.07.17 - Release Updates
- 2025.04.17 - Release Updates
- 2025.04.15 - Release Candidate
- 2025.02.06 - Release Updates
- 2025.02.04 - Release Candidate
- 2024.11.26 - Release Updates
- 2024.11.21 - Release Candidate
- 2024.09.10 - Release Updates
- 2024.09.05 - Release Candidate
- 2024.07.11 - Release Updates
- 2024.07.03 - Release Candidate
- 2024.03.21 - Release Updates
- 2024.02.21 - Release Updates
- 2024.01.09 - Release Updates
- 2023.12.05 - Release Updates
- 2023.10.25 - Release Updates
- 2023.10.10 - Release Updates
- 2023.09.06 - Release Updates
- 2023.07.19 - Release Updates
- 2023.05.25 - Release Updates
- 2023.03.01 - Release Updates
- 2023.01.26 - Release Updates
- 2023.01.09 - Release Updates
- 2022.11.28 - Release Updates
- 2022.11.09 - Release Updates
- 2022.10.04 - Release Updates
- 2022.09.28 - Release Updates
- 2021.06.04 - Release Updates
2023.10.25 - Release Updates
In this release, we are shipping an improvement to AB Testing as well as a number of important bug fixes.
In terms of AB Testing, marketers can now receive test results from prematurely terminated tests. Although these results cannot determine a winning variant with 100% confidence, they will give marketers a sense of how their variant was performing and allow them to make educated decisions according to their specific time constraints. For more information please see the Feature Announcement.
Added Features:
- Displaying Test Results for terminated AB Tests.
- Improved the dependency and speed of syncing large amounts of users from Liferay DXP by leveraging a batch framework.
Bug Fixes:
- Fixed a bug that caused segment membership update to fail in certain situations.
- Fixed a bug that allowed segments to include activities from other properties in the workspace when calculating segment membership.
- Fixed a bug that caused a failure when syncing large amounts of commerce channels (i.e. 100+).
- Fixed a bug that made certain static segments unable to be edited.
- Fixed a bug that caused irregularities with the "reads" metric in the Content Dashboard.
このページで