Target release notes (current)
These release notes provide information about features, enhancements, and fixes for each ۶Ƶ Target Standard and Target Premium release. In addition, release notes for Target APIs, SDKs, the ۶Ƶ Experience Platform Web SDK, at.js, and other platform changes are also included, when applicable.
(The issue numbers in parentheses are for internal ۶Ƶ use.)
Target Standard/Premium 25.6.2 (June 12, 2025)
This release includes the following fixes and updates:
- Added a new FAQ article to address common questions about the updated Target UI and Visual Experience Composer (VEC).
- Fixed an issue where the “URL - does not contain” rule in Page Delivery was not working, allowing content to be shown even when it should have been blocked. (TGT-52754)
- Fixed an issue where Page Delivery incorrectly displayed the error message: "Duplicate page URLs are not allowed. (TGT-52765)
- Fixed an issue where audiences for Page Delivery URLs containing experience fragments were created with # erroneously appended. (TGT-52786)
- Fixed an issue where copying an activity and editing settings on the Goals and Settings page caused the Target UI to become unresponsive. (TGT-52797)
- Fixed an issue in the updated Visual Experience Composer (VEC) that incorrectly allowed redirecting an additional page in an A/B Test activity to the same URL. (TGT-51838)
- Fixed an issue where changes to metrics on the Goals and Settings page were not saved when editing an activity. (TGT-52799)
- Fixed an issue where adding a new experience while the web editor was still loading caused the new experience to duplicate content from the previous experience. (TGT-51397)
- Restored the ability to use custom code outside the
<head>
tag, a feature previously available in the legacy Target UI. (TGT-52304 & TGT-52300) - Removed unnecessary validation when selecting the default workspace during activity creation. Mandatory property validation no longer applies to the default workspace, but remains in place for non-default workspaces. (TGT-52449)
- Fixed an issue in the updated Visual Experience Composer (VEC) where
triggerView()
calls were not being detected. (TGT-52575) - Fixed an issue in the updated Visual Experience Composer (VEC) that prevented users from adding modifications to Single Page Application (SPA) views. (TGT-52556)
- Fixed an issue in the updated Target UI that prevented customers from viewing offer details. (TGT-52607)
- Fixed an issue where updates made to offers in the Offers Library were not reflected in the updated Visual Experience Composer (VEC). (TGT-52637)
- Fixed an issue that prevented the Offers section from displaying properly while creating an activity. (TGT-52773)
- Added validation to ensure that all
optionLocalIds
referenced inoptionGroups
exist in the options array. Invalid references are automatically removed during activity creation. (TGT-52687) - Fixed an issue where reporting groups and exclusions were not retained after adding a new offer. (TGT-52728)
- Fixed an issue where activities without an Activity QA button displayed an empty option selector. (TGT-52733)
- Fixed an issue where QA links failed to render content properly. (TGT-52718)
- Fixed an issue where replacing an element with an experience fragment did not reflect changes correctly in the QA environment. (TGT-52762)
- Fixed an issue in the updated Visual Experience Composer (VEC) that caused an “Invalid Input” error when users attempted to add experience fragments. (TGT-52701)
- Fixed an issue where the “Edit Audience” modal appeared empty when editing audience targeting in the updated Visual Experience Composer (VEC). (TGT-52749)
- Added a message to inform users when an entity is not accessible in the selected workspace. (TGT-52767)
- Fixed an issue where the UI failed to allow manual assignment of an environment ID to a criteria. Instead, it defaulted to the ID for the Product Catalog Search host group. This fix ensures that criteria changes are now applied across all environments, not just the default. (TGT-52817)
- Fixed an issue where the “Download Recommendations data” option was missing for Experience Targeting (XT) activities with recommendations. (TGT-52730 & TGT-52756)
Target Standard/Premium 25.6.1 (June 6, 2025)
This release includes the following fixes and updates:
- Fixed an issue where QA links did not deliver the correct experience for the associated activity. (TGT-52163 & TGT-52790)
- Fixed an issue where QA links were missing the associated audience ID. (TGT-52722)
- Fixed an issue to ensure that experiences are delivered only when their configured Page Delivery URL conditions are accurately met. (TGT-52696)
- Fixed an issue that prevented customers from creating a Recommendations design template. Attempting to create a template triggered the error: “There should be at least 1 entity variable used inside the script.” (TGT-52395)
- Fixed an issue that prevented saving Recommendations designs using Velocity arrays. The error message “There should be at least 1 entity variable used inside the script” was incorrectly triggered. (TGT-52734)
- Fixed an issue where modifications were inaccessible in the Visual Experience Composer (VEC) when the page failed to load for internal web pages. (TGT-52488 &TGT-52470)
- Fixed an issue where the Modifications panel was not visible on smaller screen sizes in the VEC. (TGT-52470)
- Fixed an issue in the updated VEC where switching from Browse mode back to Design mode caused a console error and prevented further interaction. (TGT-52532)
- Fixed an issue in the VEC where clicking certain elements unintentionally expanded their size. (TGT-52497)
- Fixed an issue where certain page elements failed to load or be recognized in the VEC, preventing interactions such as selecting buttons or banners and disrupting accurate event tracking in activities. (TGT-52663)
- Fixed an issue that prevented customers from deleting or removing offers in Automated Personalization (AP) activities. (TGT-52690)
- Fixed an issue that caused inconsistent activity qualification behavior in multi-page activities. (TGT-52694)
- Fixed an issue that caused the activity’s Overview page to show an invalid URL for the Activity Location. (TGT-52695)
- Fixed an issue in the updated Target UI that caused duplicate entries to appear for activity locations. (TGT-52693)
- Fixed an issue that triggered a
getAudiencesV3
error, preventing customers from editing or copying activities. (TGT-52709) - Fixed an issue that caused an invalid payload error when adding Experience Fragments or HTML offers to an activity. (TGT-52779 & TGT-52773)
- Fixed an issue in the updated Target UI where Experience Fragments failed to display correctly due to an invalid input error. (TGT-52701)
- Fixed an issue that prevented customers from editing activities in the Form-based Experience Composer due to an invalid user error. (TGT-52470)
- Fixed a localization issue in the Korean language where previous translations used characters outside the Basic Multilingual Plane. The updated translation uses appropriate characters that accurately convey the intended meaning. (TGT-52508 & TGT-52509)
- Fixed a localization issue in the Korean language where the translation for “date” was inconsistent when selecting start and end dates for an activity. (TGT-52510)
Target UI version toggle deprecation (May 23, 2025) toggle
The rollout of the new Target user interface will be complete by May 27, 2025. At that point, all customers will have access to the latest UI version.
Starting June 22, 2025, the UI version toggle will be removed. All users will transition permanently to the new interface, with no option to revert to the previous version.
Important information about the UI version toggle
We’re offering a temporary feature that lets you switch between the updated Target UI and the legacy version using a toggle button. This option is available only during the final phase of the UI rollout.
Once the rollout is complete, the toggle will be removed, and all users will transition permanently to the updated UI on June 22, 2025. ۶Ƶ recommends planning ahead, as this feature will be phased out soon.
Limitations of the UI toggle behavior
- Visibility of new activities: Activities created in the updated UI will not be visible if you switch back to the legacy UI.
- Editing existing activities: Changes made to existing activities (originally created in the legacy UI) while using the updated UI will be published to your website. However, these updates will not be visible in the legacy UI if you switch back; only the last updates made from the legacy UI will appear there.
- Consistency of activity details: The most recent changes, regardless of which UI you use, will be reflected on your live website. However, the legacy UI will only show the latest changes made from within that version. This might cause confusion if activities edited in the updated UI look different than what you see in the legacy UI.
More information about the updated UI
-
Target Standard/Premium 25.2.1 (February 17, 2025) release notes: Provides a summary of the key UI changes in Target for Activities, Recommendations, and the Visual Experience Composer (VEC).
-
Target Standard/Premium 25.1.1 (January 9, 2025) release notes: Provides a summary of the key UI changes in Target for the Offers Library.
-
Understand the Target UI: Provides a brief overview to help you get familiarized with Target and provides links for more in-depth information and step-by-step instructions.
-
Visual Experience Composer changes: The ۶Ƶ Target Standard/Premium 25.2.1 release (February 17, 2015) introduces an updated Visual Experience Composer (VEC). This article explains the differences between the legacy and updated versions of the VEC.
-
Visual Experience Composer options: This article explains the updated VEC UI and its options.
-
Target UI update FAQs: This FAQ addresses common questions about the new Target UI and Visual Experience Composer (VEC), including navigation changes, feature locations, and the deprecation of the temporary UI version toggle. Whether you’re a marketer, developer, or admin, this FAQ helps you transition smoothly and make the most of the updated UI.
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.