- 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 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
- A4T support for Auto-Allocate and Auto-Target activities
- 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
Transition from Target legacy APIs to Adobe I/O
Information to help you use transition from the Target legacy APIs to the new APIs on Adobe I/O.
With the decommissioning of Adobe Target Classic, the APIs that are connected to your Target Classic account have also been made unavailable. This document will help you transition your legacy API-based integrations to the Target APIs powered by Adobe I/O.
For more information about the Target API documentation, see Target APIs and NodeJS SDK.
Terminology
| Term | Description |
|---|---|
| Legacy API | APIs that are linked to your Target Classic account. These API calls are based on a username and password-based authentication and use the hostname testandtarget.omniture.com. If your API calls contain a user name and password in the request URL, you must transition to Adobe I/O APIs. |
| Adobe I/O | Adobe I/O is the new gateway for Target APIs. These APIs are connected to your Target Standard/Premium account. The Target APIs on Adobe I/O use a JWT-based authentication, which is the industry standard for secure enterprise APIs. |
Timeline
The legacy APIs will be decommissioned when you Target Classic is decommissioned:
| Date | Details |
|---|---|
| October 17, 2017 | All API methods that perform a write operation (saveCampaign, copyCampaign, saveHTMLOfferContent, and setCampaignState) were decommissioned.This is the same date when all Target Classic user accounts were set to read-only status. |
| November 14, 2017 | The remaining APIs were decommissioned. This is the date when the Target Classic user interface was decommissioned |
Recommendations Classic APIs won’t be impacted by this time line.
Equivalent Methods
The following table lists the equivalent new Target API methods for the legacy API methods. The new APIs return JSON when compared to the XML response provided by the legacy APIs.
The new API methods are linked to the corresponding section in the API documentation site. An example is provided for each API method. You can also use the Admin Postman Collection that contains sample API calls for all the new Adobe API methods on Adobe I/O.
| Grouping | Legacy API Method | New API Method | Notes |
|---|---|---|---|
| Campaign/Activity | Campaign Create | Create AB Activity Create XT Activity |
The new APIs provide separate create methods for AB and XT |
| Campaign Update | Update AB Activity Update XT Activity |
||
| Copy Campaign | N/A | Use the Activity Create APIs | |
| Campaign List | List Activities | ||
| Campaign State | Update Activity State | ||
| Campaign View | Get AB Activity by ID Get XT Activity by ID |
||
| Third-Party Campaign ID | N/A | If you are using a thirdpartyID, the relevant Activity methods can be used | |
| Offers | Offer Create | Create Offer | |
| Offer Get | Get Offer by ID | ||
| Offer List | List Offers | ||
| Folder List | N/A | Folders aren’t supported in Target Standard/Premium | |
| Reporting | Campaign Performance Report | Get AB Performance Report Get XT Performance Report |
|
| Audit Report | Get Audit Report | ||
| 1-1 Content Report | Get AP Performance Report | ||
| Account Settings | Get Host Groups | List Environments |
Exceptions
If you require an exception, please contact your Customer Success Manager.
Help
Please contact Adobe Target Client Care (tt-support@adobe.com) if you have any questions or need help transitioning to the new Target APIs on Adobe I/O.
On this page
