- 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
Server Side: implement Target
Information about Adobe Target server-side Delivery APIs, SDKs, and Target Recommendations APIs.
If your implementation uses at.js and AppMeasurement in client-side, you should use the Target Delivery API and server-side SDKs discussed below.
If your implementation uses the Adobe Experience Platform Web SDK, you should use the Adobe Experience Platform Edge Network Server API.
The following process occurs in a server-side implementation of Target:
- A client device makes a request for an experience through your server.
- Your server sends that request to Target.
- Target sends the response back to your server.
- Your server makes the decision on which experience to deliver to the client device for it to render.
The experience does not need to display in a browser. The experience can display in an email or kiosk, via a voice assistant, or through some other non-visual experience or non-browser-based device. Because your server sits between the client and Target, this type of implementation is also ideal if you need greater control and security or have complex backend processes that you want to run on your server.
A first-time visitor can be initialized only on the client-side. A first-time visitor cannot be initialized on the server-side. This is due to the ECID, which depends on the third-party demdex cookie and therefore needs to be initialized via Visitor API.js on an implementation where the browser is involved.
The following sections provide more information about the various server side APIs and SDKs:
Server Side Delivery APIs
Link: Server Side Delivery APIs
/rest/v1/delivery
Through the Target Delivery API, you can:
- Deliver experiences across web, including SPAs, and mobile channels as well as non-browser based IoT devices, such as connected TVs, kiosks, or in-store digital screens.
- Deliver experiences from any server-side platform or application that can make HTTP/s calls.
- Deliver consistent and personalized experiences to a visitor regardless of which channel or devices the visitor used to engage with your business.
- Cache experiences for a visitor within a session on your server so that multiple API calls can be avoided, which achieves better performance.
- Seamlessly integrate with Adobe Experience Cloud products, such as Adobe Analytics, Adobe Audience Manager (AAM), and the Experience Cloud ID Service from the server side.
Server Side SDKs
The Adobe Target server-side SDK documentation helps you implement Target on your servers in your language of choice.
Through Adobe Target’s server-side SDKs, you can:
- Execute and run feature flagging, rollouts, and A/B experiments at near-zero latency.
- Deliver experiences across web, including SPAs, and mobile channels, as well as non-browser based Internet of Things (IoT) devices such as a connected TV, kiosk, or in-store digital screen.
- Deliver Machine Learning (ML) driven personalized experiences to a user, no matter which channel or device the user has engaged with your business.
- Seamlessly integrate with Adobe Experience Cloud products such as Adobe Analytics, Adobe Audience Manager, and the Experience Cloud ID Service from the server side.
See the Getting Started page to learn how to run a simple feature flagging use case via on-device decisioning.
Check out our Sample Apps to have fun and play around!
Target Recommendations APIs
Link: Target Recommendations APIs and Adobe Recommendations API Overview.
The Recommendations APIs let you programmatically interact with Target recommendations servers. These APIs can be integrated with a range of application stacks to perform functions that you would typically do via the Target user interface.
