Target Standard/Premium 25.2.3 (February 26, 2025)

This release includes the following updates:

  • Resolved an issue preventing activity updates post Target 25.2.1 release for some activities. (TGT-51781)
  • Resolved an issue where all in-state audience changes were removed upon canceling the activity-creation process (selecting Cancel instead of Add Audience). (TGT-51769 & TGT-51770)
  • Resolved an issue where the Visual Experience Composer (VEC) failed to load for some activities, particularly when custom code was used. issue led to the VEC displaying a blank screen or the Target UI reverting to its older version. (TGT-51758)
  • Resolved an issue where modifications were discarded after editing page delivery for audiences. (TGT-51756)
  • Resolved an issue where all non-metric audiences (page and experience audiences) were removed from activities upon changing a metric type on the Goals & Settings page. (TGT-51753)
  • Resolved an issue where clicking Cancel while editing an activity navigated the Target UI to the Activities List instead of the Activity Details page. (TGT-51731)
  • Resolved an issue preventing customers from downloading reports via the Export Reports to CSV option. (TGT-51708)
  • Resolved an issue in the Form-Based Experience Composer where Target Standard customers were incorrectly shown as using Properties, a Target Premium feature. (TGT-51678)
  • Fixed an issue that blocked Adobe Experience Platform attributes from displaying when creating new offers. (TGT-51665)
  • Moved all active filters for Recommendations inventory to the quick search, aligning the UI with Catalog Search instead of the Filter rail. (TGT-50723)

at.js version version 2.11.7 (February 26, 2025)

This release includes the following update:

  • Fixed Telemetry logging when localStorage is not available. Telemetry was causing an issue for some customers that had localStorage disabled in their browsers.

For information about this and previous at.js releases, see at.js version details.

Target Standard/Premium 25.2.1 (February 17, 2025)

This release includes the following updates:

  • Activities user interface update
  • Recommendations user interface update

Activities user interface update

As the Adobe Target UI modernization effort continues, we are pleased to announce the general availability of the updated Activities User Interface.

NOTE
Starting February 17, customers will gradually have access to the new Activities UI. To ensure a seamless rollout for all customers, this release will be deployed in controlled stages. The first stage will upgrade the initial group of Target customers to the new Activities UI. Subsequent stages will upgrade the remaining customers.

Based on the latest Adobe Spectrum design system, the update standardizes previously inconsistent design patterns, while adding new enhancements, such as:

Activities refresh

Recommendations user interface update

As the Adobe Target UI modernization effort continues, we are pleased to announce the general availability of the updated Recommendations User Interface.

NOTE
Starting February 17, customers will gradually have access to the new Recommendations UI. To ensure a seamless rollout for all customers, this release will be deployed in controlled stages. The first stage will upgrade the initial group of Target customers to the new Activities UI. Subsequent stages will upgrade the remaining customers.

Based on the latest Adobe Spectrum design system, the update standardizes previously inconsistent design patterns, while adding new enhancements, such as:

Recommendations UI refresh

Target Standard/Premium 25.1.1 (January 9, 2025)

This release includes the following updates:

Offers Library user interface update

To enhance the user experience for Adobe Target users, this release updates the Offers Library user interface.

NOTE
To ensure a seamless rollout for all customers, this release will be deployed in controlled stages. The first stage upgraded the initial group of Target customers to the new Offers UI. Subsequent stages will upgrade the remaining customers.

Using the latest Adobe Spectrum design system, this update standardizes inconsistent design patterns and introduces new enhancements, including the following:

  • Bulk offer management: Select and delete or move multiple offers simultaneously.

  • Code Editor upgrades: Refreshed HTML and JSON editors with syntax highlighting and line numbering.

  • Improved offer cards: Enhanced quick information and detail cards for easier information access.

  • Persistent search and filters: Adds session-persistent search and filter options.

For more information see Offers and the sub-articles in this section. All Offers articles in this section have been updated to reflect these UI changes.

Here’s a short video that highlights the changes in this release:

Offers UI refresh video

Release notes - 2024

Adobe Experience Platform Web SDK __view__ scope optimization (October 22, 2024)

Between July 22, 2024 and August 15, 2024, the Target team optimized the __view__ scope, enhancing the accuracy of activity impression, visit, and visitor reporting. This optimization aims to automatically capture reporting data for auto-rendered propositions and should be transparent to most accounts.

All new Adobe Experience Platform Web SDK customers will have this optimization enabled. However, customers who migrated from at.js and have not followed the implementation steps below have the optimization disabled. We urge these customers to review their implementations by February 3, 2025. After this date, we will enable the optimization for all customers. Failure to review and adjust implementations by then might impact reports, as mentioned below. Please contact Adobe Customer Care if you need to confirm whether your implementation is affected or if you require more time to adjust your implementation.

IMPORTANT
If you cannot complete your implementation review and resolve any issues by February 3, 2025, you can request a one-time, six-month extension. Ensure that your request is submitted by January 31, 2025. Adobe will review and decide on your request.

To benefit from this optimization in case of manual proposition rendering, review your Platform Web SDK implementation to ensure that you are sending notifications after manually rendering experiences or when using the applyPropositions method (or the corresponding Launch action as a helper) to render experiences.

The most-common scenarios when experiences are manually rendered include:

  • Using JSON offers
  • Using a custom decision scope in an activity created in the Form-Based Experience Composer
  • Not using renderDecisions: true when fetching an activity created using the Form-Based Experience Composer that uses the global __view__ scope

If notifications are not implemented as documented in Render personalized content in the Data Collection guide, reporting data might be missing in Target and in Analytics for Target reporting (A4T). In certain scenarios, you might notice an incorrect traffic split because the reporting data is not captured. Or, in other scenarios, reporting the same event repeatedly.

Depending on your implementation, check for Analytics and A4T reporting impacts.

The Platform Web SDK supports two implementation types for rendering experiences and personalizations:

  • Single call for personalization and measurement.

    Initially recommended, the single-call approach for the Platform Web SDK is scheduled to be deprecated in favor of the split-call approach. Adobe advises all new implementations to use the new split-call approach and recommends that existing customers transition to the split-call method as well.

    If you continue to use the single-call approach, you might notice the following unexpected changes in your Analytics reports:

    • A dip in bounces.
    • A4T and Page View hits not stitched together, making it challenging to perform certain breakdowns and correlations of your A4T reports using Analytics eVars and events.
  • Split calls (also known as top and bottom of page events).

    This implementation type is the new split-call implementation approach recommended by Adobe. With this approach, the new optimization does not impact Analytics or A4T reports.

If you have questions, contact Adobe Customer Care. (KB-2179)

at.js version 2.11.6 (September 29, 2024)

  • Fixed an issue that prevented Target from operating correctly with redirect offers within the Visual Experience Composer (VEC) or Form-Based Experience Composer.

For more information about at.js releases, see at.js version details in the Adobe Target Developer Guide.

Target reporting in Adobe Customer Journey Analytics (May 8, 2024)

The integration between Adobe Customer Journey Analytics and Target provides powerful analysis and timesaving tools for your optimization program.

The primary benefits of using Customer Journey Analytics as the reporting source for Target are:

  • Marketers can dynamically apply Customer Journey Analytics success metrics to Target activity reports at any time. It is not required to specify everything before running the activity.
  • Marketers can take advantage of Customer Journey Analytics features, such as the Experimentation Panel, to further analyze their website personalization.

For more information, see Target reporting in Adobe Customer Journey Analytics.

Visual Experience Composer helper extension (April 23, 2024)

The legacy Target Visual Experience Composer helper extension was created using Manifest V2. Google announced that it will no longer allow extensions created using Manifest V2 starting in June 2024. For more information, see Visual Experience Composer helper extension.

Adobe recommends that customers move to the newer Visual Editing Helper extension as soon as feasible.

Updates for Browser:iPad and Browser:iPhone in Browser audience attributes (April 30, 2024)

Updates
Details
Browser:iPad and Browser:iPhone updated in Browser attributes used when creating audiences.

Adobe Target lets you target on any of several category attributes, including visitors who use a specific browser or browser options when they visit your page.

Starting with the Target Standard/Premium 24.3.1 (March 4-6, 2024), built-in audiences created using the Target UI, such as Browser:iPad and Browser:iPhone will be updated to perform proper targeting for iPad and iPhone using profile.mobile.deviceVendor, profile.mobile.isMobilePhone and profile.mobile.isTablet.

This update requires no action on the customers’ side.

Important: For customers to perform proper targeting for iPad and iPhone in profile scripts (and JavaScript segments), manual changes must be made by the customer by April 30, 2024. For examples of alternate settings that must be manually changed, see Updates for iPad and iPhone in Browser audience attributes.

Visual Editing Helper extension (March 14, 2024)

This release contains the following enhancements and fixes for the Adobe Experience Cloud Editing Helper extension for Google Chrome:

  • Enhanced the iFrame loading mechanism when performing authoring in customers’ websites.
  • Fixed an issue that caused the extension to duplicate cookies while performing authoring in the Visual Experience Composer (VEC).

Target Standard/Premium 24.3.1 (March 4-6, 2024)

This release contains the following enhancements and fixes:

  • Fixed the logic that computes the number of unique selectors in an activity. (TGT-47878)
  • Fixed an issue that caused Multivariate (MVT) activities configured with Analytics for Target (A4T) reporting to not display properly. (TGT-47490)
  • Improved the warning message displayed in reporting when an experience with no traffic is used as the control experience. (TGT-47537)
  • Added many backend and localization fixes.

Target Standard/Premium 24.1.1 (January 22, 23, & 25, 2024)

This release contains the following enhancements and fixes:

  • Analytics for Target (A4T) activities with revenue goal metrics did not display “Revenue” as the column name and the revenue metric did not display in ($) format in reporting. This was a cosmetic issue that has been remedied. (TGT-46995)
  • Fixed an issue that caused reporting date intervals to not work correctly. (TGT-47396)
  • Fixed an issue that caused the incorrect status to display on the All Activities page after customers activated or deactivated an activity using the More Actions icon. (TGT-47367)
  • Fixed an issue that caused the Important Attributes report to not display for a single customer. (TGT-47272)
  • Fixed an issue that caused an “Invalid payload” message to display when a single customer tried to enable “Require Authentication.” (TGT-47195)
  • Updated numerous localized strings in the Target UI.

Release notes - 2023

Target Standard/Premium 23.11.1 (November 13 & 14, 2023)

This release is scheduled for the following days:

  • November 13: Asia-Pacific (APAC) region
  • November 14: Americas region
  • November 14: Europe, Middle East, and Africa (EMEA) region

This release contains the following enhancements and fixes:

  • Enhanced the Activity QA feature to support disallowing duplicate offers for experiences in Automated Personalization activities. (TGT-46627)

  • Added a tooltip in the Target UI to help customers understand why there might not be data available in activity reports if no traffic is allocated to the control experience. A link to more information is included in the tooltip: Why is there no data available for my activity’s report?. (TGT-46610)

  • Fixed an issue that prevented activities from displaying properly on the Activities page for a few customers. (TGT-46830)

  • Fixed the following issues that affected activities that use Analytics for Target (A4T) as the reporting source:

    • Fixed an issue that prevented some customers from viewing reporting data. (TGT-46557)
    • Fixed an issue that sometimes caused the View in Analytics link on activity reporting pages to not function properly. (TGT-46731)
    • Fixed an issue that prevented data for Lift and Confidence to display properly in the Target UI. (TGT-46592, TGT-46554, & TGT-46586)