Release notes for previous releases

Release notes for previous Adobe Target releases, including release notes for Target Standard/Premium, the Target platform, and the Target Javascript library (at.js).

Release notes are arraigned in descending order by month and year of release.

Release notes - 2025

Target Standard/Premium 25.3.1 (March 3, 2025)

This release includes the following fixes and updates:

• A combined audience can include subgroups, each containing multiple audiences. This release fixed an issue that prevented subgroup audiences from displaying in the Rules dialog box. (TGT-51813)
• Resolved an issue where some experience audiences were replaced with All Visitors when opening older activities. (TGT-51812)
• Resolved an issue that prevented editing activities with activity-only audiences. (TGT-51807)
• Resolved an issue that prevented editing page head modifications in the updated Target UI. (TGT-51797)
• Resolved a null error that occurred when duplicating an experience, deleting another experience, and then trying to save the activity. (TGT-51796)
• Resolved an issue that prevented audience exclusion rules from displaying in the audience’s info panel during the Targeting step of creating activities. (TGT-51579)
• Updated error messages localized in Korean. (TGT-51701 & TGT-51699)

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.

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

• Redesigned reporting for better insights into activity results.

• Updated Change Log page, now getting the information from the Audit Query API for real-time insights.

• Customizable list views to for better flexibility across different team needs.

• Enhanced quick info and detail screens for easier access to information.

• Session-persistent search and filter options.

• Completely rebuilt Visual Editing Composer with support for latest security updates from browser providers and a modern user interface.

  For information about how the updated VEC differs from the previous version, see:

  • Visual Experience Composer changes
  • Visual Experience Composer options

• Updated Chrome extension supporting Manifest V3 for increased security and improved support for first-party cookies.

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.

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

• The product catalog search now features an updated database allowing a real-time synchronization of products.
• Recommendations objects (Criteria, Designs, Collections, and Exclusions) created over API are now available in the UI.
• Recommendations settings have been consolidated under the Administration section.
• Customizable list views for better flexibility across different team needs.
• Refreshed HTML and JSON code editors with syntax highlighting and line numbering.
• Enhanced quick info and detail screens for easier access to information.
• Session-persistent search and filter options.

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.

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:

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.

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)

Activities page user interface refresh (October 25, 2023)

As part of the Adobe Target team’s ongoing effort to improve the user-experience for Target users, this release refreshes the Activities page in the Target UI. This update unifies and standardizes design patterns that were previously inconsistent, while adding new enhancements.

Starting Wednesday, October 25, a percentage of customers will have access to the new UI with additional customers getting access in the next several days.

For more information see Activities.

Target Standard/Premium 23.10.2 (October 24, 2023)

This release contains the following enhancements and fixes:

• Enhanced the new Activities UI so that the Visual Experience Composer (VEC) opens with the default settings for selectorCriteria when creating a new activity. (TGT-46586)
• Fixed an issue that prevented some customers from editing elements in Composer mode when using the VEC. (TGT-46470)
• Added the ability to specify a generic preferred selector when using custom attributes. (TGT-46545)
• Fixed an issue that sometimes prevented an Auto-Target report that uses Analytics for Target (A4T) from displaying in the Target UI, even though the report displayed correctly in Adobe Analysis Workspace. (TGT-46494)
• Updated various localized strings in the Target UI. (TGT-18899)

Target Standard/Premium 23.9.4 (October 4-6, 2023)

This release contains the following enhancements and fixes:

Feature	Details
Recommendations implementation pattern	The Recommendations implementation pattern using at.js articles help you understand and create your Adobe Target Recommendations implementation when using the at.js JavaScript library. For more information, see Recommendations implementation pattern using at.js overview in the Adobe Target Developer Guide.

• Added Visual Experience Composer (VEC) enhancements for dynamic frameworks. (TGT-44064)
• Fixed an issue that caused the selected date in the getViewInAnalyticsId request to not update properly. This fix helps recompute the Analytics link in reporting when the date range and metrics report settings are changed. (TGT-46246)

Target Standard/Premium 23.9.3 (September 18, 2023)

This release contains the following enhancements and fixes:

• Enhanced the Visual Experience Composer (VEC) to support Lightning Web Components (Light DOM). (TGT-45422)
• Fixed an issue that caused VEC actions to be applied in the incorrect order. In some cases, the VEC applied some modifications asynchronously and adding extra modifications to an element caused errors if that element displays after an Insert action. Also fixes the VEC URL that now updates when clicking anchor links. (TGT-45983)
• Fixed an issue with the VEC Overlay feature, which now supports elements in Shadow DOMs. (TGT-45202 & TGT-45262)
• Fixed an issue when opening a Single Page Application (SPA) page in the VEC and then going to Browse mode caused the Back and Forward arrows to not function correctly. (TGT-45956)
• Fixed an issue that prevented some web pages from loading in the VEC. (TGT-45983)

Target Standard/Premium 23.9.2 (September 12-14, 2023)

This release contains the following enhancements and fixes:

• Changed the Analytics API to the new Analytics API version 2.0. (TGT-45345)
• Fixed issues that impacted Automated Personalization (AP) activities for some customers, including timely syncing the activity on the Target backend and delivering the expected experience in preview links. (TGT-46202)

Target Standard/Premium 23.9.1 (September 6-11, 2023)

This release contains the following enhancements and fixes:

• Fixed an issue that caused inconsistent reporting data in the Target UI and the Adobe Analytics UI for Auto-Allocate activities that use Analytics for Target (A4T) as the reporting source. (TGT-46112)
• Increased the timeout for PUT calls to the Target Delivery API to 15 seconds to avoid timeout errors. (TGT-46091)
• Fixed an issue that prevented the URL from consistently updating when browsing through a Single Page Application (SPA) website. (TGT-45417)

Adobe Target Edge planned infrastructure upgrade

The planned edge infrastructure upgrade requires additional IP or domains to be allow-listed. Review and allow-list the NAT and IP/domains for edge deployments 41-48. Infrastructure upgrades begin August 9, 2023.

For more information, see Allowlist Target edge nodes in the Adobe Target Developer Guide.

Target Standard/Premium 23.8.1 (August 9, 2023)

This release contains the following enhancements and fixes:

• Fixed an issue that sometimes prevented activities from syncing properly, as shown in the “Status” column on the Activity list page. (TGT-46010 & TGT-44831)
• Fixed an issue that sometimes prevented the “View in Analytics” link from displaying on the Reports page of activities that use Analytics for Target (A4T) as the reporting source. (TGT-45808)
• Adjusted the presentation of values in tables to display as percentages instead of numbers with decimals. For example, 8% instead of .08. (TGT-45548)
• Fixed an issue that prevented customers from using keyboard focus to move to the next element in the Goals & Settings page for Experience Targeting (XT) activities. (TGT-44526)
• Fixed an issue that caused keyboard loss of focus after opening the “Add audiences” dialog while creating an activity. (TGT-44525)

Target Standard/Premium 23.7.1 (July 24-26)

This release contains the following enhancements and fixes:

• Improved search when navigating elements using the DOM path in the Visual Experience Composer (VEC) to include shadow DOM elements. (TGT-45262)
• Fixed an issue that prevented the Change Overlay setting from working properly. (TGT-45202)
• Fixed an issue that prevented some customers from downloading activity reports after receiving the following error message: “User is not authorized to access the report.” (TGT-45724 & TGT-45747)

Target Standard/Premium 23.6.1 (June 27-29)

This release contains the following enhancements:

Feature	Details
QA mode for Automated Personalization activities	Adobe Target QA mode is now available for Automated Personalization activities, replacing Preview links functionality. For more information, see Activity QA.

• Performance enhancements to disallow duplicates functionality (including reduction in load time) while managing exclusions in Automated Personalization activities.

Target Standard/Premium 23.5.2 (May 31, 2023)

This release contains the following enhancements and fixes:

• Fixed an issue that caused a blank page to display while generating a Profile API authorization token. (TGT-45387 & TGT-45423)
• Fixed an issue that prevented an image from displaying in the Create Design panel if the image name contains GB 18030 characters. (TGT-44614)
• Fixed an issue in which some GB 18030 symbol characters were incorrectly escaped in Text/HTML in experiences. (TGT-44600)
• Fixed an issue that caused reports for Auto Personalization activities to freeze during analysis. (TGT-44820)
• Fixed an issue that prevented searching for an activity on the Activity page if the activity name contains a square bracket ( [ or ] ). (TGT-44777)
• Fixed an issue that prevented an activity from syncing if the activity’s objective contains special characters. (TGT-44982)
• Fixed an issue that caused no activities to display in the Target UI for the Default workspace for certain customers. (TGT-45286)
• Updated the behavior of the “Disallow Duplicates” flag. Excluded repeating offers flags are updated to allow repeating offers if they are the default content offer (for APIs v3, v4) and allow duplicate options if the options reference the default content offer and have no templates defined. (TNT-46617)
• Fixed an issue in which a query parameter was added to a URL that prevented the page from loading in the Visual Experience Composer (VEC). (TGT-44873)
• Made various localization fixes throughout the Target UI.

Real-Time CDP Profile Attributes shared with Target Real-Time CDP Profile Attributes (June 13, 2023)

This release contains the following enhancement:

Feature	Details
Real-Time CDP Profile Attributes shared with Target	Real-Time CDP Profile Attributes can be shared with Target for use in HTML and JSON offers. For more information, see Share Real-Time CDP Profile Attributes with Target.

Target Standard/Premium 23.5.1 (May 23-25, 2023)

This release contains the following new enhancements and fixes:

• Fixed an issue that prevented certain customers from creating audiences with visitor profiles using “greater than” or “less than” operators. (TGT-45271)
• Made various localization fixes throughout the Target UI.
• Updated the Target UI in various places for an upcoming UI refresh (changes are behind a feature flag until the updates are released).

Target Standard/Premium 23.4.1 (April 25-27, 2023)

This release contains security updates and the following new features:

Feature	Details
AEM Content Fragments for headless personalization and experimentation	Use Adobe Experience Manager (AEM) Content Fragments in Target activities. Combine the ease-of-use and power of AEM with powerful Artificial Intelligence (AI) and Machine Learning (ML) capabilities in Target to aid headless personalization and experimentation. For more information, see AEM Content Fragments.
Adobe Target Developer Guide	The Adobe Target Developer Guide has been relocated to Adobe Experience League. The move to Experience League aids in localization of text in additional languages, unifies search within Experience League to span and offer search results from both the Adobe Target Business Practitioner Guide and the Adobe Target Developer Guide, and provides additional benefits. You will be redirected from the previous location to Experience League automatically. Please update your bookmarks as necessary.

Target Standard/Premium 23.3.1 (March 28-30, 2023)

This release contains the following new features, enhancements, and fixes:

Feature

Details

Optimized A4T metrics for Auto-Allocate and Auto-Target (Release date March 30, 2023)

Target lets you choose metrics based on binomial events or metrics based on continuous events when using A4T for Auto-Allocate and Auto-Target activities. Be aware of the following change in supported metrics: Target preserved the previous behavior for existing activities until September 9, 2023. After this date, activities using non-supported metrics will be discontinued to force existing activity migration to the new behavior. For more information, see “Supported goal metrics” in A4T support for Auto-Allocate and Auto-Target activities. With this feature, the following tutorials have been updated: Setting up A4T reports in Analysis Workspace for Auto-Allocate activities Setting up A4T reports in Analysis Workspace for Auto-Target activities

• Enhanced audience and activity synchronization so that items created in Adobe Experience Platform and Adobe Audience Manager are available in the Target UI quicker. (TGT-44568)
• Enhanced UI to let users remove the Default URL under Administration > Visual Experience Composer > Default URL. This change lets customers change the default URL back to an empty string, which was previously not possible after initial configuration. (TGT-44577)
• Removed restrictions that prevented customers from editing or deleting out-of-the box audiences (audiences with reserved names). (TGT-44655)
• Disabled the “Done” option while loading spinners were visible in the Target UI when creating combined audiences. (TGT-44079)
• Fixed the Language link at the bottom of the Audiences page so that it correctly links to the “Account communication preferences” page. (TGT-43562)
• Resolved an issue that sometimes prevented customers from creating A/B Test activities after selecting the Adobe Analytics option under Administration > Reporting > Reporting Experience Cloud Solution. (TGT-44844)
• Fixed an issue that prevented customers from viewing the last experience in a Multivariate Test activity with many experiences from within the Visual Experience Composer (VEC). The DOM path at the bottom of the VEC sometimes prevented customers from seeing the last experience. (TGT-44578)
• Fixed an issue that caused the Browse URL in the VEC to not reflect the current page that is visible in a normal browser session if the page requires authorization or invokes redirects. (TGT-44350)
• Fixed an issue that prevented customers from changing the Filter Incompatible Criteria setting in Recommendations > Settings. (TGT-44398)
• Fixed an issue that caused POST requests to create Recommendations feeds to fail when using Analytics Classifications with report suites with dots in their names. (TGT-44598)
• Updated links in the Target UI to point to the new Visual Editing Helper extension. (TGT-44459)
• Enhanced security to prevent Server-Side Request Forgery (SSRF) attempts in Recommendations feeds. (TGT-43769)
• Made various localization fixes throughout the Target UI.

at.js version 2.10.2 (March 7, 2023)

• Fixed an issue that caused the trackEvent function to always return an error.

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

Target Standard/Premium 22.15.1 (March 8 & 9, 2023)

This release will be available according to the following staggered schedule:

• March 8: Americas region
• March 9: Europe, Middle East, and Africa (EMEA) region
• March 9: Asia-Pacific (APAC) region

This release contains the following fixes:

• Updates for custom web components authoring with the Visual Experience Composer (VEC):

  • Fixed Shadow DOM elements selection in the VEC by improving the authoring process so there is no dependency on the Target implementation type when authoring the shadow root. Now, selecting Shadow DOM elements in the VEC should work for any website.
  • Fixed an issue that prevented loading HTML elements using #Shadow DOM in the VEC. (TGT-35801)
  • Fixed VEC issues with SPA websites using ShadowDOM. (TGT-43169)
  • Fixed an issue with the Optimization Goal: “clicked an element” that did not properly identify the CSS selector in ShadowDOM.

Known issue: Click-tracking on a shadow root element when using Adobe Experience Platform Web SDK is not working correctly. (TNT-47012)

at.js version 2.10.2 (March 7, 2023)

• Fixed an issue that caused the trackEvent function to always return an error.

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

Target Standard/Premium 22.14.5 (February 13-15, 2023)

This release will be available according to the following staggered schedule:

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

This release contains the following fixes:

• Fixed an issue that caused the following error message even though a property was specified in Automated Personalization (AP) activities: “Errors: At least one property has to belong to a non-default workspace” (TGT-44607)
• Fixed a potential security issue impacting server-side Recommendations feeds. (TGT-43769)

at.js version 2.10.1 (February 2, 2023)

• Fixed a bug in which activities involving audience rules containing parameters with dots in their names were not returning the expected experience, for on-device decisioning.
• Fixed a bug introduced in at.js 2.6.0 in which at.js was firing a delivery call, even when mboxDisable was enabled.

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

Target Standard/Premium 22.13.3 (January 25-26, 2023)

This release will be available according to the following staggered schedule:

• January 25: Europe, Middle East, and Africa (EMEA) region
• January 25: Asia-Pacific (APAC) region
• January 26: Americas region

This release contains the following new features, enhancements, and fixes:

Feature	Details
JSON offer support in Automated Personalization (AP)	Added support for JSON offers in Automated Personalization (AP) activities using the Form-Based Experience Composer. (TGT-41460)
AEM experience fragments	Added the ability to distinguish between Adobe Experience Manager fragment (AEM XF) types that are exported to Target. Instead of the “Experience Fragment” option, Target now lets you filter and search by “HTML XF” and “JSON XF.” (TGT-44132)

• Fixed an issue that caused a “500 error” in A/B Test and Experience Targeting (XT) activities that contain recommendations. This issue was caused when Target failed to properly delete criteria objects from the Target UI and Recommendations backend that are no longer in use. (TGT-44383)
• Removed the location from the displayed offer name in the Offer Level report for Automated Personalization activities. This change makes the report more readable. (TGT-44294)
• Removed the 45-day and 90-day calendar options from the AP and Auto-Target Personalization Insights and Important Attributes reports in the Target UI. Because of usage patterns and to improve performance, these date ranges have been deprecated. The UI has been updated to reflect the currently allowed ranges: 15, 30, and 60 days. (TGT-39357)
• Disallowed the ability to change the Same as Optimization Goal setting on the Goals & Settings page after the activity is live. (TGT-43923)
• Fixed an issue that caused issues with the default workplace in the Target backend when upgrading from Target Standard to Target Premium. (TGT-44081 & TGT-44306)
• Made a change to allow Analytics report suites that contain a dot character “.” in their names to be used in the Target UI to create Analytics classification feeds.
• Changed the link on the Implementation page (Administration > Implementation) for “Implementation Methods with On-Device Decisioning” to point to the page that explains how to use on-device decisioning for all supported SDKs: Node.js, Java, .NET, and Python. For more information, see Getting Started with Target SDKs in the Adobe Target Developer Guide.
• Fixed an issue that caused file-upload issues when using Scene7 and Target.
• Enhanced the accessibility of the Target UI for persons with disabilities by using results from an internal usability audit. These accessibility enhancements include access to features that were previously not accessible via the keyboard, alt text enhancements, the ability to zoom parts of the UI to be more usable, improved keyboard focus, and more. (TGT-42759)
• Made various localization fixes throughout the Target UI.

Release notes - 2022

Models API release (November 23, 2022)

The new Adobe Target Models API, also called the Blocklist API, lets users view and manage the list of features used in machine learning models for Automated Personalization (AP) and Auto-Target (AT) activities.

For more information, see Models API Overview in the Adobe Target Developer Guide.

Target Standard/Premium 22.10.3 (staggered release October 25-27, 2022)

This release contains the following fixes:

• Added tooltips in the Target UI to help customers navigate the audience builder more efficiently and to learn how to use features that might be unfamiliar. (TGT-44139)

• Added functionality to prevent customers from editing an activity that was disabled by Target because it uses unsupported metrics. A message in the UI directs customers to duplicate the activity and then update the conversion metric.

  With this release averagetimespentonsite, bouncerate, and entries metrics in Target activities will be deprecated for new activities. Existing activities can continue using these metrics until May 2023.

• Added a tooltip in the Target UI to help customers select an optimization criteria while creating or editing an Auto-Target activity that uses A4T.

Target Standard/Premium 22.10.1 (staggered release October 10-13, 2022)

This release contains the following new features, enhancements, and fixes:

Feature	Details
Adobe Experience Manager (AEM) experience fragments	Updates to the AEM experience fragments functionality include the following: Added the ability to filter AEM experience fragments by type (HTML or JSON) in the Offers list. (TGT-43121) Fixed an issue that allowed customers to insert JSON Experience Fragment offers when using the VEC, which is not supported. JSON offers can be inserted only when using the Form-Based Experience composer. (TGT-43846) For more information, see AEM experience fragments.
New Visual Experience Composer extension for Google Chrome	A new Adobe Target Visual Experience Composer (VEC) extension for Chrome is available in the Chrome Web Store. Starting in January 2023, the current Target VEC Helper extension will stop working in Google Chrome because Google won’t allow extensions using Manifest V2. Download the new extension to continue to visually author your websites in Target starting with the new year. The following links show the two extensions in the Chrome Web Store: New extension Old Extension For more information, see Visual Editing Helper extension.

• Fixed an issue that prevented audience rule information from displaying properly in the Audiences Refinements information window. (TGT-43917)
• Improved the performance of the Target UI when loading audiences that approach the recommended limit of targeting rules. (TGT-43675)
• Fixed an issue that caused some components to not display properly in the Modifications panel on the Experiences page when creating or editing activities in the VEC after switching from Compose to Browse mode. (TGT-43300)
• Fixed an issue that prevented some customers from archiving A/B Test activities that use Auto-Target. (TGT-40978)
• Added the ability to automatically use a single offer in multiple locations within a single reporting group. (TGT-40689)

Target Standard/Premium 22.9.1 (staggered release September 13-15, 2022)

This release will be available according to the following staggered schedule:

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

This release contains the following enhancements and fixes:

• Added a Cross-Domain option when downloading at.js 2.10.0 (and later) to allow or disable setting 3rd-party cookies. (TGT-43674)
• Updated notifications in the Target UI to inform customers if the import of Recommendations feeds fails. (TGT-35811)
• Fixed an issue that caused Decision Offers to not work properly within the Visual Experience Composer (VEC). (TGT-43866)
• Fixed an issue that caused an error message to display when selecting the Clicked an Element conversion goal while creating an Multivariate Testing (MVT) activity. (TGT-43842)
• Fixed an issue that prevented the Impressions column from displaying in the downloaded CSV report file for Automated Personalization (AP) activities. (TGT-43780)
• Fixed an issue that prevented customers from editing HTML/JSON offers after duplicating experiences when using the Form-Based Experience Composer. (TGT-43633)
• Fixed an issue that prevented customers from copying an A/B Test activity from a non-default workspace to another non-default workspace. (TGT-41910)
• Fixed an issue to ensure that customers can properly display usages of Recommendations objects (designs, criteria, collections, and so forth) in A/B Test and Experience Targeting (XT) activities that contain recommendations and also delete criteria objects that are no longer in use from Target UI and Recommendations backend. (TGT-42331)
• Fixed an issue that causes a network timeout alert to appear in the Target UI when fetching parameters. (TGT-43737)
• Made UI updates to ensure that certain drag-and-drop actions are accessible by keyboard. (TGT-42969)
• Made UI updates to ensure that text stings are properly localized.

at.js version 2.10.0 (September 13, 2022)

• Added a Cross-Domain option when downloading at.js 2.10.0 (and later) to allow or disable setting 3rd-party cookies. (TGT-43674)

Target Standard/Premium 22.8.1 (staggered release August 17-18, 2022)

This maintenance release includes backend and localization fixes.

Target platform release (July 20, 2022)

This release contains the following features, enhancements, and fixes:

Feature	Description
Improved audience evaluation accuracy and reduced end-user latency through IPv6 support (TNT-43364, TNT-44692)	Visitors’ geo-locations are now determined by IPv6 addresses, if available, as opposed to only IPv4 addresses. Delivery APIs also support IPv6 input parameters. Filtering and allow-listing support both IPv4 and IPv6 addresses. The IPv6 support in this release means visitors will be more accurately included in audiences (more accurately qualify for activities or be included in filtering criteria). It also improves data latency, as IPv6 clients will route directly, avoiding the overhead of the the IPv6-to-IPv4 gateway.
Fixed A4T client-side payload handling issue (TNT-44926)	With A4T server-side integration, if Adobe Target identifies a request as coming from a bot, it does not forward the payload to Analytics, and there is no mod_stats event in recorded in the Target logs. With this release, A4T client-side logging has been enhanced so that the behavior regarding the A4T payload is the same as with A4T server-side: Visitors that are identified as bots are excluded from Target counting/reporting. (Note the issue in question was limited to implementations that used client-side payload handling; server-side was not impacted. With this release, the behavior is now consistent for both server-side and client-side payload handling.)

Target Standard/Premium 22.6.2 (June 30, 2022)

This release contains the following features, enhancements, and fixes:

Feature	Description
In-product notifications	Get the following relevant in-product notifications: Activities: Notifications for all activity types when an activity is approved or deactivated, either manually or when it reaches its start or end date. The notification includes the name of the activity with a link to the activity’s overview page. Profile scripts Notifications when a profile script is activated or deactivated, either manually or by Target. Recommendations feeds: Notifications when a Recommendations feed is activated or deactivated, either manually or by Target. Notifications are also sent when a Recommendations feed fails. By default, notifications are received by product admins, publishers, and approvers. Notifications are configurable inside Experience Cloud preferences. For more information see Notifications and announcements.
Adobe Target Developer Guide	The Adobe Target Developer Guide consolidates all Target developer content in one convenient guide. The guide includes information about implementing Target and Recommendations, Target SDKs, and Target APIs. For more information, see Adobe Target Developer Guide.

• Users with the Editor role can no longer edit audiences in live activities. (TGT-43582)
• A warning message displays if a customer attempts to save an audience with an exclamation mark ( ! ) as the first character of the audience’s name (for example !London). (TGT-43643)
• Fixed an issue that caused audiences definition details cards for some customers to indicate that an ended activity is still live. (TGT-43527)

Target Standard/Premium 22.6.1 (staggered release: June 7-9, 2022)

This release will be available according to the following staggered schedule:

• June 7: Asia-Pacific (APAC) region
• June 8: Americas region
• June 9: Europe, Middle East, and Africa (EMEA) region

This release contains the following enhancements and fixes:

• An enhancement was delivered for the new Audiences page to prevent an inconsistent state between the old database where the audiences were stored in the past and the new architecture that is retrieving the information directly from the backend. (TGT-43552)
• Fixed an issue that prevented some customers from saving combined audiences caused by the Target UI creating “empty” containers. (TGT-43588)

Target platform release (May 25, 2022)

This release contains the following enhancements and fixes:

• Added User Agent Client Hints support.
• Fixed an issue that intermittently caused timeouts when rendering Offer Decisions in Experience Targeting (XT) activities. (TNT-44611)

at.js version 2.9.0 (May 27, 2022)

• Added User Agent Client Hints support.
• Fixed a bug where multiple mbox requests on the same page have different impression IDs.

Target Standard/Premium 22.5.1 (staggered release; May 11-13, 2022)

This release will be available according to the following staggered schedule:

• May 11: Asia-Pacific (APAC) region
• May 12: Americas region
• May 13: Europe, Middle East, and Africa (EMEA) region

This release contains the following enhancements and fixes:

• Fixed an issue that caused a JavaScript error and prevented some customers from accessing the activity details for certain Automated Personalization (AP) activities. (TGT-43526)
• Fixed an issue that prevented some customers from adding (or editing) a specific offer to an AP activity. (TGT-43503)
• Fixed an issue in the Target UI that displayed the following error message: “Your global mbox may not be in sync. Please try resaving it.” This issue was a UI issue and did not impact customers’ implementations. (TGT-43475)
• Fixed an issue that prevented one customer from editing experience-level refinements and audiences for an activity if the refinements and audiences were created before the new Audiences UI was deployed. (TGT-43433)
• Fixed an issue that allowed customers to select duplicate Adobe Audience Manager (AAM) audiences while editing reporting audiences for an activity. (TGT-43430)
• Fixed an issue that prevented customers from creating duplicate audiences, but in different workspaces. (TGT-43423)
• Fixed an issue that prevented customers from deleting locations that have ad-hoc offers in activities created in the Form-Based Experience Composer. (TGT-43315)
• Fixed an issue that prevented customers from accessing code offers after clicking image offers and then refreshing the UI. (TGT-43566)
• Fixed an issue that caused edits to profile scripts to revert to the original, unedited script after the script is edited, activated, and then deactivated. The profile script now remains in its edited state. (TGT-43249)
• Fixed an issue that caused the following error when attempting to move an audience to another workspace: “We cannot complete your request. Please contact Adobe Client Care if the problem persists”. (TGT-43212)
• Fixed an error that caused an error when cloning custom code modifications for Single Page App (SPA) pages. (TGT-43137)
• Fixed an issue that caused the original promotion to be affected after duplicating an experience and then editing the promotion. (TGT-41775)

Target Standard/Premium 22.4.1 (April 28, 2022)

This release contains the following fix:

• Fixed an issue that caused three cart-based algorithms to use the same Bought/Bought condition on the Target backend. (TGT-43456)
• Enabled Target UI token refresh for organizations enabled with Business ID accounts and Policy Based Authentication (PBA). (TGT-42590)

Target platform release (April 27, 2022)

This release contains the following change:

• With this release you can prefetch content for Auto Personalization (AP) and Auto-Target (AT) activities (previously not returned by Target). This might change the experiences the end users see in case of a pre-fetch call (no changes to the “execute” flow) if an AP/AT activity is on the delivery path and is higher in priority than other AB/XT activities that use the same location for content delivery.

Target platform release (March 30)

This release contains the following enhancement:

• Click-track metrics will include analytics payload in Delivery API requests for activities that use Analytics as the reporting source (A4T) and process events on client-side. (TNT-43073)

Target Standard Audiences refresh (March 28)

This release contains the following update:

• The new Audiences UI will be enabled for all Target Standard customers.

Target Standard/Premium customer engineering fixes (March 22, 2022)

This maintenance release contains the following enhancements:

• Added functionality to return Analytics payload data for prefetch views and pageLoad click metrics when using the Delivery API with activities that use Analytics as the reporting source (A4T). (TNT-43198)
• Updated the bot filtering user agent list to allow a browser type commonly used in Japan. (TNT-43867)

Target Standard/Premium 22.2.1 (February 1, 2022)

This maintenance release contains the following fixes and enhancements for the new Audiences UI announced in the Target Standard/Premium 22.1.2 release that is rolling out to customers across all regions in the next six weeks. These fixes align the functionality of audiences created in Adobe Target Standard/Premium.

• Fixed an issue that prevented imported audiences from Adobe Experience Platform, Adobe Experience Cloud, and Adobe Target Classic from being assigned as reporting audiences. (TGT-43140)
• Added a Delete option in the Audiences list for imported audiences from Adobe Experience Platform, Adobe Experience Cloud, and Adobe Target Classic. Also added bulk-delete functionality. (TGT-42914)

at.js version 2.8.1 (January 28, 2022)

• Fixed pageLoad not being mapped to target-global-mbox in On Device Decisioning (ODD) hybrid execution mode.
• Fixed an issue with analytics details for mbox request.
• Upgraded dev dependencies to fix security vulnerabilities.

Target Standard/Premium 22.1.2 (January 26, 2022)

Feature	Details
Adobe Experience Platform audiences in Target	You can now consume and use Adobe Experience Platform audiences in Target. The Target team, Experience Platform Destinations team and the Unified Profile Service team is pleased to announce the general availability of the “Same Page/Next Page Personalization” use cases. Using audiences created in Adobe Experience Platform provide richer customer data that leads to more impactful personalization. The Real-time Customer Data Platform (RTCP), built on Adobe Experience Platform helps companies bring together known and anonymous data from multiple enterprise sources to create customer profiles that can be used to provide personalized customer experiences across all channels and devices in real time. For more information, see Use audiences from Adobe Experience Platform in Create audiences. Be sure to read the Adobe blog and watch the video: Adobe announces Same Page Enhanced Personalization with Adobe Target and Real-time Customer Data Platform.
Audiences UI refresh	As part of the Adobe Target team’s ongoing effort to improve the user-experience for Target users, this release refreshes the Audiences and Profile Scripts pages in the Target UI. This update unifies and standardizes design patterns that were previously inconsistent, while adding new enhancements, such as: The ability to select and delete multiple audiences simultaneously A refreshed audience builder design Exclusion rule support in the Audience library rule builder A new “Audience Source” filter, to allow for faster audience discovery Session persistent search and filter options The ability to move audiences between workspaces for Target Premium customers. For more information, see Audiences. NOTE: This feature will be rolled out to customers in different regions in the next eight weeks.
Profile Scripts UI refresh	The Profile Scripts library was also updated, and includes a refreshed interface along and several productivity updates: The ability to select and delete multiple profile scripts simultaneously A new code editor for profile scripts Syntax highlighting and error checking inside the code editor Auto-complete tokens (mbox or profile) parameters through keyboard shortcuts For more information, see Visitor Profiles. NOTE: This feature will be rolled out to customers in different regions in the next eight weeks.

Target Standard/Premium 22.1.1 (January 12, 2022)

This release includes bug fixes and pre-requisite capabilities for future integrations.

Target Platform release (April 13, 2022)

This release contains the following update:

• Fixed issue to ensure that the last octet of IP addresses are properly obfuscated when captured using profile scripts. (TNT-44076)

Target Standard/Premium 22.3.1 (April 5, 2022)

This release contains the following changes and enhancements:

• Fixed an issue that caused the Include and Exclude options to be disabled for combined audiences when editing an activity. (TGT-43422)
• Fixed an issue that prevented some customers from seeing the list of available audiences while editing an activity. (TGT-43404)
• Fixed an issue that prevented some customers from deleting an IP address from the “IPs to exclude from Target reporting data” list in Administration > Reporting. (TGT-43384)
• Fixed an issue that prevented the use of negative numbers in audience criterion that check that any variable is “greater than,” “greater than or equal to,” “less than,” or “less than or equal to.” (TGT-43367)
• Fixed an issue that prevented customers from seeing the Audience Details card when creating combined audiences. (TGT-43303)

at.js version 2.8.0 (January 7, 2022)

The Target at.js JavaScript library now collects feature usage and performance telemetry data. Personal data is not collected. Opt-out for this feature is available by setting telemetryEnabled to false in targetGlobalSettings. For more information, see telemetryEnabled in targetGlobalSettings.

Release notes - 2021

at.js version 2.7.0 (October 28, 2021)

This release contains the following enhancement:

• Added support for Web Components. This version of at.js is required to create and test personalized experiences and offers on custom elements and on elements inside custom elements. This functionality is included in the Target Standard/Premium 21.10.5 release.

Target Standard/Premium 21.10.5 (October 28, 2021)

This maintenance release contains the following enhancement:

Feature	Details
Visual Experience Composer (VEC)	Added support for Web Components. Personalized experiences and offers can be created and tested on custom elements and on elements inside custom elements. For more information, see Visual Experience Composer options.

Target Standard/Premium 21.10.4 (October 21, 2021)

This maintenance release contains the following enhancement:

Feature	Details
Cart-based Recommendations	Added a new family of algorithms to deliver recommendations based on the contents of the visitor’s cart. For more information, see “Cart-Based” in Create criteria, “Cart adds/cart views/checkout pages” and “Exclude items already in the visitor’s cart” in Plan and implement Recommendations, and “Cart-Based” in Base the recommendation on a recommendation key.

Target Standard/Premium 21.10.3 (October 19, 2021)

This maintenance release contains the following enhancements, fixes, and changes:

• Fixed issues that prevented customers from opening the A4T panel in Analysis Workspace by clicking the View in Analytics button in Target activity reporting. (TGT-42099, TGT-42100)
• Fixed an issue that caused the Edit Design button to not display while editing A/B Test and Experience Targeting (XT) activities using the Form-Based Experience Composer. (TGT-41980)
• Fixed an issue that prevented the Compatible checkbox from displaying in criteria selection while creating a new Recommendations activity. (TGT-42053)
• Fixed an incorrect error message that displayed when not being able to select Analytics as the reporting source (A4T) because of lack of Analytics permissions. (TGT-41954)
• Implemented multiple accessibility fixes to improve keyboard navigation across the Target UI.

Target Standard/Premium 21.10.2 (October 13, 2021)

The following enhancements have been added when using Target Audiences with the Adobe Experience Platform Web SDK:

• Added warning icons, popovers, and messages in various places in the Target UI to indicate that the audience was deleted at the source and is no longer available for use in Target activities.

  The following illustrations show some of the places the icons, popovers, and messages display:

  • Activity list page

    

  • Activity Overview pages:

    

  • Experiences step of the activity-creation workflow:

    

  • Targeting step of the activity-creation workflow:

    

  • Goals & Settings step of the activity-creation workflow:

    

  • Audience refinements (Replace Audience on the Targeting step of the activity-creation workflow):

• If you attempt to use the Combine Audiences feature and one of audiences was deleted at the source, Save is disabled.

Target Standard/Premium 21.10.1 (October 6, 2021)

This release contains the following new features:

Feature	Details
Audiences UI refresh	As part of the Adobe Target team’s ongoing effort to improve the user-experience for Target users, this release refreshes the Audiences and Profile Scripts pages in the Target UI. This update unifies and standardizes design patterns that were previously inconsistent, while adding new enhancements, such as: The ability to select and delete multiple audiences simultaneously A refreshed audience builder design Exclusion rule support in the Audience library rule builder A new “Audience Source” filter, to allow for faster audience discovery Session persistent search and filter options For more information, see Audiences.
Profile Scripts UI refresh	The Profile Scripts library was also updated, and includes a refreshed interface along and several productivity updates: The ability to select and delete multiple profile scripts simultaneously A new code editor for profile scripts Syntax highlighting and error checking inside the code editor Auto-complete tokens (mbox or profile) parameters through keyboard shortcuts For more information, see Visitor Profiles.
Premium Recommendations Criteria create and edit	The Recommendations Criteria creation and editing workflow has been streamlined to simplify choosing the right recommendations algorithm and settings to achieve your goals. For more information, see Create criteria.
Recommendations lookback window and algorithm refresh rate improvements	You can now run “Most Viewed” and “Top Sellers” algorithms with a six-hour lookback window to capture the content that’s trending most recently. When the six-hour lookback window is selected, your recommendations results are updated every 3-6 hours throughout the day. For more information, see Data Source in Create criteria.

Target Standard/Premium 21.9.1 (September 14, 2021)

This maintenance release contains the following enhancements, fixes, and changes.

• Fixed issues that prevented customers from logging in to the Visual Experience Composer (VEC) due to new security policies for third-party cookies in some web browsers. This issue was discussed in “Pages not loading in the Visual Experience Composer (VEC) or Enhanced Experience Composer (EEC) when using Google Chrome version 80+” in Troubleshooting Issues Related to the Visual Experience Composer and Enhanced Experience Composer.
• Fixed an issue that caused offer names in the VEC to display the offer’s path instead of the offer’s friendly name. (TGT-41300)
• Experience names are now reflected in Analysis Workspace for A4T activities (TGT-38674)
• Fixed an issue in Recommendations that erroneously applied entity ID changes in a promotion in a duplicated activity to the original activity. (TGT-41482)
• Fixed an issue that prevented the “Edit Criteria” button from displaying properly on the Experiences page for Recommendations activities in the VEC. (TGT-39512)
• Fixed an issue that prevented synchronization of activities when duplicated and copied to a test workspace. (TGT-40686)
• Fixed an issue that prevented modifications to a selector with experience fragments when using “Insert After” in the VEC. (TGT-41802)
• Fixed an issue that prevented empty JSON content in an offer from being sent to the backend. Target now sends the JSON object even though it is empty. (TGT-41555)
• Fixed an issue that caused legacy Analytics reporting to open instead of Analysis Workspace when customers clicked “View in Analytics” while viewing a report. (TGT-41867)
• Added additional clarification to the displayed UI message when a customer attempts to select Analytics as the reporting source (A4T) for an Automated Personalization activity. The message states that, “Target is the only supported source for Automated Personalization activities.” (TGT-41954)
• Added additional clarification to the error message when customers attempt to separate hosts with “newline” instead of commas. (TGT-40671)
• Fixed an issue that caused some activities’ “Last Updated” dates to differ from the English UI for Spanish and Japanese customers (when viewing the UI in Spanish and Japanese). (TGT-38980)

at.js 2.6.1 (August 16, 2021)

• Bug fix for “No cached artifact available for hybrid mode” when using on-device decisioning.

Target node.js SDK 2.2.0 (August 11, 2021)

• Added SDK telemetry data collection
• Automated Delivery API client openapi codegen

For more information about this and previous releases, see the Change log in the Target node.js SDK documentation on Github.

Target Standard/Premium 21.8.1 (August 10, 2021)

This maintenance release contains many backend enhancements, including the following customer-facing change:

• Fixed an issue that caused reports for Auto Personalization activities created in the Form-Based Experience Composer to reference deleted offers in reports. This issued caused the following error message to display, “We are having trouble retrieving data for this report. Please contact Adobe Client Care if the problem persists.” (TGT-41028)

Target Delivery API (August 3, 2021)

This release contains the following enhancements:

• The limit for mbox parameters has been increased to 100 parameters. The previous limit was 50 parameters. (TNT-41717)

• The limit for categoryId has been increased to 256 characters. The previous limit was 128 characters.

• The following Adobe Audience Manager (AAM) details have been added to the Delivery API:

  • AAM UUID: The internal AAM ID used to uniquely identify a user.
  • dataPartnerId: The ID for a data partner.
  • dataPartnerUserId: The user ID provided by a data partner.

  Previously, the Delivery API included dcsLocationHint and blob only. (TNT-41644)

Target Standard/Premium 21.6.1 (June 30, 2021)

This release contains the following new features and enhancements. The issue numbers in parentheses are for internal Adobe use.

Feature	Details
Analytics for Target (A4T)	Clicking the “View in Analytics” link on the Reports page from an activity that uses Analytics as the reporting source (A4T), Analysis Workspace now opens. Previously, the link opened Analytics reporting. (TGT-36959)

Python SDK 1.0.0 (June 16, 2021)

The new Adobe Target Python SDK with on-device decisioning capabilities is now available. This newest addition bolsters the Target suite of server-side SDKs. These SDKS help you integrate with Target and expedite your time to value, in the language of your choice. Server-side integrations are becoming a popular choice given that the market is shifting to a cookie-less world in which first-party data is valuable. Target SDKs are available in the most popular programming languages in the market (Python, Java, JavaScript, C# / .Net).

For more information, see the Python SDK documentation in the Adobe Target Developer Guide.

Target Standard/Premium 21.5.1 (June 7, 2021)

This release includes the following enhancements:

Feature

Details

Recommendations Catalog Search API

Search your Recommendations product and content catalog programmatically via API to identify items that match a search criteria and simplify administration of your catalog. Limitations and notes: Catalog search via API is not supported for environments with more than 2,000,000 items. Catalog search results via API are updated more rapidly than catalog search results via the Target UI. The catalog search in the Target UI can take additional time to reflect the latest results. For more information, see Searching Entities in the Adobe Target Recommendations API guide.

This release maintenance release contains the following fixes.

• Fixed an issue that caused the default workspace to change to another workspace when refreshing the Audiences page. (TGT-38871)
• Fixed an issue in Administration > Implementation that sometimes caused an error message stating, “Your global mbox may not be in sync. Please try resaving it.”

Adobe Experience Platform Web SDK version 2.5.0 (June 1, 2021)

This release of the Platform Web SDK includes support for the following:

Feature	Details
Redirect support with Analytics for Target (A4T)	The Platform Web SDK now supports Target redirects when using A4T. For more information, see see Analytics for Target implementation.

at.js version 2.5.0 (May 13, 2021)

This release of at.js includes the following enhancements and changes:

• On-device decisioning support for at.js.
• Preview links support for Automated Personalization activities

This release also removes support for Microsoft Internet Explorer 10, Internet Explorer 11, and all older versions. Microsoft Edge continues to be supported in at.js 2.5.0 and later.

Target Standard/Premium 21.4.1 (April 19, 2021)

This release contains the following new features and enhancements. The issue numbers in parentheses are for internal Adobe use.

Feature	Details
On-device decisioning support for at.js (Date to be announced)	On-device decisioning lets marketers and developers deliver experimentation and personalization on a user’s browser at near-zero latency. For more information, see On-device decisioning for at.js.
List-based operators for entity filtering rules	Target Recommendations supports new list-based operators for entity filtering rules. (TGT-39234) Newly added operators include: Is Contained In List Is Not Contained In List List Contains An Item In List Does Not Contain An Item In List Contains All Items In List Does Not Contain All Items In For more information, see “Available operators” in Use dynamic and static inclusion rules.

This release contains the following fixes.

• Fixed an issue that prevented an activity from syncing after changing the audience to All Visitors. (TGT-40259)
• Fixed an issue that prevented offers from being duplicated when used in different locations in Automated Personalization activities even though the Disallow Duplicates option is enabled. (TGT-39567)
• Fixed an issue that prevented the Administration > Scene7 configuration page from loading properly. (TGT-39918)
• Fixed an issue that caused properties to be mapped to the incorrect workspace. (TGT-39869)
• Fixed an issue that caused infinite loading if the request fails after changing the environment while creating a recommendations exclusion. (TGT-39948)

at.js 2.4.1 (March 23, 2021)

This release of at.js is a maintenance release and includes the following enhancements and fixes:

• Fixed an issue with targetPageParams being included in mbox requests. targetPageParams should be included in pageLoad requests only. (TNT-40247)
• Fixed an issue with document and window global objects in the Adobe Experience Platform Launch extension by replacing the Platform Launch global object dependencies with direct references to them. (TNT-37124)

IP address changes for Recommendations feed-processing servers (March 16, 2021)

The Target Recommendations feed-processing server IP addresses were updated on March 16, 2021. For more information, see IP addresses used by Recommendations feed-processing servers.

Target Standard/Premium 21.2.1 (March 9, 2021)

This maintenance release contains the following enhancements, fixes, and changes.

The issue numbers in parentheses are for internal Adobe use.

• Increased the allowable offer size (TGT-38304):

  Type	Previous Limit	New Limit
  HTML	256 KB	1024 KB
  Visual offers from the Target UI	64 KB	1024 KB for each experience
  Via API	512 KB	1024 KB

• Personalization Insights reports for Auto-Target (AT) and Automated Personalization (AP) activities are now produced daily. You can choose a report providing Automated Segments or Important Attributes for the last 15, 30, and 60 days. The 45-day and 90-day options have been removed to enable the other lookback window settings to run daily. (TGT-39472)

• Fixed an issue that caused the current dependency to not display when customers click Edit Dependency on an activity’s Goals & Settings page. (TGT-39340)

• Fixed an issue when refreshing a workspace’s Audience Library. Before the refresh, the audiences for the currently selected workspace displayed. After the refresh, the Default Workspace and its audiences displayed. The current workspace and its audiences now persist after the refresh. (TGT-38871)

• Fixed an issue when copying a Recommendations activity and later editing the original activity by changing its criteria sequence. The change in the criteria sequence in the original activity was also incorrectly applied to the copied activity. (TGT-39155)

• Fixed an issue that caused the incorrect number of products to display for Recommendations exclusions. (TGT-39599)

Target Standard/Premium 21.1.1 (January 19, 2021)

This maintenance release contains the following enhancements, fixes, and changes.

The issue numbers in parentheses are for internal Adobe use.

• Added a warning when selecting an Adobe Analytics metric when using Analytics as the reporting source (A4T) in an Auto-Target activity. Auto-Target models are optimized to work with binary (conversion-based) metrics. Selecting a continuous metric, such as revenue, might have sub-optimal outcomes and the Personalization Insights reports might not be accurate. (TGT-38926)
• Added a status icon in the Auto-Target Summary report for Auto-Target activities that use A4T. The green check icon next to each experience in the report indicates that a personalized machine-learning model has been generated for that experience. The clock icon indicates that not enough traffic has been served to build the model. (TGT-38925)
• The Automated Segments and Important Attributes reports for Auto-Target activities that use A4T and Analytics conversion metrics are generated and look the same as when using Target as the reporting source. (TGT-38931)
• Added an environment filtering option to the Recommendations Collections list. (TGT-38353)
• Fixed an issue that caused the incorrect product count to display in Recommendations collections. (TGT-39162)
• Added a Last Updated filter to the Recommendations Catalog Search. (TGT-38340)
• Fixed an issue in Recommendations that caused the Create Sequence page to hang after changing the industry vertical. (TGT-38160)
• Fixed an issue that prevented users from removing an audience from an offer in an Automated Personalization (AP) activity. (TGT-39058)
• Fixed an issue that caused the incorrect time frame (start and end dates) to display in Audience Info cards for some customers. (TGT-39150)
• Fixed an issue that prevented some customers from seeing the list of activities in the Default Workspace. (TGT-38526)

at.js 2.4.0 (January 14, 2021)

This release of at.js is a maintenance release and includes the following fixes:

• Adds support for unified profile/platform id to delivery API customerIds.
• Fixes invalid style tag injection.

Release notes - 2020

Target Standard/Premium 20.10.1 (October 27, 2020)

This release contains the following new features:

Feature

Details

On-device decisioning

On-device decisioning lets both marketers and product developers deliver experimentation and Machine Learning-driven personalization from within a user’s device, across channels, at near-zero latency. Speed and performance matters–in customer insights and user satisfaction. On-device decisioning lets you compile key personalization and experimentation instructions in A/B Test and Experience Targeting (XT) activity types into “optimization artifacts:” JSON objects that are loaded onto customer devices via the CDN. And because on-device decisioning connects natively with Adobe Experience Cloud products, Target users get rapid analysis and faster experience iterations. For more information, see *On-device decisioning for at.js and Introduction to on-device decisioning for server-side.

This release contains the following enhancements, fixes, and changes:

• Fixed an issue that prevented Average Lift Confidence Interval and Confidence from displaying in Auto-Target reporting for the Total row. Measurements displayed correctly for all individual experiences. (TGT-37301)

• Fixed an issue that impacted Adobe Target Premium users’ Auto-Target reporting from September 15, 2:30 p.m. (PDT) to October 6, 9:25 a.m. (PDT). When viewing reports for the impacted conversion metrics (configured using either the “Viewed a page” or “Clicked on mbox” option), the conversions rates are incorrectly reported. There is no known delivery issue at this time.

• Added a selectable Last Updated At column in the Catalog Search table and a Last Updated At filter. This enhancement saves time and effort because you don’t have to open each individual item to see when it was last updated and you can filter by date the items were last updated.

  

• Updates were made to help make the Target UI compliant with Web Content Accessibility Guidelines 2.0 Level A and AA Success Criteria (WCAG 2.0 AA). (TGT-34384 & TGT-24679)

• Made Content Security Policy (CSP) improvements. (TGT-37035)

• Introduced a way to specify the client code as a parameter for customers using CNAME. (TNT-38571)

• Adobe Experience Cloud documentation is moving to Experience League. During October, all release notes, articles, videos, and tutorials will move from their current location at docs.adobe.com to Experience League. This move ensures that all learning, self-help, enablement, and community content is served from a single location. When this change occurs, there is nothing you need to do, as all links will be redirected to Experience League. We will update the release notes when the cutover begins.

Target Standard/Premium 20.9.1 (September 30, 2020)

This maintenance release contains the following enhancements, fixes, and changes:

• Improved navigation and functionality for keyboard-only users. (TGT-34487, TGT-34516, TGT-34517, TGT-34514)
• Added labels in the UI to aid users using assistive technologies. (TGT-34500, TGT-34501, TGT-34502, TGT-24504)
• Improved text and color contrast for images and text in UI. (TGT-34513)

Target Standard/Premium 20.8.3 (September 15, 2020)

Feature

Details

Analytics for Target (A4T) support for Auto-Target activities

Auto-Target activities now support Analytics for Target. This integration allows you to use the Auto-Target ensemble machine learning algorithm to choose a best experience for each visitor based on their profile, behavior, and context. If you’ve already implemented A4T for use with A/B Test and Experience Targeting activities, you’re all set! For more information, see A4T support for Auto-Allocate and Auto-Target activities.

Target Standard/Premium 20.8.2 (September 10, 2020)

Feature	Details
Control recommendations slots within criteria sequences	Criteria Sequences now allow you to control the number of slots taken up by each recommendations criteria, enabling you to mix and match different types of items or different algorithm logic. See Create criteria sequences to learn more.

Target Standard/Premium 20.8.1 (September 2, 2020)

This release contains the following enhancements, fixes, and changes:

• Fixed an issue that caused errors to display when loading the new Administration pages after switching organizations. (TGT-37730)
• Fixed a display issue that caused the incorrect client code to display on the Administration > Implementation page. (TGT-37849)
• Fixed an issue that sometimes prevented users from using the editing features in the Visual Experience Composer (VEC) after successfully loading the VEC. (TGT-37162)
• Fixed an issue that prevented pages from loading in the VEC and Enhanced Experience Composer (EEC) even though the VEC Helper extension was installed. This was due to changes in Google Chrome 80+. Download the updated VEC Helper extension. (TGT-37893)
• Fixed an issue that sometimes prevented users from downloading at.js from the Administration > Implementation page after switching organizations. (TGT-37668)
• The at.js download button is now disabled while loading to prevent Target from sending multiple requests if users click the download button multiple times. (TGT-37633)
• Fixed an issue in Experience Targeting (XT) activities that caused experiences to display “fetching results” for an extended period of time. (TGT-37684)
• Improved navigation and functionality for keyboard-only users. (TGT-34479 & TGT-34473)
• Added labels in the UI to aid users using assistive technologies. (TGT-34480)
• Improved the error message when deleting a mobile viewport that is currently used in an activity. The error message now reads: “This viewport is currently associated to one or multiple activities. You need to remove the viewport from those activities before being able to delete it.” (TGT-37030)
• Added support in the VEC to allow click tracking on a css selector that matches more than one element in the page. (TGT-37323)
• Fixed an issue that prevented certain users from displaying the Activity list. The following error message was displayed: “Unable to fetch URLsuggestions.” The error occurred for users using carriage returns in their FirstName (FirstName/r/n) in the Adobe Backend system. (TGT-37330)
• Fixed an issue that prevented users from displaying the Activity page if the workspace name (specified in the Adobe Admin Console for Enterprise) contains an apostrophe. (TGT-37709)
• Fixed an issue in Auto-Allocate activities while selecting optimization and conversion metrics where an error message incorrectly informed users to select a report suite, even though a report suite was already specified. (TGT-37689)
• Fixed an issue that sometimes caused metrics on the Goals and Settings page to be blank after navigating to the Targeting page and then back. (TGT-37691)
• Fixed an issue that caused an incorrect last-modified value for Recommendations criteria. (TGT-37666)
• Fixed an issue that caused mbox IDs to display in the Mboxes drop-down list instead of mbox names. (TGT-37739)

at.js 2.3.2 (July 24, 2020)

This release of at.js is a maintenance release and includes the following fix:

• Fixed a bug when a script or code adds default property to the window or document.

Target Standard/Premium 20.7.1 (July 27, 2020)

This release includes the following changes:

Administration section UI refresh

We are gradually rewriting the entire Target UI using a new tech stack to be able to offer improved performance, reduce the maintenance time required when releasing new features, and to improve the user experience across the product. The first section refreshed is the Setup section, which has been renamed Administration.

As part of this refresh, you will be able to easily perform many actions using the pages in the Administration section, such as:

• Download the latest at.js file from the Implementation tab (Administration > Implementation).
• Customize your at.js settings and be able to easily review your changes (Administration > Implementation).
• Modify enhanced reporting settings, such as the default currency and time zone, IPs to exclude from reporting, etc. (Administration > Reporting)
• Obfuscate visitor IP addresses for privacy reasons (Administration > Implementation)
• View the existing list of users per workspace and their roles, before managing them in Adobe Admin Console (Administration > Users).
• Search and filter all tables in the Administration section.

For more information, see Administer Target Overview.

Enhancements, fixes, and changes

This release contains the following enhancements, fixes, and changes:

• Fixed an issue that prevented site preferences from being retained after refresh. (TGT-37239)
• Fixed an issue that prevented Insert After > Image from functioning properly with Scalable Vector Graphics (SVG) images. (TGT-37242)
• Fixed an issue for users with the Publisher role that prevented the deletion of draft activities. (TGT-37358)
• Fixed an issue that prevented users from editing an activity when All My Workspaces is selected. (TGT-37276)

Target Standard/Premium 20.5.1 (June 17, 2020)

Feature / Enhancement	Description
Analytics for Target (A4T) support for Auto-Allocate activities	Auto-Allocate activities now support Analytics for Target. This integration allows you to use the Auto-Allocate multi-armed bandit capability to drive traffic to winning experiences, while using an Adobe Analytics goal metric and/or Adobe Analytics reporting and analysis capabilities. If you’ve already implemented A4T for use with A/B Test and Experience Targeting activities, you’re all set! For more information, see A4T support for Auto-Allocate and Auto-Target activities.
Response tokens for Traffic Allocation Method for Auto-Target and Automated Personalization activities	Two response tokens have been added to Auto-Target and Automated Personalization activities to enable determination of whether a visitor received a particular experience as a result of being assigned to “control” or to “targeted” traffic. experience.trafficAllocationId will return 0 if a visitor received an experience from being in “control” traffic and 1 if a visitor received an experience from the “targeted” traffic distribution. experience.trafficAllocationType will return “control” or “targeted.” For more information on control vs. targeted traffic, see Select the control for your Automated Personalization or Auto-Target activity.
Publisher role	This new role is similar to the current Observer role (can view activities, but cannot create or edit them). However, the Publisher role has the additional permission to activate activities. For more information, see: Target Standard users: Specify roles and permissions in Users. Target Premium users: Step 6: Specify roles and permissions in Configure enterprise permissions.
A4T support in Analysis Workspace June 25, 2020	Anaytics for Target (A4T) is now supported in Analysis Workspace. The Analytics for Target (A4T) panel lets you analyze your Adobe Target activities and experiences in Analysis Workspace. For more information, see Reports in Analytics in A4T reporting and Analytics for Target (A4T) panel in the Analytics Tools Guide.

Enhancements, fixes, and changes

• Fixed an issue that caused the “visitors” metric to be stored in the activity’s definition instead of “UniqueVisitors.” (TGT-37098)
• Fixed an issue in the Target UI that caused the vertical scrollbar to not function correctly on the Audiences page. (TGT-36968)

at.js 1.8.2 and at.js 2.3.1 releases (June 15, 2020)

The following improvements and fixes have been made in the Target at.js libraries:

Feature / Enhancement	Description
at.js 1.8.2	This release of at.js is a maintenance release and includes the following fix: Fixed an issue when using CNAME and edge override, at.js 1.x might incorrectly create the server domain, which resulted in the Target request failing. (TNT-35064) For more information, see at.js version details.
at.js 2.3.1	This release of at.js is a maintenance release and includes the following enhancements and fixes: Made the deviceIdLifetime setting overridable via targetGlobalSettings. (TNT-36349) Fixed an issue when using CNAME and edge override, at.js 2.x might incorrectly create the server domain, which resulted in the Target request failing. (TNT-35065) Fixed an issue when using the Target Launch extension v2 and the Adobe Analytics Launch extension, Target delayed the Analytics sendBeacon call. (TNT-36407, TNT-35990, TNT-36000) For more information, see at.js version details.

Profile Batch Status API v2 changes (May 14, 2020)

With the May 20 release, Profile Batch status will return only row-level failure data going forward (success data will not be returned). Failed profile IDs will be returned by the API going forward.

The previous and new API responses are as follows:

ProfileBatchStatus Api
http://<<edge>>/m2/<<client>>/profile/batchStatus?batchId=<batchid>

Currently we see the response as:

<response>

    <batchId>samplebatch-1585929692655-59449976</batchId>

    <status>complete</status>

    <batchSize>164</batchSize>

    <profile>

        <id>1514187733806-729395</id>

        <status>success</status>

    </profile>

    <profile>

        <id>1573612762055-214017</id>

        <status>success</status>

    </profile>

    <profile>

        <id>some profile id</id>

        <status>failed</status>

    </profile>

</response>

After May 4, the response will be:

<response>

    <batchId>samplebatch-1585929692655-59449976</batchId>

    <status>complete</status>

    <batchSize>164</batchSize>

    <profile>

        <id>some profile id</id>

        <status>failed</status>

    </profile>

</response>

Target Standard/Premium 20.4.1 (May 6, 2020)

This release contains the following enhancements, fixes, and changes:

• Fixed an issue that incorrectly qualified a device and browser type for an audience. (TGT-36266)
• Fixed an issue that prevented report data from displaying when viewed on screens less than 963 pixels wide. (TGT-36549)
• Fixed an issue that caused Auto Personalization reports to not render correctly. (TGT-36619)
• Fixed an issue that allowed incompatible metrics to be selected in Auto-Allocate and Auto-Target activities that use Analytics for Target (A4t). (TGT-36646)
• Fixed an issue that caused certain options in the Visual Experience Composer (VEC) to not display correctly. (TGT-36571)
• Fixed an issue in the Target UI that caused other Recommendations offer previews to display the edited content after a user replaced the content in a single experience. (TGT-36053 & TGT-36894)
• Fixed an issue that prevented some users from deleting items from a Recommendations catalog. (TGT-36455)
• Fixed an issue that prevented users from saving Recommendations criteria on a multi-page activity. (TGT-36249)
• Fixed an issue that caused the behavioral data source radio buttons to disappear when editing the criteria for a second consecutive time. (TGT-36796)
• Fixed a display issue that caused a Recommendations algorithm to display “fetching results” for an extended period. (TGT-36550 & TGT-36551)
• Updated many UI strings localized in various languages.

Target at.js (March 25, 2020)

The following new versions of the Target at.js JavaScript libraries are available:

• at.js version 2.3.0
• at.js version 1.8.1

For more information, see at.js version details.

Target Standard/Premium 20.2.1 (March 23, 2020)

This release contains the following enhancements, fixes, and changes:

• Fixed an issue that prevented customers from selecting a collection when performing a catalog search. (TGT-36230)

• Fixed an issue in which a criteria created via API, but not referenced by an activity created in the Target UI, could be erroneously deleted from the UI. (TGT-35917)

• Implemented security improvements to the Content Security Policy (CSP). (TGT-36190)

• Fixed an issue that caused “NaN%” to display when sliding the Attribute Weighting percentage bar to the far left. (TGT-36211)

• Resolved localization issues so that UI text in various languages displays correctly.

• We’ve standardized the list of available metrics from Adobe Analytics for Target (A4T) activities by deprecating Adobe Analytics metrics not supported in the current version of Adobe Analytics APIs. This will enable us to extend our A4T support in future Adobe Target releases.

  The following changes have been made:

  • “Average Time Spent on Page” has been replaced by “Average Time Spent on Site.” Any activities using this as metric the Primary Goal Metric will have “Average Time Spent on Site” (note: measured in minutes rather than seconds) selected as the Primary Goal Metric the next time the activity is edited.
  • “Visitors” has been replaced by “Unique Visitors.” Any activities using this metric as the Primary Goal Metric will have “Unique Visitors” selected as the Primary Goal Metric the next time the activity is edited.

• The following metrics have been deprecated and can no longer be selected as the Primary Goal Metric when creating a new A4T activity.

  Deprecated Metric(s)	Suggested Replacement Metric(s)
  Daily Visitors, Hourly Visitors, Monthly Visitors, Quarterly Visitors, Weekly Visitors, Yearly Visitors	Unique Visitors
  Average Visit Depth	n/a. Not suggested as a primary goal metric
  Bots	n/a. Not suggested as a primary goal metric
  Mobile Crash Rate, Mobile Avg Prev Session Length, Mobile App Store Avg Rank, Mobile App Performance Crash Rate, Mobile App Store Avg Rating	n/a. Not suggested as a primary goal metric

Adobe Experience Cloud navigation (February 22, 2019)

• When you log in to the Adobe Experience Cloud, you will be taken to the new header navigation. It looks very similar to the previous navigation with the black bar at the top, but it provides the following improvements:

  • Easier switching between Identity Management System (IMS) organizations or to a different solution.

  • Improved user help: Search results include results from the Target product documentation, as well as community forums and more video content, giving you easier access to more content to help get the most out Target. We’ve also added a feedback mechanism right in the Help menu, making it easier to report issues or to share your ideas.

  • Improved Net Promoter Score (NPS) feedback functionality, so the survey modal doesn’t disturb your flow of work.

  • Notifications for Target are not currently available in the Notifications drop-down in the header.

  NOTE

  As part of the rollout of the new navigation bar, you will also notice some URL changes. All previous bookmarked links continue to work but we encourage you to bookmark new links for faster opening.

Target Standard/Premium 20.1.1 (February 4, 2020)

The Target Standard/Premium 20.1.1 release is a maintenance release and includes backend enhancements and improvements. In addition, the following fixes are included:

• Fixed an issue that caused the Adobe Analytics tracking server field to be blank on the Goals and Settings page for existing Adobe for Target (A4T) activities. (TGT-35960)
• Fixed an issue in the user interface that caused your selection in the second drop-down list to not display while creating an audience for category affinity. (TGT-36098)

Release notes - 2019

Target Java SDK version 1.1.0 (December 16, 2019)

• Support for proxy config added due to an open source contribution made by @hisham-hassan.

Target Java SDK version 1.0.1 (November 11, 2019)

The following issue was fixed in version 1.0.1:

• Send supplemental data ID in a Target request even when there is no Visitor API cookie present.

Target platform (October 31, 2019)

Feature / Enhancement

Description

Java SDK

The Target Java SDK lets you deploy Target server-side. This Java SDK helps you easily integrate Target with other Adobe Experience Cloud solutions, such as the Adobe Experience Cloud Identity Service, Adobe Analytics, and Adobe Audience Manager. The Java SDK introduces best practices and removes complexities when integrating with Target via our delivery API so that your engineering teams can focus on business logic. The following are notable features that we are introducing in the latest version: Support for prefetching and notifications that allows you to optimize for performance via caching. Support for optimizing performance when you have a hybrid integration of Target on both your web pages and server-side. We are introducing a setting called serverState that is populated by experiences retrieved via the server-side so that at.js 2.2 will no longer make an additional server call to retrieve the experiences. This approach optimizes page load performance. Support for retrieving VEC-created activities via the Java SDK, which is made possible by the new Delivery API. Open sourced so your developers can contribute to the Target Java SDK. Learn more about the Target Java SDK on the Adobe Tech Blog - Server-Side Optimization with the new Target Java SDK.

Target Standard/Premium 19.10.2 (October 31, 2019)

Feature / Enhancement

Description

Multi-value attribues

Sometimes you want to work with a multi-value field. Consider the following examples: You offer movies to users. A given movie has multiple actors. You sell tickets to concerts. A given user has multiple favorite bands. You sell clothing. A shirt is available in multiple sizes. To handle recommendations in these scenarios, you can pass multi-value data to Target Recommendations and use special multi-value operators. For more information, see Work with multi-value attributes.

Target Standard/Premium 19.10.1 (October 22, 2019)

Feature / Enhancement

Description

User-Based Recommendations (October 24, 2019)

Recommends items based off of each visitor’s browsing, viewing, and purchasing history. These items are generally referred to as “Recommended for You.” This criteria lets you deliver personalized content and experiences to both new and returning visitors. The list of recommendations is weighted towards the visitor’s most-recent activity and is updated in-session and becomes more personalized as the visitor browses your site. For more information, see “User-Based Recommendations” in Criteria/Algorithms.

Adobe Experience Cloud navigation

• When you log in to the Adobe Experience Cloud, you will be taken to the new header navigation. It looks very similar to the previous navigation with the black bar at the top, but it provides the following improvements:

  • Easier switching between Identity Management System (IMS) organizations or to a different solution.

  • Improved user help: Search results include results from the Target product documentation, as well as community forums and more video content, giving you easier access to more content to help get the most out Target. We’ve also added a feedback mechanism right in the Help menu, making it easier to report issues or to share your ideas.

  • Improved Net Promoter Score (NPS) feedback functionality, so the survey modal doesn’t disturb your flow of work.

  • Notifications for Target are not currently available in the Notifications drop-down in the header.

  NOTE

  These features will not be rolled out at once, nor will they be rolled out to all customers together. We will be rolling out these features over the course of the next few weeks, starting with the Target Standard/Premium 19.10.1 (October 22, 2019) release.

  As part of the rollout of the new navigation bar, you will also notice some URL changes. All previous bookmarked links continue to work but we encourage you to bookmark new links for faster opening.

at.js versions 2.2 and 1.8 (October 10, 2019)

Feature / Enhancement

Description

at.js version 2.2 and at.js version 1.8

These versions of at.js provide: Improved performance when using both Experience Cloud ID Service (ECID) v4.4 and at.js 2.2 or at.js 1.8 on your web pages. Previously, the ECID made two blocking calls before at.js could fetch experiences. This has been reduced to a single call, which significantly improves performance. In order to take advantage of these performance improvements, upgrade to at.js 2.2 or at.js 1.8 along with ECID Library v4.4. at.js 2.2 provides: serverState: A setting available in at.js v2.2+ that can be used to optimize page performance when a hybrid integration of Target is implemented. Hybrid integration means that you are using both at.js v2.2+ on the client-side and the delivery API or a Target SDK on the server-side to deliver experiences. serverState gives at.js v2.2+ the ability to apply experiences directly from content fetched on the server side and returned to the client as part of the page being served. For more information, see “serverState” in targetGlobalSettings.

Target platform (October 9, 2019)

Feature / Enhancement	Description
Node.js SDK version 1.0	The Target Node.js SDK lets you deploy Target server-side. This Node.js SDK helps you easily integrate Target with other Experience Cloud solutions, such as the Adobe Experience Cloud Identity Service, Adobe Analytics, and Adobe Audience Manager. The Node.js SDK introduces best practices and removes complexities when integrating with Adobe Target via our delivery API so that your engineering teams can focus on business logic. The following are notable features that we are introducing in the latest version: Support for prefetching and notifications that allows you to optimize for performance via caching. Support for optimizing performance when you have a hybrid integration of Target on both your web pages and server-side. We are introducing a setting called serverState that will be populated by experiences retrieved via the server-side so that at.js 2.2 will no longer make an additional server call to retrieve the experiences. This approach optimizes page load performance. Support for retrieving VEC-created activities via the Node.js SDK, which is made possible by the new Delivery API. Open sourced so your developers can contribute to the Node.js SDK.
Delivery API	An entirely new delivery API endpoint (/v1/delivery?lang=en) is available in production. Notable features are: One endpoint to retrieve experiences for one or more mboxes. Retrieve VEC-created activities via the API. Support for an entirely new object called Views that is used for Single Page Applications (SPAs) and Mobile applications.

Target Standard/Premium 19.9.2 (September 30, 2019)

This maintenance release includes the following enhancement:

• Several security fixes, including a security update to the Rich Text Editor (RTE) in the Visual Experience Composer (VEC). (TGT-35383)
• Recommendations Offers can now be added to elements other than DIV (e.g. P, UL, H1), in addition to DIV, in A/B Test and Experience Targeting activities. (TGT-34333)
• Event notifications (the bell icon in the Target UI) is no longer available. A new look for notifications is coming soon.

Target Standard/Premium 19.9.1 (September 10, 2019)

Feature / Enhancement	Description
Enterprise Permissions	With the Target September 2019 release, Enterprise Permissions provides customers with the following access controls: You can choose the workspaces to which the integration can be applied. You can apply a role to the Adobe I/O integration: Approver, Editor, or Observer. For step-by-step instructions and more information, see Grant Adobe I/O integrations access to workspaces and assign roles.

Target Standard/Premium 19.7.1 (July 24, 2019)

This release includes the following new features and enhancements:

(The issue numbers in parentheses are for internal Adobe use.)

Feature / Enhancement	Description
Recommendations in A/B Test and Experience Targeting (XT) activities	The Recommendations offer (algorithm) status displays on the Overview page for A/B Test and XT activities that contain Recommendations offers. Statuses include: Results Ready, Results Not Ready, and Feed Failure. (TGT-33649) See Recommendations as an offer.
Cross-domain tracking support for at.js 2.0+ via the Experience Cloud ID (ECID) library	Previously, cross-domain tracking was not supported in at.js 2.x. With this release, customers using at.js 2.0 or above can now utilize cross-domain tracking through the ECID library. The ECID library must be installed on the page in conjunction with at.js 2.0 or above in order for cross-domain tracking to work. Experience Cloud ID library 4.3.0+ must be used. See Cross-domain tracking support in at.js 2.x.
Target support for Apple’s ITP 2.1 and ITP 2.2 via the Experience Cloud ID (ECID) library 4.3	Today, Target customers can mitigate Apple’s ITP 2.1 and ITP 2.2 by leveraging Adobe’s CNAME certification program. With this release, Target introduces a seamless integration with the ECID library 4.3, which leverages a server-side cookie to mitigate ITP 2.1 and ITP 2.2. It is highly recommended that Target customers deploy ECID library 4.3+ in conjunction with Target’s JavaScript library to mitigate any future ITP releases. The ECID library will continue to roll out enhancements that provide a robust solution to the ever-changing cookie policies introduced by browsers. See Apple Intelligent Tracking Prevention (ITP) 2.x.

Enhancement, fixes, and changes

• Fixed an issue that prevented exclusion values in Recommendations activities from being cleared when adding duplicate values. (TGT-34996)
• You can now remove a design in a Recommendations activity from the Targeting page (Step 2 of the three-part guided workflow). Note that to remove a design, there must be more than one design selected. (TGT-35118)
• Fixed an issue that prevented custom criteria cards for some customers to load properly in the Target UI or to be editable. (TGT-35170)

at.js version 2.1.1 (July 24, 2019)

This release of at.js is a maintenance release and includes the following enhancements and fixes:

(The issue numbers in parentheses are for internal Adobe use.)

• Fixed an issue that caused multiple beacons to fire when using the Click Tracking metric on the Goals & Settings page in the Visual Experience Composer (VEC). (TNT-32812)
• Fixed an issue that caused triggerView() to not render offers more than once. (TNT-32780)
• Fixed an issue with triggerView() to ensure that the request contains Marketing Cloud ID (MCID) information. (TNT-32776)
• Fixed an issue that prevented the triggerView() notification to fire even if there are no saved views. (TNT-32614)
• Fixed an issue that caused an error due to the use of decodeURIcomponent that caused issues when the URL contains a malformed query string parameter. (TNT-32710)
• The beacon flag is now set to “true” in the context of delivery requests sent via the Navigator.sendBeacon() API. (TNT-32683)
• Fixed an issue that prevented Recommendations offers from displaying on websites for a few customers. Customers could see the offer content in the delivery API call but the offer was not applied on the website. (TNT-32680)
• Fixed an issue that caused click-tracking across multiple experiences to not work as expected. (TNT-32644)
• Fixed an issue that prevented at.js from applying the second metric after the rendering of the first metric fails. (TNT-32628)
• Fixed an issue when passing mboxThirdPartyId using the targetPageParams function that caused the request payload to not be present in either the query parameters or in the request payload. (TNT-32613)
• Fixed an issue that caused display and click notification responses to be blocked in Chromium-based browsers (including Google Chrome). (TNT-32290)

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

Target Standard/Premium 19.6.1 (June 26, 2019)

This release includes the following new features and enhancements:

(The issue numbers in parentheses are for internal Adobe use.)

Feature / Enhancement	Description
Visual Experience Composer (VEC)	New VEC menu options: When you click a page element in the VEC, a menu shows the options that are available for that element type. You can now use the Styles > Background option to change the background image and color for the selected element. (TGT-15001) See Styles in Visual Experience Options. Click-tracking improvements: We have improved the process for configuring click tracking within the VEC and the Single Page Application (SPA) VEC. While selecting elements to use in click tracking, the names of all available elements display in the Modifications panel on the right side, making it quick and easy to select the desired elements. The Goals & Settings page of the three-part guided activity workflow displays a number representing the number of elements selected for click tracking. You can hover over this number to see the names of all selected elements. (TGT-33878) See Click tracking.
Single Page App Visual Experience Composer (SPA VEC)	Guided workflow: A new guided workflow helps you understand how page-delivery-rule settings should be configured to execute and run an activity successfully for your Single Page App. (TGT-33718) See Single Page App (SPA) Visual Experience Composer. Clone modifications: You can now define a modification using the SPA VEC and then clone that modification for use in other views in your Single Page App. (TGT-33882) See Single Page App (SPA) Visual Experience Composer.
Automated Personalization (AP) & Auto-Target	Specific experience as control: You can select an experience to be used as control while creating an AP or Auto-Target activity. This feature lets you route the entire control traffic to a specific experience, based on the traffic allocation percentage configured in the activity. You can then evaluate the performance reports of the personalized traffic against control traffic to that one experience. The current control option (randomly served experiences) will continue to be available. (TGT-32801, TGT-26572, & TGT-26571) See Select the control for your Automated Personalization or Auto-Target Activity. Personalization Insights reports: The marketer-friendly naming for attributes when a visitor sees a specific piece of content in a specific location provides more meaningful information. (TGT-33421 & TGT-34957) See Data collection for the Target personalization algorithms.
Recommendations	You can use the Recommend Previously Purchased Items toggle while creating Recently Viewed Items logic. (TGT-34030) For more information, see Recently Viewed Items in “Create criteria.”
Google Chrome SameSite cookie policies	Google recently announced that starting with Chrome 76, which is slated for a July 30, 2019 release, developers must explicitly specify which cookies can work across websites and which cookies can track users. As the industry makes strides to create a more secure web for consumers, Target is absolutely committed to delivering personalized experiences while meeting and exceeding the privacy expectations of visitors. See Google Chrome SameSite cookie policies.

at.js version 2.1.0 (June 3, 2019)

We are thrilled to announce the following exciting features in at.js 2.1.0:

Feature / Enhancement	Description
Adobe Opt-in support	Adobe Opt-In is a way to simplify Adobe solutions integrations with consent management platforms. For more information about Adobe Opt-in, see Privacy and General Data Protection Regulation (GDPR).
Industry-standard CSP compliant	at.js no longer uses eval() to execute JavaScript.
Client-side analytics logging	Gives customers full control on how they want to send analytics data to Adobe Analytics, whether on the client-side or server-side. For more information, see Client-side Analytics logging in Before you implement.
Send notifications	Allows developers to send notifications when an experience is rendered by their code instead of using applyOffer() or applyOffers(). For more information, see adobe.target.sendNotifications(options).
Reduced file size	The size of at.js is reduced by ~24%. The smaller file size improves page load performance and reduces the time to download at.js on the page.
at.js documentation updates	For a full list of all articles updated due to the at.js 2.1.0 release, see the June 3, 2019 entries in Documentation changes.

Target Standard/Premium 19.5.1 (May 21, 2019)

(The issue numbers in parentheses are for internal Adobe use.)

Feature updates

Feature / Enhancement

Description

Single Page App Visual Experience Composer (SPA VEC)

The SPA VEC includes the following enhancements to make your work quicker and more efficient: Clicking an action in the SPA highlights the element on the site where this action will be applied. Each VEC action created under a View has four corresponding icons: Information, Edit, Move, and Delete. New “Move” functionality in this release lets you move the action to a Page Load Event or any other View that already exists in the modifications panel. (TGT-33746) You can perform many actions before the page loads in the VEC, or even if the page fails to load altogether (for example, custom code is no longer operational). Actions that cannot be edited before the site loads are disabled in the Target UI. (TGT-33851 & TGT-34149) For more information, see Single Page App (SPA) Visual Experience Composer.

Enhancement, fixes, and changes

• Toolbar icons display appropriately after you cancel loading of a page within the VEC. If specific actions cannot be performed until after the page is fully loaded, the associated toolbar icons are disabled. (TGT-33811)

Target Standard/Premium 19.4.2 (April 30, 2019)

This release includes the following features, changes and enhancements:

(The issue numbers in parentheses are for internal Adobe use.)

Feature updates

Feature / Enhancement

Description

Visual Experience Composer

The Visual Experience Composer (VEC) includes the following enhancements to make your work quicker and more efficient: The DOM path feature is now available when setting up click tracking. For more information, see click tracking. Use the Styles panel to view or edit the value of existing styles for the selected element. You can also add additional styling. To access the Styles panel, click a page element from within the VEC, then click Edit > Styles. The Styles panel displays on the right side of the VEC. The panel contains a list of styles that lets you edit or add to the selected element. A real-time CSS Editor lets you view changes and add styles if you are comfortable using Cascading Style Sheets (CSS) or if you receive code from your developer. For more information, see Styles in Visual Experience Composer Options. The Rich Text Editor now supports nested HTML5 elements. HTML5 specifications allow new combinations of tags for nesting. The previous version of the rich text editor did not support new nesting of tags as allowed by the HTML5 specification. As a result, any nested elements selected in the VEC were not handled properly, which led to unwanted HTML changes. (TGT-33618) For more information, see Edit Text/HTML in Visual Experience Composer options.

Enhancement, fixes, and changes

• We improved the workflow when you delete assets using the VEC. Deleted assets are now removed from the Offers library and from Scene7 (if applicable). Deleted assets no longer display in search results. (TGT-31981)

• You can now delete asset folders even if they contain images (non-empty folders). (TGT-33265)

  Previously, you could not delete a non-empty folder from the Target image offers library (Offers > Image Offers). You would get a “Folder is not empty!” notification when trying to delete the folder from the UI. With this feature, we are adding the capability to let you perform the folder deletion to remove an entire folder containing any number of assets and sub-folders inside. This feature is available in the Target UI as well in the Adobe Experience Cloud Assets UI.

  • Non-empty folders in the Image Offer library can be deleted. If all images within the folder are not referenced in any activity, the entire folder and its contents are deleted. If some images within the folder are referenced in any activity, all unreferenced images are deleted, but referenced images and folders containing those images are retained.
  • Rendering of image offers in the Image Asset picker is made faster and more efficient.

  For more information, see Work with content in the library. (TGT-32897)

• We improved the rendering of image offers in the Assets picker. Displaying and selecting image offers is now quicker and more efficient. (TGT-32897)

• We improved the handling of redirects to URLs when you cancel loading of a page within the VEC. (TGT-33815)

• After you select a Recommendations collection from the Collections picker, you must now click the Save button. This workflow is consistent with other workflows within Target. (TGT-33205)

• Fixed an issue that caused a small set of Insights reports to return 0% conversion rates instead of the actual conversion rates. (TNT-32125)

Target Standard/Premium 19.4.1 (April 15, 2019)

This release is a maintenance release and includes the following change:

(The issue numbers in parentheses are for internal Adobe use.)

• Updated the Adobe Experience Cloud UI to reflect branding and product changes. (TGT-33546, TGT-33272, and TGT-33331)

Target Standard/Premium 19.3.1 (March 29, 2019)

This release includes the following features, changes and enhancements:

(The issue numbers in parentheses are for internal Adobe use.)

Feature / Enhancement

Description

Visual Experience Composer

The Visual Experience Composer (VEC) includes the following enhancements to make your work quicker and more efficient: You can now cancel the loading of a website in the VEC to unblock editing of an activity. This enhancement is useful, for example, if you want to make a small edit to the activity, review its settings, or add custom code and you don’t want to wait for the site to load. (TGT-31288) See Cancel loading of a page within the VEC. You can perform many actions before the page loads in the VEC, or even if the page fails to load altogether (for example, custom code is no longer operational). Actions that cannot be edited before the site loads are disabled in the Target UI. (TGT-31288, TGT-31611, and TGT-32602) See Edit a page while the page is loading or after the page fails to load. The VEC displays the DOM path so you can easily select the proper element while creating or editing experiences. (TGT-13422) See Navigate elements using the DOM path.

at.js version 2.0.1 (March 19, 2019)

This is a maintenance release and includes the following enhancements and fixes:

(The issue numbers in parentheses are for internal Adobe use.)

• Fixed a race condition in the DOM polling code that caused JavaScript exceptions for certain customers. (TNT-31869)
• Notifications that views were rendered have been decoupled from click-tracking event handlers. Initially, Target did not send notifications if click-event handlers belonging to a rendered view could not be attached. Target now sends a view notification even when click elements are not found. (TNT-31969)
• Fixed an issue that caused the request-succeeded event redirect flag to always be set to true. (TNT-31907)
• Fixed an issue that caused the VEC rearrange action to be logged as success, even when elements were missing. (TNT-31924)
• Fixed an issue that caused notifications for certain customers to not contain the Enterprise Permissions property token. (TNT-31999)

at.js version 1.7.1 (March 19, 2019)

This is a maintenance release and includes the following fix:

(The issue numbers in parentheses are for internal Adobe use.)

• Fixed a race condition in the DOM polling code that caused JavaScript exceptions for certain customers. (TNT-31869)

Platform Changes (February 19, 2019)

Feature/Enhancement	Description
at.js version 2.0.0 February 19, 2019	at.js 2.x is now available. The newest version of at.js provides rich feature sets that equip your business to execute personalization on next generation client-side technologies. This new version is focused on upgrading at.js to have harmonious interactions with single page applications (SPAs). Here are some benefits of using at.js 2.x that are not available in previous versions: The ability to cache all offers on page load to reduce multiple server calls to a single server call. Tremendously improve your end-users’ experiences on your site because offers are shown immediately via the cache without any lag time that traditional server calls introduce. Simple one-line of code and one-time developer setup to enable your marketers to create and run A/B and Experience (XT) activities via the Visual Experience Composer (VEC) on your single page applications. at.js 2.x introduces the following new functions: getOffers() applyOffers() triggerView() The following functions have been deprecated with the introduction of at.js 2.x: mboxCreate() mboxDefine registerExtension() For more information, see Upgrading from at.js 1.x to at.js 2.x and at.js functions. Note: If you require Adobe Opt-in support for the General Data Protection Regulation (GDPR){target=_blank}, you must currently use at.js 1.7.0. Opt-in support is not supported in at.js 2.x.
at.js version 1.7.0 February 14, 2019	at.js 1.7.0 is available. This release brings Adobe Opt-In support. Adobe Opt-In is a way to simplify Adobe solutions integrations with consent management platforms. For more information about Adobe Opt-in, see Privacy and General Data Protection Regulation (GDPR){target=_blank}. This release also fixes an issue where Target might override redirect URL parameters with parameters that are coming from the redirect URL. Note: If you require Adobe Opt-in support for GDPR, you must currently use at.js 1.7.0. Opt-in support is not supported in at.js 2.x. For a list of all versions, see at.js version details.

Target Standard/Premium 19.2.1 (February 19, 2019)

This release includes the following features, changes and enhancements:

(The issue numbers in parentheses are for internal Adobe use.)

Feature / Enhancement	Description
Single Page App Visual Experience Composer	The Visual Experience Composer (VEC) for Single Page Apps (SPAs) lets marketers create tests and personalize content on SPAs in a do-it-yourself fashion without continuous development dependencies. The VEC can be used to create activities on most popular frameworks, such as React and Angular. (TGT-27916) For more information, see Single Page App (SPA) Visual Experience Composer and Single Page Application integration. In addition to the above article, there are many topics related to SPAs and at.js that address this feature and how to implement it. For more information see Documentation changes.
Visual Experience Composer	The Visual Experience Composer (VEC) includes the following enhancements to make your work quicker and more efficient: You can now use the Insert Before and Insert After options in the VEC while inserting AEM experience fragments. See Visual Experience Composer options. (TGT-32385) The Adobe Target VEC Helper browser extension for Google Chrome lets you load websites reliably within the VEC to rapidly author and QA web experiences. See Visual Experience Composer helper extension. (TGT-32746)
Recommendations in A/B Test and Experience Targeting activities	You can now include recommendations inside A/B Test (including Auto-Allocate and Auto-Target) and Experience Targeting (XT) activities. This opens up entirely new capabilities, such as: Test and target recommendations and non-recommendations content within the same activity. Easily experiment with placement of recommendations on the page, including the order of multiple recommendations. Automatically push traffic to the best-performing recommendations experience using Auto-Allocate. Dynamically assign visitors to tailored recommendations experiences based on their individual profiles using Auto-Target. To get started, create an A/B Test or Experience Targeting activity using the VEC and use the Insert Before, Insert After, or Replace With action to add recommendations to an experience. (RECS-6166) For more information, see Recommendations as an offer.
Enterprise Permissions support in Target APIs	Adobe Target Admin APIs will now take full advantage of the same Enterprise Permissions capabilities found in the Target UI. Starting Feb 21, 2019, system administrators can programmatically access report data as well as create and manage activities, offers, and audiences within any workspace. These actions were previously limited to the default workspace only. Support for Automated Personalization (AP) activities will come in a future release.

Enhancement, fixes, and changes

• To improve security, Target now prevents accessing Amazon Web Services (AWS) metadata endpoints while loading the VEC. (TGT-33129)

Platform Changes (January 2019)

Feature / Enhancement	Description
Targeting January 25, 2019	Made changes to how targeting matches function for “equals” comparisons with non-decimal and decimal values returned by profile scripts or any other source of input, such as mbox parameters, profile parameters, etc. For more information, see Targets and audiences FAQ.
Profile scripts January 17, 2019	For performance reasons, we recommend a return value that is no longer than 256 characters. For a String return value, if the size of the return value exceeds 2048 characters, the script is disabled by the system. For an array return value, if the size of the concatenated values of the array exceeds 2048 characters, the script is disabled by the system. For more information about the character limits and other limits (offer size, audiences, profiles, values, parameters, etc.) that affect activities and other elements in Target, see Limits.
at.js January 16, 2019	at.js 1.6.4 is a maintenance release and addresses the following issues: Fixed a race condition manifesting in Microsoft Internet Explorer 11 that caused duplicate offers to be applied. (TNT-31374) Fixed an issue that affected click tracking when there is a default offer with a click-token and html offers. (TNT-31493) Extended the mboxEdgeCluster cookie with each Target request. This is used only when mboxEdgeOverride is enabled. (TNT-31485)

Target Standard/Premium 19.1.1 (January 22, 2019)

This release includes the following features, changes and enhancements:

(The issue numbers in parentheses are for internal Adobe use.)

Feature / Enhancement	Description
Enterprise Permissions support in Target APIs	Adobe Target Admin APIs will now take full advantage of the same Enterprise Permissions capabilities found in the Target UI. Starting Feb 21, 2019, system administrators will be able to programmatically access report data as well as create and manage activities, offers, and audiences within any workspace. These actions were previously limited to the default workspace only. Support for Automated Personalization (AP) activities will come in a future release.
Recommendations: filter collections and exclusions by environment (host group)	You can now preview the contents of Recommendations collections and exclusions for a selected environment (host group). Previously, when you viewed a collection or exclusion, the displayed items contained were results for the default host group (specified in Recommendations > Settings > Default Host Group). Now, when creating or updating a collection or exclusion, you can use the Environment selector to choose the environment to preview results for. The new Environment filter saves you time and effort because you no longer need to navigate to the Settings page to select the appropriate default host group before creating or editing collections and exclusions. Note: After changing the selected environment, you must click Search to update the returned results. The new Environment filter is available from the following places in the Target UI: Catalog Search (Recommendations > Catalog Search) Create Collection dialog box (Recommendations > Collections > Create New) Update Collection dialog box (Recommendations > Collections > Edit) Create Exclusion dialog box (Recommendations > Exclusions > Create New) Update Exclusion dialog box (Recommendations > Exclusions > Edit) For more information, see the following topics: Collections Exclusions Catalog Search Settings Recommendations: filter collections and exclusions by environment (host group) (TGT-20622)

Enhancement, fixes, and changes

• Fixed an issue that caused the Save button to remain disabled when the user logs in through the login pop dialog box on session expiry while editing an audience. (TGT-32722)

Release notes - 2018

Platform (November 15, 2018)

Feature / Enhancement

Description

at.js 1.6.3

at.js version 1.6.3 is now available. Selectors are now CSS-escaped if they contain IDs or CSS classes that start with a digit, two hyphens, or a hyphen followed by a digit (for example #-123). (TNT-31061) Fixed an issue introduced with at.js 1.6.2 where Visual Experience Composer (VEC) offers from different activities that apply to the same CSS selector did not respect activity priority. (TNT-31052) Fixed an issue with timing out a promise in environments where there was no native support for promises. (TNT-30974) Issues are now correctly captured and reported via the content-rendering failed event. Previously, JavaScript might have been reported to have run successfully, even if that wasn't the case. (TNT-30599) For more information, see at.js Version Details.

Target Standard/Premium 18.11.1 (November 12, 2018)

The Target Standard/Premium release on November 12 includes back-end enhancements, fixes, and changes. The Personalization Insights reports will be available November 14.

Feature / Enhancement

Description

Personalization Insights reports Note: Available November 14, 2018.

Two specialized reports are available to users of Automated Personalization (AP) and Auto-Target (AT) activities: Automated Segments: Different visitors respond differently to the offers/experiences in your AP/AT activity. This report shows how different automated segments defined by Target's personalization models responded to the offers/experiences in the activity. Important Attributes: In different activities, different attributes are more, or less, important to how the model decides to personalize. This report shows the top attributes that influenced the model and their relative importance. See Personalization Insights reports.

Target Standard/Premium 18.10.1 (October 24, 2018)

This release includes the following features and enhancements:

(The issue numbers in parentheses are for internal Adobe use.)

Feature / Enhancement	Description
Experiences	You can now copy an experience in an Experience Targeting (XT) activity so you can make minor changes to it without having to re-create the experience from scratch. This capability was already available for A/B Tests. (TGT-31504) See Create experience .
Offers in Automated Personalization (AP) activities	In the September 2018 release, we added an enhancement that lets you filter offers by reporting groups. You can now filter for Unassigned Offers so you can assign a reporting group to an offer that is not currently assigned to any reporting group. (TGT-31882) See Create an Automated Personalization activity .
Reporting source for activities	In Administration > Visual Experience Composer , you can select the reporting source for your activities, either Target or Adobe Analytics . You can also choose to select your reporting source per activity. Starting with this release, there are some important workflow considerations you should be aware of when you choose the reporting source in Preferences or per activity.

Enhancements, Fixes, and Changes

This Target release includes the following enhancements, fixes, and changes:

• Improved the handling of audiences referenced in Target activities that have been deleted in Adobe Audience Manager (AAM). (TGT-23338)

  • If an audience was deleted in AAM, a warning icon in both the Audience list and the audience picker displays. A tool-tip in the UI also indicates that the audience was deleted in AAM.
  • If you attempt to combine multiple audiences with a deleted audience, or if you attempt to save an activity that references a deleted audience, a warning message displays.

  See About audiences.

• Fixed an issue that prevented users in certain situations from being able to create an activity when Adobe Analytics was selected as the reporting source on the Administration page. Users saw a “Please select a report suite” message even though they were not given the option of selecting the report suite. (TGT-31968)

Platform (October 19, 2018)

Feature / Enhancement

Description

at.js 1.6.2

This is a maintenance release and addresses the following issue: Fixed an issue that on some customer sites lead to an infinite "async" loop. Important: In addition, at.js Version 1.6.2 also contains all of the enhancements and fixes included in at.js Version 1.6.1 and 1.6.0. These versions are no longer available for download. We recommend that you upgrade to version 1.6.2 if using 1.6.1 or 1.6.0. For more information, see at.js Version Details .

Target Standard/Premium 18.9.1 (September 26, 2018)

This release includes the following features and enhancements:

Feature / Enhancement	Description
Offers in Automated Personalization (AP) activities	You can now use multiple offers from the same location in an exclusion group. For a large number of exclusions (order of 1,000s), you will also observe faster loading of the Manage Content dialog box and preview page while authoring an Automated Personalization (AP) activity. (TGT-31329) See Manage Exclusions . You can now filter offers by reporting groups. (TGT-31643) See Creating an Automated Personalization Activity .
Visual Experience Composer (VEC)	We have added an Insert Before action to the (VEC). This is similar to the previously existing Insert After option. When you select an element on the page, you can click Insert Before and choose whether you want to insert an image, HTML, or text. The inserted element appears before the selected element. (TGT-30473) See Visual Experience Composer Options .

Enhancements, Fixes, and Changes

This Target release includes the following enhancements, fixes, and changes:

• We updated the look and feel of Criteria cards to be more intuitive and user-friendly. (TGT-30469)
• Performance improvements in UI for faster loading of pages.

Target Standard/Premium 18.8.1 (August 21, 2018)

This release includes the following features and enhancements:

Feature / Enhancement	Description
Personalization Insights reports	Access specialized reports for your Automated Personalization (AP) and Auto-Target (AT) activities: Automated Segments: See how different automated segments defined by Target's personalization models respond to offers/experiences in your activity. Model Attribute Ranking: See the top attributes that influenced Target's personalization models and the relative importance of each attribute. Note: This feature will be available soon. Stay tuned for an announcement of the exact date when this feature will be ready for you to use. See Personalization Insights Reports .
Visual Experience Composer (VEC)	You can dock the Modifications panel vertically along the side of the Target UI or horizontally at the bottom. See Modifications . We have grouped various VEC actions to make your job quicker and more efficient. (TGT-30472) See Visual Experience Composer Options . You can edit offers more efficiently, thanks to a larger edit window. (TGT-31052)
Tips and Tricks	Get the most out of Adobe Target by learning more about various features and see why you should give them a try. The Tips and Tricks functionality displays on the Activities list page and provides links to videos, use-cases, blogs, documentation, and much more. Become a Target Power User! See Tips and Tricks .
Target Basics Webinar Series	Participate in the new Target Basics Webinar Series, a Customer Success Webinar Series brought to you by the Community. The next webinar, Best Practices in Reporting & Value Socialization, is scheduled for August 22, 2018 from 8 to 9 a.m. (PDT). See Target Basics Webinar Series .

Enhancements, Fixes, and Changes

This Target release includes the following enhancements, fixes, and changes:

• We have added several improvements to make Target even more secure than it was before. (TGT-31090, TGT-31089, TGT-31143)

Target Standard/Premium 18.7.1 (July 25, 2018)

This release includes the following features and enhancements:

Feature / Enhancement	Description
A/B and Experience Targeting (XT) activities	Edit and delete experiences right from the activity diagram. Now you can jump into the Visual Experience Composer (VEC) for a specific experience or delete an experience right from the diagram. See: A/B activity: Add Experience XT activity: Create Experience (TGT-30229)
Audiences	Compare one profile attribute to another profile attribute instead of to a static number. See Creating a Profile Attribute Comparison Audience . (TGT-28406)
Custom Code	"Custom Code" is now available from the "Add Modifications" panel instead of having its own tab. You can also add more than one custom code and optionally name each custom code. (TGT-28504) See Modifications .
Recommendations	View a list of activities that reference a selected criteria on its Criteria card. The card lists active and inactive activities. (TGT-27672) From the activity diagram, Criteria cards now show when results are ready to display. (TGT-27673) See Criteria .
Experience Templates	Adobe Target Experience Templates are pre-coded offer samples with configurable inputs to be used in Target to execute some common marketer use cases. These experience templates are provided free to developers and marketers as a starting point to execute some common external use cases in Adobe Target - either via the Visual Experience Composer or Form-Based Experience Composer. Customization might be required to integrate successfully with your webpage or platform architecture. See Experience Templates .
Target Basics Webinar Series	Participate in the new Target Basics Webinar Series , a Customer Success Webinar Series brought to you by the Community.

Enhancements, Fixes, and Changes

This Target release includes the following enhancements, fixes, and changes:

• Increased the Rich Text Editor modal’s size for better usability. (TGT-24775)
• The diagrams in the Target step (step 2 of the three-step guided workflow) for Automated Personalization (AP) and Multivariate Test (MVT) activities have been redesigned to be more consistent with the designs used for A/B, Experience Targeting (XT), and Recommendations activities. (TGT-30712)
• The metric value for the Multivariate Test (MVT) Location Contribution report is now more consistent with the values for other metrics, which is rounded to two decimal places. (TGT-30921)

at.js Version 1.5.0 (June 22, 2018)

Feature / Enhancement

Description

at.js

at.js version 1.5.0 is now available. Note: The issue numbers in parentheses are for internal Adobe use. The details of the at-request-succeeded event contain the redirect flag. This flag can be used to determine if the page will be redirected to a different URL. If you want to know the URL, subscribe to at-content-rendering-redirect . (TNT-29834) Fixed an issue that caused window.targetGlobalSettings.enabled to fail with a runtime exception if it was set to false. (TNT-29829) Fixed an issue that caused the page to fail while loading in the Visual Experience Composer (VEC) if using custom code to a fire global mbox request and using body hiding. (TNT-29795) Added support for screenOrientation , devicePixelRatio , and webGLRenderer . These new Target request parameters are used for iPhone X and other modern device detection. For more information, see Mobile . (TNT-29781) Fixed an issue where the Adobe Audience Manager (AAM) location hint wasn't always sent. (TNT-29695) For browsers that support it, at.js 1.5.0 switches to MutationObserver for selector polling. Versions prior to at.js 1.0.0 used a MutationObserver polyfill, which proved to be problematic. To avoid the polyfill issues, version1.5.0 uses the following pseudo code to decide which scheduling mechanism to use: if MutationObserver is supported scheduler = MutationObserver else if document is visible scheduler = requestAnimationFrame else scheduler = setTimeout

Target Standard/Premium 18.6.1 (June 20, 2018)

This release includes the following features and enhancements:

Feature / Enhancement	Description
Visual Experience Composer (VEC)	When you click an action in the Modifications panel, the VEC automatically scrolls the web page and the corresponding element is highlighted. You no longer need to manually scroll down to find the HTML element that was affected by the modification. (TGT-30441)
Supported browsers	Added Microsoft Edge support for the Target UI and for content delivery. For more information, see . Supported Browsers (TGT-14102)
Recommendations	The Recently Viewed Items criteria now returns results specific to a given environment . If two sites belong to different environments and a visitor switches between the two sites, each site shows only recently viewed items from the appropriate site. If two sites are in the same environment and a visitor switches between the two sites, the visitor will see the same recently viewed items for both sites.

Enhancements, Fixes, and Changes

This Target release includes the following enhancements, fixes, and changes:

• The Backup row of the Recommendations CSV download now has a leading “*” (double quotes enclosing an asterisk) instead of * (a single asterisk).
• The Top Sold / Top Viewed row in the Recommendations CSV download no longer has a leading comma.

Target Platform Changes (June 19, 2018)

This release includes the following enhancement:

• Updated the device list to include the latest phone models. Added the capability to deliver targeted content to specific iPhone models by using the Device Marketing Name or Device Model.

  Customers using the Mobile SDK do not need to do anything to leverage this functionality. Customers using at.js must upgrade to at.js version 1.5.0.

  For more information, see Mobile. (TNT-26714 & TNT-28288)

Target Download API (June 5, 2018)

You can use the recommendations download API to download your recommendations in a .CSV file that can be viewed in a spreadsheet or text editor. For improved security, starting on June 5, 2018, Target will block HTTP requests and allow only HTTPS requests.

Target Standard/Premium 18.5.1 (May 22, 2018)

This release includes the following features and enhancements:

Feature	Description
Reports	You can save up to ten different presets of an individual activity's report after configuring it as desired (metrics, audiences, advanced settings, and so forth). All Target users can display, edit, and delete the various presets, regardless of who created them. (TGT-21268) You can configure an individual activity's report as desired and then save that configuration as your default/favorite preset. This is the view that displays whenever you view that activity's report going forward. (TGT-10082) Alerts and messages inside reports let you know if one (or more) audience, metric, host group, or experience has been deleted from a previously configured preset report. The alert or message instructs you to choose another audience, metric, host group, or experience to make a preset again. (TGT-29424) For more information, see the Target Preset section in Report Settings .
Profile scripts	You can view profile script information pop-up cards similar to offer information cards. These profile script information cards let you view the list of activities that reference the selected profile script, along with other useful metadata. (TGT-28253) For more information, see the Viewing Profile Script Information Cards section in Profile Script Attributes .
Audiences	Custom Audience creation now allows using the mbox parameter directly without having to mandatorily specify the mbox name. The mbox name is now optional. This change lets you use parameters from multiple mboxes or reference a parameter that has not yet been recorded on the edge. Alternately, you can also filter on mbox parameter with the mbox name filter. This same improvement has also been extended to Recommendations Criteria, Recommendations Promotions, and Template Testing rules. For more information, see Custom Parameters .
Recommendations	While selecting Recommendations criteria in the Form-Based Experience Composer, there is now a direct link to the selected Criteria card so you can quickly and easily edit the criteria. (TGT-28483) For more information, see Form-Based Experience Composer . Recommendations Criteria, Recommendations Promotions, and Template Testing rules creation now allow using the mbox parameter directly without having to mandatorily specify the mbox name. The mbox name is now optional. This change lets you use parameters from multiple mboxes or reference a parameter that has not yet been recorded on the edge. Alternately, you can also filter on mbox parameter with the mbox name filter. This same improvement has also been extended to Custom Audience creation. For more information, see Recommendations FAQ . Updated the UI for Recommendations Design cards.

Enhancements, Fixes, and Changes

This Target release includes the following enhancements, fixes, and changes:

• Updated the UI for Step 2 of the Target three-step guided workflow used to create or edit an A/B Test, Experience Targeting (XT), or Recommendations activity. (TGT-18911)

Target Standard/Premium 18.4.1 (April 25, 2018)

This release includes the following features and enhancements:

Feature	Description
Adobe Experience Manager (AEM) Experience Fragments	Using experience fragments created in AEM in Target activities lets you combine the ease-of-use and power of AEM with powerful Automated Intelligence (AI) and Machine Learning (ML) capabilities in Target to test and personalize experiences at scale.   AEM brings together all of your content and assets in a central location to fuel your personalization strategy. AEM lets you easily create content for desktops, tablets, and mobile devices in one location without writing code. There's no need to create pages for every device—AEM automatically adjusts each experience using your content. Target lets you deliver personalized experiences at scale based on a combination of rules-based and AI-driven machine learning approaches that incorporate behavioral, contextual, and offline variables.  With Target you can easily set up and run A/B and Multivariate activities to determine the best offers, content, and experiences. Experience fragments represent a huge step forward to link the content/experience creators and managers to the optimization and personalization professionals who are driving business outcomes using Target. For more information, see AEM Experience Fragments .
Reports	You can now refresh a report to update the report's table and graph view without refreshing the entire page, its configuration, or its date range. (TGT-28125) For more information, see Report Settings . The calendar in reports now contains pre-defined date ranges, such as Last 7 Days, Last 15 Days, and so forth. (TGT-29171) For more information, see Report Settings . The table view column width was modified to reduce horizontal scrolling when multiple metrics are applied. (TGT-26575)
UI localization	The Target UI is now available in the following languages: Chinese Simplified Chinese Traditional Korean Italian Portuguese
Audiences	When creating a custom audience based on an mbox parameter, mboxParameter no longer prompts you for mboxName . mbox name is now optional. This change lets you use parameters from multiple mboxes or reference a parameter that has not yet been recorded on the edge. (TGT-25807) Note: This feature is visible in the Target UI but is currently disabled. This feature will be enabled soon (date to be communicated).

Enhancements, Fixes, and Changes

This Target release includes the following enhancements, fixes, and changes:

• Transport Layer Security (TLS) is the most-widely deployed security protocol used today for web browsers and other applications that require data to be securely exchanged over a network. Adobe has security compliance standards that require the end-of-life of older protocols and is mandating the use of TLS 1.2 in order to have the most up-to-date and secure version in use. Starting with the Target 18.4.1 release (April 25, 2018), Adobe Target will take steps to move towards TLS 1.2 encryption and phase out support for TLS 1.0 encryption completely by September 12, 2018. It is important that you go through the specifics and plan out the changes for a smooth transition. For more information, see TLS (Transport Layer Security) Encryption Changes.
• UI for Recommendations Criteria Cards has been improved for better usability. (TGT-27829)

at.js (April 3, 2018)

This release includes the following features and enhancements:

Feature

Description

at.js

at.js version 1.3.0 is now available. For more information, see Download at.js and at.js Version Details . The following new events are available to help in tracing, debugging, and customizing interaction with at.js: LIBRARY_LOADED REQUEST_START CONTENT_RENDERING_START CONTENT_RENDERING_NO_OFFERS CONTENT_RENDERING_REDIRECT For more information, see at.js custom events . You can augment an at.js request with additional parameters that come from data providers. Data providers should be added to window.targetGlobalSettings under the dataProviders key . For more information, see "Data Providers" in targetGlobalSettings() . at.js requests now use GET, but it will switch to POST when the URL size exceeds 2048 characters. There is a new property named urlSizeLimit where you can increase the size limit if necessary. This change allows Target to align at.js to AppMeasurement, which uses the same technique. Target now enforces that the mbox key in the adobe.target.applyOffer(options) function is used. This key has been required in the past, but Target now enforces its use to ensure that Target has proper validation and customers are using the function correctly. For more information, see adobe.target.applyOffer(options) . at.js has improved event and click tracking functionality. at.js uses navigator.sendBeacon() to send event tracking data and will fallback to synchronous XHR when navigator.sendBeacon() is not supported. This fallback mostly affects Internet Explorer 10 and 11 and some versions of Safari. Safari will add support for navigator.sendBeacon() in the iOS 11.3 release. at.js can now render offers even when a page is opened in background tabs. Some Target Customers encountered an issue when requestAnimationFrame() was disabled because of the browser throttling behavior for background tabs. This release adds many performance improvements, including shorter callstacks when inspecting a Chrome CPU profile. at.js 1.3.0 no longer supports content delivery on Microsoft Internet Explorer 9. For a list of supported browsers, see Supported Browsers . Going forward, all requests are executed via XMLHttpRequest with CORS support with no JSONP requests. This change greatly improves security.

Target Standard/Premium 18.3.1 (March 20, 2018)

This release includes the following features and enhancements:

Feature	Description
Popularity by Entity Attribute	New: March 22, 2018 You can now choose the Popularity by Entity attribute in the existing flow when a Custom attribute is selected as the key. After selecting the desired key (in this case, a custom profile attribute), for "Recommendation Logic," you can choose two new options: Most Viewed Top Sellers
Audiences	While viewing an audience's definitions pop-up card (for example, from the Audience Library), you can now see other activities that reference that audience, if applicable. This way you can avoid accidental impact to activities while editing audiences. Previously, when you tried to delete an audience that was referenced by activities, a warning displayed informing you that the audience cannot be deleted with at maximum of 10 activities referencing the audience. For more information, see About Audiences .
Reports	Improved the lift and bounds information in reports to be more comprehensive and useful, including a tooltip that explains how bounds are calculated. (TGT-28729) For more information, see Average Lift, Lift Bounds, and Confidence Interval .
Automated Personalization (AP) and Auto-Target activities	Additional guidance is available in the UI and in Help to help you allocate traffic percentages more effectively in Automated Personalization (AP) and Auto-Target activities. For more information, see Determining Traffic Allocation and Creating an Automated Personalization Activity .
Recommendations: Inclusion rules, collections, and exclusions for Custom Criteria	You can now perform real-time filtering on top of your own custom criteria output. For example, you can limit your recommended items to only those from a visitor's favorite category or brand. This gives you the power to combine off-line calculations with real-time filtering. With the addition of inclusion rules on Custom Criteria, this turns otherwise static recommendations into dynamic recommendations based a visitor's interests. Custom Criteria are now configurable, like other criteria in recommendations. You can use collections, exclusions, and inclusions (including the special rules for Price and Inventory) in the same way as any other criteria. Collections and exclusions were already supported. This release adds inclusions. For more information, see Criteria . (TGT-28488)
Recommendations: Inclusion rules, collections, and exclusions for Recently Viewed Criteria	Recently Viewed items can now be filtered so that only items with a particular attribute are displayed. For example, a multi-national company with multiple businesses might have a visitor view items across multiple digital properties. In this case, you can limit the recently viewed items to display only for the respective property where it was viewed. This prevents Recently Viewed items from displaying on another digital property's site. Recently Viewed Criteria are now configurable, like other criteria in recommendations. You can use collections, exclusions, and inclusions (including the special rules for Price and Inventory) in the same way as any other criteria. Collections and exclusions were already supported. This release adds inclusions. For more information, see Criteria . (TGT-22843)
Target Extension for Adobe Launch	Launch is the next-generation of tag management capabilities from Adobe. Launch gives customers a simple way to deploy and manage all of the analytics, marketing, and advertising tags necessary to power relevant customer experiences. The Target extension lets you quickly and easily implement Target in your environment. For more information, see Implementing Target using Adobe Launch .

Enhancements, Fixes, and Changes

This Target release includes the following enhancements, fixes, and changes:

• When creating or editing A/B and Experience Targeting (XT) activities, Target retains information about the last opened experience, page, or experience version (via multiple audiences feature) and opens the appropriate page the next time you open the Target UI. (TGT-28225)
• Security fixes have been made for compliance purposes.

Target Standard/Premium 18.2.1 (February 15, 2018)

This release includes the following features and enhancements:

Feature

Description

The Adobe Marketing Cloud has been re-branded and is now called the Adobe Experience Cloud.

The Experience Cloud is Adobe's integrated family of digital marketing solutions and services. It's also an intuitive interface that lets you quickly access your cloud solutions and core services. Re-branding and UI Changes: Adobe Marketing Cloud has been re-branded and is now called the Adobe Experience Cloud. In addition, you will see UI changes in the Target interface and in the Solution Switcher.

Enhancements, Fixes, and Changes

This Target release includes some back-end enhancements, fixes, and changes.

Target Platform (January 18, 2018)

This release includes the following features and enhancements:

Feature	Description
at.js	at.js 1.2.3 adds support for JSON offers. JSON offers are supported only in activities created using the Form-based Experience Composer. Currently the only way to use JSON offers is via direct API calls. See Create JSON Offer .
Other changes	Exclusion rules, catalogs, algorithm inclusion rules, and run-time filtering are now case in-sensitive.

Target Standard/Premium 18.1.1 (January 23, 2018)

This release includes the following features and enhancements:

Feature	Description
Audiences	You can now create Time Frame audiences without start or end dates. This lets you use the same audience in multiple activities (without making a copy of the audience) while controlling the start and end dates at the activity level. See Time Frame . (TGT-25975) Copy and Edit functionality is available for activity-only audiences when you hover over an audience on the Choose Audience > Activity Only Audience page. Previously, this functionality existed only for Library audiences. See Creating an Activity-Only Audience . (TGT-27410) Activity-only audiences across activities can have the same name. Previously, duplicate names would result in the addition of time stamps—a duplicate audience named "Target on Weekday" would get saved as "Target on Weekday-1456732099201." Library audiences continue to require unique names. (TGT-17967)
Reports	You can now view confidence intervals for continuous variables. (TGT-22085) Target now displays lift bounds when statistically significant in reports.(TGT-27301, TGT-27794, and TGT-26387) See Report Settings .
Offers	Target now supports creation of JSON offers in the Offer Library for use in the Form-Based Experience Composer. See Create JSON Offer . (TGT-27064) You can now view the activities that reference a code offer in each offer's definition pop-up card. This functionality does not apply to image offers. See Offers . (TGT- 26277)
Recommendations	The UI now displays the status of uploading custom algorithm data for recommendations. See Uploading Custom Criteria . (TGT-23891) The Value is Present and Value is Not Present operators are now available while creating algorithm inclusion rules. See Use Dynamic and Static Inclusion Rules . (TGT-24110)
Adobe Target Insider newsletter	The Adobe Target Insider is a monthly newsletter for members of the Adobe Target community. Learn about product updates and future plans, personalization and optimization tips and tricks, customer successes, upcoming events, information-filled white papers, popular blog posts, and more. Read the announcement letter to learn more. Subscribe to the newsletter to help you deliver the exceptional customer experiences that drive business success.

Enhancements, Fixes, and Changes

This Target release includes the following customer-facing enhancements, fixes, and changes:

• You can now scroll the page while rearranging experiences on Step 2 of the three-step guided workflow while creating activities. (TGT-27652)
• You can right-click an activity from the Activity List to open the activity in a new tab. For example, in Firefox, right-click the desired activity > Open Link in New Tab. (TGT-27409)
• Made performance improvements to the Designs page (Recommendations > Designs). The speed to display and search for designs has been improved. (TGT-21792)
• at.js is now the default implementation option to download. (TGT-24676)
• URL validation now allows the use of double hyphens in the URL. Previously, a URL with double hyphens could not be loaded into the Visual Experience Composer (VEC). (TGT-28176)
• Multiple UI localization fixes for supported languages.

Releases 2017

Target Platform (November 8, 2017)

This release includes the following features and enhancements:

Feature

Description

at.js

at.js version 1.2.2 is now available. For more information, see Download at.js . Fixed an issue that returned a JavaScript error when the Target library loaded on a page using QUIRKS mode. (TNT-28312) Fixed an issue that caused Target click tracking to break Analytics data collection calls. (TNT-28261) Fixed an issue that caused getOffer() params to fail when targetPageParams() returns an empty string. (TNT-28359) Fixed an issue with session ID generation when using x-only. (TNT-28361) The default timeout for at.js is changed from 15 seconds to 5 seconds. If your current setting was 15 seconds, it will be updated to the new default of 5 seconds. If you previously changed it to something different, your setting will not be affected.

Target Standard/Premium 17.11.1 (November 8, 2017)

This release includes the following features and enhancements (issue numbers in parentheses are for internal Adobe use):

Feature	Description
Offers	If a user has the "Editor" permission, that user cannot edit an offer referenced to a live or scheduled activity. Note: For Target Premium customers using Enterprise User Permissions , if a user selects the All Workspaces option, Target uses the highest permission of the user across workspaces. If the highest permission is "Editor," Target restricts editing as mentioned above . These restrictions apply to all offers, not just offers created in Target. (TGT-27276)
Response tokens	Added the following built-in parameters: profile.tntId profile.marketingCloudVisitorId profile.thirdPartyId profile.categoryAffinity profile.categoryAffinities For more information, see Response Tokens .

Target Standard/Premium 17.10.1 (October 25, 2017)

This release includes the following features and enhancements (issue numbers in parentheses are for internal Adobe use):

Feature	Description
Audiences	You can create activity-only audiences from within the three-step guided workflow when creating an activity. This audience can be used in other places within the same activity, but is not stored in the Audiences Library for use in other activities. (TGT-25474) For more information, see Creating an Activity-Only Audience . For all activities, you can choose a success metric that qualifies the user for the audience. In the past, Target qualified users for an audience when they entered the activity, whereas now you can choose when to evaluate the audience by choosing a success metric. (TGT-15805) For more information, see Apply a Reporting Audience to a Success Metric .
Auto-Target	Auto-Target activities now support segment-level reporting. (TGT-22777) For more information, see Auto-Target For Personalized Experiences . You can change the Control percentage for Auto-Target activities. (TGT-26467) For more information, see Auto-Target For Personalized Experiences .
Offers	You can now view offer definition details on a pop-up card in the Offers Library without opening the offer. (TGT-26377) For more information, see Offers . You can copy and edit offers and folders in the Offer selector while creating an activity. (TGT-26936) For more information, see Offers .
Form-based Experience Composer	In the Form-based Experience Composer, Refinements have been replaced with full audience functionality. Refinements for existing activities have been migrated to activity-only audiences. (TGT-13646) For more information, see Form-Based Experience Composer .
Response Tokens	You can now create response tokens from Target without waiting for them to be created in or imported to Target. Previously, in the Response Token UI, you could see only the tokens created via API. Changes to the feature also help you avoid response tokens duplicates. (TGT-26534) For more information, see Response Tokens .

Enhancements, Fixes, and Changes

This Target release includes the following customer-facing enhancements, fixes, and changes:

• You can delete imported audiences (Target Classic, Experience Cloud, etc.) from the Audience Library. Target warns you if you try to delete an audience used for an active activity. (TGT-25171)
• Audiences imported from Target Classic are now labeled as Adobe Target Classic in the Audience Library. In the past, the UI did not differentiate between Target Standard/Premium and Target Classic. (TGT-27093)
• Collections now apply to all criteria (including recently viewed items). (TGT-26646)
• You can filter by Workspace in the Audience Library and Offer Library (applies to Target Premium users with Enterprise User Permissions). (TGT-26813)
• Made improvements in the Reports UI for better scrolling in tables and placements of filter drop-down lists. (TGT-23713 & TGT-26819)

Target Platform Changes (October 13, 2017)

Change	Details
at.js	October 13, 2017 at.js version 1.2.1 is now available. For more information, see at.js Version Details . Fixed an issue when click tracking on a link with target="_blank" prevented Target from opening the link in a new tab.

Target Standard/Premium 17.9.1 (September 25, 2017 & October 12, 2017)

This release includes the following features and enhancements (issue numbers in parentheses are for internal Adobe use):

Feature	Description
Mobile Experience Preview	Updated: October 12, 2017 You can now select multiple mobile app activities from the UI and preview them on your device. This feature will allow you to enroll yourself into multiple experiences for previewing and QA without relying on special test builds and simulators. This feature requires that you download and install the appropriate 4.14 (or later) version of the Adobe Mobile SDK. For more information, see Target Mobile Preview .
Mobile Batch and Prefetch Delivery	Updated: October 12, 2017 Content for multiple mboxes can be pre-fetched in a single call and cached locally on the device without worrying how, when, and if the end user will see the content. This feature requires that you download and install the appropriate 4.14 (or later) version of the Adobe Mobile SDK. For more information, see Prefetch Offer Content .
Activities	The following enhancements have been made in the activity-creation workflow: While editing an activity, you can make the desired changes on the currently displayed step, click the drop-down on the split button, then select Next to advance to the next step, click Save and Close to save your changes and display the activity's Overview page, or click Save to save your changes and remain on that step. For more information, see Edit an Activity or Save as Draft . While editing an activity, you can open the desired workflow step, make your changes (for example experience percentages, audiences, and so forth), then save or close the activity without having to advance through the three-step guided workflow. For more information, see Edit an Activity or Save as Draft . When you are creating a new activity that has not yet been saved, or you are editing an activity that was previously saved in draft form, the Save Draft options display in the split button. For more information, see Edit an Activity or Save as Draft . You can now edit or copy an audience by hovering over the desired audience in the Choose Audience dialog box while choosing targeting in step 2 of the three-step guided workflow. For more information, see Select Audience .
Reporting	The following new features and enhancements are available for reporting: You can choose the counting methodology for graphs in reports. Note that this is not supported in Auto-Target and Automated Personalization (AP) activities. For more information, see the "Counting Methodology" row in Report Settings . You can view multiple metrics in a single report for Auto-Target A/B activities. (TGT-23464) For more information, see View Multiple Metrics in a Report .
Audiences	You can now view the definitions of audiences imported from Target Classic or created via API. (TGT-22630) For more information, see "Viewing Audience Definitions" in About Audiences .
Code Editor	The Form-based Experience Composer and the HTML offers editor now use the same code editor that the Visual Experience Composer (VEC) uses in custom code. (TGT-25808) This enhancement gives you the following features when using the code editor in the Form-based Experience Composer and when creating HTML offers: Line numbers are now visible for better usability. Syntax highlighting helps you avoid incorrect syntax for HTML offers. For more information, see Code Editor .
Geo Targeting	You can now use latitude and longitude in geo-targeting. (TGT-12129) For more information, see Geo .
Node.JS SDK	You can install the node.js SDK from npm @adobe/target-node-client to easily implement and run server-side tests on your node.js applications. The VisitorID service is enabled in the node SDK to connect all your Adobe data and you can use choose to use Adobe Analytics as your reporting source (A4T).

Enhancements, Fixes, and Changes

This Target release includes the following customer-facing enhancements, fixes, and changes (issue numbers in parentheses are for internal Adobe use):

• Users with Approver permissions can now generate and enable profile API authentication tokens. (TGT-24074)

  For more information, see Profile API Settings.

• When creating an activity in the Visual Experience Composer and the user reloads the page, the activity URL and associated properties are retained in the UI. The need to reload can occur if the activity uses mixed content (secure and insecure content) or there are permission issues. (TGT-28230)

• Improved the messaging when an activity uses mixed content (secure and insecure content). The message provides information to help users perform the necessary steps needed to open an HTTP site or a site that has mixed calls (HTTPS and HTTP). (TGT-26271)

For more information, see Enabling Mixed Content in Your Browser.

• Improved the workflow when a user’s Target session times out while configuring options on the Administation, Audiences, and Recommendations pages. When the user clicks Save, the session-expired message displays, but after logging back in, a dialog informs the user of a successful login and the UI remains on the same page in Target with no data loss. (TGT-25557)

Target Platform Changes (September 27, 2017)

Change	Details
at.js	September 27, 2017 at.js version 1.2.0 is now available as a maintenance release that contains mostly bug fixes. For more information, see at.js Version Details . Fixed an issue that prevented default actions for click-tracking special cases. (TNT-28089) Fixed an issue when click-tracking on a link with target="_blank" that prevented Target from opening the link in a new tab. (TNT-28072) IP addresses can be used as the cookie domain. (TNT-28002) Fixed an issue that caused flicker in redirect offers with a global mbox or other regional mboxes. (TNT-27978) Fixed an issue in Experience Targeting activity setup failing within the VEC when switching between Browse and Compose. (TNT-27942) Fixed incorrect handling on flicker style classes for click-track elements. (TNT-27896) Fixed an issue that caused global mbox parameters to become mixed up with all mbox parameters. (TNT-27846) Made changes to ensure that Handlebars, Mustache, and other client-side templating libraries are properly handled by at.js . (TNT-27831) Made changes to ensure that sdidParamExpiry is properly initialized and passed to the Visitor API. This is a regression that has been added to at.js 1.1.0 . Previous at.js versions are not affected. This affects only clients using redirect offers and A4T. (TNT-27791) Made changes to ensure that SCRIPT is executed regardless of the type attribute being used. (TNT-27865)
Experience Targeting (XT)	September 21, 2017 With the release on September 21, Target will change the way users are placed into experiences in Experience Targeting (XT) activities (Landing Page campaigns in Target Classic). For all new and existing activities in both Target Standard/Premium and Target Classic, users must meet the experience targeting rules on every impression to continue to see the experience's content and to be counted in reports. Previously, if the user no longer qualified for any experience, the user would continue to see the content from, and be counted in reports for, the last experience they did qualify for. This change will happen automatically as part of the release for all existing activities and for any new activities created post-release. If the previous method (prior to September 21) is desired, you can create audiences using profile scripts so a user only must meet a condition once to continue to fall into that audience in the future. Then, use those audiences for each experience in the activity.

Target Standard/Premium 17.8.1 (August 22, 2017)

Feature	Description
Enterprise User Permissions for Target Premium	Create separate workspaces in Target and then assign users different roles and permissions for individual digital properties. For more information, see Enterprise User Permissions .
QA Mode	Perform easy activity QA with preview links that never change, optional audience targeting, and QA reporting that stays segmented from live activity data. For more information, see Activity QA .

Enhancements, Fixes, and Changes

This Target release includes the following customer-facing enhancements, fixes, and changes: (issue numbers in parentheses are for internal Adobe use):

• We’ve added more places where you can view audience definition details on a pop-up card in the Target UI without opening the audience. Note that this functionality applies only to audiences created in Target Standard/Premium. (TGT-25772)
• You can now view definitions of adhoc audiences inside activity creation/overview. (TGT-25570)
• The following variables are now available as Velocity arrays: entiites and entityN.categoriesList.

Target Platform Changes (August 3, 2017)

Change

Details

at.js

August 3, 2017 at.js version 1.1 is now available. For more information, see Download at.js . The following enhancements and fixes are included in at.js version 1.1: Added response token handling. For more information, see Response Tokens . Resolved issue so that document.currentScript polyfill doesn't interfere with Angular 1.X. Made changes to ensure that click tracking doesn't interfere with visibility property. Click tracking elements are marked with the at-element-click-tracking CSS class instead of at-element-marker .

Target Standard/Premium 17.7.3 (August 3, 2017)

Feature

Description

Response Tokens

Response tokens let you automatically output eligible variables (e.g., profile attributes) in the Target responses that deliver activities (i.e. display mboxes). Response tokens can be used for debugging purposes or for integration with 3rd-party providers (such as Clicktale). Response tokens are similar to Adobe Target Classic server plug-ins and provide feature parity between the two solutions. Note: Response tokens are available with at.js 1.1 or later.. For more information, see Response Tokens .

Target Standard/Premium 17.7.2 (July 27, 2017)

Feature

Description

Auto-Target

Auto-Target in now available to all Target Premium customers. Auto-Target uses advanced machine learning to identify multiple high performing marketer-defined experiences, and serves the most tailored experience to each visitor based on their individual customer profile and the behavior of previous visitors with similar profiles, in order to personalize content and drive conversions. While creating an A/B activity using the three-step guided workflow, you can choose to allocate traffic using the Auto-Target For Personalized Experiences option: For more information, see Auto-Target For Personalized Experiences .

Target Standard/Premium 17.7.1 (July 20, 2017)

Feature	Description
Audiences	You can now view audience definition details on a pop-up card in various places in the Target UI without opening the audience. Note that this functionality applies only to audiences created in Target Standard/Premium.
Success metrics	Previously, Target allowed dependency on a single metric and that metric had to be reached before its count incremented. You can now provide dependency on multiple metrics along with the flexibility to choose whether the metric should be reached or not reached for the count to increment. Multiple-metric dependency functionality is not supported for the following: Recommendations activities. This functionality is supported for all other activity types. If you use Analytics as your reporting source (A4T). The "Viewed a Page" metric type. The "Clicked an Element" metric type for Visual Experience Composer (VEC) activities. For more information, see the following topics: A/B: Goals and Settings Automated Personalization (AP): Creating an Automated Personalization Activity Experience Targeting (XT): Goals and Settings Multivariate (MVT): Goals and Settings
Reporting (Auto-Allocate A/B Tests)	The ability to view multiple metrics is now available for Auto-Allocate A/B activities. For more information, see View Multiple Metrics in a Report .
Audiences	Audience site page types and comparison operators now match types and comparison operators in Target Classic. You can now create site pages audiences using you own "user-defined query parameter" or "user-defined header." For more information, see Site Pages .
Activities	The Activity list now lets you filter on Auto Allocate and Auto Target activity types. For more information, see Activities .
Recommendations Criteria & Promotions	You can now handle empty values when filtering by Entity Attribute Matching, Profile Attribute Matching, and Parameter Matching. For more information, see Use Dynamic and Static Inclusion Rules .

This Target release includes the following customer-facing enhancements and fixes: (issue numbers in parentheses are for internal Adobe use):

• Improved the workflow when a user’s Target session times out while creating or editing an activity or offer. When the user clicks Save, the session-expired message displays, but after logging back in, a dialog informs the user of a successful login and the UI remains on the same page in Target with no data loss.

  If a user performs intermittent action on a Target page and experiences a session timeout, the user is directed to re-log in and is then directed to the last page worked on in the Target UI.

• Fixed an issue that caused custom code changes to be lost if the user browses away (changes experiences, switches page, switches audience, clicks Next, etc.) and forgets to save changes. The user is now prompted to save the changes. (TGT-23766)

• When an activity is archived, “Archived the activity” displays instead of “Updating the activity.” (KB-1517)

• The drop-down picker in the following locations within the Target UI has been replaced with auto-complete functionality to improve speed and performance: (TGT-22939)

  • Activity Page > activity > Step3 > Report Suite picker
  • Audiences > Create Audience > Visitor Profile
  • Recommendations > Feed Creation > When source type > Analytics > Report Suite picker

• Improved error messaging when a site has “X-Frame-options” set to SAMEORIGIN and the site cannot be loaded in the Visual Experience Composer (VEC). The message prompts the user to switch to the Enhanced Experience Composer in Administration > Visual Experience Composer. (TGT-17356)

• Reports in Target Standard/Premium now display in your account’s time zone rather than the Target server time zone (US EST). (TGT-24868)

• If activities created in Target are updated from outside of Target (for example, via Adobe I/O), the following activity attributes are imported back into Target:

  thirdpartyId

  startDate

  endDate

  status

  priority

  marketingCloudMetadata(remoteModifiedBy)

  This import job will run when the activities page is opened, with a maximum delay of ten minutes. (KB-1526)

Target Standard/Premium 17.6.2 (June 22, 2017)

Feature	Description
Automated Personalization (AP) activities	Automated Personalization activities can be created using the form-based composer. New confidence numbers for Automated Personalization
Recommendations: Criteria and Promotions	You can now create dynamic criteria and promotions based on profile attribute matching and parameter matching. Note: If you are familiar with how inclusion rules were configured prior to the Target 17.6.1 release (June 2017), you'll notice that some of the options and operators have changed. Only those operators applicable to the selected option display and some operators were renamed ("matches" is now "equals") to be more consistent and intuitive. All existing exclusion rules created prior to this release were automatically migrated into the new structure. No restructuring is necessary on your part.
VEC Code Editor improvements	If the page format changes and actions cannot be applied, an alert now appears next to each failing action. Previously, a general error notified the user that the page structure had changed. Now, the code editor highlights each failed action.

This Target release includes the following customer-facing enhancements and fixes:

• Improved performance on host groups and recommendations entity search pages.
• More descriptive error messages throughout Target, especially when related to sync failures.
• Fixed an issue that caused the count on activity diagram to sometimes be incorrect in UI when auto-dedupe is applied after creating exclusion groups.
• Fixed an issue where the manual inclusions might not be correctly reflected in UI when an existing activity with Exclusion Group is edited.

Target Standard/Premium 17.6.1 (June 8, 2017)

Feature	Description
Experience Targeting (XT) activities	Drag-and-drop functionality lets you arrange audiences and experiences in the desired order while creating or editing XT activities. Visitors will be evaluated for experiences in order, from top to bottom. For more information, see Create Experience .
Reporting: A/B, XT, and Recommendations	Reports for A/B, XT, and Recommendations activities include visual representations that let you visually see the confidence interval and lift so that you can more accurately determine a winner. You can mouse over the representations to see the actual numbers. This feature is not available for activities that use Analytics as the reporting source (A4T). For more information, see Report Settings .
Automated Personalization (AP) activities	You can create Exclusion Groups in AP activities to ensure that experiences with the designated offers are automatically excluded.
Recommendations: Criteria and Promotions	(Scheduled to be released June 22, 2017) You can now create dynamic criteria and promotions based on profile attribute matching and parameter matching. For more information, see Use Dynamic and Static Inclusion Rules . Note: If you are familiar with how inclusion rules were configured prior to the Target 17.6.1 release (June 2017), you'll notice that some of the options and operators have changed. Only those operators applicable to the selected option display and some operators were renamed ("matches" is now "equals") to be more consistent and intuitive. All existing exclusion rules created prior to this release were automatically migrated into the new structure. No restructuring is necessary on your part.
Naming activities	You are now prompted to name the activity before saving. You cannot save an activity without a name.
New location for Target Forum	The Target Forum has moved to the new Adobe Community Platform .

Target Standard/Premium 17.4.1 (April 27, 2017)

This release includes the following features and enhancements:

Feature	Details
Reporting	View Multiple Goals/Metrics: You can now view multiple metrics in A/B and Experience Targeting (XT) activities, with the exception of Auto-Allocate and Auto-Target A/B activities. For more information, see View Multiple Metrics in a Report .

This Target release focuses on back-end fixes and includes the following customer-facing enhancements and fixes: (issue numbers in parentheses are for internal Adobe use):

• Fixed an issue that caused the “Increment Count, Release User & Allow Reentry” setting in Advanced Settings for activities to not function correctly. (TNT-26556)
• Fixed an issue that prevented Customer Attribute data from being removed from Target after being updated with NULL in the Experience Cloud user interface. (TNT-26462)

Target Platform Changes (April 13, 2017)

Change

Details

at.js

at.js version 0.9.6 is now available. For more information, see Download at.js . The following enhancements and fixes are included in at.js version 0.9.6: Redirect offer support for A4T. After you download and install at.js version 0.9.6, you can use redirect offers in activities that use Adobe Analytics as the Reporting Source for Target (A4T). Besides at.js version 0.9.6, there are other minimum requirements your implementation must meet in order to use redirect offers and A4T. For more information and additional important information you should know, see Redirect Offers - A4T FAQ . Prior to at.js 0.9.6, when the Visitor API was present on the page and the visitorApiTimeout setting was too aggressive, Target could run into a situation when no MCID data was sent in the Target request. This could lead to issues like unstitched hits in Analytics when using A4T. This behavior has been changed in at.js 0.9.6, even if the visitorApiTimeout is set to say 1 ms, Target will try to collect SDID, tracking servers, and customer IDs data and send those in the Target request. Added the selectorsPollingTimeout setting. For more information, see targetGlobalSettings() . The format of the response from getOffer() has been changed. For more information, see adobe.target.getOffer(options) . Console logging has been added for unsupported <!DOCTYPE> declarations. Fixed an issue where Target Classic plugins weren't being applied correctly when multiple default offers were delivered to a single mbox. (TGT-22664) Improved cookie-setting for two letter top-level-domains (TLDs) to ensure that the mbox cookie is set correctly for these domains (for example, test.no , autodrives.ca , and so forth). The algorithm for extracting the top-level domain that should be used when saving cookies has changed in at.js version 0.9.6. Because of this change, cookies cannot be saved to addresses that use IP. Most of the time, IP addresses are used for testing purposes, but as workarounds you can use DNS entries or adjust the hosts file on a local box. Fixed move and rearrange actions handling when properties are string values instead of integers. For information about this and previous versions of at.js , see at.js Version Details .

Target Standard/Premium 17.3.1 (March 30, 2017 - Updated April 13, 2017)

This release includes the following features and enhancements:

Feature	Description
Analytics for Target (A4T) Redirect Offers	Updated April 13, 2017. You can now use redirect offers in activities that use Analytics as the reporting source. These libraries must be included on both the page with the redirect offer and the page to which the visitor is redirected. As a part of this change, new URL parameters will automatically be added to your redirect URLs if the Visitor Id service is implemented on your site, regardless of whether or not you are using Analytics as the reporting source for that activity. For more information, see Redirect Offers - A4T FAQ .
Audiences	The following enhancements have been made to audience targeting: Week and Day Parting: You can set Week and Day Parting options to create recurring patterns for audience targeting. For more information, see Time Frame . Exclusions in Combined Audiences: You can now add exclusion rules and exclude audiences when combining multiple audiences. For more information, see Combining Multiple Audiences .
Recommendations	Dynamic Promotions: Target Recommendations now supports dynamic matches for promotions. For more information, see Use Dynamic and Static Inclusion Rules .

This Target release includes the following enhancements and fixes: :

• The Target user interface has been updated to support redirect offers in activities that use Analytics for Target (A4T) as the reporting source. This functionality will require at.js 0.9.6, which will be available soon.

• The Target user interface was updated in some places:

  • In reports and activities, some options ( Edit, Share to Feed, View Experience URLs, etc.) are now accessed by clicking the More Options icon (

    ).

  • In the Offers library, offers now display in a list rather as cards. Other minor UI changes were made throughout the Offers library UI.

• Significantly improved performance on the Activity and Audience lists. Also, load times for search results return significantly faster.

• “Views” is now “Visits” in the Offer Level Report for Automated Personalization reports.

• Target now supports switching of environments (host groups) for Automated Personalization activities.

• Automated Personalization activities now support host groups.

Target Standard/Premium 17.2.1 (February 21, 2017)

This Target release focuses on usability and performance improvements and includes the following enhancements and fixes (issue numbers in parentheses are for internal Adobe use):

• Added additional items to the Help menu that can be accessed from the top right corner of the Target user interface. New options include: “Blogs” and “Videos.” The “Adobe Experience Cloud Status” option is now “Adobe Target Standard/Premium Status.” (TGT-22629)

• When deleting an audience, Target displays a list of activities that reference that audience. Users can click each activity in the list to display its Overview page. (TGT-17997)

• Improved user.activeCampaigns to return the campaign ID for all campaigns/activities that the user is in, even if he or she has not interacted with the campaign/activity in the current session. (TNT-26237)

• The Create Activity button on the Activities page is now active before all activity names are loaded in the list. This improvement lets users create new activities faster, especially when the account has many configured activities. (TGT-21470)

• Made enhancements to the Enhanced Experience Composer (EEC) to improve loading time for websites running HTTPS accessed via proxy. Target no longer fetches static resources via proxy. (TGT-21793)

• Made performance improvements on the Goals & Settings page, especially load time when many metrics are defined for an activity. (TGT-21654)

• Added a tool tip on the Goals & Settings page of all activities using Analytics for Target (A4T) reporting informing users that a tracking server is not required if the activity’s pages have at.js (version 0.9.1 or later) loaded. (TGT-22607)

• Metric names now display on the Goals & Settings page without users needing to expand each metric to view the entire metric name. This improvement lets users edit metrics quicker and more efficiently. (TGT-21276)

• You can now apply Recommendations inclusion rules to custom criteria (uploaded via CSV), just like any other criteria. (TGT-21896)

• Improved the user interface and usability of the Offers page, especially when creating or managing folders and creating offers. (TGT-22509 and TGT-22187)

• Improved the user experience in the Visual Experience Composer (VEC) when selecting items to hide.
  (TGT-22224)

• Improved the user experience when creating activities using the Form-Based Experience Composer. When choosing an mbox location, the validation border remains highlighted after clicking Next. (TGT-22221)

• Enhanced the downloaded reports to differentiate between active and deleted offers. (TGT-22449)

• Fixed an issue that prevented older assets from displaying in the infinitely scrollable asset list in the Experience Cloud Assets core service user interface. (TGT-19733)

• Fixed an issue where the extreme order setting was not honored in downloaded CSV reports. (TGT-21871)

• Fixed an issue where extreme orders were not marked correctly in the downloaded Order DetailsCSV report. (TGT-22500)

• Fixed an issue that caused the incorrect order time to display in the downloaded Campaign Audit CSV report, even though the report displayed the correct order date. (TNT-26469)

• Fixed an issue that prevented the Disable JavaScript option from working correctly on multi-page activities. (TGT-15130)

• If you use the Form-Based Experience Composer with an mbox other than the auto-created global mbox ( target-global-mbox), and then choose an engagement metric as a success metric, the metric increments only on pages that have the mbox used in the activity. As an example, if your mbox is homepage_mbox, the Pages Per Visit metric is the number of hits to the homepage_mbox during that visit.

  If this is not what you want, you can add another location to the activity and assign the global mbox to that location and give it default content. This workaround connects the global mbox to the activity and allows Target to count the metric for reporting.

Target Platform Changes (January 18, 2017)

Change

Details

at.js version 0.9.4

January 18, 2017 at.js version 0.9.4 contains the following changes: mbox names can now contain special characters, including ampersands ( & ). (TNT-26144) For more information, see at.js Configurations . Added secureOnly setting that indicates whether at.js should use HTTPS only or be allowed to switch between HTTP and HTTPS based on the page protocol. This is an advanced setting that defaults to False and can be overridden via targetGlobalSettings . (TNT-26183) For more information, see targetGlobalSettings() . The Legacy Browser Support option is available in at.js version 0.9.3 and earlier. This option was removed in at.js version 0.9.4. For more information, see at.js Configurations . For detailed information about the changes in each version of at.js , see at.js Version Details .

Target Standard/Premium 17.1.1 (January 19, 2017)

This release includes the following features and enhancements:

Feature	Description
Content/Offers	The following enhancements are now available for offers: The Content page has been renamed to Offers. In addition, there are now two tabs along the right side to separate code offers from image offers. If you had code and images in the same folder before this release, Target will split them into two duplicate folders. Offers created via Target Classic, Adobe Experience Manager (AEM), Adobe Mobile Services (AMS), and APIs are now visible in the Target Standard/Premium user interface. Offers created in Target Classic are editable in Target Standard/Premium. (TGT-15738) Offers updated in the last two years using these methods will be visible in Target Standard/Premium (i.e. January 2015 and beyond). You can now filter offers by source and type. For more information, see Offers . The following enhancement has been made to geo-location targeting: You can now use profile.geolocation values directly as tokens in offers, plugins, and so forth. (TNT-25967) For more information, see Geo .
Reporting Note: These enhancements do not apply to Analytics for Target (A4T) reports.	The following reporting enhancements are now available for Target reports. The user interface for reports has been redesigned. Target reports now have an option to reset reporting data to remove old data. (TGT-5933) The counting methodology options for reporting includes Visitors (the default), Visits, and Activity Impressions. (TGT-10002) For more information, see Report Settings and Counting Methodology . The following reporting enhancements are now available for downloadable CSV reports: The offer-level CSV report now has additional details about each offer. (TGT-18995) Downloaded offer-level CSV files now always include data from control and targeted segments for Automated Personalization reports. (TGT-22000) The following reporting enhancements are now available for Automated Personalization (AP) reports. Improved reporting load time for Automated Personalization activities. The confidence interval for continuous variables (Revenue and Engagement metric types) is now displayed in Automated Personalization (AP) summary reports.
Activities	The following enhancements are now available for Target activities: Activities created in Adobe Mobile Services now display within the Target Standard/Premium user interface. (TGT-10806) For more information, see Activities . When creating multivariate tests, you can now exclude more than 10 percent of experiences from the test, provided you acknowledge the warning that you must then use offline reporting for analysis. (TGT-21719) For more information, see Preview Experiences for a Multivariate Test . The Campaign ID is now visible on each activity's Overview page. This is useful for API and troubleshooting operations. (TGT-20928) The design for the Collisions and Change Log pages have been improved. The maximum allowed length of anonymous offer names in Automated Personalization (AP) activities has been increased from 30 to 250 characters.
Audiences	The following enhancements are now available for audiences: Device Marketing Name is now available as a built-in option from the drop-down list when creating audiences targeting mobile devices. This change lets you easily pick a device model name rather than searching for the appropriate device model number. For example, the Galaxy S7's marketing device name is "Samsung Galaxy S7 Edge," while the device model is "SM-G9350." (TGT-18393) For more information, see Mobile .
Recommendations	The following enhancements have been made to Recommendations: The Backup Algorithm result line is now included in Top Viewed and Top Bought CSV downloads. The backup Recommendation starts with "*," Additional statuses let you know the progress of your Recommendation feeds. For more information, see Feeds .
Enhanced Visual Experience Composer (VEC)	Updated the IP addresses for the Enhanced Visual Experience Composer (VEC). If you allowlist IP addresses used for the VEC, add the new IP addresses. For more information, see Troubleshooting the Visual Experience Composer .

Releases 2016

Target Standard/Premium 16.10.2 (November 8, 2016)

Fixes

This release includes the following fixes:

• Fixed an issue in Recommendations where feeds could not be created for any non-default environments (host groups).
• Made several improvements to reduce activity syncing errors.
• You can no longer create redirect offers for activities using Analytics for Target (A4T).

Target Standard/Premium 16.10.1 (October 25, 2016)

This release includes the following features and enhancements:

Feature	Description
Auto-Allocate: Winner Badge	We've now made it easier to determine a winner in an Auto-Allocate A/B activity. Many marketers make the mistake of prematurely declaring a winning experience before the results indicate the clear winner. When using the Automated Traffic Allocation feature, Target displays a badge at the top of the activity's page indicating "No Winner Yet" until the activity reaches the minimum number of conversions with sufficient confidence. When a clear winner is declared, Target displays "Winner: Experience X." For more information, see Automated Traffic Allocation and Determine a Winner . Note: Auto-Allocate A/B activities are no longer supported in Analytics for Target (A4T) going forward. With this release, any active Auto-Allocate A/B activities with A4T enabled will be switched to Manual mode (equal traffic allocation).
Target mobile devices by carrier	Create an audience to target mobile devices based on mobile carrier (Verizon, Sprint, AT&T, T-Mobile, etc.). The Mobile Carrier option is under the Geo settings. For more information, see Geo .
Generate mboxTrace authentication token from Target UI	Enable advanced Target debugging tools by creating a temporary authentication token. Click Generate Authentication Token on the Implementation Details page ( Administration > Implementation ). You can then add the resulting parameter to your web page URLs for troubleshooting purposes. For more information, see "Retrieve the Authorization Token to Use With Debugging Tools" in Troubleshooting Content Delivery .
Recommendations: Criteria set sequencing	Use sets of up to five pre-created criteria in a single experience for greater control over the recommendations presented to visitors. For more information, see Create Criteria Sequences .
Recommendations: Insert external promotions	Add promoted items and control their placement in your Recommendations designs. For more information, see Adding Promotions .
First Look Auto-targeting in A/B activities	Note: This "First Look" offering is enabled for a few customers in this release for testing and feedback. Automatically target experiences in A/B tests to serve the right experience to the right visitor. For more information, see Auto-Target For Personalized Experiences .

Target Platform Changes (October 10, 2016)

Change

Details

at.js version 0.9.3

October 10, 2016 at.js version 0.9.3 is available. Ensures mbox calls fire in Microsoft Internet Explorer 11 when legacy browsers are disabled in the at.js settings. Ensures that default content is rendered if a dynamic remote offer fails (for example, if the URL is incorrect and returns a 404 error). Ensures that elements are revealed quickly when VEC click-tracking selectors can't be found in the DOM. For more information, see at.js Version Details .

Target Standard/Premium 16.9.1 (September 22, 2016)

This release includes the following features and enhancements:

Feature	Description
Combine audiences	Combine multiple audiences (including Adobe Experience Cloud audiences and Target audiences) on the fly during the activity-creation workflow. For example, you can target all loyalty customers by including a specific Audience Manager segment for loyalty status and combine it with a Target segment made up of people who signed up for your loyalty program during the current session, instead of creating a third, permanent audience. For more information, see Combining Multiple Audiences .
Target visitors during a specific time period	Add start and end dates to target an audience. For example, using the new combined, ad-hoc audiences mentioned above, you can target low-spenders with specific content during the three days leading up to Black Friday and other content after Black Friday. For more information, see Time Frame .
Save smart collections	Search functionality on the Content page now includes saved folders, called smart collections, to save time when performing similar searches. For more information, see Search Content and Create Smart Collections .
Form-based Experience Composer	Add a link to an image. The link can be a click-through link, destination link, or a landing link. For more information, see Form-Based Experience Composer .

Enhancements

This release includes the following enhancements:

Enhancement	Description
Visual Experience Composer (VEC)	Improved error messaging.

Known Issues

• The Render Using JavaScript option is currently not supported if it is used along with custom code in the Visual Experience Composer.

Target Platform Changes (September 2016)

Change

Details

at.js version 0.9.2

September 21, 2016 at.js version 0.9.2 is available. Added an optoutEnabled setting to enable or disable the Device Graph opt-out. If this setting is set to true and the visitor has opted out of tracking, the visitor's browser will not make any mbox calls. Device Graph is currently in Beta. This setting is set to false by default, but must be set to true if you are using Device Graph. Added CustomEvent support for the notification mechanism. Previously, the at.js event notification mechanism could not be used via standard DOM APIs, such as document.addEventListener() . Now you can use document.addEventListener() to subscribe to at.js events, such as request events and content rendering events. Fixed an issue related to offers created in the Visual Experience Composer (VEC). Prior to this release, Target hid the selectors and un-hid them only when all selectors matched. In at.js 0.9.2 Target un-hides the selectors as soon as they are matched. For more information, see at.js Version Details .

Target Standard/Premium 16.9.1 (September 22, 2016)

This release includes the following features and enhancements:

Feature	Description
Combine audiences	Combine multiple audiences (including Adobe Experience Cloud audiences and Target audiences) on the fly during the activity-creation workflow. For example, you can target all loyalty customers by including a specific Audience Manager segment for loyalty status and combine it with a Target segment made up of people who signed up for your loyalty program during the current session, instead of creating a third, permanent audience. For more information, see Combining Multiple Audiences .
Target visitors during a specific time period	Add start and end dates to target an audience. For example, using the new combined, ad-hoc audiences mentioned above, you can target low-spenders with specific content during the three days leading up to Black Friday and other content after Black Friday. For more information, see Time Frame .
Save smart collections	Search functionality on the Content page now includes saved folders, called smart collections, to save time when performing similar searches. For more information, see Search Content and Create Smart Collections .
Form-based Experience Composer	Add a link to an image. The link can be a click-through link, destination link, or a landing link. For more information, see Form-Based Experience Composer .

Enhancements

This release includes the following enhancements:

Enhancement	Description
Visual Experience Composer (VEC)	Improved error messaging.

Known Issues

• The Render Using JavaScript option is currently not supported if it is used along with custom code in the Visual Experience Composer.

Adobe Target Standard/Premium 16.8.1 (August 23, 2016)

The Adobe Target Standard/Premium 16.8.1 (August 23, 2016) release includes the following features and enhancements:

Feature	Description
Hosts and environment (host group) management	Organize your sites and pre-production environments for easy management and separated reporting. Hosts are bundled into environments for ease of management. The preset environments include Production, Staging, and Development. You can also add new environments. This feature achieves feature parity with Target Classic . For more information, see Hosts .
Category Affinity	The category affinity feature automatically captures the categories a user visits and calculates the user's affinity for the category so it can be targeted and segmented on. This helps to ensure that content is targeted to visitors who are most likely to act on that information. This feature achieves feature parity with Target Classic . For more information, see Category Affinity .
Enable/Disable Enhanced Experience Composer at the activity level	Enable/disable the Enhanced Experience Composer at the account level (applies to all activities created in the account) or at the individual activity level. Previously, you could enable/disable the Enhanced Experience Composer only at the account level. For more information, see Experiences .
Automated Personalization: Offer performance report	Download an offer performance report with all Automated Personalization activity success metrics.

Enhancements

This release includes the following enhancements:

Enhancement	Description
Code Editor UI redesign	The code editor UI has been updated to be more intuitive and easier to use. For more information, see Code Editor .

The following known issues have been reported:

• Some of the UI text for the Category Affinity feature displays in English only. Text in other languages will be available in the September Target release.

Target Platform Changes (July 2016)

Change	Details
at.js version 0.9.1	July 14, 2016 at.js version 0.9.1 is now available. For more information, see at.js Version Details .

Adobe Target Standard/Premium 16.7.1 (July 21, 2016)

The Adobe Target Standard/Premium 16.7.1 (July 21, 2016) release includes the following features and enhancements:

Feature	Description
Priority settings for activities	You can now set activity priority levels from 0-999 to allow for finer control over which activity displays if multiple activities are assigned to the same location with the same audience. This option must be enabled in Administration > Reporting . The Fine-grained priorities option applies to A/B Test, Automated Personalization, Experience Targeting, and Multivariate Test activities. For more information, see the following topics: A/B Test: Goals and Settings Automated Personalization: Automated Personalization Experience Targeting: Goals and Settings Multivariate Test: Goals and Settings Activities: Activity Settings
Multi-valued Recommendations attributes	All custom Recommendations attributes can now contain multiple entity values. For more information, see Custom Entity Attributes .
Dynamic/remote offer support	Dynamic content can be part of any form-based activity in Target Standard/Premium . Dynamic content is stored outside of Target . For more information, see Create Remote Offers .
Copy audiences and profile scripts	You can now copy an existing audience that you can then edit to create a similar audience. For more information, see Creating an Audience . You can also copy existing profile scripts. For more information, see Profile Script Attributes .
Use classes to determine element selectors	Element selectors can now be based on classes or IDs in Automated Personalization and Multivariate Test activities. In previous versions, this option was only available for A/B Test activities. For more information, see Element Selectors Used in the Visual Experience Composer .
Recommendations: Content similarity	Use Content Similarity rules to make recommendations based on item or media attributes.

Enhancement	Description
Reporting improvements	Success metric report downloads now show metric and segment names instead of IDs.
Evaluate mbox entry condition on each request in Automated Personalization activities	In Automated Personalization activities, entry criteria (URL targeting, template rules, audience target) are evaluated for each request for more accurate offer delivery. For more information, see Automated Personalization .

Adobe Target Standard/Premium 16.6.1 (June 16, 2016)

There is no customer-facing release planned for June.

Fixes

This release includes the following fixes:

• Fixed an issue where some customers saw a white screen when trying to edit their page inside the Visual Experience Composer.

Known Issues

The following known issues have been reported:

• When “Disable JavaScript” is selected for page A in a multipage activity, JavaScript is disabled everywhere, even though “Disable JavaScript” isn’t selected on other pages.

• Issue with experience preview URLs for experiences with a redirect. As a workaround, in the Experience Composer, click Configure, choose Multiple Audiences, and add All visitors as the only audience. Continue to save your activity. This does not change the delivery of your activity, but allows preview to work. This will be fixed in the July release of Adobe Target.

• The documentation shows the expected behavior for the Redirect URL checkbox. However, due to a bug, the check box does not show as selected by default. This defect will be fixed soon.

  To check this option in an existing activity with a redirect offer, use the following workaround:

  1. Open the Redirect to URL popup.
  2. Change the URL to a dummy URL and save.
  3. Change the dummy URL again to your campaign’s expected redirect URL.
  4. Check the “Include Current Query Parameters” option, and save.

  If you check the option while creating a new redirect offer, you can expect your query parameters to be included in the redirection.

  For older activities, if this option is checked in the experience composer of your activity, it means your redirection will include the query parameters. If it is not checked, current query parameters will not be included in redirection.

Adobe Target Standard/Premium 16.5.1 (May 19, 2016)

The Adobe Target Standard/Premium 16.5.1 (May 19, 2016) release includes the following features and enhancements:

Feature	Description
Experience Versions	Versions targeted to different audiences can now be set up within experiences in A/B activities. See Target an Experience to Multiple Audiences .
Recommendations custom algorithms	Custom algorithm mappings can be uploaded in a CSV file. It is no longer required to use the XML-based API. See Uploading Custom Criteria .
Analytics for Target: Analytics tracking server	To ensure proper reporting tracking, you must specify a tracking server when you create or edit activities that use Analytics for Target (A4T). Existing activities will continue to run using current settings. See Using an Analytics Tracking Server .
New Instructional Videos	The following instructional videos have been added to help: Using DTM to pass parameters to the global mbox Using DTM to deploy Target Setting up a multivariate test Creating an A/B activity Understanding activity types Configuring activity settings Targeting an activity Creating audiences Using audiences Using the Content Library Using profile scripts Setting account preferences Understanding Visual Experience Composer modes Creating and managing Target users Setting success metrics
User Interface improvements	User interface improvements have been made to the Visual Experience Composer and Recommendations search.
Recommendations CSV download	CSV downloads now have a line for all environments, including those that do not have entity recommendations (for example: # environment: 1724 ).

Enhancements

Improvement made to improve the A4T provisioning process.

Known Issues

The following known issues have been reported:

• When “Disable JavaScript” is selected for page A in a multipage activity, JavaScript is disabled everywhere, even though “Disable JavaScript” isn’t selected on other pages.
• Issue with experience preview URLs for experiences with a redirect. As a workaround, in the Experience Composer, click Configure, choose Multiple Audiences, and add All visitors as the only audience. Continue to save your activity. This does not change the delivery of your activity, but allows preview to work. This will be fixed in the July release of Adobe Target.

New Target Implementation Library, at.js 0.8.0 (May 5, 2016)

at.js is a new implementation library for Target designed for both typical Web implementations and single-page applications.

Among other benefits, at.js improves page load times for Web implementations, improves security, and provides better implementation options for single-page applications.

at.js contains the components that were included in target.js, so there is no longer a call to target.js.

When implementing at.js, be aware of the following:

• Visual Experience Composer redirects do not work.
• Internet Explorer versions earlier than 8 are not supported.
• Asynchronous implementation means legacy integrations like the Test&Target to SiteCatalyst plugin may not work.
• All calls to Target are made via XMLHTTPRequest and content is returned via JSON.

Adobe Target Standard/Premium 16.4.1 Fix (May 5, 2016)

• at.js v 0.8.0 is now available for download from the Target interface.

• Target APIs changed. applyOffer now requires mbox param [0].

  adobe.target.applyOffer({
      "mbox": "target-global-mbox",
   "params": {"test": "true"},
      "selector": ".banner-text",
      "offer": offer
  });
  

Adobe Target Standard/Premium 16.4.1 (April 21, 2016)

This release includes the following features and enhancements:

Feature	Description
User Interface Improvements	The user interface has been changed significantly in this release. Among the most noticeable changes are: Navigation has moved from the left to the top Improved dialog boxes Improved activity creation flow The way Experience Cloud solutions, including Target, are selected has also changed. To access Experience Cloud solutions and services, click the menu icon: For more information about accessing Target and making Target your default page after logging in to the Experience Cloud, see Access Target from the Adobe Experience Cloud .
Inclusion rules can be disabled for backup recommendations	When backup recommendations are enabled, you can choose not to apply inclusion rules to your backup recommendations. .
Recommendations: New debugging capabilities in text area via mboxTrace	Adding &mboxTrace to a URL replaces recommendations on that page with debugging details, including information about served recommendations, criteria, design, exclusions, inclusions, backup recommendations served, and more.
Recommendations API: Upload a CSV for the Custom Criteria	You can upload a CSV for the Custom Criteria via API. This ability will be added to the Target Premium user interface in an upcoming release.
Recommendations API: New Design APIs	New Design APIs make it possible to manage your Recommendations designs via API.
AP: Dependent Success Metrics	Automated Personalization now supports the ability to limit a success metric to only count if a previous success metric has already been met. For more information, see Success Metrics .
AP: Reports Summary View Download	The download option now allows users to download summary view (i.e. comparing Control and Automated traffic) as broken down by all available success metrics.
Customer attributes can be used as tokens in offers	Previously, customer attributes could be referenced in profile scripts, formatted as crs.get('< Datasource Name >.< Attribute name >') . Now, the attributes are available as tokens in profile scripts and directly in offers without first requiring a profile script. The token should be in the form: $crs. datasourceName . attributeName . See CRS Tokens .
Custom Code enhancement	Custom code can now execute the JavaScript code in the <head> tag. Execution of code no longer waits for the <body> tag to be present in DOM. Earlier, the selector was only the first element in the <body> tag.
New Instructional Videos	Instructional videos have been added to help. Currently, you can view videos about the Visual Experience Composer and Form-Based Experience Composer . More videos will be added in the coming weeks.

Fixes

This release includes the following fixes:

• The issue introduced by Chrome version 48 that caused the Visual Experience Composer to function incorrectly in Chrome has been fixed. To benefit from this fix, update to Chrome version 50.

Known Issues

The following known issues have been reported:

• When “Disable JavaScript” is selected for page A in a multipage activity, JavaScript is disabled everywhere, even though “Disable JavaScript” isn’t selected on other pages.

Adobe Target Standard/Premium 16.3.1 (March 15, 2016)

This release includes the following features and enhancements:

Feature	Description
First Look: New Target implementation library, at.js	Note: This "First Look" offering is available via API download. It will be available via the Target interface in an upcoming release. In the meantime, you can download the at.js library, test it in your environment, and deploy it in your production Target implementation. at.js is a new implementation library for Target designed for both typical Web implementations and single-page applications. Among other benefits, at.js improves page load times for Web implementations, improves security, and provides better implementation options for single-page applications. at.js contains the components that were included in target.js, so there is no longer a call to target.js. When implementing at.js, be aware of the following: Visual Experience Composer redirects do not work. Internet Explorer versions earlier than 8 are not supported. Asynchronous implementation means legacy integrations like the Test&Target to SiteCatalyst plugin may not work.
Dependent Success Metrics	This features provides the option per success metric to count someone as reaching the success metric only if they've previously reached a different success metric. For example, a test might change the hero image on the homepage. The marketer might only want to count conversions for people who clicked the hero image. So, the marketer can set a success metric for "clicked on homepage hero" and then another metric for purchasing. Then, the marketer can add a rule on the "purchasing" metric to ensure visitors have first reached the "clicked on homepage hero" success metric. Note: If audience targeting on a location in a success metric is set, this feature is not supported for that metric. Dependent Success Metrics are only supported in AB, XT, and MVT activities. Automated Personalization and Recommendations support will be available later. For more information, see Success Metrics .
Auto-Allocate usability improvements	After the model for an Auto-Allocate activity is ready, the following operations from the UI are not allowed: Switching the "Traffic Allocation" mode to "Manual" Changing the reporting source from "Adobe Target" to "Analytics" and vice-versa Changing the goal metric type Changing options in the "Advanced Settings" panel Refer to Automated Traffic Allocation for documentation about Auto-Allocate.

Known Issues

The following known issues have been reported:

• When “Disable JavaScript” is selected for page A in a multipage activity, JavaScript is disabled everywhere, even though “Disable JavaScript” isn’t selected on other pages.

• Some interface issues might occur in Internet Explorer 10, including screen flicker and possible slowness.

• The Chrome version 48 update introduced an issue that causes the Visual Experience Composer to function incorrectly in Chrome. Google is working on a solution. For information, refer to https://code.google.com/p/chromium/issues/detail?id=582603. To work around this issue:

  • Use Firefox or Internet Explorer.
  • Enable the Enhanced Experience Composer, which can be configured from within the Administration > Visual Experience Composer tab.

Adobe Target Standard/Premium 16.2.1 (February 18, 2016)

This release includes the following features and enhancements:

Feature	Description
Activity entry targeting by percentage.	You can now limit entries into A/B and multivariate activities to a percentage of visitors or audience members. For example, you might limit entries to 50% of all visitors or 45% of your “Californians” audience.
Support for Revenue, Orders, and Engagement in Auto-Allocate	You can now choose Revenue (RPV), Orders, and Engagement metrics as goals for A/B activities with Auto-Allocation selected. Previously, only conversion metrics were supported. See Automated Traffic Allocation.
Filter by source	You can now filter the Activities list by the source where the activity was created. Choice are Adobe Target and Adobe Experience Manager. See Activities.
Automated Personalization performance enhancements	Automated Personalization has been redesigned to perform better with a large number of offer/location combinations.

Known Issues

The following known issues have been reported:

• When “Disable JavaScript” is selected for page A in a multipage activity, JavaScript is disabled everywhere, even though “Disable JavaScript” isn’t selected on other pages.

• Some interface issues might occur in Internet Explorer 10, including screen flicker and possible slowness.

• The Chrome version 48 update introduced an issue that causes the Visual Experience Composer to function incorrectly in Chrome. Google is working on a solution. For information, refer to https://code.google.com/p/chromium/issues/detail?id=582603. To work around this issue:

  • Use Firefox or Internet Explorer.
  • Enable the Enhanced Experience Composer, which can be configured from within the Administration > Visual Experience Composer tab.

Adobe Target Standard/Premium 16.1.1 (January 28, 2016)

This release includes the following features and enhancements:

Feature	Description
User interface improvements.	The Activities list and Audience list design have been improved, as has the search/sort functionality. Additional user interface changes will be included in upcoming releases. See Activities .
"Super" audiences	Use nested AND/OR logic when configuring audiences. See Creating an Audience .
Select host groups in reports	Host groups are available in reports. Note: This option is not available for Automated Personalization.
Support for Internet Explorer 11	Internet Explorer 11 is now supported in the Target interface. See Supported Browsers .
View Confidence Interval in Target reports for continuous variables	Display the Confidence Interval Range for the revenue metric type (RPV, AOV, Sales, Orders), and for engagement metrics. For example, if RPV = 200.00 and CI Range = 50.00 , then this should be displayed for RPV: 200.00 +/- 50.00 This change applies to A/B, Experience Targeting, and Multivariate tests. See Confidence Level and Confidence Interval .
Visual Experience Composer URL rules enhancement	Previously, the URL template rules in the Visual Experience Composer formed an OR condition with the Page URL. Now you can choose AND or OR when specifying multiple URLs. OR is the default.
Recommendations: Change in global mbox delivery coding	When creating a design, it is now the default to wrap an HTML design in a <div> element. For information about creating a design, see Create a Design .
Life Time Value (LTV) machine learning reinforcement technique	This new algorithm focuses on long-term conversion across many sessions instead of focusing on improving conversion just in this session. This technique is suitable for sites with many returning visitors because it optimizes on overall revenue for the entire interaction with the visitor. See Automated Personalization .
Enhancement: Allow targeting on hash (#) fragments	You can now target on the part of a URL that follows a hash (#). See Include the Same Experience on Similar Pages and other relevant topics.
Download success metrics report	Download a single csv file with all success metric listed, instead of a report that only had the final activity goal. See Reports .

Fixes

This release includes the following fixes:

• Fixed an issue that caused all AEM-based activities as Experience Targeting (XT) activities. AEM now uses the correct activity types for A/B and XT activities.
• Removed an option to use non-conversion metrics as a goal in new Auto Allocated activities. This restriction will be lifted in an upcoming release.
• Fixed an issue that prevented deletion of a profile script created in Target Classic from Target Standard.
• Fixed an issue that wrapped a non-HTML Recommendations template in a <div> element when used in a form-based workflow.
• Fixed an issue that caused collision calculations to time out with a large number of activities.
• Fixed an issue that resulted in the CSV download showing the Summary report rather than the Success Metrics report.
• Removed “Unique ID” pop-up message that sometimes appeared when editing elements.

Known Issues

The following known issues have been reported:

• When “Disable JavaScript” is enabled for pageA in a multipage activity, JavaScript remains enabled for all pages but the functionality remains disabled.

• Some interface issues might occur in Internet Explorer 10, including screen flicker and possible slowness.

• The Chrome version 48 update introduced an issue that causes the Visual Experience Composer to function incorrectly in Chrome. Google is working on a solution. For information, refer to https://code.google.com/p/chromium/issues/detail?id=582603. To work around this issue:

  • Use Firefox or Internet Explorer.
  • Enable the Enhanced Experience Composer, which can be configured from within the Administration > Visual Experience Composer tab.

Releases 2015

Adobe Target Standard/Premium 15.10.1 (November 2, 2015)

This release includes the following features and enhancements:

Feature	Description
Auto-Allocate in A/B Tests	You now have the option to automatically allocate traffic to increase overall campaign lift and discover winning experiences faster. This algorithm increases the overall campaign performance while maintaining the integrity of an A/B test. The algorithm relies on measured performance (e.g. conversion rate) and confidence intervals to produce a traffic distribution that is changed up to twice per hour. Key Benefits Preserves the integrity of an A/B test by ensuring that visitors remain in the same experience, like they do in a manual A/B test Finds a statistically significant winner faster than a manual A/B test Provides higher average campaign lift than a manual A/B test Allows you to toggle to a manual test at any time See Automated Traffic Allocation .
Customer Attributes	Upload 1st party data, called Customer Attributes, using the Experience Cloud core service and choose attributes to share to Target. This functionality launched in March for Analytics and now integrates directly with Target. For example, you might use customer data such as membership status (gold, silver, etc.), purchase history, favorite destination, local store, and so on in your CRM or eCommerce/POS system. Now you can upload that data to Experience Cloud. After the user authenticates on your site, Target can match that data to their web behavior. See Customer Attributes .
Multiple companies are available when selecting Analytics as the reporting source for Target.	When selecting Analytics as the reporting source for Target, you select an Analytics report suite to receive Target activity data. To do this, first choose from any of the Analytics companies your account is tied to, and then select the appropriate report suite for the activity. Only report suites that are provisioned to connect to Adobe Target will be available for selection. If you don't see the report suite(s) you expect, first try logging out and logging back in to the Adobe Experience Cloud to try again. If the report suite is still missing from the list, please contact Customer Care.
New Built-in Options for Audience Creation	There are new built-in audience options: Target visitors based on which language they use on their browser. This is more accurate than geo-based language targeting. Target visitors based on browser version, not just which browser is being used. You can now Target multiple browsers rather than only one. See Browser Options .
Recommendations Exclude Past Purchases	Target now automatically excludes previously purchased items from a visitor's recommendations. This option can be disabled for any criteria. All out-of-the-box criteria now have this option enabled, including those used in activities that were running prior to this release. If you do not want to exclude past purchases, you should edit those activities.
Recommendations Attribute Weighing	Recommendations ranking rules have changed for criteria. This change affects existing Recommendations. Use attribute weighting to "nudge" the algorithm. Marketers can influence the algorithm based on important description or metadata about the content catalog. Apply a higher weighting to these on-sale items so they show more often in the recommendation. Non-sale items are not completely excluded, but they display less often. Multiple weightings can be applied to the same algorithm, and the weightings can be tested on split traffic in the recommendation. These new weights have automatically been applied to all activities.
Recommendations Set the Time for Feed Processing	Specify the time when you want a feed to update. See Create Feed .
Recommendations Use the Feed List to Set a Feed to Never Run	From the feed list, set a feed to never run if you do not want to update that feed. See Create Feed .
Recommendations Set a New Criteria Type Based on Content Similarity	An item-based criteria that can be used for the following: Current items with similar attributes Last purchased item with similar attributes Custom attributes that match a specified entity.id and use items with similar attributes Last viewed item with similar attributes Most viewed item with similar attributes
New Activity List Filters	Several filters have been added to help you show the activities you are most interested in seeing in the Activities list. See Activities .
Recommendations Enhancement: Industry-Relevant Criteria Configuration	Irrelevant options during setup have been eliminated. In the past, some setup options for some industry verticals, such as Media, were not always relevant.
Recommendations New Out-of-the-Box Criteria	More Videos Like This More Articles Like This More Content Like This More Slideshows Like This More Products Like This See Criteria .
Enhancement: Improved reporting details shown when using Analytics as your reporting source.	The details shown by default in an Analytics report when using A4T now match the details shown in the Target report.

Fixes

This release includes the following fixes:

• Fixed an issue in the Global Experience Composer that prevented dragging a corner to resize a custom viewport.

Known Issues

The following known issues have been reported:

• When “Disable javascript” is enabled for pageA in a multipage activity, JavaScript remains enabled for all pages but the functionality remains disabled.

Adobe Target Standard/Premium 15.9.1 (September 30, 2015)

This release includes the following features and enhancements:

Feature	Description
Mobile Web Experience Composer	View your site as it looks on various mobile devices and different screen sizes. Set responsive site breakpoints once and use them across your activities to make sure your optimization activities look great on all the devices your visitors use. See Mobile Viewports for Responsive Experiences .
Location targeting on form-based activity creation	Apply targeting to your mbox locations to limit where your activity displays. See Form-Based Experience Composer .
Background color selection in Visual Experience Composer for MVT and Automated Personalization activities	A color picker enables you to set background colors when editing Automated Personalization and Multivariate Test activities. This feature was previously only available for A/B and Experience Targeting activities. See Visual Experience Composer Options .
Rich Text and HTML editing in Visual Experience Composer for MVT and Automated Personalization activities	Text and HTML formatting in a word processor-like window when editing Automated Personalization and Multivariate Test activities. This feature was previously only available for A/B and Experience Targeting activities. These actions provide rich-text editing capabilities by adding HTML tags or applying styles. These modifications by the rich-text editor for any action can be seen in its source view. Users can press the HTML button in the rich-text editor to see the source view. The styles added by the rich-text editor can interfere with customer websites' styles. In this case, users can go to the source view and edit the modifications to align them with their websites' styles. See Visual Experience Composer Options .
Recommendations Form-based recommendations	Create recommendations activities for non-site locations including emails, consoles, kiosks, etc. See Form-Based Experience Composer .
Recommendations Display information about the key in the design	Show the key item in your Recommendations design.
Automated Personalization Conversion-based report	If the optimization goal is a conversion metric, then the Offer Detail report now shows the impact of the top predictive variables in lift and incremental conversions. This report was only revenue-based before, so this ability ensures that activities with no revenue data still produce relevant and actionable insights. See Automated Personalization Reports .
Adobe Campaign e-mail integration with Target Standard	Previously, it was required to use Target Classic to set up a targeted e-mail campaign using Adobe Campaign. With the release of two new features in Target Standard (form-based activity creation and redirect offers) it is now possible to use Target Standard to set up a targeted e-mail campaign with Adobe Campaign.
Redirect Offers in Form-Based activity creation	Support for the redirect offers functionality of Target Classic added in Target Standard form-based activity creation flow. See Form-Based Experience Composer .
Enhancement: Experience URLs in activities no longer use on-site cookie	The preview experience URLs available per activity are now more reliable. Easily copy the URLs and share with other team members, even if they don't use Adobe Target. Note: Updated experience URLs only work on activities created after July 30, 2015. Older activities continue to use the cookie-based preview functionality.
Reporting enhancement for Analytics as the reporting source for Target	Click to view the full Analytics report directly from the activity report page.
Activity List performance improvements	Greatly improved the load time for activities in the list. Searching and filtering are much faster, particularly when there are a lot of activities in the list.

Fixes

This release includes the following fixes:

• Fixed an issue that prevented Target report suites from showing up in the Target report suite selector, after being enabled for Analytics for Target.
• Fixed an issue that prevented searching for activities by URL.

Known Issues

The following known issues have been reported:

• When “Disable javascript” is enabled for pageA in a multipage activity, JavaScript remains enabled for all pages but the functionality remains disabled.

Adobe Target Standard/Premium 15.8.1 (August 20, 2015)

The goal of this release is to provide feature parity with Target Classic. The most commonly used features of Target Classic are now available in Target Standard.

This release includes the following features and enhancements:

Feature	Description
Create and edit profile scripts	Profile scripts run profile attribute "catchers" on each mbox request. When an mbox request is received, Target runs any relevant profile scripts, determines which activity should run, and displays content that is appropriate to that activity and that experience, then tracks the success of the activity. This enables you to track information about the visit, such as the visitor's location, time of day, number of times that visitor has been to the site, if they've purchased before and so on. This information is then added to the visitor's profile so you can better track that visitor's activity on your site. See Profile Attributes .
Confidence interval for binary metrics	Updated reports using Target-based data show the confidence interval of the lift, compared to the control. See Confidence Level and Confidence Interval .
Download export activity report data	Download data in a .csv format for quick import into Excel or other data analysis programs. This feature works for A/B, Experience Targeting, and Multivariate activities. See Downloading Reports .
Rich text and HTML editing in Visual Experience Composer	Text formatting options are available when editing text and HTML for A/B and Experience Targeting activities in the Visual Experience Composer. You can choose a font, select a font style, change text alignment, and other standard text formatting options. When modifying HTML, you can toggle between the code view and rich-editing view of the HTML. See Visual Experience Composer Options .
Background color selection in Visual Experience Composer	A color picker enables you to set background colors when editing A/B and Experience Targeting activities in the Visual Experience Composer. This option is not available if a background image is set. See Visual Experience Composer Options .
Archive activity	Send an activity to the archive. You can approve an archived activity to make it active again. Activities in the archive do not display by default in the Activities list. See Activities .
Automated Personalization Offer-level targeting	Allows marketers to apply targeting rules to offers in Automated Personalization. Makes it possible to exclude specific offers from being shown to a specified group of people. See Target AP Offers .
Recommendations Premium Show number of activities using design	The design library shows how many live and inactive activities are using each design.
Recommendations Premium Customized dynamic title displays in design	Choose a title to display when using a particular design. This title does not have to match the title displayed to visitors on the page.
Recommendations Premium API Token	You can set your Client API token from Recommendations Premium.
Enhancement: Frequently used URLs	When entering a URL for an activity or a new page within an activity, a menu shows the most recent and most frequently used URLs.
New mobile device targeting options	You can now target multiple mobile devices without requiring a profile script. See Mobile .

Adobe Target Standard/Premium 15.7.1 (July 30, 2015)

This release includes the following features and enhancements:

Feature	Description
Activity change log	The change log lists changes made to an activity. The action and the user are listed with a timestamp for each change. See Activity Change Log .
Multipage activity	A multipage activity enables you to create a story over multiple pages, with a design that is specific to each page. For example, you might want to test an offer for free shipping with purchases above a certain amount. You might want that offer to appear on your landing page, a category page, and certain product pages, but you want it to be a different size and in a different location on each page type. You could display a prominent offer on your home page, then reinforce that offer with smaller offers on other relevant pages. You can also use a multipage activity to define different layouts for your desktop and non-responsive mobile sites. See Multipage Activity .
Form-based activity creation	Create an activity without using the Visual Experience Composer. Instead, choose locations and offers through a form. With this, Target Standard activities can be delivered in emails, mobile apps, kiosks, and other places that don't work with a Visual Experience Composer. See Form-Based Experience Composer .
Configurable success metrics	Fine-grained options let you determine how to count success metrics. Options include counting the metric per impression or once per visitor, and choosing whether to keep the user in the activity or removing them. This is equivalent to the "advanced options" for success metrics available in Target Classic. See Success Metrics .
Enhancement: Experience Targeting experience limit removed.	The previous limit of ten experiences in Experience Targeting has been removed.
Real-time profile syncing for 3rdPartyId data	When a site visitor logs in mid-session and gets a 3rdpartyId, all previously-loaded profile attributes tied to the 3rdPartyId are now immediately available. See Visitor Profile .
Recommendations Premium: Facet Name Search	You can now search for a facet name.
Automated Personalization: Post-goal metric tracking	Previously, Target restarted an experience when the visitor hit the modeling goal. Now, users can be kept in the activity for tracking purposes after reaching the modeling goal. For example, often an Automated Personalization activity is used to improve click-rates, and that is set as the modeling goal. However, it's important to see how increased click-rates lead to final conversion, so tracking through the final conversion is essential. See Automated Personalization .

Fixes

This release includes the following fixes:

• Analytics as the reporting source for Target is now supported for XT activities.
• Fixed an issue that caused the control experience displayed in Analytics to change once the activity became live.
• Fixed an issue where values after a # in a URL were considered part of the path during audience/segment creation.

Known Issues

The following known issues have been reported:

• When “Disable javascript” is enabled for pageA in a multipage activity, JavaScript remains enabled for all pages but the functionality remains disabled.

Adobe Target Standard/Premium 15.6.1 (June 25, 2015)

This release includes the following features and enhancements:

Feature	Description
Visual Experience Composer compatibility improvements	A new account-wide setting to make it easier for Target to generate the right CSS selectors. For example, it can be specified if Target should use classes or IDs. This improves compatibility with AEM. This setting can be overridden per activity
Experience Targeting support for Analytics as a reporting source	You can now use Analytics as a reporting source for Experience Targeting activities.
Automated Personalization: Visual indication of model status	Once a predictive model passes the required quality criteria and is deemed valid, it is considered ready and is used to calculate a personalized score for offer decisioning. A clock icon changes to a check mark when the model is ready and Target is able to begin delivering personalized content. Since lift is expected only after the models are ready, the visual indication allows you to set the right expectation. Use the traffic estimator in the Visual Experience Composer to get a guideline of when the models will be ready.
Premium Recommendations: Browse and Navigate in the Visual Experience Composer	Allows you to open the visual experience composer on one page, and then follow links and form submissions to reach other pages on your site, such as a shopping cart. Once on the page you want to test, flip the Visual Experience Composer back to "Compose" mode and create your experiences. For example, you can change a message on the Shipping page, then test it against the default.
Premium Recommendations: Faceted Catalog Search	Provides a more robust way to search your catalog. Also makes it easier to narrow down the search results to very specific set of products.
Show external campaigns in the Target Standard Activities list	You will now see Target Classic campaigns within the Target Standard Activities list. If you want to filter out Target Classic campaigns and only view Target Standard you can use the "Source" search filter option. For example, to view only Adobe Target Standard activities select the source filter and type "Adobe Target" as the source. The ability to view activities created in Recommendations Classic or Adobe Mobile Services will be added in a future release. You can activate and deactivate activities created in other solutions using the Target user interface. For all other changes you will be need to edit the activities in the source solution. For activities created in other solutions, audience information is not visible on the Overview page. View the audience information in the solution where the activity was created. See Activities .

Fixes

This release includes the following fixes:

• Added message to indicate that an activity that cannot be viewed is available for viewing in Target Classic.
• Fixed an issue that caused URLs to redirect slowly.
• Fixed an issue that broke click-tracking success metrics if other success metrics in the activity were deleted.
• Fixed an issue where the image uploaded to the Recommendations design did not display correctly in the Visual Experience Composer.
• Fixed an issue with the traffic estimator in Automated Personalization activities where the number of combinations was used instead of the sum of offers across locations.
• Fixed an issue where mbox parameters would not always display on the audience creation screens.
• Fixed an issue that blocked updates on the thumbnail for Recommendations designs.

Adobe Target Standard/Premium 15.5.1_Hotfix (May 28, 2015)

This hotfix release includes the following fixes:

• Fixed an issue where the Estimated Lift in revenue checkbox was not visible.
• Fixed an issue that prevented the Create Activity button from displaying properly for some users.
• Fixed an issue that caused the Activity Name text box to disappear in the Visual Experience Composer while editing A/B and Experience Targeting activities.

Adobe Target Standard/Premium 15.5.1 (May 21, 2015)

This release includes the following features and enhancements:

Feature	Description
Custom code entry and editing in Visual Experience Composer	Enables you to see, edit, and add new actions using a code editor within the Visual Experience Composer. See Code Editor for more information.
Add JavaScript and CSS to the top of your page	Add JavaScript code to your page(s) right below the <body> tag, without requiring the selection of an element on your page. See Code Editor for more information.
New Audience Creation Options	You can now target by the following (located in the Geo section when creating an audience): ISP Network domain Connection speed (options are: broadband, dialup, mobile, t1, t3, satellite) See Audiences .
Recommendations Premium New Features	New Preview mode to view designs with JavaScript Catalog Search now supports free search for English language Account-level support for inputting a static, base url to prepend to all relative entity.thumbnailUrl values
Recommendations Premium Enhancements	Improvements to design preview in VEC Layout improvements on out-of-the-box designs Collection shown in targeting diagram
Recommendations Classic functionality now supported in Recommendations Premium	Partial template rendering See Content Settings . Specify backup rules per criteria Support FTPS for product feeds Custom algorithms now appear automatically as criteria Hourly automatic reindexing of product catalogs for customers without feeds
Automated Personalization: QA links added	You can now preview how your experiences will look when delivered. View and share links to your AP experiences on your site to get a "true preview" of the experiences outside of Target's Visual Experience Composer. See Automated Personalization .
Analytics-powered MVT: Preview experience from Performance report	When using Analytics as the reporting source for multivariate tests, you can preview your MVT activities from the Performance report.
A/B tests and Experience Targeting: three-step activity creation flow	Create A/B and Experience Targeting activity in three steps instead of four. This change makes the process of creating these activities more like the workflow of other activities types, such as Automated Personalization and Multivariate Tests.
Analytics as a reporting source is available with most activity types.	The A/B with Analytics activity type no longer exists. The option of using Analytics as your reporting source is now available on the Goal & Settings page for all activity types except Automated Personalization and Experience Targeting. As a result, there is no longer a separate activity type called A/B Test with Analytics Data.
Show external campaigns in the Target Standard Activities list	You will now see Target Classic campaigns within the Target Standard Activities list. If you want to filter out Target Classic campaigns and only view Target Standard you can use the "Source" search filter option. For example, to view only Adobe Target Standard activities select the source filter and type "Adobe Target" as the source. The ability to view activities created in Recommendations Classic or Adobe Mobile Services will be added in a future release. See Activities .
Export Order Audit Report	Ability to export/download Order Audit Report added to Target reports.
Beta: A4T lift and confidence	Lift and confidence now available for Analytics' standard metrics and custom events.

Fixes

This release includes the following fixes:

• Fixed an issue in audience creation where changing operators deleted attribute values.
• Made improvements so custom-coded regional mboxes are selectable in the Visual Experience Composer.
• Fixed an issue in Recommendations where attributes with double-byte characters (for multilingual cases) bypassed inclusion filtering rules.
• All activity types now support activity names up to 200 characters in length.

Adobe Target Standard/Premium15.3.1 (March 26, 2015)

This release includes the following features and enhancements:

Feature	Description
Visual Experience Composer improvements	Content that only appears on hover, such as flyout menus and mini-carts, is now selectable for editing in the Visual Experience Composer. See Experiences .
Automated Personalization: Traffic Estimator	The Traffic Estimator, formerly available only in the Multivariate Test activity type, is now available for Automated Personalization activities. See Estimate the Traffic Required for Success .
Automated Personalization: Visual Preview	Visually preview every content combination inside the Visual Experience Composer. See Preview Experiences for an Automated Personalization Test .
Recommendations: Improved content viewing	You can now see every item that qualifies for a collection or exclusion when viewing or editing the collection.
Recommendations: Improved search results	The total number of items that meet each search string is displayed.
Upload Customer Attributes in Adobe Analytics	Analytics users who capture enterprise customer data in a customer relationship management (CRM) database can upload that data into the Experience Cloud. Once the data is in the Experience Cloud, you can, for example, create an audience segment in Analytics that includes customer attributes in the segment definition, and then share that audience with Target. Note: Target is not yet able to consume raw customer attributes directly.

Fixes

This release includes the following fixes:

• For Analytics for Target based activities, the Lift and Confidence columns are now hidden for Analytics metrics where the calculations cannot be performed.
• Fixed an issue where the short format of the charset metatag was not recognized in the Enhanced Experience Composer

Known Issues

• Target-based conversion events for multivariate testing in Target Standard/Premium are not being reported when Analytics is being used as the reporting source for Target. This issue is expected to be fixed soon.

Adobe Target 15.2.1 (February 19, 2015)

This release includes the following features and enhancements:

Feature	Description
New activity type: Recommendations	Recommendations activities automatically display products or content that might interest your customers based on previous user activity. Recommendations help direct customers to relevant items they might otherwise not know about. Recommendations is available as part of the Target Premium solution. It is not included with Target Standard without a Target Premium license.

Fixes

This release includes the following fixes:

• Fixed an error that caused a redirect offer not to work when revisiting a page.

Adobe Target 15.1.1 (January 22, 2015)

This release includes the following features and enhancements:

Feature	Description
New activity type: Multivariate test	A full-factorial multivariate test compares all possible combinations of offers in your content areas to help you determine the best possible combination of content. Multivariate tests also show which content in which areas most contributes to activity success. A common use of multivariate tests is to optimize an entire page after you've used an A/B test to determine an optimal layout. With the multivariate test, you can optimize the individual assets on the page (such as the main image, headlines, or promotional content). For an introductory video, see https://my.adobeconnect.com/p2k6u8iiu6l/ .
Browse to pages and in-page elements in the Visual Experience Composer	Allows you to open the visual experience composer on one page, and then follow links and form submissions to reach other pages on your site, such as a shopping cart. Once on the page you want to test, flip the Visual Experience Composer back to "Compose" mode and create your experiences. For example, you can change a message on the Shipping page, then test it against the default. The Browse mode also lets you interact with a page to get to the right state, such as going through an image carousel, open a mini-cart, or close a pop-up. Once the page is in the state you need, flip to "Compose" mode and create your test. Currently works with A/B tests, experience targeting, and A/B tests with Analytics. See Experiences for more information.
Mobile device targeting	You can select mobile device options when creating an audience. See Audiences for more information.
Click tracking (Automated Personalization)	You can now track clicks in Automated Personalization.
mboxTrace debugging utility	Examine details about your Target page implementation and activity/experience delivery status for improved troubleshooting. See Troubleshooting Content Delivery for more information.

Fixes

This release includes the following fixes:

• Fixed an issue where scrolling did not work properly in IE10.

Releases 2014

Adobe Target 14.10.2 (November 6, 2014)

This minor release is focused mainly on server stability. There are no new features as part of this patch.

Adobe Target 14.10.1 (October 30, 2014)

This release includes the following features and enhancements:

Feature	Description
Redirect offers	Redirect an experience to a different URL so you can test one page against another page. See Create a Redirect Offer.
Apply targeting on success metrics	Choose a saved audience to apply on a success metric. With this feature you can limit what actions count for a particular success event. An example might be limiting conversions to when the order is more than $0, or only counting success when a user views a particular page in the same session as entering the activity.
Automated Personalization: Select and report against RPV/AOV metrics	You can now select the RPV and AOV metrics in the Automated Personalization experience creation flow. For more information about creating n Automated Personalization activity, see Automated Personalization.
Improved permission controls	Only users with sufficient permissions can edit audiences.

This release includes the following enhancements:

• Overview page shows the activity goal.
• A warning displays when JavaScript is entered in the HTML editing box.

Adobe Target 14.9.1 (September 19, 2014)

This release includes the following features and enhancements:

Feature/Enhancement	Description
Allow insertion and editing of JavaScript	Added the ability to edit and inject custom JavaScript in the experience editor when you choose Edit HTML from the actions menu.
Automatic audience import	Audiences are automatically imported in the background when a user opens the audience list and the imported audiences are more than 10 minutes old.
Increased size of HTML offers than can be synced to Target Classic	Increased the former 64KB limit to 256KB.

This release includes the following fixes:

• Fixed an issue where video offers were not delivered correctly on Firefox.
• Fixed an issue that prevented an undo on Edit Link from showing as undone in the Visual Experience Composer.
• Fixed an issue in the Automated Personalization experience editor that caused a changed video offer to not appear as changed.
• Fixed an error that caused an activity’s Collision page from displaying in Google Chrome as a blank page.

Adobe Target 14.8.1 (August 21, 2014)

This release includes the following new features and enhancements:

Feature/Enhancement	Description
Enhanced syncing of HTML offers with Target Classic by increasing the character limit	Raised the character limit of an HTML offer created under Content to align with the 256 KB limit of HTML offers synced to Target Classic.
Improved user experience when an error is created in the Experience Editor.	The Experience Editor displays a message when DOM structure changes on the page breaks the selectors.

Fixes

• Fixed an issue where the Reporting graph was not generated while navigating between activities.

• Fixed a problem where selected links were not marked as selected when users clicked Select Link on the Goals and Settings page.

• Fixed an error that prevented a new activity from appearing in the Activity List after being activated on the Overview page.

• Fixed a problem that prevented users from selecting a link for click tracking.

• Fixed an issue that caused duplicate offers to appear in an offer-level report.

• Fixed an issue that prevented mbox elements from being inserted.

• Fixed an error that caused link click conversions not to work.

• Fixed a click-track conversion error that negated target="_blank" functions.

• Fixed a problem where click tracking was navigating off the page.

Adobe Target 14.6.1 (June 25, 2014)

This release includes the following new features:

Feature	Description
Automated Personalization (Target Premium)	Automated Personalization provides advanced machine learning algorithms to drive personalized experiences and improved conversion rates for digital experiences. Note: Automated Personalization is available as part of the Target Premium solution. It is not included with Target Standard without a Target Premium license. If you have a Target Standard or Target Premium license, use the Target card in the Adobe Experience Cloud. Implement one file on your site and to enable the ability to point and click on any content and then visually create and select additional content options for that area. Then, the modeling system automatically determines which piece of content to deliver to each individual based on all behavioral data the system has about the visitor. This ability provides a personalized experience for each visitor. The marketer does not need to run a test, then analyze the results, then deliver a winner before realizing the lift found from optimization. Automated Personalization provides: Two machine-learning algorithms: Random Forest Residual Variance Model Single line of code implementation with WYSIWYG content editing Primary goal for the activity currently uses the Conversion metric. Revenue and engagement are available as additional metrics. Connection to the Master Marketing Profile for seamless collection of advance visitor behavioral data See Automated Personalization .
Multiple activities on one page	Content from multiple Target Standard activities can be delivered on one page from one Target server call. Note: This does not affect the Target Classic priorities evaluation. For information about how Target determines which experience to show when multiple activities target the same location on a page, see Priority .

Fixes

• Fixed an issue where some shared audiences that have been deleted still show in the Audiences list.

• Fixed an error where an unexpected Save dialog box appeared in Internet Explorer 10.

• Fixed a synchronization error when saving a campaign.

• Fixed an issue where the audience for an experience was not shown on reports.

• Fixed an issue that prevented the metrics lists in Target and Analytics from matching.

• Fixed an issue that allowed users to specify their global mbox to be an mbox that is used to deliver HTML content by Target Standard. Using the global mbox in that way negatively affects content delivery and Target Classic’s ability to deliver multiple campaigns to a single page in a single request.

• Fixed an error that resulted in removed items continuing to be displayed.

Adobe Target Standard 14.5 (May 28, 2014)

This release includes the following bug fixes:

• Fixed an issue where previewing an experience did not work as expected.

Adobe Target Standard 1.7 (April 28, 2014)

Target Standard 1.7 Release Webinar

This release includes the following new features:

Feature	Description
Adobe Analytics-enhanced reporting for Adobe Target	Adobe Analytics customers can select Analytics as the default reporting source during the test set-up process . Selecting all success metrics or audiences you want to use to filter your results is no longer required. Within reporting, you can select any success metric or audience segment defined in Analytics and retroactively apply it to your reporting for extensive filtering and drill-down analysis of your optimization results. Note: To request access to this feature, visit https://survey.adobe.com/jfe/form/SV_ekBHTLSoP5Zki2y .
Master marketing profile real-time audiences	Leverage the master marketing profile that unifies visitor IDs and data into a single, actionable profile for use across solutions. A checkbox during the segment creation process in Adobe Analytics allows the segment to be available within the Adobe Target's custom audience library. A segment created in Analytics or Audience Manager can be used to target visitors in Target. Note: To request access to this feature, visit https://survey.adobe.com/jfe/form/SV_ekBHTLSoP5Zki2y .
Experience targeting activity type	Target different experiences to different audiences in one activity . Note: This provides similar functionality to the Landing Page campaign in Target Advanced.
Multi-page testing	Choose to run a test or targeted activity across a set of webpages . You can now deliver tests to every product page, or modify your global nav on every page of the site. Use a simple rule builder to specify what the group of pages should be.

Bug Fixes

This release includes the following bug fixes:

• Fixed an issue that prevented target.js from being compressed by Edge.
• Fixed an issue in reports that prevented the conversion count in the Activity row from displaying for A/B activities.
• Fixed an issue where a report no longer displayed after an experience with data was deleted.
• Created a workaround to automatically bypass a Chrome version 34 defect that prevented pages with mixed content from displaying. All versions of Chrome can now be used.

Known Issues

This release includes the following known issues. This issue will be fixed in an upcoming update.

• Click tracking does not work on elements that have been rearranged using the Visual Experience Composer. Avoid setting up click tracking on rearranged elements until this is bug is fixed.
• A synchronization error occurs if Geo audiences are created in Target Standard when geolocation is disabled in Target Advanced.
• Unable to swap an image when the image is referenced in CSS.
• If you swap an image, and then resize it, the experiences in the Experience Editor do not display correctly.

Adobe Target Standard 1.6 (March 17, 2014)

This release includes the following new features:

Feature	Description
Localized versions available	Target Standard has been localized in French, German, Japanese, and Spanish
Simplified implementation	Target Standard has been improved to make it easier to implement for existing Target Advanced users. The new implementation uses your existing global mboxes to run Adobe Standard activities.

Bug Fixes

This release includes the following bug fixes:

• Fixed an issue that caused Remove Item and Edit HTML to not work in certain cases.

Known Issues

This release includes the following known issues. This issue will be fixed in an upcoming update.

• Winner works based on Goal only and does not change based on metrics selected.
• Click tracking does not work on elements that have been rearranged using the Visual Experience Composer. Avoid setting up click tracking on rearranged elements until this is bug is fixed.
• A synchronization error occurs if Geo audiences are created in Target Standard when geolocation is disabled in Target Advanced.
• Unable to swap an image when the image is referenced in CSS.
• The new viztarget mbox type does not work with the Target Advanced/Adobe Analytics integration v4, the current version.
• In reports, the number format and currency shown on the graph does not match the table if the locale is set to something other than dollar.
• Audiences search box does not support non-ASCII characters.
• For users of the Spanish and Japanese versions, saving an activity after setting the start and end dates results in an error. It is recommended that you save without setting start and end dates, and then activate and stop your activity from the Activity Overview or Activity List page when required.

Adobe Target Standard 1.5 (February 25, 2014)

This release includes the following new features:

Feature	Description
Activity collisions	Target Standard now provides a list of activity collisions. An activity collision occurs when multiple activities are set up to deliver content to the same page. If an activity collision occurs, you may not see the expected content on your page because you've entered a different activity. All activities on the same URL are listed, regardless of any audience targeting in each activity. If your activity contains collisions, a Collisions tab is available the on the activity overview page. Open this tab for a list of activities that are colliding. Click an activity in the list to view the overview page for that activity. See Activity Collisions .
New targeting options: Profile, User	You can now target profile and user parameters. See Audiences .
Insert elements	You can now add any kind of element to your page in addition to modifying existing content. Add text, code, lists, and more to create entirely different experiences to test. See Visual Experience Composer Options .

This release includes the following known issues. This issue will be fixed in an upcoming update.

• Winner works based on Goal only and does not change based on metrics selected.
• Click tracking does not work on elements that have been rearranged using the Visual Experience Composer. Avoid setting up click tracking on rearranged elements until this is bug is fixed.
• A synchronization error occurs if Geo audiences are created in Target Standard when geolocation is disabled in Target Advanced.
• Unable to swap an image when the image is referenced in CSS.

Adobe Target Standard 1.4 (January 20, 2014)

This release includes the following new features and enhancements:

Feature	Description
Estimate revenue lift	Target can estimate the revenue lift you would attain if all users view the winning experience. This estimate calculates the amount of lift achieved by the winning experience and your total number of visitors over the life of the test, and shows the lift you might achieve if every visitor sees the winning experience, if the trends continue as they have during the test. The accuracy of the estimate depends on a number of factors, including projected figures if current trends continue. These values are estimates based on past performance and should not be used for financial guidance. Future results may vary.
Undo/Redo	You can undo changes you make to your activities during an editing session. You can also redo undone changes. See Visual Experience Composer Options .
Move element	You can move elements on your page. Unlike Rearrange Elements, Move does not shift other elements to make room for the element being moved. Use your arrow keys to fine tune the move. See Visual Experience Composer Options .
Resize element	You can resize an element on your page. When you select Resize, a handle appears in a corner of the element that lets you drag that corner to resize. See Visual Experience Composer Options .
Target a location when setting up an audience	When creating an audience, you can select a location (mbox) and specify parameters for that location. See Creating a New Audience .
Preview links (Enhancement)	Preview links work as expected.

This release includes the following fixes:

• Fixed issues that prevented preview links from displaying as expected.

This release includes the following known issues. These issues will be fixed in an upcoming update.

• If Estimated Lift is enabled in Target Standard, and Target Advanced is set to a different time zone than the user’s browser, the predicted revenue value might not appear on the Activities list or in the Reports status bar for up to one full day. Because Report View uses date but not time, the data appears in Report View but not for projected lift.
• Click tracking does not work on elements that have been rearranged using the Visual Experience Composer. Avoid setting up click tracking on rearranged elements until this is bug is fixed.
• A synchronization error occurs if Geo audiences are created in Target Standard when geolocation is disabled in Target Advanced.
• Unable to swap an image when the image is referenced in CSS.

Releases 2013

Adobe Target Standard 1.3 (November 19, 2013)

This release includes the following new features and enhancements:

Feature	Description
Geo-targeting	Target on Country, State, City, Zip code, or DMA.
Use the Visual Experience Composer to rearrange elements.	You can rearrange child elements inside their parent element using the Visual Experience Composer.
Preview experiences directly on your site.	Once you save an activity, you can preview it directly on your site, even if the activity is not live. This allows you to see how it will appear, without serving it through an iFrame. You can copy links to each test experience to view those experiences in your browser or to send them to your team members for them to view. People who view these pages will not be counted in the reports.

This release includes the following fixes:

• Fixed an issue where the click tracking metric was not deleted from an activity if the experience URL was reset.
• Fixed an issue in the experience composer that caused the default experience to flash quickly before new content displays when navigating through experiences.

This release includes the following known issues. These issues will be fixed in an upcoming update.

• A synchronization error occurs if Geo audiences are created in Target Standard when geolocation is disabled in Target Advanced.
• Unable to swap an image when the image is referenced in CSS.
• Click tracking does not work on elements that have been rearranged using the Visual Experience Composer. Avoid setting up click tracking on rearranged elements until this is bug is fixed.
• Users cannot select the Remove action for content that is wrapped in an mbox.

Adobe Target Standard 1.2 (Oct. 31, 2013)

There are four known issues with this release. These issues will be fixed in an upcoming update.

• On some clusters, editing a reusable offer may not be reflected on customer’s site for activities that use that offer outside of an mbox.
• Swapped images in area of a page that is not controlled by an mbox might result in a 404 error.
• When you create a new audience, or edit and save an existing audience, it does not show in the Audiences list until you refresh the screen or search for the audience.
• When you delete an HTML offer from Target Standard, it is not deleted from Target Advanced.

This release includes the following fixes and enhancements:

• Fixed multiple issues that caused some activities and experiences to fail to sync properly with Target Advanced.

• Fixed an issue where target.js moves other scripts out of the <head> section of a page.

• Fixed an issue that caused some referenced assets to copy when an activity is copied.

• Fixed an issue that caused an updated image offer content to fail to update in both Scene7 and Target Advanced.

• Fixed an issue where applying a search filter clears the audiences selected in “Audiences for Reporting.”

• Enhanced graphs to default to hourly results when a test has been live for less than two days.

• Fixed an issue that caused copying a non-synced activity to fail.

• Added keyboard input functionality to drop down menus for location.

• Improved the error message that displays when deleting an offer used in an activity.

Adobe Target Standard 1.1 (Oct. 18, 2013)

This release includes the following fixes and enhancements:

• Fixed an issue that caused the activity sync to fail in the first sync attempt after adding valid experiences to a partial activity.
• Fixed an issue that resulted in a 500 error on the Summary report after deleting and adding an experience.
• Fixed an issue that caused inaccurate visitor data when a visitor views multiple experiences.
• Activity start and end times now sync correctly between Standard and Advanced.
• Improved the display of mixed content.
• Fixed an issue that caused the Visual Experience Composer to malfunction if JavaScript in the HTML code overrides the browser definition of the JSON object.
• Fixed an issue where the displayed number of activities was incorrect when sorting according to status.
• Fixed an issue where white space in the Goal field did not validate correctly.
• Fixed an issue that caused the creation of multiple offers for a single in Advanced when the image was swapped.
• Fixed an issue that caused search not to work on images in the content picker.
• Fixed a defect that inverted activity list sorting when sorting by Name or State.
• Fixed an issue where anonymous offers were not being deleted when no longer used in an activity.
• Fixed a defect that caused an incorrect experience name to display on a shared card when editing an activity.
• Fixed a defect where an updated image offer did not correctly update the content in both Scene7 and Target Advanced.
• Fixed an issue where copying an image asset also copied Scene7-related properties that should not have been copied.