51黑料不打烊

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. 51黑料不打烊 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
  51黑料不打烊 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 51黑料不打烊 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鈥檙e 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 51黑料不打烊 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

• Improved user attribution for AEM Experience Fragment offers. Resolved an issue in the VEC where the 鈥淟ast updated鈥� field for AEM Experience Fragment (XF) offers incorrectly displayed a Code ID instead of the user name. This discrepancy occurred during offer selection in the updated UI, creating inconsistency with the legacy UI and HTML offers, which correctly showed the name of the last editor. This fix ensures consistent user attribution across offer types, improving transparency and alignment with expected behavior. (TGT-52880 & TGT-52898)

See details

• Offer Decision error resolved for ODE offers. Resolved an issue where Offer Decision Engine (ODE) offers injected through Target returned a 400 error due to missing format metadata. The error message indicated that the MIME type was null, preventing successful processing of offer decisions. This fix ensures proper handling of offer metadata, restoring functionality for personalized content delivery and enabling uninterrupted execution of marketing campaigns. (TGT-53635)
• ODS offer rendering issue resolved. Resolved an issue where Offer Decision Service (ODS) offers created via 51黑料不打烊 Journey Optimizer (AJO) were not rendering when activities were built using the VEC in the updated UI. The same configuration worked correctly in the legacy UI, leading to confusion and blocked campaign execution. This fix ensures consistent offer delivery across both UI versions, restoring expected behavior for AJO-driven personalization.

See details

• Download option restored in reports section of the updated Reports overview UI. Resolved an issue in the new overview UI where the Download button was missing from the Reports section, preventing users from exporting attribute importance scores. This update restores full export functionality, enabling streamlined access to downloadable data for analysis and reporting. (TGT-53222)

• Download full CSV report button restored in the Important attributes view. Resolved an issue in the updated activity creation UI where the Download full CSV report button was missing from the Important Attributes section in the reports view. This fix restores access to downloadable insights, ensuring consistent functionality across both the updated and legacy UIs. (TGT-53238)

• Resolved UI issues affecting Auto Target reporting in the updated overview UI. Fixed multiple UI issues in the updated overview interface impacting Auto Target activity reporting. These fixes include:

  • Missing lift and confidence metrics in summary reports
  • Incorrect color indicator for the 鈥渕odels built鈥� checkbox
  • Non-functional graph report despite data variance in Analytics
  • Missing download link for Automated Segments and Important Attributes reports
  • Broken Automated Segments report display

  These fixes restore expected reporting behavior and improve visibility into Auto Target performance across the updated UI. (TGT-53484)

See details

• Form validation corrected for parameter presence conditions in updated UI. Resolved an issue in the updated UI where selecting 鈥淐ustom mbox parameter value is present鈥� or 鈥淧arameter is present鈥� incorrectly required customers to enter a value. This behavior conflicted with the intended logic, which simply checks for the existence of a parameter regardless of its value. The fix aligns form validation with expected behavior, enabling smoother activity setup and supporting full adoption of the updated UI. (TGT-53638)

• Form logic corrected for parameter presence rules in page delivery." Resolved an issue in the updated UI where selecting page delivery rules such as 鈥淧arameter is present,鈥� "Parameter is not present,鈥淧arameter value is present,鈥� or 鈥淧arameter value is not present鈥� incorrectly required users to enter an additional parameter value. This behavior was inconsistent with the legacy UI and contradicted the intended logic of detecting parameter presence without specifying a value. This fix restores expected rule configuration behavior, streamlining activity setup and improving usability. (TGT-53640)

• Validation logic improved for multi-page rule builder in the updated UI. Resolved multiple validation issues in the multi-page rule builder within the updated UI. These fixes include:

  • Preventing rule creation when the mbox parameter is empty
  • Displaying appropriate error messages for invalid rule states
  • Correcting validation logic for unary and parameter-based operators that don鈥檛 require operand values
  • Enabling hash fragment rules with unary operators by restoring save functionality

  These updates ensure accurate rule configuration and improve usability across complex page delivery scenarios. (TGT-53722)

• Location rename issue resolved in A/B and MVT activities. Fixed a bug in the updated UI where renaming a location in an A/B Test or Multivariate Test (MVT) activity did not persist after navigating between the location list, targeting, and back. This update ensures that location name changes are saved and consistently reflected throughout the activity workflow. (TGT-52367)

• Location name persistence fixed for MVT and AP activities in the updated UI. Resolved an issue in the updated UI where location names edited in Multivariate Test (MVT) and Automated Personalization (AP) activities were not saving correctly. After renaming a location, navigating between tabs, such as Targeting and Experiences, caused the names to revert to their previous state. This fix ensures consistent location naming across tabs and improves reliability during activity setup. (TGT-52927)

• Location labeling corrected in the manage experiences panel for MVT activities. Resolved an issue in the updated UI where the Manage Experiences panel in Multivariate Test (MVT) activities displayed inconsistent location numbering. This fix ensures that location labels are sequential and correctly aligned with user-defined modifications, improving clarity and usability during experience setup. (TGT-52929)