Target release notes (current)
These release notes provide information about features, enhancements, and fixes for each Adobe Target Standard and Target Premium release. In addition, release notes for Target APIs, SDKs, the Adobe Experience Platform Web SDK, at.js, and other platform changes are also included, when applicable.
(The issue numbers in parentheses are for internal Adobe use.)
Adobe Experience Platform Web SDK __view__ scope optimization (October 22, 2024)
Between July 22, 2024 and August 15, 2024, the Target team optimized the __view__ scope, enhancing the accuracy of activity impression, visit, and visitor reporting. This optimization aims to automatically capture reporting data for auto-rendered propositions and should be transparent to most accounts.
All new Adobe Experience Platform Web SDK customers will have this optimization enabled. However, customers who migrated from at.js and have not followed the implementation steps below have the optimization disabled. We urge these customers to review their implementations by February 3, 2025. After this date, we will enable the optimization for all customers. Failure to review and adjust implementations by then might impact reports, as mentioned below. Please contact Adobe Customer Care if you need to confirm whether your implementation is affected or if you require more time to adjust your implementation.
To benefit from this optimization in case of manual proposition rendering, review your Platform Web SDK implementation to ensure that you are sending notifications after manually rendering experiences or when using the applyPropositions method (or the corresponding Launch action as a helper) to render experiences.
The most-common scenarios when experiences are manually rendered include:
- Using JSON offers
- Using a custom decision scope in an activity created in the Form-Based Experience Composer
- Not using
renderDecisions: truewhen fetching an activity created using the Form-Based Experience Composer that uses the global__view__scope
If notifications are not implemented as documented in Render personalized content in the Data Collection guide, reporting data might be missing in Target and in Analytics for Target reporting (A4T). In certain scenarios, you might notice an incorrect traffic split because the reporting data is not captured. Or, in other scenarios, reporting the same event repeatedly.
Depending on your implementation, check for Analytics and A4T reporting impacts.
The Platform Web SDK supports two implementation types for rendering experiences and personalizations:
-
Single call for personalization and measurement.
Initially recommended, the single-call approach for the Platform Web SDK is scheduled to be deprecated in favor of the split-call approach. Adobe advises all new implementations to use the new split-call approach and recommends that existing customers transition to the split-call method as well.
If you continue to use the single-call approach, you might notice the following unexpected changes in your Analytics reports:
- A dip in bounces.
- A4T and Page View hits not stitched together, making it challenging to perform certain breakdowns and correlations of your A4T reports using Analytics eVars and events.
-
Split calls (also known as top and bottom of page events).
This implementation type is the new split-call implementation approach recommended by Adobe. With this approach, the new optimization does not impact Analytics or A4T reports.
If you have questions, contact Adobe Customer Care. (KB-2179)
Additional release notes and version details
Documentation Changes, Past Release Notes, and Experience Cloud Release Notes
In addition to the notes for each release, the following resources provide additional information:
Prerelease Information section_5D588F0415A2435B851A4D0113ACA3A0
The following resources let you see what’s coming in the next Target release.