- Adobe Target Guide Home
- Target release notes
- Introduction
- Introduction to Target
- Access Target from the Adobe Experience Cloud
- Target key concepts
- Understand the Target UI
- Adobe Target welcome kit
- Adobe Target welcome kit overview
- Chapter 1: Introduction
- Chapter 2: Adobe Target at a glance
- Chapter 3: Develop your testing an personalization ideas
- Chapter 4: Tips for using Target
- Chapter 5: Inspiration for testing and personalization activities
- Chapter 6: Easily avoidable pitfalls
- Chapter 7: Create and run your first Target activity
- Chapter 8: Communicate your activity results
- Chapter 9: Next steps and resources
- Glossary
- How Adobe Target works
- Training and certification
- Training videos for Adobe Target Standard and Premium
- Target optimization and personalization FAQ
- Administer Target
- Implement Target
- Implement Target overview
- Before you implement
- Client-side web: implement Target
- Overview: implement Target for client-side web
- Adobe Experience Platform Web SDK implementation
- at.js implementation
- How at.js works
- How to deploy at.js
- at.js functions
- at.js functions overview
- adobe.target.getOffer()
- adobe.target.getOffers() - at.js 2.x
- adobe.target.applyOffer()
- adobe.target.applyOffers() - at.js 2.x
- adobe.target.triggerView() - at.js 2.x
- adobe.target.trackEvent()
- mboxCreate() - at.js 1.x
- targetGlobalSettings()
- mboxDefine() and mboxUpdate() - at.js 1.x
- targetPageParams()
- targetPageParamsAll()
- registerExtension() - at.js 1.x
- sendNotifications() - at.js 2.1
- at.js custom events
- Debug at.js using the Adobe Experience Cloud Debugger
- Use cloud-based instances with Target
- at.js frequently asked questions
- at.js version details
- Upgrading from at.js 1.x to at.js 2.x
- at.js cookies
- mbox.js implementation (legacy)
- Understand the Global mbox
- Target for mobile apps
- Target for mobile apps overview
- How Target works in mobile apps
- Enable Target in the SDK
- iOS - create a Target location and success metric
- iOS - send custom user data
- Send activity information to Adobe Analytics
- Target mobile preview
- Prefetch offer content
- Target for mobile apps FAQ
- Use Location Service
- Server Side: implement Target
- Hybrid implementation
- Email: implement Target
- Integrate Adobe Target with the Experience Cloud
- Adobe Analytics as the reporting source for Adobe Target (A4T)
- A4T overview
- Before you implement
- Analytics for Target implementation
- User permission requirements
- Create an activity that uses Analytics as the reporting source
- Use an Analytics tracking server
- A4T reporting
- Troubleshooting the Analytics and Target integration (A4T)
- A4T Frequently Asked Questions
- Initial provisioning - A4T FAQ
- Activity settings - A4T FAQ
- View reports - A4T FAQ
- Redirect offers - A4T FAQ
- Lift and confidence - A4T FAQ
- Metric definitions - A4T FAQ
- Inflated visit and visitor counts - A4T FAQ
- Classifications - A4T FAQ
- Share metrics, audiences, and reports - A4T FAQ
- Legacy SiteCatalyst to Test&Target Integration - A4T FAQ
- Expected data variances between Target and Analytics when using and not using A4T
- Experience Cloud Audiences
- Integrate Target with Adobe Audience Manager
- Integrate Target with Adobe Campaign
- Experience Cloud Device Co-op
- Adobe Analytics as the reporting source for Adobe Target (A4T)
- Activities
- Activities overview
- Target activity types
- A/B Test
- Auto-Allocate
- Auto-Target
- Automated Personalization
- Automated Personalization overview
- Random Forest Algorithm
- Create an Automated Personalization activity
- Upload data for the Target personalization algorithms
- Data collection for Target’s personalization algorithms
- Estimate the Traffic Required for Success
- Preview Experiences for an Automated Personalization Test
- Target Automated Personalization offers
- Manage exclusions
- Select the control for your Automated Personalization or Auto-Target activity
- Automated Personalization FAQ
- Preview Automated Personalization activities with experience preview URLs
- Troubleshoot Automated Personalization
- Experience Targeting
- Multivariate Test
- Recommendations activity
- Edit an activity or save as draft
- Priority
- Activity settings
- Success metrics
- Activity Change Log
- Troubleshoot activities
- Activity QA
- Audiences
- Experiences and offers
- Experiences and offers overview
- Visual Experience Composer (VEC)
- Visual Experience Composer overview
- Visual Experience Composer Options
- Include the Same Experience on Similar Pages
- Multipage Activity
- Activity Collisions
- Modifications
- Element Selectors Used in the Visual Experience Composer
- Mobile Viewports for Responsive Experiences
- Visual Experience Composer Best Practices and Limitations
- Troubleshooting the Visual Experience Composer
- Troubleshooting the Visual Experience Composer overview
- Troubleshooting the Visual Experience Composer and Enhanced Experience Composer
- Troubleshooting the Visual Experience Composer
- Troubleshooting the Enhanced Experience Composer
- Enabling Mixed Content in Your Browser
- Page Modification Scenarios
- Visual Experience Composer helper extension
- Redirect to a URL
- Creating Carousels that Work in the Visual Experience Composer
- Form-Based Experience Composer
- Single Page App (SPA) Visual Experience Composer
- Offers
- Reports
- Reports overview
- Report settings
- Auto-Target Summary report
- Automated Personalization Summary reports
- Personalization Insights report
- Offer reporting groups in Automated Personalization
- Experience Performance report (MVT)
- Location Contribution report (MVT)
- Analytics for Target (A4T) reporting
- Conversion rate
- Downloading data in a CSV file
- Reporting FAQ
- Recommendations
- Recommendations overview
- Introduction to Recommendations
- Plan and implement Recommendations
- Entities
- Criteria
- Design
- Activity
- Recommendations as an offer
- Frequently asked questions
- Recommendations Classic documentation
- Troubleshoot Target
- Target APIs
- Resources and Contact Information
Target release notes (current)
These release notes provide information about features, enhancements, and fixes for each Target Standard and Target Premium release. In addition, release notes for Target APIs, SDKs, the JavaScript library (at.js), and other platform changes are also included, when applicable.
IMPORTANT
mbox.js end-of-life: On March 31, 2021, Adobe Target will no longer support the mbox.js library. Post March 31, 2021, all calls made from mbox.js will gracefully fail and impact your pages that have Target activities running by serving default content. We recommend that all customers migrate to the most recent version of the new Adobe Experience Platform Web SDK or the at.js JavaScript library before this date to avoid any potential issues with your sites.
-
Adobe Experience Platform Web SDK: The Adobe Experience Platform Web SDK lets you interact with the various services in the Experience Cloud (including Target) through the Adobe Experience Edge Network. If you choose to migrate to the Adobe Experience Platform Web SDK, see What is Adobe Experience Platform Web SDK in the Web SDK Guide.
-
at.js: The at.js JavaScript library provides many advantages over mbox.js. Among other benefits, the at.js improves page load times for web implementations, improves security, and provides better implementation options for single page applications. If you choose to migrate to at.js, see How At.js Works and Adobe Target Skill Builder: Developer chat, migrate Adobe Target’s mbox.js to at.js.
Although, mbox.js is currently supported (until March 31, 2021), we have not provided feature updates to this library since July 2017. By moving all customers to the Adobe Experience Platform Web SDK or at.js, our engineers and support staff will be able to provide you with new functionality and offer the support you have come to expect from Adobe.
(The issue numbers in parentheses are for internal Adobe use.)
Target Standard/Premium 21.1.1 (January 19, 2021)
This maintenance release contains the following enhancements, fixes, and changes.
The issue numbers in parentheses are for internal Adobe use.
- Added a warning when selecting an Adobe Analytics metric when using Analytics as the reporting source (A4T) in an Auto-Target activity. Auto-Target models are optimized to work with binary (conversion-based) metrics. Selecting a continuous metric, such as revenue, might have sub-optimal outcomes and the Personalization Insights reports might not be accurate. (TGT-38926)
- Added a status icon in the Auto-Target Summary report for Auto-Target activities that use A4T. The green check icon next to each experience in the report indicates that a personalized machine-learning model has been generated for that experience. The clock icon indicates that not enough traffic has been served to build the model. (TGT-38925)
- The Automated Segments and Important Attributes reports for Auto-Target activities that use A4T and Analytics conversion metrics are generated and look the same as when using Target as the reporting source. (TGT-38931)
- Added an environment filtering option to the Recommendations Collections list. (TGT-38353)
- Fixed an issue that caused the incorrect product count to display in Recommendations collections. (TGT-39162)
- Added a Last Updated filter to the Recommendations Catalog Search. (TGT-38340)
- Fixed an issue in Recommendations that caused the Create Sequence page to hang after changing the industry vertical. (TGT-38160)
- Fixed an issue that prevented the activity from being saved if Device Co-op was enabled and the user changed from Target as the reporting source to Analytics (A4T). (TGT-38163)
- Fixed an issue that prevented users from removing an audience from an offer in an Automated Personalization (AP) activity. (TGT-39058)
- Fixed an issue that caused the incorrect time frame (start and end dates) to display in Audience Info cards for some customers. (TGT-39150)
- Fixed an issue that prevented some customers from seeing the list of activities in the Default Workspace. (TGT-38526)
at.js 2.4.0 (January 14, 2021)
This release of at.js is a maintenance release and includes the following fixes:
- Adds support for unified profile/platform id to delivery API customerIds.
- Fixes invalid style tag injection.
Additional release notes and version details
| Resource | Details |
|---|---|
| at.js version details | Details about changes in each version of the Adobe Target at.js JavaScript library. |
Documentation Changes, Past Release Notes, and Experience Cloud Release Notes
In addition to the notes for each release, the following resources provide additional information:
| Resource | Details |
|---|---|
| Documentation changes | View detailed information about updates to this guide that might not be included in these release notes. For more information, see Documentation Changes. |
| Release notes for previous releases | View information about new features and enhancements in previous releases of Target Standard and Target Premium. For more information, see Release notes for previous releases. |
| Adobe Experience Cloud release notes | View the latest release notes for the Adobe Experience Cloud solutions. For more information, see Experience Cloud Release Notes. |
Prerelease Information
The following resources let you see what’s coming in the next Target release.
| Resource | Details |
|---|---|
| Adobe Priority Product Update list | To receive advance notifications about upcoming product enhancements to Target and other Adobe Experience Cloud solutions, sign up for the Adobe Priority Product Update: https://www.adobe.com/subscription/priority-product-update.html |
| Upcoming release notes | For information about the current month’s Target releases, including prerelease information, see the Target Release Notes - Prerelease page. |