Target release notes (current)

Last update: June 23, 2025

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.)

Target Standard/Premium 25.6.3 (June 20, 2025)

This release includes the following fixes and updates:

  • Fixed an issue where copying an activity from one workspace to another workspace triggered errors such as “must not be null” or “Something went wrong.” (TGT-52474)
  • Fixed an issue where Automated Segments and Important Attributes reports were not generated for certain activities. (TGT-52904)
  • Fixed an issue in the updated VEC where default content handling in Automated Personalization (AP) activities did not match the legacy UI. The system now automatically adds a default optionGroup named “Default Content” with optionGroupLocalId = 0 when no group is explicitly added. This group includes the default option (for example, optionLocalId: 0). If the default content is removed, the corresponding option group is also removed. (TGT-52651)
  • Fixed an issue in Multivariate Test (MVT) activities where reusing an experienceLocalId from previously removed experiences was incorrectly disallowed. (TGT-52672)
  • Fixed an issue that prevented copying or editing activities containing an experience fragment. This triggered the error: Enum "AemOfferType" cannot represent value: "html". (TGT-52635)
  • Fixed an issue where URLs in activity locations failed to display query parameters due to invalid characters, such as slashes (/). (TNT52845)
  • Improved the validation error message for A/B Test activity updates via the backend API. When duplicate location names are present, the message now clearly states: “Duplicate names are not allowed” for locations.selectors. (TGT-52589)
  • Fixed an error that occurred when updating a live Recommendations activity due to an unrecognized property in the request payload. The system now properly handles the “Invalid JSON. Unrecognized property name” error. (TGT-52723)
  • Fixed an issue that prevented creating a Recommendations design. Clicking Create triggered the message: “There should be at least 1 entity variable used inside the script.” (TGT-52395 & TGT-52899)
  • Fixed an issue where re-saving a Recommendations design without modifications was blocked. (TGT-52879)
  • Fixed a backend validation error that caused a “400 Bad Request” error when saving a Recommendations activity. (TGT-52716)
  • Fixed an issue in the Form-Based Experience Composer where hovering over an mbox with special characters in the Location drop-down caused the editor to go blank and triggered a “Failed to execute ‘querySelector’ on ‘Element’.” error. (TGT-52717)
  • Improved feed-status accuracy with a new “PARTIALLY_IMPORTED” indicator. Previously, feeds were marked as “success” even when not all rows in a file were imported, which was misleading. (TGT-52892)
  • Fixed an error where, after migrating to AP V2, certain API calls to /admin/rest/ui/v1/campaigns returned client-side errors (HTTP 4xx). (TGT-52721)