Show Menu
TOPICS×

Release notes for previous releases

Release notes for previous Target releases, including release notes for Target Standard/Premium, the Target platform, and the Target Javascript libraries (at.js and mbox.js). Release notes are arraigned in descending order by month and year of release.
See Target release notes (current) for information about the current month's Target releases (platform and Target Standard/Premium).

Release notes - 2018

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()
Note: If you require Adobe Opt-in support for the General Data Protection Regulation (GDPR), 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).
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)
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:
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.
Note: There is a known issue regarding this functionality.
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:
(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)

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.

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)
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)
Reporting source for activities
In Setup > Preferences , 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.
  • 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 Setup 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:
The issue numbers in parentheses are for internal Adobe use.
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:
The issue numbers in parentheses are for internal Adobe use.
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.
Visual Experience Composer (VEC)
  • You can dock the Modifications panel vertically along the side of the Target UI or horizontally at the bottom.
  • We have grouped various VEC actions to make your job quicker and more efficient. (TGT-30472)
  • 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!
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).
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:
The issue numbers in parentheses are for internal Adobe use.
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:
(TGT-30229)
Audiences
Compare one profile attribute to another profile attribute instead of to a static number.
(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)
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)
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.
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:
The issue numbers in parentheses are for internal Adobe use.
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.
For more information, see Base the Recommendation on a Recommendation Key . (RECS-5865)
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:
The issue numbers in parentheses are for internal Adobe use.
  • 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:
The issue numbers in parentheses are for internal Adobe use.
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.
  • The Target Recommendations API documentation can be found on the Adobe I/0 Adobe Target website (https://www.adobe.io/apis/experiencecloud/target/docs/getting-started.html).
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:
The issue numbers in parentheses are for internal Adobe use.
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
The Target Product Documentation is currently being localized and will be posted in the above languages when ready.
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:
The issue numbers in parentheses are for internal Adobe use.
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
For more information, see the "Custom Attribute" row in Base the Recommendation on a Recommendation Key .
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)
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.
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.
For more information about this change, see About the new cloud names in Experience Cloud .
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:
The issue numbers in parentheses are for internal Adobe use.
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)
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
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.
mbox.js
The default timeout for mbox.js 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)
Auto-Target
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 Setup, 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 .
See Known Issues and Resolved Issues for more information about the rollout.
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 .
mbox.js
July 18, 2017
mbox.js version 63 is now available. For more information, see Download mbox.js .
The following enhancements and fixes are included in mbox.js version 63:
  • Fixes an issue with SDID generation when using mboxDefine() and mboxUpdate() . This affects only clients that have Visitor API on the page.

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. Response tokens are not supported with mbox.js .
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:

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:
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 Setup > Preferences. (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 Platform Changes (July 18, 2017)

Change Details
mbox.js
July 18, 2017
mbox.js version 63 is now available. For more information, see Download mbox.js .
The following enhancements and fixes are included in mbox.js version 63:
  • Fixes an issue with SDID generation when using mboxDefine() and mboxUpdate() . This affects only clients that have Visitor API on the page.
at.js
July 7, 2017
at.js version 1.0 is now available. For more information, see Download at.js .
The following enhancements and fixes are included in at.js version 1.0:
  • Support for loading at.js asynchronously for faster page loads.
  • Support for pre-hiding page content when loading at.js asynchronously.
  • Better error messaging when content delivery is disabled.
  • Performance improvements when delivering multiple activities.
  • Support for YUI Compressor.
  • Bug/error reporting for custom events during activity delivery.
  • Fix for performance issues in Microsoft Internet Explorer 11.
  • Fix for getOffer() function giving an error on some websites.
  • Load the Target library asynchronously.

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 .
This Target release includes the following customer-facing enhancements and fixes: (issue numbers in parentheses are for internal Adobe use):
  • Fixed an XSS security issue with mbox.js. This fix is a server-side fix that does not require an mbox.js update.

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) For more information, see Plug-Ins in the Adobe Target Classic documentation.
  • 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 .
The ability to view multiple metrics in a report, included in the Target 17.3.1 release (March 30, 2017) has been removed due to unexpected behavior. This feature will be available again in an upcoming release.
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)

Adobe Experience Manager 6.2 with FP-11577 (or later) now supports at.js implementations with its Adobe Target Cloud Services integration. For more information, see Feature Packs and Integrating with Adobe Target in the Adobe Experience Manager 6.2 documentation.
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) or mbox.js (version 61 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 ( & ), to be consistent with naming requirements for mbox names using mbox.js . (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 .
mbox.js version 62
January 18, 2017
mbox.js version 62 contains the following enhancement and fixes:
  • Fixed flicker issues in redirect activities when viewed in Google Chrome browsers. (TNT-24928)
  • Added secureOnly setting that indicates whether mbox.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. (TNT-26183)
    For more information, see Configure mbox.js .
For detailed information about the changes in each version of mbox.js , see mbox.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)
  • 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 whitelist IP addresses used for the VEC, add the new IP addresses.

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."
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 ( Setup > 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 Creating 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.

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.
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. A similar option is part of mbox.js v61.
  • 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.
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 (August 2016)

Change Details
mbox.js version 61
August 23, 2016
mbox.js version 61 includes the following changes in the August release:
  • mbox.js version 61 is now the default download in the Target Standard/Premium and Target Classic user interfaces.
  • Added an optoutEnabled setting to support future Adobe Experience Cloud opt-out functionality. The default value is false. If this property is enabled, all requests execute asynchronously against the /ajax endpoint, just like version 60.
For more information about all the changes in mbox.js version 61, see mbox.js Version Details .

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 .
mbox.js version 61
July 28, 2016
mbox.js version 61 is now available for download. Version 61 is not currently the default download.
For more information, see mbox.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 Setup > Preferences .
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:
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.
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.
QA/Preview URLs
Preview URLs are now available for the form-based experience composer.
Recommendations custom algorithms
Custom algorithm mappings can be uploaded in a CSV file. It is no longer required to use the XML-based API.
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.
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
  • Configuring and implementing mbox.js
  • 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.
at.js replaces mbox.js for Adobe Target implementations.
Although at.js replaces mbox.js, mbox.js will continue to be supported. For most people, at.js provides advantages over mbox.js. This gives you time to test at.js and to change the implementation on your pages.
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.
  • Target plugins that reference mbox.js objects and methods are not supported.
  • All calls to Target are made via XMLHTTPRequest and content is returned via JSON.

Target Platform Changes

  • Mbox.js version 60 is now the default download.
  • Mbox.js versions earlier than 50 are no longer actively tested. If your implementation is not yet updated, ensure additional QA is performed on all Target content delivery and reporting collection.
  • Flash campaigns and other Flash-related items have been removed from Target.
  • Internet Explorer 10 is no longer supported in the Target interface.
  • Support for content delivery in Internet Explorer 8, 9, and 10 is expected to end in an upcoming release.
    Active testing will be discontinued in a future release for these browsers, following the end of active support for these browsers by Microsoft. Target will continue to deliver content to these browsers, but you should test content delivery and data collection for reports.

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
Experience Cloud Notifications
Notifications from Target are visible in all Adobe Experience Cloud solutions. Notifications are automatically sent when an activity is activated or deactivated. These notifications are available to all users with access to Target Standard/Premium.
Notifications are also visible in Target Standard/Premium.
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 .
For more information about the user interface improvements, see What's New in the Adobe Experience Cloud - Spring 2016 .
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 .
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.
at.js replaces mbox.js for Adobe Target implementations.
Note: Although at.js replaces mbox.js, mbox.js will continue to be supported, although, for most people, at.js provides advantages over mbox.js. This gives you time to test at.js and to change the implementation on your pages.
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.
  • Target plugins that reference mbox.js objects and methods are not supported.
See at.js Implementation for documentation.
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 Setup > Preferences 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 Setup > Preferences 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.
"Super" audiences
Use nested AND/OR logic when configuring audiences.
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.
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.
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.
Enhancement: Allow targeting on hash (#) fragments
You can now target on the part of a URL that follows a hash (#).
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.
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 Setup > Preferences 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
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.
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.
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.
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.
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.
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
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.
Location targeting on form-based activity creation
Apply targeting to your mbox locations to limit where your activity displays.
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.
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.
Recommendations
Form-based recommendations
Create recommendations activities for non-site locations including emails, consoles, kiosks, etc.
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.
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.
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.
Confidence interval for binary metrics
Updated reports using Target-based data show the confidence interval of the lift, compared to the control.
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.
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.
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.
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.
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.
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.

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.
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.
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.
New mbox.js
Version 58 of mbox.js ensures the Experience Cloud Visitor ID service is ready before the Target calls are made. This ensures that audience data shared through the Profiles and Audiences core service are available on the same hit. However, flicker can occur on the page while Target waits for the service to return, so full QA is important before upgrading. This mbox.js version is only available via API.
See the mbox.js change log for information about each version of mbox.js.
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.
Enhancement: Experience Targeting experience limit removed. The previous limit of ten experiences in Experience Targeting has been removed.
Mbox.js management and editing options
All mbox.js configuration and editing is now available within Target Standard. You no longer need to make modifications in Target Classic.
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 that affected the enabling of target.js when newly provisioned users downloaded mbox.js.
  • 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.
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)
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
    See Setup .
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
  • 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.
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.
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.
Automated Personalization: Traffic Estimator
The Traffic Estimator, formerly available only in the Multivariate Test activity type, is now available for Automated Personalization activities.
Automated Personalization: Visual Preview
Visually preview every content combination inside the Visual Experience Composer.
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.
See Customer Attributes in the Experience Cloud Product Documentation..
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.
  • mbox.js version 56 moved the "extra JavaScript" section so it is executed before global mbox.
    All settings in v56+ are name spaced. If there are functions declared in "extra JavaScript," they must be prefixed with window. See mbox.js Change Log.

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.
mbox.js v56
  • Changes for Premium Recommendations to support passing parameters into global mbox
  • Adds a 5 second timeout to the target.js load call. In the rare case that the file doesn't load, the page will render and no Target Standard activities will display.
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).
See Multivariate Test for more information.
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:
Some features in this release are available only as part of the Target Premium solution.
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
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.
To learn more about the Target priorities decision process, refer to the Target Standard help .
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)

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://www.adobe.com/go/audiences .
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://www.adobe.com/go/audiences .
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.
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.
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.
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.
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.
Target a location when setting up an audience
When creating an audience, you can select a location (mbox) and specify parameters for that location.
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.
  • Fixed an issue where an mbox.js file downloaded from Target Standard is named mboxEditor.at.js.
  • 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 feature:
Feature
Description
mbox.js download from within Target Standard
The mbox.js file can now be downloaded directly from Setup > Implementation in the Target Standard interface. Previously, the file had to be downloaded from within Target Advanced or be supplied by your account representative or consultant.
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.