- Adobe Target Developer Guide
- Getting started
- Before you implement
- Privacy and security
- Privacy overview
- Privacy and data protection regulations
- Target cookies
- Delete the Target cookie
- The impact of third-party cookie deprecation on Target (at.js)
- Google Chrome SameSite cookie policies
- Apple Intelligent Tracking Prevention (ITP) 2.x
- Content Security Policy (CSP) directives
- Allowlist Target edge nodes
- Methods to get data into Target
- Target security overview
- Supported browsers
- TLS (Transport Layer Security) encryption changes
- CNAME and Adobe Target
- Client-side implementation
- Overview: implement Target for client-side web
- Adobe Experience Platform Web SDK implementation overview
- at.js implementation
- at.js overview
- How at.js works
- How to deploy at.js
- On-device decisioning
- 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 FAQs
- at.js version details
- Upgrading from at.js 1.x to at.js 2.x
- at.js cookies
- User-agent and client hints
- Understand the Global mbox
- Server Side implementation
- Server Side: implement Target overview
- Getting started with Target SDKs
- Sample apps
- Transition from Target legacy APIs to Adobe I/O
- Core principles
- Integration
- On-Device Decisioning
- Node.js SDK Reference
- Java SDK Reference
- .NET SDK Reference
- Python SDK Reference
- Hybrid implementation
- Recommendations implementation
- Mobile app implementation
- Email implementation
- API guides
- Implementation patterns
Target API overview
This article describes the different Target APIs in general, before focusing on requirements specific to the Admin and Profile APIs. If you wish to administer Target via the UI, see the administration section of the Adobe Target Business User Guide.
API Types
The Adobe Target APIs are a collection of APIs that power Adobe Target products, such as Adobe Recommendations. These APIs allow for the creation of data-rich user interfaces you can use to manipulate and integrate data.
Adobe Target APIs may be grouped according to type: Admin, Profile, Delivery, and Reporting.
The Admin APIs and Profile APIs are often referred to collectively (“Admin and Profile APIs”), but may also be referred to separately (“Admin APIs” and “Profile APIs”). The Recommendations API is a specific implementation of a Target Admin API.
| API type | What it enables you to do | Download link | Other helpful links |
|---|---|---|---|
| Admin | Create, modify, and delete activities, audiences, offers, and other objects (including Recommendations entities, criteria, designs, and so on. The Recommendations APIs are a type of Admin API.) | Use Recommendations APIs | |
| Profile | Retrieve and modify user profiles stored in Adobe Target. | Target Profile API Postman Collection | |
| Delivery | Retrieve optimized and personalized content from Target for delivery to an end user. | Target Delivery API Postman Collection | |
| Reporting | Export activity results and other reporting results. | Reporting APIs are included within the Target Admin API Postman collection. | |
| Models | Manage the list of features you want Target to exclude from its machine-learning models (the “blocklist”). The Models API is a type of Admin API, but it is listed here separately due to its unique operations against objects (blocklists) not accessible through the UI. |
API Differences
There are important distinctions between Target Admin APIs (including the Recommendations APIs) and Target Delivery APIs:
-
Admin APIs let you configure various aspects of Target that you can also configure in the Target UI. The exception to this is the Models API, which lets you configure aspects of Target not available in the UI. Regardless, all Admin APIs require authentication.
-
Delivery APIs let you retrieve content. Delivery APIs do not require authentication.
To use Target Admin APIs, you must configure authentication using the Adobe Developer Console. For more information, see How to Configure Authentication.
