2017 releases

Target Platform (November 8, 2017)

This release includes the following features and enhancements:

Feature Description

at.js

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

  • Fixed an issue that returned a JavaScript error when the Target library loaded on a page using QUIRKS mode. (TNT-28312)

  • Fixed an issue that caused Target click tracking to break Analytics data collection calls. (TNT-28261)

  • Fixed an issue that caused getOffer() params to fail when targetPageParams() returns an empty string. (TNT-28359)

  • Fixed an issue with session ID generation when using x-only. (TNT-28361)

The default timeout for at.js is changed from 15 seconds to 5 seconds.

If your current setting was 15 seconds, it will be updated to the new default of 5 seconds. If you previously changed it to something different, your setting will not be affected.

mbox.js

The default timeout for mbox.js changed from 15 seconds to 5 seconds.

If your current setting was 15 seconds, it will be updated to the new default of 5 seconds. If you previously changed it to something different, your setting will not be affected.

Target Standard/Premium 17.11.1 (November 8, 2017)

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

Feature Description

Offers

If a user has the "Editor" permission, that user cannot edit an offer referenced to a live or scheduled activity.

Note: For Target Premium customers using Enterprise User Permissions, if a user selects the All Workspaces option, Target uses the highest permission of the user across workspaces. If the highest permission is "Editor," Target restricts editing as mentioned above
.

These restrictions apply to all offers, not just offers created in Target. (TGT-27276)

Response tokens

Added the following built-in parameters:

  • profile.tntId

  • profile.marketingCloudVisitorId

  • profile.thirdPartyId

  • profile.categoryAffinity

  • profile.categoryAffinities

For more information, see Response tokens.

Target Standard/Premium 17.10.1 (October 25, 2017)

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

Feature Description

Audiences

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

    For more information, see Create an activity-only audience.

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

For more information, see Apply a reporting audience to a success metric.

Auto-Target

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

    For more information, see Auto-Target.

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

    For more information, see Auto-Target.

Offers

  • You can now view offer definition details on a pop-up card in the Offers Library without opening the offer. (TGT-26377)

    For more information, see Offers.

  • You can copy and edit offers and folders in the Offer selector while creating an activity. (TGT-26936)

    For more information, see Offers.

Form-based Experience Composer

In the Form-based Experience Composer, Refinements have been replaced with full audience functionality. Refinements for existing activities have been migrated to activity-only audiences. (TGT-13646)

For more information, see Form-Based Experience Composer.

Response Tokens

You can now create response tokens from Target without waiting for them to be created in or imported to Target. Previously, in the Response Token UI, you could see only the tokens created via API. Changes to the feature also help you avoid response tokens duplicates. (TGT-26534)

For more information, see Response tokens.

Enhancements, Fixes, and Changes

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

  • You can delete imported audiences (Target Classic, Experience Cloud, etc.) from the Audience Library. Target warns you if you try to delete an audience used for an active activity. (TGT-25171)

  • Audiences imported from Target Classic are now labeled as Adobe Target Classic in the Audience Library. In the past, the UI did not differentiate between Target Standard/Premium and Target Classic. (TGT-27093)

  • Collections now apply to all criteria (including recently viewed items). (TGT-26646)

  • You can filter by Workspace in the Audience Library and Offer Library (applies to Target Premium users with Enterprise User Permissions). (TGT-26813)

  • Made improvements in the Reports UI for better scrolling in tables and placements of filter drop-down lists. (TGT-23713 & TGT-26819)

Target Platform Changes (October 13, 2017)

Change Details

at.js

October 13, 2017

at.js version 1.2.1 is now available. For more information, see at.js version details.

  • Fixed an issue when click tracking on a link with target="_blank" prevented Target from opening the link in a new tab.

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

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

Feature Description

Mobile Experience Preview

Updated: October 12, 2017

You can now select multiple mobile app activities from the UI and preview them on your device. This feature will allow you to enroll yourself into multiple experiences for previewing and QA without relying on special test builds and simulators.

This feature requires that you download and install the appropriate 4.14 (or later) version of the Adobe Mobile SDK.

For more information, see Target mobile preview.

Mobile Batch and Prefetch Delivery

Updated: October 12, 2017

Content for multiple mboxes can be pre-fetched in a single call and cached locally on the device without worrying how, when, and if the end user will see the content.

This feature requires that you download and install the appropriate 4.14 (or later) version of the Adobe Mobile SDK.

For more information, see Prefetch offer content.

Activities

The following enhancements have been made in the activity-creation workflow:

  • While editing an activity, you can make the desired changes on the currently displayed step, click the drop-down on the split button, then select Next to advance to the next step, click Save and Close to save your changes and display the activity's Overview page, or click Save to save your changes and remain on that step.

    For more information, see Edit an activity or save as draft.

  • While editing an activity, you can open the desired workflow step, make your changes (for example experience percentages, audiences, and so forth), then save or close the activity without having to advance through the three-step guided workflow.

    For more information, see Edit an activity or save as draft.

  • When you are creating a new activity that has not yet been saved, or you are editing an activity that was previously saved in draft form, the Save Draft options display in the split button.

    For more information, see Edit an activity or save as draft.

  • You can now edit or copy an audience by hovering over the desired audience in the Choose Audience dialog box while choosing targeting in step 2 of the three-step guided workflow.

For more information, see Select audience.

Reporting

The following new features and enhancements are available for reporting:

Audiences

You can now view the definitions of audiences imported from Target Classic or created via API. (TGT-22630)

For more information, see "Viewing Audience Definitions" in About audiences.

Code Editor

The Form-based Experience Composer and the HTML offers editor now use the same code editor that the Visual Experience Composer (VEC) uses in custom code. (TGT-25808)

This enhancement gives you the following features when using the code editor in the Form-based Experience Composer and when creating HTML offers:

  • Line numbers are now visible for better usability.

  • Syntax highlighting helps you avoid incorrect syntax for HTML offers.

For more information, see Modifications.

Geo Targeting

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

For more information, see Geo.

Node.JS SDK

You can install the node.js SDK from npm @adobe/target-node-client to easily implement and run server-side tests on your node.js applications. The VisitorID service is enabled in the node SDK to connect all your Adobe data and you can use choose to use Adobe Analytics as your reporting source (A4T).

Enhancements, Fixes, and Changes

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

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

    For more information, see Profile API settings.

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

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

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

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

Target Platform Changes (September 27, 2017)

Change Details

at.js

September 27, 2017

at.js version 1.2.0 is now available as a maintenance release that contains mostly bug fixes. For more information, see at.js version details.

  • Fixed an issue that prevented default actions for click-tracking special cases. (TNT-28089)

  • Fixed an issue when click-tracking on a link with target="_blank" that prevented Target from opening the link in a new tab. (TNT-28072)

  • IP addresses can be used as the cookie domain. (TNT-28002)

  • Fixed an issue that caused flicker in redirect offers with a global mbox or other regional mboxes. (TNT-27978)

  • Fixed an issue in Experience Targeting activity setup failing within the VEC when switching between Browse and Compose. (TNT-27942)

  • Fixed incorrect handling on flicker style classes for click-track elements. (TNT-27896)

  • Fixed an issue that caused global mbox parameters to become mixed up with all mbox parameters. (TNT-27846)

  • Made changes to ensure that Handlebars, Mustache, and other client-side templating libraries are properly handled by at.js. (TNT-27831)

  • Made changes to ensure that sdidParamExpiry is properly initialized and passed to the Visitor API. This is a regression that has been added to at.js 1.1.0. Previous at.js versions are not affected. This affects only clients using redirect offers and A4T. (TNT-27791)

  • Made changes to ensure that SCRIPT is executed regardless of the type attribute being used. (TNT-27865)

Experience Targeting (XT)

September 21, 2017

With the release on September 21, Target will change the way users are placed into experiences in Experience Targeting (XT) activities (Landing Page campaigns in Target Classic). For all new and existing activities in both Target Standard/Premium and Target Classic, users must meet the experience targeting rules on every impression to continue to see the experience's content and to be counted in reports. Previously, if the user no longer qualified for any experience, the user would continue to see the content from, and be counted in reports for, the last experience they did qualify for.

This change will happen automatically as part of the release for all existing activities and for any new activities created post-release. If the previous method (prior to September 21) is desired, you can create audiences using profile scripts so a user only must meet a condition once to continue to fall into that audience in the future. Then, use those audiences for each experience in the activity.

Target Standard/Premium 17.8.1 (August 22, 2017)

Feature Description

Enterprise User Permissions for Target Premium

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

For more information, see Enterprise user permissions.

See Known issues and resolved issues for more information about the rollout.

QA Mode

Perform easy activity QA with preview links that never change, optional audience targeting, and QA reporting that stays segmented from live activity data.

For more information, see Activity QA.

Enhancements, Fixes, and Changes

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

  • We've added more places where you can view audience definition details on a pop-up card in the Target UI without opening the audience. Note that this functionality applies only to audiences created in Target Standard/Premium. (TGT-25772)

  • You can now view definitions of adhoc audiences inside activity creation/overview. (TGT-25570)

  • The following variables are now available as Velocity arrays: entiites and entityN.categoriesList.

Target Platform Changes (August 3, 2017)

Change Details

at.js

August 3, 2017

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

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

  • Added response token handling. For more information, see Response tokens.

  • Resolved issue so that document.currentScript polyfill doesn't interfere with Angular 1.X.

  • Made changes to ensure that click tracking doesn't interfere with visibility property. Click tracking elements are marked with the at-element-click-tracking CSS class instead of at-element-marker.

mbox.js

July 18, 2017

mbox.js version 63 is now available. For more information, see Download mbox.js.

The following enhancements and fixes are included in mbox.js version 63:

  • Fixes an issue with SDID generation when using mboxDefine() and mboxUpdate(). This affects only clients that have Visitor API on the page.

Target Standard/Premium 17.7.3 (August 3, 2017)

Feature Description

Response Tokens

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

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

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

For more information, see Response tokens.

Target Standard/Premium 17.7.2 (July 27, 2017)

Feature Description

Auto-Target

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

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

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

For more information, see Auto-Target.

Target Standard/Premium 17.7.1 (July 20, 2017)

Feature Description

Audiences

You can now view audience definition details on a pop-up card in various places in the Target UI without opening the audience. Note that this functionality applies only to audiences created in Target Standard/Premium.

Success metrics

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

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

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

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

  • The “Viewed a Page” metric type.

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

For more information, see the following topics:

Reporting (Auto-Allocate A/B Tests)

The ability to view multiple metrics is now available for Auto-Allocate A/B activities.

For more information, see View multiple metrics in a report.

Audiences

Audience site page types and comparison operators now match types and comparison operators in Target Classic.

You can now create site pages audiences using you own "user-defined query parameter" or "user-defined header."

For more information, see Site Pages.

Activities

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

For more information, see Activities.

Recommendations Criteria & Promotions

You can now handle empty values when filtering by Entity Attribute Matching, Profile Attribute Matching, and Parameter Matching.

For more information, see Use dynamic and static inclusion rules.

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

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

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

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

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

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

    • Activity Page > activity > Step3 > Report Suite picker

    • Audiences > Create Audience > Visitor Profile

    • Recommendations > Feed Creation > When source type > Analytics > Report Suite picker

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

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

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

    thirdpartyId

    startDate

    endDate

    status

    priority

    marketingCloudMetadata(remoteModifiedBy)

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

Target Platform Changes (July 18, 2017)

Change Details

mbox.js

July 18, 2017

mbox.js version 63 is now available. For more information, see Download mbox.js.

The following enhancements and fixes are included in mbox.js version 63:

  • Fixes an issue with SDID generation when using mboxDefine() and mboxUpdate(). This affects only clients that have Visitor API on the page.

at.js

July 7, 2017

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

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

  • Support for loading at.js asynchronously for faster page loads.

  • Support for pre-hiding page content when loading at.js asynchronously.

  • Better error messaging when content delivery is disabled.

  • Performance improvements when delivering multiple activities.

  • Support for YUI Compressor.

  • Bug/error reporting for custom events during activity delivery.

  • Fix for performance issues in Microsoft Internet Explorer 11.

  • Fix for getOffer() function giving an error on some websites.

  • Load the Target library asynchronously.

Target Standard/Premium 17.6.2 (June 22, 2017)

Feature Description

Automated Personalization (AP) activities

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

Recommendations: Criteria and Promotions

You can now create dynamic criteria and promotions based on profile attribute matching and parameter matching.

Note: If you are familiar with how inclusion rules were configured prior to the Target 17.6.1 release (June 2017), you'll notice that some of the options and operators have changed. Only those operators applicable to the selected option display and some operators were renamed ("matches" is now "equals") to be more consistent and intuitive. All existing exclusion rules created prior to this release were automatically migrated into the new structure. No restructuring is necessary on your part.

VEC Code Editor improvements

If the page format changes and actions cannot be applied, an alert now appears next to each failing action. Previously, a general error notified the user that the page structure had changed. Now, the code editor highlights each failed action.

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

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

Target Standard/Premium 17.6.1 (June 8, 2017)

Feature Description

Experience Targeting (XT) activities

Drag-and-drop functionality lets you arrange audiences and experiences in the desired order while creating or editing XT activities. Visitors will be evaluated for experiences in order, from top to bottom.

For more information, see Create Experience.

Reporting: A/B, XT, and Recommendations

Reports for A/B, XT, and Recommendations activities include visual representations that let you visually see the confidence interval and lift so that you can more accurately determine a winner. You can mouse over the representations to see the actual numbers. This feature is not available for activities that use Analytics as the reporting source (A4T).

For more information, see c_report-settings.html#concept_4BB6A7FDAB6F4806A632F9CD989B8BFA.

Automated Personalization (AP) activities

You can create Exclusion Groups in AP activities to ensure that experiences with the designated offers are automatically excluded.

Recommendations: Criteria and Promotions

(Scheduled to be released June 22, 2017) You can now create dynamic criteria and promotions based on profile attribute matching and parameter matching.

For more information, see Use dynamic and static inclusion rules.

Note: If you are familiar with how inclusion rules were configured prior to the Target 17.6.1 release (June 2017), you'll notice that some of the options and operators have changed. Only those operators applicable to the selected option display and some operators were renamed ("matches" is now "equals") to be more consistent and intuitive. All existing exclusion rules created prior to this release were automatically migrated into the new structure. No restructuring is necessary on your part.

Naming activities

You are now prompted to name the activity before saving. You cannot save an activity without a name.

New location for Target Forum

The Target Forum has moved to the new Adobe Community Platform.

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

  • Fixed an XSS security issue with mbox.js. This fix is a server-side fix that does not require an mbox.js update.

Target Standard/Premium 17.4.1 (April 27, 2017)

This release includes the following features and enhancements:

Feature Details
Reporting

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

For more information, see View multiple metrics in a report.

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

  • Fixed an issue that caused the "Increment Count, Release User & Allow Reentry" setting in Advanced Settings for activities to not function correctly. (TNT-26556)

  • Fixed an issue that prevented Customer Attribute data from being removed from Target after being updated with NULL in the Experience Cloud user interface. (TNT-26462)

Target Platform Changes (April 13, 2017)

Change Details

at.js

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

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

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

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

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

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

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

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

  • Fixed an issue where Target Classic plugins weren’t being applied correctly when multiple default offers were delivered to a single mbox. (TGT-22664) For more information, see Plug-Ins in the Adobe Target Classic documentation.

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

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

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

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

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

This release includes the following features and enhancements:

Feature Description

Analytics for Target (A4T)

Redirect Offers

Updated April 13, 2017.

You can now use redirect offers in activities that use Analytics as the reporting source.

Your implementation must meet the following minimum requirements:

  • Experience Cloud Visitor ID Service: visitorAPI.js version 2.1

  • Adobe Analytics: appMeasurement.js version 2.1

  • Adobe Target (depending on your implementation): at.js version 0.9.6 or mbox.js version 61

These libraries must be included on both the page with the redirect offer and the page to which the visitor is redirected. As a part of this change, new URL parameters will automatically be added to your redirect URLs if the Visitor Id service is implemented on your site, regardless of whether or not you are using Analytics as the reporting source for that activity.

For more information, see Redirect offers - A4T FAQ.

Audiences

The following enhancements have been made to audience targeting:

  • Week and Day Parting: You can set Week and Day Parting options to create recurring patterns for audience targeting.

    For more information, see Time Frame.

  • Exclusions in Combined Audiences: You can now add exclusion rules and exclude audiences when combining multiple audiences.

    For more information, see Combine multiple audiences.

Recommendations

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

For more information, see Use dynamic and static inclusion rules.

Note: The ability to view multiple metrics in a report, included in the Target 17.3.1 release (March 30, 2017) has been removed due to unexpected behavior. This feature will be available again in an upcoming release.

This Target release includes the following enhancements and fixes::

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

  • The Target user interface was updated in some places:

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

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

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

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

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

  • Automated Personalization activities now support host groups.

Target Standard/Premium 17.2.1 (February 21, 2017)

Note: Adobe Experience Manager 6.2 with FP-11577 (or later) now supports at.js implementations with its Adobe Target Cloud Services integration. For more information, see Feature Packs and Integrating with Adobe Target in the Adobe Experience Manager 6.2 documentation.

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

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

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

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

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

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

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

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

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

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

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

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

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

  • Enhanced the downloaded reports to differentiate between active and deleted offers. The following text is appended to deleted offers: [Deleted]. (TGT-22449)

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

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

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

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

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

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

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

Target Platform Changes (January 18, 2017)

Change Details

at.js version 0.9.4

January 18, 2017

at.js version 0.9.4 contains the following changes:

  • mbox names can now contain special characters, including ampersands ( & ), to be consistent with naming requirements for mbox names using mbox.js. (TNT-26144)

    For more information, see at.js Configurations.

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

    For more information, see targetGlobalSettings().

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

    For more information, see at.js Configurations.

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

mbox.js version 62

January 18, 2017

mbox.js version 62 contains the following enhancement and fixes:

  • Fixed flicker issues in redirect activities when viewed in Google Chrome browsers. (TNT-24928)

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

    For more information, see Configure mbox.js.

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

Target Standard/Premium 17.1.1 (January 19, 2017)

This release includes the following features and enhancements:

Feature Description

Content/Offers

The following enhancements are now available for offers:

  • The Content page has been renamed to Offers. In addition, there are now two tabs along the right side to separate code offers from image offers.

    If you had code and images in the same folder before this release, Target will split them into two duplicate folders.

  • Offers created via Target Classic, Adobe Experience Manager (AEM), Adobe Mobile Services (AMS), and APIs are now visible in the Target Standard/Premium user interface. Offers created in Target Classic are editable in Target Standard/Premium. (TGT-15738)

    Offers updated in the last two years using these methods will be visible in Target Standard/Premium (i.e. January 2015 and beyond).

  • You can now filter offers by source and type.

For more information, see Offers.

The following enhancement has been made to geo-location targeting:

  • You can now use profile.geolocation values directly as tokens in offers, plugins, and so forth. (TNT-25967)

For more information, see Geo.

Reporting

Note: These enhancements do not apply to Analytics for Target (A4T) reports.

The following reporting enhancements are now available for Target reports.

  • The user interface for reports has been redesigned.

  • Target reports now have an option to reset reporting data to remove old data. (TGT-5933)

  • The counting methodology options for reporting includes Visitors (the default), Visits, and Activity Impressions. (TGT-10002)

For more information, see c_report-settings.html#concept_4BB6A7FDAB6F4806A632F9CD989B8BFA and Counting Methodology.

The following reporting enhancements are now available for downloadable CSV reports:

  • The offer-level CSV report now has additional details about each offer. (TGT-18995)

  • Downloaded offer-level CSV files now always include data from control and targeted segments for Automated Personalization reports. (TGT-22000)

The following reporting enhancements are now available for Automated Personalization (AP) reports.

  • Improved reporting load time for Automated Personalization activities.

  • The confidence interval for continuous variables (Revenue and Engagement metric types) is now displayed in Automated Personalization (AP) summary reports.

Activities

The following enhancements are now available for Target activities:

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

    For more information, see Activities.

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

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

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

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

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

Audiences

The following enhancements are now available for audiences:

  • Device Marketing Name is now available as a built-in option from the drop-down list when creating audiences targeting mobile devices.

    This change lets you easily pick a device model name rather than searching for the appropriate device model number. For example, the Galaxy S7's marketing device name is "Samsung Galaxy S7 Edge," while the device model is "SM-G9350." (TGT-18393)

    For more information, see Mobile.

Recommendations

The following enhancements have been made to Recommendations:

  • The Backup Algorithm result line is now included in Top Viewed and Top Bought CSV downloads. The backup Recommendation starts with "*,"

  • Additional statuses let you know the progress of your Recommendation feeds.

    For more information, see Feeds.

Enhanced Visual Experience Composer (VEC)

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

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

For more information, see Troubleshooting the Visual Experience Composer and Enhanced Experience Composer.