- Adobe Target Developer Guide
- Getting started
- 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
How Target works in mobile apps
The Adobe Mobile SDK contacts the Target server to get the content along with other data points to show the right experience to the user.
Support for the Adobe Mobile version 4.x SDKs has ended as of August 31, 2021 and is no longer recommended for Adobe Target mobile users.
The Adobe Experience Platform SDK for Mobile Apps is the recommended solution to power Adobe Experience Cloud solutions and services in your mobile apps.
Target locations and success metrics
A target location is also referred to as an mbox. An identified location in the app is enabled for testing or personalization (for example, the welcome message on the home screen). These locations are identified during the test creation process.
A success metric is an action performed by the user that identifies if a specific activity was successful (such as signing up, making a purchase, booking a ticket, and so on).
-
Target location: The content that shows below the register button.
This particular user is offered free shipping until 6 PM. This location can be reused across multiple Target activities to run A/B tests and personalization.
-
Success metric: The action performed by the user where the user taps the register button.
Understand how Target works in the SDK
Business.Adobe.com resources
Resources
Adobe Account
