Target release notes (current)
- Topics:
- Release Notes
Explore the latest features, enhancements, and fixes in Adobe Target. These release notes also cover updates to Target APIs, SDKs, the Adobe Experience Platform Web SDK, at.js, and other platform components when applicable.
(The issue numbers in parentheses are for internal Adobe use.)
Time-sensitive updates you need to know
Important
For time-sensitive updates related to Adobe Target and your implementation, Adobe provides detailed release notes and documentation through Experience League. Here are some key highlights relevant to your implementation:
Target UI version toggle deprecation
The Target team is 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. Adobe recommends planning ahead, as this feature will be phased out soon.
Deprecation timeline
Due to recent issues identified, primarily related to complex customer customizations, the Target team has adjusted the deprecation timeline:
-
June 17, 2025: All IMS Organizations have been enabled for the updated Target UI, either for specific users or organization-wide, to begin testing the new experience.
-
June 30, 2025: The updated Target UI became the default experience for all IMS Orgs that have enabled the UI version toggle.
- Customers who currently see the legacy UI, by default, now see the updated UI upon login.
- The UI version toggle remains available through the end of July, allowing users to switch back if needed.
IMPORTANTAdobe strongly recommends using the updated Target UI. Switch back to the legacy UI only if a blocker issue occurs, due to limitations of the toggle switch behavior. -
July 15 to July 30, 2025: The UI version toggle will be permanently disabled in phases. Affected IMS Orgs are no longer able to revert to the legacy UI.
- Exceptions are reviewed on a case-by-case basis.
- Delays to the toggle deprecation are granted only briefly (a few days) while blocker issues are resolved.
Contact Adobe Customer Care with any concerns or if you anticipate issues during this transition.
Limitations of the UI toggle behavior
The following information describes the limitations that you should be aware of when choosing to use the version toggle:
- 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 resources to learn about the updated UI
- 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.
- 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 Adobe 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 Standard/Premium 25.7.1 (July 11, 2025)
Due to recent issues identified, primarily related to complex customer customizations, this release includes the following fixes and updates:
Activities
- Fixed an issue where the Activity QA URL included an unnecessary query parameter:
at_preview_evaluate_as_true_audience_ids. (TGT-52907) - Fixed an issue where Preview URLs incorrectly included additional audiences beyond the one explicitly typed by the user. This behavior has been corrected to ensure that only the specified audience is applied when generating a QA or preview link. (TGT-52912)
- Fixed an issue that prevented users from creating Auto-Target (AT) activities if Auto-Allocate (AA) is selected first during traffic allocation setup. This issue resulted in a backend validation error and prevents the activity from being saved. (TGT-53096)
Audiences
- Fixed an issue where users with the Approver role were unable to add or save activity-only audience refinements. Attempting to do so resulted in a 403 Forbidden error, stating that the “[editor]” privilege was required, even though the user had sufficient permissions to approve and manage activities. (TGT-52984)
- Fixed an issue when an activity-specific audience is removed using the Remove Audience Refinement option, the audience no longer appears in the audience list for re-selection within the same activity. This behavior prevented users from re-adding the same audience unless it is recreated from scratch. (TGT-52979)
- Fixed an issue where activity-only audience refinements disappeared from the UI immediately after being removed from a location, even before the activity was saved. This behavior contradicted the expected functionality and the tooltip guidance, which states: “All unused audiences from this library will be deleted once the activity is saved.” (TGT-52982)
- Fixed an issue when attempting to assign an audience other than All Visitors to an activity. Upon saving, the following error message displayed: “We cannot complete your request. Please contact Adobe Client Care if the issue persists.” (TGT-53008)
- Fixed an issue that blocked saving an activity after creating and assigning a new audience within the activity editor. The error message displayed was: “We cannot complete your request. Please contact Adobe Client Care if the problem persists.” (TGT-52977)
Analytics for Target (A4T)
- Fixed an issue where copying an existing activity and changing the reporting source to Adobe Analytics (A4T) would result in an “Invalid user input” error. The error was triggered when certain metric actions incompatible with Analytics reporting, such as
restart_same_experience,restart_random_experience, andrestart_new_experience, were retained from the original activity. (TGT-52900) - Fixed an issue that blocked customers from creating or saving an activity when selecting Adobe Analytics (A4T) as the reporting source in the Goals & Settings step. The issue occurred specifically when selecting a Custom Event metric (for example, “Custom Event 16”), resulting in the following error: “Invalid User Input.” (TGT-52910)
- Fixed an issue where clicking the “View in Analytics” link redirected users to the homepage instead of the intended Analytics dashboard. (TGT-53092 & TGT-53093)
Experiences and Offers
- Fixed an issue where the Manage Content feature did not properly validate the state of a location after all content options were removed. This could lead to inconsistent behavior or errors when attempting to save or proceed with the activity configuration. (TGT-52801)
- Fixed an issue where users encountered an “Invalid input” error when adding a new page and deleting specific elements within different experiences. The error was triggered by duplicate
LocalIdsbeing generated during element manipulation, particularly when switching between experiences and modifying shared page structures. (TGT-52720) - Fixed an issue where using the Generate Adhoc Offer feature resulted in undefined locations appearing in the Manage Content panel. (TGT-53076 & TGT-53070)
- Clarified the behavior to the customer where modifications made using an HTML Offer might appear to be missing when navigating from the Targeting step back to Experiences. For this customer, the affected website dynamically generated multiple DOM selectors that changed with each page load. As a result, the selector originally used for the modification cannot be found when the editor is reopened, causing the modification to appear missing or invalid. This is working as designed. To ensure that modifications persist visually in the editor, it is recommended that clients use stable, consistent selectors that do not change across page reloads. (TGT-52874)
- Fixed an issue where attempting to delete or deactivate an offer that was part of an excluded experience triggered an “Invalid user input” error. This issue occurred even though the offer was not actively used in the included experiences. (TGT-52917)
Form-Based Experience Composer
- Fixed an issue in form-based activities where duplicating an experience and editing the custom code in one of the duplicated experiences would unintentionally apply those changes to all duplicated experiences. Each experience now retains its own custom code independently after duplication. (TGT-51600)
Localization
- Fixed a contextual translation issue in the Korean locale (ko-KR) for the string “Preview Experience”. (TGT-52928)
- Fixed terminology inconsistencies identified in the Simplified Chinese (zh_CN) translation of several text strings. (TGT-52954 & TGT-52955)
Recommendations
- Added a new Recommendations feed status: Partial Import Failed. (KB-2215)
- Fixed an issue affecting the activity-create workflow when adding Recommendations with promotions. When users selected “Promote by Attribute” and added a filtering rule (for example, Parameter Matching), the selected rule type and operand values were not retained after saving and re-editing the activity. Upon reopening, the filtering rule type would change unexpectedly, and operand values would be missing. (TGT-53059)
- Fixed an issue in the Recommendations UI where any promotion created with a single rule was incorrectly interpreted and displayed as a “List of items” promotion type, regardless of the rule’s logic. (TGT-53063)
- Fixed an issue when using the updated Overview UI, the “Download Recommendations Data” button was missing for Experience Targeting (XT) activities that include Recommendations. (TGT-52730 & TGT-52756)
- Previously, the Recommendations UI displayed only the number of entities successfully imported from a feed. However, the backend message format includes both the number of imported entities and the total number of entities in the format:
# of entities imported / # of total entities. Due to this discrepancy, users were only seeing the first value (imported count) in the UI, which led to confusion. The UI now displays both numbers. (TGT-53073)
Reports
- Fixed an issue where selecting “Export order details to CSV” from the Reports page resulted in an empty file being downloaded. This issue occurred even when valid order data was present in the activity. (TGT-52225)
- Fixed an issue when attempting to save an activity after creating and assigning a new reporting audience. The error message returned was: “Access denied. To perform this operation, all of the following privileges are required: [editor].” This issue occurred despite the user having approver-level access. (TGT-53103)
Visual Experience Composer (VEC)
-
Resolved an issue where applying a modification to a view would result in the view being duplicated and the activity returning an “Invalid user input” error. This fix ensures that view modifications are applied correctly without triggering duplication or validation errors. (TGT-52886)
-
Fixed an issue where custom code modifications were incorrectly displayed for the wrong experience. Specifically, changes intended for one experience were shown in a different experience, leading to confusion and potential misconfiguration of live activities. (TGT-52776)
-
Fixed an issue that prevented editing or saving custom code modifications in the New VEC UI. Specifically:
- After editing a custom code block and saving, the changes were not reflected in the UI or in the QA preview.
- In some cases, modifications could not be deleted unless the activity was closed and reopened.
- As a workaround, users had to copy the code, delete the modification, and recreate it manually with the updated content. (TGT-53072)
-
Fixed an issue where editing and saving custom code caused the Modifications panel to become unresponsive. (TGT-53075)
-
Fixed an issue where modifications made to custom code in variant experiences were unintentionally reflected in the Control experience. This caused unintended changes in delivery behavior. The Control experience now remains isolated from custom code edits made to other experiences. (TGT-52413)
-
Fixed an issue where modifications made to one experience (for example, Experience B) were unintentionally duplicated to another experience (Experience A) if the user clicked on the second experience before the editor fully loaded. This behavior could also result in modifications being lost if the initially selected experience had no changes. (TGT-52597)
-
Fixed an issue where changes made in the Modifications step of activity creation were not consistently saved. In some cases, after completing all steps and clicking Save, the custom script added in the Modifications section would not reflect on the live site, despite no visible errors during the save process. (TGT-52661)
-
Fixed an issue where custom code changes were not saving correctly and were unintentionally mirrored across multiple experiences within the same activity. Additionally, users encountered access issues when opening or refreshing certain activities, resulting in blank screens. These issues have now been resolved to ensure stable activity editing and accurate experience isolation. (TGT-52594)
-
Fixed an issue where users were unable to browse to a different URL while in Browse Mode. This prevented testers and editors from validating or previewing alternate pages within the same activity session. (TGT-53052)
-
Fixed an issue where multiple Visual Experience Composer (VEC) instances opened simultaneously during activity creation. This issue occurred when users disabled the Enhanced Experience Composer (EEC) and removed the trailing slash from the website URL in the Page Delivery step. (TGT-52782)
-
Fixed an issue where the Revenue metric dropdown in the Goals & Settings step would incorrectly default to Revenue per Visit (RPVISIT), even after the user selected a different metric. issue occurred when collapsing and re-expanding the metric configuration panel, causing the previously selected value to reset. (TGT-52811 & TGT-52878)
-
Fixed several issues in the activity-create workflow related to offer naming and content translation in Automated Personalization (AP) and Multivariate Testing (MVT) activities:
Key Issues Addressed:
- Creating multiple HTML Offers with the same name (for example, “Experience”) triggered a “Duplicate offer names are not allowed” error, but the UI did not clearly indicate which offers were causing the conflict.
- Renaming offers via the right panel updated the name in the UI, but the change was not reflected in the Manage Content tab or the Offers tab, causing persistent validation errors.
- In MVT activities, although the duplicate name error did not persist after renaming, the UI still failed to reflect updated offer names consistently across tabs. (TGT-52933)
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
The following resources let you see what’s coming in the next Target release.