Release notes for previous releases

The Recommendations implementation pattern using at.js articles help you understand and create your Adobe Target Recommendations implementation when using the at.js JavaScript library.

For more information, see Recommendations implementation pattern using at.js overview in the Adobe Target Developer Guide.

Adobe Target QA mode is now available for Automated Personalization activities, replacing Preview links functionality.

For more information, see Activity QA.

Real-Time CDP Profile Attributes can be shared with Target for use in HTML and JSON offers.

For more information, see Share Real-Time CDP Profile Attributes with Target.

Use Adobe Experience Manager (AEM) Content Fragments in Target activities. Combine the ease-of-use and power of AEM with powerful Artificial Intelligence (AI) and Machine Learning (ML) capabilities in Target to aid headless personalization and experimentation.

For more information, see AEM Content Fragments.

The Adobe Target Developer Guide has been relocated to Adobe Experience League. The move to Experience League aids in localization of text in additional languages, unifies search within Experience League to span and offer search results from both the Adobe Target Business Practitioner Guide and the Adobe Target Developer Guide, and provides additional benefits.

You will be redirected from the previous location to Experience League automatically. Please update your bookmarks as necessary.

Optimized A4T metrics for Auto-Allocate and Auto-Target

(Release date March 30, 2023)

Target lets you choose metrics based on binomial events or metrics based on continuous events when using A4T for Auto-Allocate and Auto-Target activities.

Be aware of the following change in supported metrics:

• Target preserved the previous behavior for existing activities until September 9, 2023. After this date, activities using non-supported metrics will be discontinued to force existing activity migration to the new behavior.

For more information, see “Supported goal metrics” in A4T support for Auto-Allocate and Auto-Target activities.
With this feature, the following tutorials have been updated:

• Setting up A4T reports in Analysis Workspace for Auto-Allocate activities
• Setting up A4T reports in Analysis Workspace for Auto-Target activities

Updates to the AEM experience fragments functionality include the following:

• Added the ability to filter AEM experience fragments by type (HTML or JSON) in the Offers list. (TGT-43121)
• Fixed an issue that allowed customers to insert JSON Experience Fragment offers when using the VEC, which is not supported. JSON offers can be inserted only when using the Form-Based Experience composer. (TGT-43846)

For more information, see AEM experience fragments.

A new Adobe Target Visual Experience Composer (VEC) extension for Chrome is available in the Chrome Web Store.
Starting in January 2023, the current Target VEC Helper extension will stop working in Google Chrome because Google won’t allow extensions using Manifest V2. Download the new extension to continue to visually author your websites in Target starting with the new year.
The following links show the two extensions in the Chrome Web Store:

• New extension
• Old Extension

For more information, see Visual Editing Helper extension.

Get the following relevant in-product notifications:

• Activities: Notifications for all activity types when an activity is approved or deactivated, either manually or when it reaches its start or end date. The notification includes the name of the activity with a link to the activity’s overview page.
• Profile scripts Notifications when a profile script is activated or deactivated, either manually or by Target.
• Recommendations feeds: Notifications when a Recommendations feed is activated or deactivated, either manually or by Target. Notifications are also sent when a Recommendations feed fails.

By default, notifications are received by product admins, publishers, and approvers. Notifications are configurable inside Experience Cloud preferences.
For more information see Notifications and announcements.

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

• The ability to select and delete multiple audiences simultaneously
• A refreshed audience builder design
• Exclusion rule support in the Audience library rule builder
• A new “Audience Source” filter, to allow for faster audience discovery
• Session persistent search and filter options
• The ability to move audiences between workspaces for Target Premium customers.

For more information, see Audiences.
NOTE: This feature will be rolled out to customers in different regions in the next eight weeks.

The Profile Scripts library was also updated, and includes a refreshed interface along and several productivity updates:

• The ability to select and delete multiple profile scripts simultaneously
• A new code editor for profile scripts
• Syntax highlighting and error checking inside the code editor
• Auto-complete tokens (mbox or profile) parameters through keyboard shortcuts

For more information, see Visitor Profiles.
NOTE: This feature will be rolled out to customers in different regions in the next eight weeks.

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

• The ability to select and delete multiple audiences simultaneously
• A refreshed audience builder design
• Exclusion rule support in the Audience library rule builder
• A new “Audience Source” filter, to allow for faster audience discovery
• Session persistent search and filter options

For more information, see Audiences.

The Profile Scripts library was also updated, and includes a refreshed interface along and several productivity updates:

• The ability to select and delete multiple profile scripts simultaneously
• A new code editor for profile scripts
• Syntax highlighting and error checking inside the code editor
• Auto-complete tokens (mbox or profile) parameters through keyboard shortcuts

For more information, see Visitor Profiles.

Recommendations Criteria create and edit

Search your Recommendations product and content catalog programmatically via API to identify items that match a search criteria and simplify administration of your catalog.
Limitations and notes:

• Catalog search via API is not supported for environments with more than 2,000,000 items.
• Catalog search results via API are updated more rapidly than catalog search results via the Target UI. The catalog search in the Target UI can take additional time to reflect the latest results.

For more information, see Searching Entities in the Adobe Target Recommendations API guide.

Target Recommendations supports new list-based operators for entity filtering rules. (TGT-39234)
Newly added operators include:

• Is Contained In List
• Is Not Contained In List
• List Contains An Item In
• List Does Not Contain An Item In
• List Contains All Items In
• List Does Not Contain All Items In

For more information, see “Available operators” in Use dynamic and static inclusion rules.

Two response tokens have been added to Auto-Target and Automated Personalization activities to enable determination of whether a visitor received a particular experience as a result of being assigned to “control” or to “targeted” traffic.

• experience.trafficAllocationId will return 0 if a visitor received an experience from being in “control” traffic and 1 if a visitor received an experience from the “targeted” traffic distribution.
• experience.trafficAllocationType will return “control” or “targeted.”

For more information on control vs. targeted traffic, see Select the control for your Automated Personalization or Auto-Target activity.

This new role is similar to the current Observer role (can view activities, but cannot create or edit them). However, the Publisher role has the additional permission to activate activities.
For more information, see:

• Target Standard users: Specify roles and permissions in Users.
• Target Premium users: Step 6: Specify roles and permissions in Configure enterprise permissions.

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

• Fixed an issue when using CNAME and edge override, at.js 1.x might incorrectly create the server domain, which resulted in the Target request failing. (TNT-35064)

For more information, see at.js version details.

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

• Made the deviceIdLifetime setting overridable via targetGlobalSettings. (TNT-36349)
• Fixed an issue when using CNAME and edge override, at.js 2.x might incorrectly create the server domain, which resulted in the Target request failing. (TNT-35065)
• Fixed an issue when using the Target Launch extension v2 and the Adobe Analytics Launch extension, Target delayed the Analytics sendBeacon call. (TNT-36407, TNT-35990, TNT-36000)

For more information, see at.js version details.

The Target Java SDK lets you deploy Target server-side. This Java SDK helps you easily integrate Target with other Adobe Experience Cloud solutions, such as the Adobe Experience Cloud Identity Service, Adobe Analytics, and Adobe Audience Manager.
The Java SDK introduces best practices and removes complexities when integrating with Target via our delivery API so that your engineering teams can focus on business logic. The following are notable features that we are introducing in the latest version:

• Support for prefetching and notifications that allows you to optimize for performance via caching.
• Support for optimizing performance when you have a hybrid integration of Target on both your web pages and server-side. We are introducing a setting called serverState that is populated by experiences retrieved via the server-side so that at.js 2.2 will no longer make an additional server call to retrieve the experiences. This approach optimizes page load performance.
• Support for retrieving VEC-created activities via the Java SDK, which is made possible by the new Delivery API.
• Open sourced so your developers can contribute to the Target Java SDK.

Learn more about the Target Java SDK on the Adobe Tech Blog - Server-Side Optimization with the new Target Java SDK.

Sometimes you want to work with a multi-value field. Consider the following examples:

• You offer movies to users. A given movie has multiple actors.
• You sell tickets to concerts. A given user has multiple favorite bands.
• You sell clothing. A shirt is available in multiple sizes.

To handle recommendations in these scenarios, you can pass multi-value data to Target Recommendations and use special multi-value operators.
For more information, see Work with multi-value attributes.

These versions of at.js provide:

• Improved performance when using both Experience Cloud ID Service (ECID) v4.4 and at.js 2.2 or at.js 1.8 on your web pages.
• Previously, the ECID made two blocking calls before at.js could fetch experiences. This has been reduced to a single call, which significantly improves performance.

In order to take advantage of these performance improvements, upgrade to at.js 2.2 or at.js 1.8 along with ECID Library v4.4.
at.js 2.2 provides:

• serverState: A setting available in at.js v2.2+ that can be used to optimize page performance when a hybrid integration of Target is implemented. Hybrid integration means that you are using both at.js v2.2+ on the client-side and the delivery API or a Target SDK on the server-side to deliver experiences. serverState gives at.js v2.2+ the ability to apply experiences directly from content fetched on the server side and returned to the client as part of the page being served.
  For more information, see “serverState” in targetGlobalSettings.

The Target Node.js SDK lets you deploy Target server-side.
This Node.js SDK helps you easily integrate Target with other Experience Cloud solutions, such as the Adobe Experience Cloud Identity Service, Adobe Analytics, and Adobe Audience Manager.
The Node.js SDK introduces best practices and removes complexities when integrating with Adobe Target via our delivery API so that your engineering teams can focus on business logic. The following are notable features that we are introducing in the latest version:

• Support for prefetching and notifications that allows you to optimize for performance via caching.
• Support for optimizing performance when you have a hybrid integration of Target on both your web pages and server-side. We are introducing a setting called serverState that will be populated by experiences retrieved via the server-side so that at.js 2.2 will no longer make an additional server call to retrieve the experiences. This approach optimizes page load performance.
• Support for retrieving VEC-created activities via the Node.js SDK, which is made possible by the new Delivery API.
• Open sourced so your developers can contribute to the Node.js SDK.

An entirely new delivery API endpoint (https://experienceleague.adobe.com/v1/delivery?lang=en) is available in production. Notable features are:

• One endpoint to retrieve experiences for one or more mboxes.
• Retrieve VEC-created activities via the API.
• Support for an entirely new object called Views that is used for Single Page Applications (SPAs) and Mobile applications.

With the Target September 2019 release, Enterprise Permissions provides customers with the following access controls:

• You can choose the workspaces to which the integration can be applied.
• You can apply a role to the Adobe I/O integration: Approver, Editor, or Observer.

For step-by-step instructions and more information, see Grant Adobe I/O integrations access to workspaces and assign roles.

New VEC menu options: When you click a page element in the VEC, a menu shows the options that are available for that element type.

• You can now use the Styles > Background option to change the background image and color for the selected element. (TGT-15001)

See Styles in Visual Experience Options.
Click-tracking improvements: We have improved the process for configuring click tracking within the VEC and the Single Page Application (SPA) VEC.

• While selecting elements to use in click tracking, the names of all available elements display in the Modifications panel on the right side, making it quick and easy to select the desired elements.
• The Goals & Settings page of the three-part guided activity workflow displays a number representing the number of elements selected for click tracking. You can hover over this number to see the names of all selected elements. (TGT-33878)

See Click tracking.

The SPA VEC includes the following enhancements to make your work quicker and more efficient:

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

For more information, see Single Page App (SPA) Visual Experience Composer.

The Visual Experience Composer (VEC) includes the following enhancements to make your work quicker and more efficient:

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

The Visual Experience Composer (VEC) includes the following enhancements to make your work quicker and more efficient:

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

at.js 2.x is now available.
The newest version of at.js provides rich feature sets that equip your business to execute personalization on next generation client-side technologies. This new version is focused on upgrading at.js to have harmonious interactions with single page applications (SPAs).
Here are some benefits of using at.js 2.x that are not available in previous versions:

• The ability to cache all offers on page load to reduce multiple server calls to a single server call.
• Tremendously improve your end-users’ experiences on your site because offers are shown immediately via the cache without any lag time that traditional server calls introduce.
• Simple one-line of code and one-time developer setup to enable your marketers to create and run A/B and Experience (XT) activities via the Visual Experience Composer (VEC) on your single page applications.

at.js 2.x introduces the following new functions:

• getOffers()
• applyOffers()
• triggerView()

The following functions have been deprecated with the introduction of at.js 2.x:

• mboxCreate()
• mboxDefine
• registerExtension()

For more information, see Upgrading from at.js 1.x to at.js 2.x and at.js functions.
Note: If you require Adobe Opt-in support for the General Data Protection Regulation (GDPR){target=_blank}, you must currently use at.js 1.7.0. Opt-in support is not supported in at.js 2.x.

The Visual Experience Composer (VEC) includes the following enhancements to make your work quicker and more efficient:

• You can now use the Insert Before and Insert After options in the VEC while inserting AEM experience fragments. See Visual Experience Composer options. (TGT-32385)
• The Adobe Target VEC Helper browser extension for Google Chrome lets you load websites reliably within the VEC to rapidly author and QA web experiences. See Visual Experience Composer helper extension. (TGT-32746)

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.

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)

You can now preview the contents of Recommendations collections and exclusions for a selected environment (host group).
Previously, when you viewed a collection or exclusion, the displayed items contained were results for the default host group (specified in Recommendations > Settings > Default Host Group).
Now, when creating or updating a collection or exclusion, you can use the Environment selector to choose the environment to preview results for. The new Environment filter saves you time and effort because you no longer need to navigate to the Settings page to select the appropriate default host group before creating or editing collections and exclusions.
Note: After changing the selected environment, you must click Search to update the returned results.
The new Environment filter is available from the following places in the Target UI:

• Catalog Search (Recommendations > Catalog Search)
• Create Collection dialog box (Recommendations > Collections > Create New)
• Update Collection dialog box (Recommendations > Collections > Edit)
• Create Exclusion dialog box (Recommendations > Exclusions > Create New)
• Update Exclusion dialog box (Recommendations > Exclusions > Edit)

For more information, see the following topics:

• Collections
• Exclusions
• Catalog Search
• Settings
• Recommendations: filter collections and exclusions by environment (host group)

(TGT-20622)

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.

Personalization Insights reports

Note: Available November 14, 2018.

Two specialized reports are available to users of Automated Personalization (AP) and Auto-Target (AT) activities:

• Automated Segments: Different visitors respond differently to the offers/experiences in your AP/AT activity. This report shows how different automated segments defined by Target's personalization models responded to the offers/experiences in the activity.

• Important Attributes: In different activities, different attributes are more, or less, important to how the model decides to personalize. This report shows the top attributes that influenced the model and their relative importance.

See Personalization Insights reports.

You can now copy an experience in an Experience Targeting (XT) activity so you can make minor changes to it without having to re-create the experience from scratch. This capability was already available for A/B Tests. (TGT-31504)

See Create experience.

In the September 2018 release, we added an enhancement that lets you filter offers by reporting groups. You can now filter for Unassigned Offers so you can assign a reporting group to an offer that is not currently assigned to any reporting group. (TGT-31882)

See Create an Automated Personalization activity.

In Administration > Visual Experience Composer , you can select the reporting source for your activities, either Target or Adobe Analytics . You can also choose to select your reporting source per activity.

Starting with this release, there are some important workflow considerations you should be aware of when you choose the reporting source in Preferences or per activity.

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.

• 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.

Access specialized reports for your Automated Personalization (AP) and Auto-Target (AT) activities:

• Automated Segments: See how different automated segments defined by Target's personalization models respond to offers/experiences in your activity.

• Model Attribute Ranking: See the top attributes that influenced Target's personalization models and the relative importance of each attribute.

Note: This feature will be available soon. Stay tuned for an announcement of the exact date when this feature will be ready for you to use.

See Personalization Insights Reports.

• You can dock the Modifications panel vertically along the side of the Target UI or horizontally at the bottom.

  See Modifications.

• We have grouped various VEC actions to make your job quicker and more efficient. (TGT-30472)

  See Visual Experience Composer Options.

• You can edit offers more efficiently, thanks to a larger edit window. (TGT-31052)

Get the most out of Adobe Target by learning more about various features and see why you should give them a try. The Tips and Tricks functionality displays on the Activities list page and provides links to videos, use-cases, blogs, documentation, and much more. Become a Target Power User!

See Tips and Tricks.

Participate in the new Target Basics Webinar Series, a Customer Success Webinar Series brought to you by the Community.

The next webinar, Best Practices in Reporting & Value Socialization, is scheduled for August 22, 2018 from 8 to 9 a.m. (PDT).

See Target Basics Webinar Series.

Edit and delete experiences right from the activity diagram. Now you can jump into the Visual Experience Composer (VEC) for a specific experience or delete an experience right from the diagram.

See:

• A/B activity: Add Experience

• XT activity: Create Experience

(TGT-30229)

Compare one profile attribute to another profile attribute instead of to a static number.

See Creating a Profile Attribute Comparison Audience.

(TGT-28406)

"Custom Code" is now available from the "Add Modifications" panel instead of having its own tab. You can also add more than one custom code and optionally name each custom code. (TGT-28504)

See Modifications.

• View a list of activities that reference a selected criteria on its Criteria card. The card lists active and inactive activities. (TGT-27672)

• From the activity diagram, Criteria cards now show when results are ready to display. (TGT-27673)

  See Criteria.

Adobe Target Experience Templates are pre-coded offer samples with configurable inputs to be used in Target to execute some common marketer use cases. These experience templates are provided free to developers and marketers as a starting point to execute some common external use cases in Adobe Target - either via the Visual Experience Composer or Form-Based Experience Composer. Customization might be required to integrate successfully with your webpage or platform architecture.

See Experience Templates.

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

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)

Added Microsoft Edge support for the Target UI and for content delivery.

For more information, see . Supported Browsers(TGT-14102)

• 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.

• 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.

• 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.

• 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.

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.

• 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)

The Target UI is now available in the following languages:

• Chinese Simplified

• Chinese Traditional

• Korean

• Italian

• Portuguese

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).

at.js version 1.3.0 is now available. For more information, see Download at.jsand 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.

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

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.

Improved the lift and bounds information in reports to be more comprehensive and useful, including a tooltip that explains how bounds are calculated. (TGT-28729)

For more information, see Average Lift, Lift Bounds, and Confidence Interval.

Additional guidance is available in the UI and in Help to help you allocate traffic percentages more effectively in Automated Personalization (AP) and Auto-Target activities.

For more information, see Determining Traffic Allocationand Creating an Automated Personalization Activity.

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)

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)

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.

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.

• 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)

• You can now view confidence intervals for continuous variables. (TGT-22085)

• Target now displays lift bounds when statistically significant in reports.(TGT-27301, TGT-27794, and TGT-26387)

See Report Settings.

• 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)

• The UI now displays the status of uploading custom algorithm data for recommendations. See Uploading Custom Criteria. (TGT-23891)

• The Value is Present and Value is Not Present operators are now available while creating algorithm inclusion rules. See Use Dynamic and Static Inclusion Rules. (TGT-24110)

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 letterto learn more.

Subscribe to the newsletterto help you deliver the exceptional customer experiences that drive business success.

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.

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)

Added the following built-in parameters:

• profile.tntId

• profile.marketingCloudVisitorId

• profile.thirdPartyId

• profile.categoryAffinity

• profile.categoryAffinities

For more information, see Response Tokens.

• You can create activity-only audiences from within the three-step guided workflow when creating an activity. This audience can be used in other places within the same activity, but is not stored in the Audiences Library for use in other activities. (TGT-25474)

  

  For more information, see Creating an Activity-Only Audience.

• For all activities, you can choose a success metric that qualifies the user for the audience. In the past, Target qualified users for an audience when they entered the activity, whereas now you can choose when to evaluate the audience by choosing a success metric. (TGT-15805)

  

For more information, see Apply a Reporting Audience to a Success Metric.

• Auto-Target activities now support segment-level reporting. (TGT-22777)

  For more information, see Auto-Target For Personalized Experiences.

• You can change the Control percentage for Auto-Target activities. (TGT-26467)

  

  For more information, see Auto-Target For Personalized Experiences.

• 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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

You can now use latitude and longitude in geo-targeting. (TGT-12129)

For more information, see Geo.

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)

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.

Create separate workspaces in Target and then assign users different roles and permissions for individual digital properties.

For more information, see Enterprise User Permissions.

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.

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 .

Response tokens let you automatically output eligible variables (e.g., profile attributes) in the Target responses that deliver activities (i.e. display mboxes). Response tokens can be used for debugging purposes or for integration with 3rd-party providers (such as Clicktale).

Response tokens are similar to Adobe Target Classic server plug-ins and provide feature parity between the two solutions.

Note: Response tokens are available with at.js 1.1 or later..

For more information, see Response Tokens.

Auto-Target in now available to all Target Premium customers.

Auto-Target uses advanced machine learning to identify multiple high performing marketer-defined experiences, and serves the most tailored experience to each visitor based on their individual customer profile and the behavior of previous visitors with similar profiles, in order to personalize content and drive conversions.

While creating an A/B activity using the three-step guided workflow, you can choose to allocate traffic using the Auto-Target For Personalized Experiences option:

For more information, see Auto-Target For Personalized Experiences.

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.

Previously, Target allowed dependency on a single metric and that metric had to be reached before its count incremented. You can now provide dependency on multiple metrics along with the flexibility to choose whether the metric should be reached or not reached for the count to increment.

Multiple-metric dependency functionality is not supported for the following:

• Recommendations activities. This functionality is supported for all other activity types.

• If you use Analytics as your reporting source (A4T).

• The "Viewed a Page" metric type.

• The "Clicked an Element" metric type for Visual Experience Composer (VEC) activities.

For more information, see the following topics:

• A/B: Goals and Settings

• Automated Personalization (AP): Creating an Automated Personalization Activity

• Experience Targeting (XT): Goals and Settings

• Multivariate (MVT): Goals and Settings

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.

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.

The Activity list now lets you filter on Auto Allocate and Auto Target activity types.

For more information, see Activities.

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.

• Automated Personalization activities can be created using the form-based composer.
• New confidence numbers for Automated Personalization

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.

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.

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.

(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.

View Multiple Goals/Metrics: You can now view multiple metrics in A/B and Experience Targeting (XT) activities, with the exception of Auto-Allocateand Auto-TargetA/B activities.

For more information, see View Multiple Metrics in a Report.

at.js version 0.9.6 is now available. For more information, see Download at.js.

The following enhancements and fixes are included in at.js version 0.9.6:

• Redirect offer support for A4T. After you download and install at.js version 0.9.6, you can use redirect offers in activities that use Adobe Analytics as the Reporting Source for Target (A4T). Besides at.js version 0.9.6, there are other minimum requirements your implementation must meet in order to use redirect offers and A4T. For more information and additional important information you should know, see Redirect Offers - A4T FAQ.

• Prior to at.js 0.9.6, when the Visitor API was present on the page and the visitorApiTimeout setting was too aggressive, Target could run into a situation when no MCID data was sent in the Target request. This could lead to issues like unstitched hits in Analytics when using A4T.

  This behavior has been changed in at.js 0.9.6, even if the visitorApiTimeout is set to say 1 ms, Target will try to collect SDID, tracking servers, and customer IDs data and send those in the Target request.

• Added the selectorsPollingTimeout setting. For more information, see targetGlobalSettings().

• The format of the response from getOffer() has been changed. For more information, see adobe.target.getOffer(options).

• Console logging has been added for unsupported <!DOCTYPE> declarations.

• Fixed an issue where Target Classic plugins weren't being applied correctly when multiple default offers were delivered to a single mbox. (TGT-22664)

• Improved cookie-setting for two letter top-level-domains (TLDs) to ensure that the mbox cookie is set correctly for these domains (for example, test.no , autodrives.ca , and so forth).

• The algorithm for extracting the top-level domain that should be used when saving cookies has changed in at.js version 0.9.6. Because of this change, cookies cannot be saved to addresses that use IP. Most of the time, IP addresses are used for testing purposes, but as workarounds you can use DNS entries or adjust the hosts file on a local box.

• Fixed move and rearrange actions handling when properties are string values instead of integers.

For information about this and previous versions of at.js , see at.js Version Details.

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.

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.

Dynamic Promotions: Target Recommendations now supports dynamic matches for promotions.

For more information, see Use Dynamic and Static Inclusion Rules.

January 18, 2017

at.js version 0.9.4 contains the following changes:

• mbox names can now contain special characters, including ampersands ( & ). (TNT-26144)

  For more information, see at.js Configurations.

• Added secureOnly setting that indicates whether at.js should use HTTPS only or be allowed to switch between HTTP and HTTPS based on the page protocol. This is an advanced setting that defaults to False and can be overridden via targetGlobalSettings . (TNT-26183)

  For more information, see targetGlobalSettings().

• The Legacy Browser Support option is available in at.js version 0.9.3 and earlier. This option was removed in at.js version 0.9.4.

  For more information, see at.js Configurations.

For detailed information about the changes in each version of at.js , see at.js Version Details.

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 Settingsand 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.

The following enhancements are now available for Target activities:

• Activities created in Adobe Mobile Services now display within the Target Standard/Premium user interface. (TGT-10806)

  For more information, see Activities.

• When creating multivariate tests, you can now exclude more than 10 percent of experiences from the test, provided you acknowledge the warning that you must then use offline reporting for analysis. (TGT-21719)

  For more information, see Preview Experiences for a Multivariate Test.

• The Campaign ID is now visible on each activity's Overview page. This is useful for API and troubleshooting operations. (TGT-20928)

• The design for the Collisions and Change Log pages have been improved.

• The maximum allowed length of anonymous offer names in Automated Personalization (AP) activities has been increased from 30 to 250 characters.

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.

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.

Updated the IP addresses for the Enhanced Visual Experience Composer (VEC).

If you allowlist IP addresses used for the VEC, add the new IP addresses.

For more information, see Troubleshooting the Visual Experience Composer.

We've now made it easier to determine a winner in an Auto-Allocate A/B activity.

Many marketers make the mistake of prematurely declaring a winning experience before the results indicate the clear winner.

When using the Automated Traffic Allocation feature, Target displays a badge at the top of the activity's page indicating "No Winner Yet" until the activity reaches the minimum number of conversions with sufficient confidence. When a clear winner is declared, Target displays "Winner: Experience X."

For more information, see Automated Traffic Allocationand Determine a Winner.

Note: Auto-Allocate A/B activities are no longer supported in Analytics for Target (A4T) going forward. With this release, any active Auto-Allocate A/B activities with A4T enabled will be switched to Manual mode (equal traffic allocation).

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.

Enable advanced Target debugging tools by creating a temporary authentication token.

Click Generate Authentication Token on the Implementation Details page ( Administration > Implementation ). You can then add the resulting parameter to your web page URLs for troubleshooting purposes.

For more information, see "Retrieve the Authorization Token to Use With Debugging Tools" in Troubleshooting Content Delivery.

Use sets of up to five pre-created criteria in a single experience for greater control over the recommendations presented to visitors.

For more information, see Create Criteria Sequences.

Add promoted items and control their placement in your Recommendations designs.

For more information, see Adding Promotions.

First Look

Auto-targeting in A/B activities

Note: This "First Look" offering is enabled for a few customers in this release for testing and feedback.

Automatically target experiences in A/B tests to serve the right experience to the right visitor.

For more information, see Auto-Target For Personalized Experiences.

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.

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.

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.

Search functionality on the Content page now includes saved folders, called smart collections, to save time when performing similar searches.

For more information, see Search Content and Create Smart Collections.

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.

September 21, 2016

at.js version 0.9.2 is available.

• Added an optoutEnabled setting to enable or disable the Device Graph opt-out. If this setting is set to true and the visitor has opted out of tracking, the visitor's browser will not make any mbox calls. Device Graph is currently in Beta. This setting is set to false by default, but must be set to true if you are using Device Graph.

• Added CustomEvent support for the notification mechanism. Previously, the at.js event notification mechanism could not be used via standard DOM APIs, such as document.addEventListener() . Now you can use document.addEventListener() to subscribe to at.js events, such as request events and content rendering events.

• Fixed an issue related to offers created in the Visual Experience Composer (VEC). Prior to this release, Target hid the selectors and un-hid them only when all selectors matched. In at.js 0.9.2 Target un-hides the selectors as soon as they are matched.

For more information, see at.js Version Details.

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.

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.

Search functionality on the Content page now includes saved folders, called smart collections, to save time when performing similar searches.

For more information, see Search Content and Create Smart Collections.

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.

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.

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 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.

The code editor UI has been updated to be more intuitive and easier to use.

For more information, see Code Editor.

July 14, 2016

at.js version 0.9.1 is now available.

For more information, see at.js Version Details.

You can now set activity priority levels from 0-999 to allow for finer control over which activity displays if multiple activities are assigned to the same location with the same audience.

This option must be enabled in Administration > Reporting .

The Fine-grained priorities option applies to A/B Test, Automated Personalization, Experience Targeting, and Multivariate Test activities.

For more information, see the following topics:

• A/B Test: Goals and Settings
• Automated Personalization: Automated Personalization
• Experience Targeting: Goals and Settings
• Multivariate Test: Goals and Settings
• Activities: Activity Settings

All custom Recommendations attributes can now contain multiple entity values.

For more information, see Custom Entity Attributes.

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.

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.

Element selectors can now be based on classes or IDs in Automated Personalization and Multivariate Test activities. In previous versions, this option was only available for A/B Test activities.

For more information, see Element Selectors Used in the Visual Experience Composer.

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.

Versions targeted to different audiences can now be set up within experiences in A/B activities.

See Target an Experience to Multiple Audiences.

Custom algorithm mappings can be uploaded in a CSV file. It is no longer required to use the XML-based API.

See Uploading Custom Criteria.

To ensure proper reporting tracking, you must specify a tracking server when you create or edit activities that use Analytics for Target (A4T). Existing activities will continue to run using current settings.

See Using an Analytics Tracking Server.

The following instructional videos have been added to help:

• Using DTM to pass parameters to the global mbox
• Using DTM to deploy Target
• Setting up a multivariate test
• Creating an A/B activity
• Understanding activity types
• Configuring activity settings
• Targeting an activity
• Creating audiences
• Using audiences
• Using the Content Library
• Using profile scripts
• Setting account preferences
• Understanding Visual Experience Composer modes
• Creating and managing Target users
• Setting success metrics

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:

img-md
w-400

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.

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.

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.

Previously, customer attributes could be referenced in profile scripts, formatted as crs.get('< Datasource Name >.< Attribute name >') .

Now, the attributes are available as tokens in profile scripts and directly in offers without first requiring a profile script. The token should be in the form: $crs. datasourceName . attributeName .

See CRS Tokens.

First Look:

New Target implementation library, at.js

Note: This "First Look" offering is available via API download. It will be available via the Target interface in an upcoming release. In the meantime, you can download the at.js library, test it in your environment, and deploy it in your production Target implementation.

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

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

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

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

• Visual Experience Composer redirects do not work.
• Internet Explorer versions earlier than 8 are not supported.
• Asynchronous implementation means legacy integrations like the Test&Target to SiteCatalyst plugin may not work.

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.

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 Allocationfor documentation about Auto-Allocate.

The Activities list and Audience list design have been improved, as has the search/sort functionality. Additional user interface changes will be included in upcoming releases.

See Activities.

Use nested AND/OR logic when configuring audiences.

See Creating an Audience.

Host groups are available in reports.

Note: This option is not available for Automated Personalization.

Internet Explorer 11 is now supported in the Target interface.

See Supported Browsers.

Display the Confidence Interval Range for the revenue metric type (RPV, AOV, Sales, Orders), and for engagement metrics.

For example, if RPV = 200.00 and CI Range = 50.00 , then this should be displayed for RPV: 200.00 +/- 50.00

This change applies to A/B, Experience Targeting, and Multivariate tests.

See Confidence Level and Confidence Interval.

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.

This new algorithm focuses on long-term conversion across many sessions instead of focusing on improving conversion just in this session. This technique is suitable for sites with many returning visitors because it optimizes on overall revenue for the entire interaction with the visitor.

See Automated Personalization.

You can now target on the part of a URL that follows a hash (#).

See Include the Same Experience on Similar Pagesand other relevant topics.

Download a single csv file with all success metric listed, instead of a report that only had the final activity goal.

See Reports.

You now have the option to automatically allocate traffic to increase overall campaign lift and discover winning experiences faster. This algorithm increases the overall campaign performance while maintaining the integrity of an A/B test.

The algorithm relies on measured performance (e.g. conversion rate) and confidence intervals to produce a traffic distribution that is changed up to twice per hour.

Key Benefits

• Preserves the integrity of an A/B test by ensuring that visitors remain in the same experience, like they do in a manual A/B test
• Finds a statistically significant winner faster than a manual A/B test
• Provides higher average campaign lift than a manual A/B test
• Allows you to toggle to a manual test at any time

See Automated Traffic Allocation.

Upload 1st party data, called Customer Attributes, using the Experience Cloud core service and choose attributes to share to Target. This functionality launched in March for Analytics and now integrates directly with Target.

For example, you might use customer data such as membership status (gold, silver, etc.), purchase history, favorite destination, local store, and so on in your CRM or eCommerce/POS system. Now you can upload that data to Experience Cloud. After the user authenticates on your site, Target can match that data to their web behavior.

See Customer Attributes.

There are new built-in audience options:

• Target visitors based on which language they use on their browser. This is more accurate than geo-based language targeting.
• Target visitors based on browser version, not just which browser is being used.
• You can now Target multiple browsers rather than only one.

See Browser Options.

Recommendations

Exclude Past Purchases

Target now automatically excludes previously purchased items from a visitor's recommendations. This option can be disabled for any criteria.

All out-of-the-box criteria now have this option enabled, including those used in activities that were running prior to this release. If you do not want to exclude past purchases, you should edit those activities.

Recommendations

Attribute Weighing

Recommendations ranking rules have changed for criteria. This change affects existing Recommendations.

Use attribute weighting to "nudge" the algorithm. Marketers can influence the algorithm based on important description or metadata about the content catalog. Apply a higher weighting to these on-sale items so they show more often in the recommendation. Non-sale items are not completely excluded, but they display less often. Multiple weightings can be applied to the same algorithm, and the weightings can be tested on split traffic in the recommendation.

These new weights have automatically been applied to all activities.

Recommendations

Set the Time for Feed Processing

Specify the time when you want a feed to update.

See Create Feed.

Recommendations

Use the Feed List to Set a Feed to Never Run

From the feed list, set a feed to never run if you do not want to update that feed.

See Create Feed.

Recommendations

Set a New Criteria Type Based on Content Similarity

An item-based criteria that can be used for the following:

• Current items with similar attributes
• Last purchased item with similar attributes
• Custom attributes that match a specified entity.id and use items with similar attributes
• Last viewed item with similar attributes
• Most viewed item with similar attributes

Several filters have been added to help you show the activities you are most interested in seeing in the Activities list.

See Activities.

Recommendations

Enhancement: Industry-Relevant Criteria Configuration

Recommendations

New Out-of-the-Box Criteria

• More Videos Like This
• More Articles Like This
• More Content Like This
• More Slideshows Like This
• More Products Like This

See Criteria.

View your site as it looks on various mobile devices and different screen sizes. Set responsive site breakpoints once and use them across your activities to make sure your optimization activities look great on all the devices your visitors use.

See Mobile Viewports for Responsive Experiences.

Apply targeting to your mbox locations to limit where your activity displays.

See Form-Based Experience Composer.

A color picker enables you to set background colors when editing Automated Personalization and Multivariate Test activities.

This feature was previously only available for A/B and Experience Targeting activities.

See Visual Experience Composer Options.

Text and HTML formatting in a word processor-like window when editing Automated Personalization and Multivariate Test activities.

This feature was previously only available for A/B and Experience Targeting activities.

These actions provide rich-text editing capabilities by adding HTML tags or applying styles. These modifications by the rich-text editor for any action can be seen in its source view. Users can press the HTML button in the rich-text editor to see the source view. The styles added by the rich-text editor can interfere with customer websites' styles. In this case, users can go to the source view and edit the modifications to align them with their websites' styles.

See Visual Experience Composer Options.

Recommendations

Form-based recommendations

Create recommendations activities for non-site locations including emails, consoles, kiosks, etc.

See Form-Based Experience Composer.

Recommendations

Display information about the key in the design

Automated Personalization

Conversion-based report

If the optimization goal is a conversion metric, then the Offer Detail report now shows the impact of the top predictive variables in lift and incremental conversions. This report was only revenue-based before, so this ability ensures that activities with no revenue data still produce relevant and actionable insights.

See Automated Personalization Reports.

Support for the redirect offers functionality of Target Classic added in Target Standard form-based activity creation flow.

See Form-Based Experience Composer.

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.

Profile scripts run profile attribute "catchers" on each mbox request. When an mbox request is received, Target runs any relevant profile scripts, determines which activity should run, and displays content that is appropriate to that activity and that experience, then tracks the success of the activity. This enables you to track information about the visit, such as the visitor's location, time of day, number of times that visitor has been to the site, if they've purchased before and so on. This information is then added to the visitor's profile so you can better track that visitor's activity on your site.

See Profile Attributes.

Updated reports using Target-based data show the confidence interval of the lift, compared to the control.

See Confidence Level and Confidence Interval.

Download data in a .csv format for quick import into Excel or other data analysis programs. This feature works for A/B, Experience Targeting, and Multivariate activities.

See Downloading Reports.

Text formatting options are available when editing text and HTML for A/B and Experience Targeting activities in the Visual Experience Composer. You can choose a font, select a font style, change text alignment, and other standard text formatting options. When modifying HTML, you can toggle between the code view and rich-editing view of the HTML.

See Visual Experience Composer Options.

A color picker enables you to set background colors when editing A/B and Experience Targeting activities in the Visual Experience Composer. This option is not available if a background image is set.

See Visual Experience Composer Options.

Send an activity to the archive. You can approve an archived activity to make it active again. Activities in the archive do not display by default in the Activities list.

See Activities.

Automated Personalization

Offer-level targeting

Allows marketers to apply targeting rules to offers in Automated Personalization. Makes it possible to exclude specific offers from being shown to a specified group of people.

See Target AP Offers.

Recommendations Premium

Show number of activities using design

Recommendations Premium

Customized dynamic title displays in design

Recommendations Premium

API Token

You can now target multiple mobile devices without requiring a profile script.

See Mobile.

The change log lists changes made to an activity. The action and the user are listed with a timestamp for each change.

See Activity Change Log.

A multipage activity enables you to create a story over multiple pages, with a design that is specific to each page.

For example, you might want to test an offer for free shipping with purchases above a certain amount. You might want that offer to appear on your landing page, a category page, and certain product pages, but you want it to be a different size and in a different location on each page type. You could display a prominent offer on your home page, then reinforce that offer with smaller offers on other relevant pages.

You can also use a multipage activity to define different layouts for your desktop and non-responsive mobile sites.

See Multipage Activity.

Create an activity without using the Visual Experience Composer. Instead, choose locations and offers through a form. With this, Target Standard activities can be delivered in emails, mobile apps, kiosks, and other places that don't work with a Visual Experience Composer.

See Form-Based Experience Composer.

Fine-grained options let you determine how to count success metrics. Options include counting the metric per impression or once per visitor, and choosing whether to keep the user in the activity or removing them. This is equivalent to the "advanced options" for success metrics available in Target Classic.

See Success Metrics.

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.

You will now see Target Classic campaigns within the Target Standard Activities list. If you want to filter out Target Classic campaigns and only view Target Standard you can use the "Source" search filter option. For example, to view only Adobe Target Standard activities select the source filter and type "Adobe Target" as the source. The ability to view activities created in Recommendations Classic or Adobe Mobile Services will be added in a future release.

You can activate and deactivate activities created in other solutions using the Target user interface. For all other changes you will be need to edit the activities in the source solution.

For activities created in other solutions, audience information is not visible on the Overview page. View the audience information in the solution where the activity was created.

See Activities.

Enables you to see, edit, and add new actions using a code editor within the Visual Experience Composer.

See Code Editorfor more information.

Add JavaScript code to your page(s) right below the <body> tag, without requiring the selection of an element on your page.

See Code Editorfor more information.

You can now target by the following (located in the Geo section when creating an audience):

• ISP
• Network domain
• Connection speed (options are: broadband, dialup, mobile, t1, t3, satellite)

See Audiences.

• 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

• Improvements to design preview in VEC

• Layout improvements on out-of-the-box designs

• Collection shown in targeting diagram

• Partial template rendering

  See Content Settings.

• Specify backup rules per criteria

• Support FTPS for product feeds

• Custom algorithms now appear automatically as criteria

• Hourly automatic reindexing of product catalogs for customers without feeds

You can now preview how your experiences will look when delivered. View and share links to your AP experiences on your site to get a "true preview" of the experiences outside of Target's Visual Experience Composer.

See Automated Personalization.

You will now see Target Classic campaigns within the Target Standard Activities list. If you want to filter out Target Classic campaigns and only view Target Standard you can use the "Source" search filter option. For example, to view only Adobe Target Standard activities select the source filter and type "Adobe Target" as the source. The ability to view activities created in Recommendations Classic or Adobe Mobile Services will be added in a future release.

See Activities.

Content that only appears on hover, such as flyout menus and mini-carts, is now selectable for editing in the Visual Experience Composer.

See Experiences.

The Traffic Estimator, formerly available only in the Multivariate Test activity type, is now available for Automated Personalization activities.

See Estimate the Traffic Required for Success.

Visually preview every content combination inside the Visual Experience Composer.

See Preview Experiences for an Automated Personalization Test.

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.

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.

A full-factorial multivariate test compares all possible combinations of offers in your content areas to help you determine the best possible combination of content. Multivariate tests also show which content in which areas most contributes to activity success. A common use of multivariate tests is to optimize an entire page after you've used an A/B test to determine an optimal layout. With the multivariate test, you can optimize the individual assets on the page (such as the main image, headlines, or promotional content).

For an introductory video, see https://my.adobeconnect.com/p2k6u8iiu6l/.

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 Experiencesfor more information.

You can select mobile device options when creating an audience.

See Audiencesfor more information.

Examine details about your Target page implementation and activity/experience delivery status for improved troubleshooting.

See Troubleshooting Content Deliveryfor more information.

Automated Personalization provides advanced machine learning algorithms to drive personalized experiences and improved conversion rates for digital experiences.

Note: Automated Personalization is available as part of the Target Premium solution. It is not included with Target Standard without a Target Premium license. If you have a Target Standard or Target Premium license, use the Target card in the Adobe Experience Cloud.

Implement one file on your site and to enable the ability to point and click on any content and then visually create and select additional content options for that area. Then, the modeling system automatically determines which piece of content to deliver to each individual based on all behavioral data the system has about the visitor. This ability provides a personalized experience for each visitor. The marketer does not need to run a test, then analyze the results, then deliver a winner before realizing the lift found from optimization.

Automated Personalization provides:

• Two machine-learning algorithms:

  • Random Forest
  • Residual Variance Model

• Single line of code implementation with WYSIWYG content editing

• Primary goal for the activity currently uses the Conversion metric. Revenue and engagement are available as additional metrics.

• Connection to the Master Marketing Profile for seamless collection of advance visitor behavioral data

See Automated Personalization.

Content from multiple Target Standard activities can be delivered on one page from one Target server call.

Note: This does not affect the Target Classic priorities evaluation.

For information about how Target determines which experience to show when multiple activities target the same location on a page, see Priority.

Adobe Analytics customers can select Analytics as the default reporting source during the test set-up process. Selecting all success metrics or audiences you want to use to filter your results is no longer required. Within reporting, you can select any success metric or audience segment defined in Analytics and retroactively apply it to your reporting for extensive filtering and drill-down analysis of your optimization results.

Note: To request access to this feature, visit https://survey.adobe.com/jfe/form/SV_ekBHTLSoP5Zki2y.

Leverage the master marketing profile that unifies visitor IDs and data into a single, actionable profile for use across solutions. A checkbox during the segment creation process in Adobe Analytics allows the segment to be available within the Adobe Target's custom audience library. A segment created in Analytics or Audience Manager can be used to target visitors in Target.

Note: To request access to this feature, visit https://survey.adobe.com/jfe/form/SV_ekBHTLSoP5Zki2y.

Target different experiences to different audiences in one activity.

Note: This provides similar functionality to the Landing Page campaign in Target Advanced.

Target Standard now provides a list of activity collisions. An activity collision occurs when multiple activities are set up to deliver content to the same page. If an activity collision occurs, you may not see the expected content on your page because you've entered a different activity.

All activities on the same URL are listed, regardless of any audience targeting in each activity.

If your activity contains collisions, a Collisions tab is available the on the activity overview page. Open this tab for a list of activities that are colliding. Click an activity in the list to view the overview page for that activity.

See Activity Collisions.

You can now add any kind of element to your page in addition to modifying existing content. Add text, code, lists, and more to create entirely different experiences to test.

See Visual Experience Composer Options.

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.

You can undo changes you make to your activities during an editing session. You can also redo undone changes.

See Visual Experience Composer Options.

You can move elements on your page. Unlike Rearrange Elements, Move does not shift other elements to make room for the element being moved. Use your arrow keys to fine tune the move.

See Visual Experience Composer Options.

You can resize an element on your page. When you select Resize, a handle appears in a corner of the element that lets you drag that corner to resize.

See Visual Experience Composer Options.

When creating an audience, you can select a location (mbox) and specify parameters for that location.

See Creating a New Audience.