SDKs
- Topics:
- APIs/SDKs
CREATED FOR:
- Developer
Adobe Target offers server-side SDKs to interact with the Target Delivery API and help ease the Target integration with other Adobe Experience Cloud solutions such as Adobe Analytics and Adobe Audience Manager.
The SDKs help you to follow best practices in managing sessions and cookies. It is highly recommended to leverage an SDK to smooth away any complexities and prevent incorrect utilization of the API.
Node.js SDK
For more information, see Node.js SDK overview.
The Node.js SDK is open sourced and maintained within Github, where you can find the documentation and usage instructions.
Read the changelog for the Node.js SDK.
Java SDK
For more information, see Java SDK overview.
The Java SDK is open sourced and maintained within Github, where you can find the documentation and usage instructions.
Read the changelog for the Java SDK.
.NET SDK
For more information, see .Net SDK overview.
The .NET SDK is open sourced and maintained within Github, where you can find the documentation and usage instructions.
Information about .NET SDK Releases
Python SDK
For more information, see Python SDK.
The Python SDK is open sourced and maintained within Github, where you can find the documentation and usage instructions.
Read the Changelog for the Python SDK.
Target
- 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