�۶���Ƶ

See details

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 transition permanently to the updated UI. �۶���Ƶ 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.

  note important
  IMPORTANT
  �۶���Ƶ 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 �۶���Ƶ Customer Care with any concerns or if you anticipate issues during this transition.

Limitations of the UI toggle behavior limitations

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 are published to your website. However, these updates are not visible in the legacy UI if you switch back; only the last updates made from the legacy UI appear there.
• Consistency of activity details: The most recent changes, regardless of which UI you use, are reflected on your live website. However, the legacy UI only shows the latest changes made from within that version. This situation 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 �۶���Ƶ 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.

See details

• Fixed activity-loading issue in updated Target UI: Fixed an issue in the updated Target UI where certain activities failed to load when attempting to edit. This issue caused customers leaving users in an indefinite loading screen. This issue impacted multiple activities and was reported to occur inconsistently across customers. With this fix, affected activities now load properly, allowing seamless editing and reducing disruption to activity workflows. (TGT-53209)
• Fixed save error in activity-create process due to optionLocalId validation: Fixed an issue in the activity-create process that prevented customers from saving changes due to a backend validation error: OptionLocalIdReferentialIntegrity.ABActivity - Invalid optionLocalIds: This issue occurred when modifying specific elements within an activity, resulting in a failed save operation. The fix ensures that optionLocalId references are now correctly validated, allowing customers to save activities without encountering this error. (TGT-53293)
• Fixed crash in activity-create process caused by invalid option references when switching pages: Fixed an issue in the activity-create process that caused the UI to crash after switching pages three times during editing. The crash was triggered by invalid option references, resulting in console errors such as “Option with localId ‘7’ not found.” With this update, customers can now switch between pages and apply modifications without encountering system failures or interruptions. (TGT-53295)
• Fixed save error in activity-create process caused by invalid user input when editing experiences: Fixed an issue in the activity-create process where customers were unable to save changes to an activity due to an invalid user input error. The error occurred when modifying experiences in the updated UI, preventing updates from being committed. The activity can now be saved successfully, allowing customers to edit and publish without interruption. (TGT-53267)
• Fixed loading issue in activity-create process that blocked editing in updated UI: Fixed an issue in the activity-create process where customers were unable to edit activities in the updated UI due to a continuous loading screen. Customers can now open and modify activities without encountering loading failures. (TGT-53415)
• Fixed experience requirement issue in activity-create process for AP activities in updated UI: Fixed an issue in the activity-create process where Automated Personalization (AP) activities required two locations instead of two experiences in the updated UI. This behavior blocked use cases where customers configured a single location with multiple offers, which was previously supported. The requirement has been corrected to match the original functionality, allowing customers to proceed with AP activities using two experiences regardless of location count. (TGT-53429)
• Fixed tracked element field behavior in Click Track mode to prevent unsaved input and improve clarity: Fixed an issue in the activity-create process where the Tracked Element field in Click Track mode was editable but did not retain the entered name, causing confusion for customers. The field is now disabled to prevent unsaved input, and the naming of selected elements has been clarified to improve goal configuration and tracking accuracy.** (TGT-53458)
• Fixed issue in activity-create process that blocked naming of tracked components in Click Track mode: Fixed an issue in the activity-create process where customers were unable to name tracked components in Click Track mode. After entering a name, the field appeared editable but did not retain the input, defaulting to generic labels like “MY PRIMARY GOAL 0” in edit mode. The tracked element field is now disabled, and naming behavior has been clarified to improve goal setup and tracking accuracy. (TGT-51396)

See details

• Fixed issue in activity-create process that allowed unintended HTML editing of AEM-exported fragments: Fixed an issue in the activity-create process that allowed customers to edit the HTML of Experience Fragments (XFs) exported from �۶���Ƶ Experience Manager (AEM) within Target. This behavior was unintended, as XFs should remain locked for editing once published from AEM. The fix ensures that the “Edit HTML” option is no longer available for AEM-exported fragments, preserving content integrity and expected governance. (TGT-53286)
• Fixed intermittent preview issue for XF content in activity-create process within updated UI: Fixed an issue in the activity-create process where XF content intermittently failed to render in preview mode within the updated UI. Although the content delivered correctly, the preview did not consistently display, making it difficult for customers to validate offer setup. XF previews now load reliably, improving confidence and efficiency during activity configuration. (TGT-53318)

See details

• Fixed issue in activity-create process where leading spaces in URLs caused broken QA links: Fixed an issue in the activity-create process where leading spaces in the activity URL were not trimmed properly when saving. This caused invalid QA links and incorrect formatting in the back-end. After the update, URLs are now saved cleanly, preventing broken links and improving the reliability of QA workflows for customers. (TGT-53427)

See details

• Fixed issue in catalog search UI where advanced search failed to provide suggestions: Fixed an issue in the new Catalog Search UI where the Advanced Search feature failed to provide suggestions. Users were required to input exact values with precise spelling, making the search experience cumbersome and error-prone. With this fix, the Advanced Search now offers relevant suggestions as users type, improving usability and reducing friction in locating products. (TGT-52008)
• Resolved multiple UI and filtering issues to improve responsiveness and entity interaction: Resolved several issues, including poor responsiveness of criteria details on small-screen devices, lack of results when selecting “All host groups” in the Environment filter, and inability to interact with entities that have no name. These fixes improve usability across screen sizes, ensure accurate filtering, and allow full interaction with all product entities, enhancing the overall experience for users. (TGT-52992)
• Fixed missing product IDs in Recommendations detail view during activity creation: Fixed an issue in the Recommendations activity-create process where product IDs were missing from the product detail screen, making it difficult for customers to copy or reference product IDs during workflows. Product IDs now appear clearly in the detail view, improving visibility and supporting more efficient product management for customers. (TGT-51964)
• Fixed issue in activity-create process where product messages failed to display in recommendations view: Fixed an issue in the activity-create process where the Message column in the Recommendations view did not display product data, even though messages were present. Customers had to manually remove and re-add the column to temporarily reveal the content, which would often disappear again when scrolling or searching. This update restores consistent visibility of product messages, improving catalog navigation and review workflows. (TGT-52777)
• Fixed issue in activity-create process where selecting ‘All host groups’ returned no results in recommendations view: Fixed an issue in the activity-create process where selecting the “All host groups” environment in the Recommendations view returned no results. Customers can now view product data across all host groups as expected, improving visibility and filtering accuracy during activity setup. (TGT-53006)
• Fixed issue in activity-create process where front-promotion toggle did not persist after saving: Fixed an issue in the activity-create process where disabling the front promotion toggle in activity settings did not persist after saving. Customers attempting to remove the front promotion found the toggle re-enabled upon revisiting the activity, preventing proper customization. This update allows changes to be saved reliably, giving customers full control over promotion settings. (TGT-53215)
• Fixed inconsistent sorting by Last Updated column: Fixed an issue in the activity-create process where sorting the catalog by the Last updated column produced inconsistent results. Customers were unable to reliably organize product data based on update timestamps, making catalog review and management more difficult. Sorting now works as expected, improving accuracy and usability in the updated UI. (TGT-53116)

See details

• Fixed activity loading and Cancel button issues in activity-create process: Fixed an issue in the activity-create process where certain activities failed to load, leaving customers unable to access modifications. Additionally, the Cancel button was unresponsive, preventing customers from stopping the loading process or exiting the edit view. This fix ensures that activities now load reliably and the Cancel button functions as expected, improving overall stability and user experience in the Visual Experience Composer. (VEC)(TGT-53218)
• Fixed experience switching issue in updated VEC UI that blocked editing and disabled Cancel button: Fixed an issue in the updated VEC UI where modifications failed to load when switching between experiences in an Experience Targeting (XT) activity. Customers were unable to edit experiences beyond the one they initially entered, and the Cancel button was either missing or unresponsive. This fix ensures that modifications now load correctly across all experiences and that the Cancel button functions reliably, even without the Helper extension, improving editing workflows and reducing frustration. (TGT-53256)
• Fixed white screen issue when switching between multiple experiences in activity-create process: Fixed an issue where switching between multiple experiences caused a white screen. Also fixed an issue in the activity-create process where customers encountered a white screen when attempting to modify multiple experiences within an activity. This issue occurred after applying changes to two experiences and then selecting a third experience, preventing further edits. The update ensures smooth transitions between experiences, allowing customers to make modifications without interruption. (TGT-53266)
• Fixed issue in VEC where custom code changes were not reliably saved across editing sessions: Fixed an issue where custom code modifications made in the Visual Experience Composer (VEC) were not reliably saved in a single attempt. Customers reported that changes, such as styling updates or HTML edit, were intermittently missing from the website and QA URLs, even after using both the Edit Content and final Save buttons. This regression has been resolved, ensuring that all custom code changes persist as expected across editing sessions.** (TGT-53418)
• Fixed missing triggerViews in updated UI during activity creation: Fixed an issue in the activity-create process where triggerViews were not appearing in the updated UI, even though they were correctly implemented on the page. This impacted multiple customers and made it difficult to validate view-based triggers during activity setup. TriggerViews now display as expected, allowing customers to complete and test their configurations reliably. (TGT-53239)
• Fixed view-loading issue in activity-create process for specific webpages in updated UI: Fixed an issue in the activity-create process where views were not loading in the updated UI for specific webpages, despite being correctly implemented and visible in delivery or interact calls. This affected multiple customers and made it difficult to validate view-based targeting. Views now populate consistently across supported pages, improving reliability during activity setup. (TGT-53246)
• Fixed intermittent view loading issue in activity-create process in updated UI: Fixed an issue in the activity-create process where views intermittently failed to appear in the updated UI during activity editing. Although the correct view name was present in the network payload, it was not consistently recognized in the interface, impacting customers’ ability to configure view-based personalization. Views now appear reliably, supporting smoother setup and validation workflows. (TGT-53223)
• Fixed issue in activity-create process where tracked action names were not saved in updated UI: Fixed an issue in the activity-create process where tracked action metrics could not be saved in the updated UI. After naming a tracked element and saving the activity, the name would reset to a default label when reopened, causing confusion and disrupting goal configuration. Tracked actions now retain their assigned names, allowing customers to set and manage conversion metrics accurately. (TGT-53453)

See details

• Fixed several issues with the updated UI, including errors when deleting page types due to spacing in input values, unreliable activity copying between workspaces, and malfunctioning page delivery rules in QA environments. (TGT-52703)
• Fixed an issue in the updated Target UI where users with the Editor role were able to access and attempt to edit live activities, which should be restricted. The activity list and overview screens incorrectly displayed edit options for live activities, leading to potential unintended changes. (TGT-53055)
• Fixed an issue in the Advanced Search UI where selecting the “value is present” or “value is not present” operators prompted users to enter an operand, which should not be required for these conditions. (TGT-51961)
• Fixed an issue in the updated UI where attempts to copy activities from the staging to production workspace consistently failed, even in sandbox environments. Customers encountered various error messages, including “Anonymous audience already used by the activity” and “Invalid audience ID,” despite using valid configurations and having appropriate workspace permissions. (TGT-52394)

See details

• Fixed an issue where Experience Fragment (XF) content fails to render in the Visual Experience Composer (VEC) preview, despite working correctly in content delivery. (TGT-53318)

See details

• Fixed a localization issue where the “Add Promotion” button in the “Promotions” section appeared unlocalized across multiple language environments in the QA tenant. (TGT-53263)

See details

• Fixed an issue where editing an existing HTML offer via the Visual Experience Composer (VEC) caused all modifications to be removed from content delivery. The changes appear grayed out in the modification tab and are not reflected in QA previews, despite being correctly applied in the legacy UI. (TGT-52863)
• Fixed an issue in the updated Target UI where HTML offer modifications made in the Visual Experience Composer (VEC) did not persist after navigating from the Targeting tab back to Experiences. (TGT-52874)
• Fixed an issue in the updated Target UI where inserting one HTML offer before and another after the same selector caused incorrect location generation. When customers returned from the Targeting tab to the Experience tab, only one selector was retained, resulting in lost modifications and broken content delivery. This behavior differed from the legacy UI, which correctly preserved both modifications with distinct location identifiers. (TGT-52891)
• Fixed an issue in the updated Target UI where clicking an added offer within the Modifications rail caused the right-hand Configuration panel to intermittently appear and disappear, making it difficult to interact with the offer settings. (TGT-53288)
• Fixed an issue where HTML offers added to audience-specific variations within an activity did not consistently save or appear in the modification section. After switching between audiences during editing, previously applied offers sometimes disappeared or failed to render, disrupting validation and delaying activity readiness. (TGT-53440)
• Fixed an issue where copying an activity that included offers resulted in duplicate offers being created in the new activity. This behavior caused unnecessary clutter and confusion, particularly when moving activities between workspaces. The fix ensures that Target offers are now correctly copied into the destination workspace without duplication, streamlining activity management and improving workflow efficiency. (TGT-53454)

See details

• Fixed an issue in the updated VEC that prevented customers from applying modifications to Single Page Application (SPA) views. While activities created in the old UI supported view-specific targeting, the new UI failed to detect or allow edits to those views, with the view-switching controls appearing disabled. (TGT-52556)

See details

• Fixed an issue where modifications made to experiences within the Visual Experience Composer were either not visible or appeared inconsistently in the UI. (TGT-TGT-53381)
• Fixed an issue in the updated VEC where the Manage Content section failed to display alt text for experience thumbnails. This issue made it difficult for users to identify documents, especially when filenames were long or truncated. (TGT-52291)
• Fixed an error where customers encountered incorrect validation errors when configuring page delivery rules in VEC activities. Specifically, operators like “equals any of” and “does not equal any of” triggered “Invalid input for the operator type” when entering text values, even though text should be supported. (TGT-52629)
• Fixed several issues that caused inconsistent behavior in the Modifications panel of the updated UI when selecting offers using the “Select an offer” button. Instead of replacing the existing offer, the UI added a duplicate, and attempted to interact with either offer resulted in console errors such as selectorNotFound. Additionally, some offers do not display the “Select an offer” button, showing only editable properties. (TGT-53321)
• Fixed an issue in the updated Target UI where HTML code changes made during activity setup did not persist on variation pages, even though they saved correctly for control groups. Despite multiple attempts and recreating tests without page groupings, the variation pages consistently failed to retain modifications, impacting content delivery and QA validation. (TGT-53436)
• Fixed an issue in the updated VEC where the “equals any of” operator in page delivery rules fails to accept input values. When configuring customer parameters across all mboxes, selecting this operator resulted in an “Invalid Input” error, preventing rule creation. (TGT-52623)

See details

• Improved the workflow when copying activities between workspaces. Copy activities between workspaces previously led to sync errors due to missing audiences and unassigned properties. This update introduces a smarter, more intuitive workflow that ensures copied activities are properly configured and ready for publishing. (TGT-47094)
• Fixed an issue where customers were unable to copy activities between workspaces due to a failure in the copyActivityBatchOperations mutation. Attempts to duplicate activities resulted in a server error (500) and a null response payload. (TGT-52405)
• Fixed an issue where activities failed to sync when offers referenced in the configuration were not accessible within the selected workspace. This caused publishing errors and left activities in a failed state. (TGT-52535)
• Fixed multiple issues when copying activities between workspaces in the updated Target UI. Customers encountered errors related to audience access, particularly with live activities, and incorrect privilege validation, even when the user had “Approver” roles in both source and destination workspaces. (TGT-53002)
• Fixed an issue in the updated UI where copying activities within the same workspace unnecessarily duplicated associated offers and audiences. (TGT-53457)
• Fixed an issue to address cases where ad-hoc (anonymous) audiences were not correctly copied between non-default workspaces or from non-default to default workspaces. While earlier updates ensured proper duplication for default-to-non-default and same-workspace scenarios, this enhancement focused on preserving combined audience configurations that span multiple workspaces. The fix ensures consistent audience behavior and accurate targeting across all workspace transitions. (TGT-53268)