Target for mobile apps FAQ
- Topics:
- Implement Mobile
CREATED FOR:
- Developer
List of frequently asked questions about Target for mobile apps.
Should I use tags in Adobe Experience Platform to deploy the SDK, or can I deploy the SDK without using Launch?
The SDK is available on the Adobe Marketing Cloud git. If you don’t use tags in Adobe Experience Platform, you must manage your own settings file and manage it in your app.
Which SDKs are available today?
The Adobe Experience Platform Mobile SDKs currently support iOS, Android, and React. For more information, see the Adobe Experience Cloud Platform Mobile SDKs guide.
What is the frequency of the location-based feature, in terms of verification about the latitude and longitude?
See the Adobe Places documentation for more information.
Do I need at.js for the Adobe Experience Platform Mobile SDKs to work?
No, you don’t need at.js to use the mobile SDKs. at.js is the Target JavaScript library for websites. The Adobe Experience Platform Mobile SDKs are for mobile apps.
Is Target Mobile a functionality of Adobe Target Premium Product SKU only?
No. For Adobe Target Standard customers, you can use our Mobile SDKs for A/B Test and Experience Targeting (XT) activities only with the Target Standard Mobile App add-on. If you want to use Recommendations or AI-powered features in the mobile app, you need an Adobe Target Premium license.
Is there a mobile app integration between Adobe Experience Manager (AEM) and Target mobile activities?
Currently, you can share JSON Experience Fragments from AEM to Target and there might be potential to then use them in a mobile app activity.
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