- 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 mobile preview
Use mobile preview links to perform easy end-to-end QA for mobile app activities and enroll yourself into different experiences using your device without any special test devices.
The mobile preview functionality lets you fully test your mobile app activities before launching them live.
Prerequisites
-
Use a supported version of the SDK: The mobile preview feature requires that you download and install the appropriate version of the Adobe Mobile SDK in your corresponding apps.
For instructions to download the appropriate SDK, see Current SDK versions in the Adobe Experience Platform Mobile SDK documentation.
-
Set up a URL scheme: The preview link uses a URL scheme to open your app. Specify a unique URL scheme for the preview.
For more information, see Visual preview in Configure the Target extension in the Data Connection UI in the Mobile SDK documentation.
The following links contain more information:
- iOs: For more information about setting URL schemes for iOS, see Defining a custom URL scheme for your app on the Apple Developer website.
- Android: For more information about setting URL schemes for Android, see Create Deep Links to App Content on the Android Developers website.
-
Set up the
collectLaunchInfoAPI (i0S only)For more information, see Visual preview in Configure the Target extension in the Data Connection UI in the Mobile SDK documentation.
Generating a Preview Link
-
In the Target UI, click the More Options icon (the vertical ellipsis), then select Create Mobile Preview Link.
-
Select the activities that you want to preview, then click Generate Mobile Preview Link.
NOTEYou can select only Form-Based A/B Test and Experience Targeting (XT) activities.
-
Specify your app’s URL scheme.
The URL scheme must be the same as what is present in your iOS or Android app. Repeat this process separately for iOS and Android, if necessary.
-
Click Generate Mobile Preview Link, then copy the link.
Preview on Your Device
Open the link in a mobile browser on a device where you have your app installed. This app can be the production app that you downloaded from the Apple App Store or the Google Play Store. The app doesn’t need to be a special build. If you have an active preview link, you can view the experiences on the device.
-
Open the link in your mobile browser.
Share the link that you copied in the previous section from the Target UI to your mobile device in a convenient way, for example using text, email, or Slack.
|
|
|Your app opens and starts the Target Mobile Preview Mode.
-
Select the combination of experiences that you want to see, then click Launch Experiences.
|
|
|
|
|
|
|
|
Limitations
- The view must load again for the new content to display after the Launch Experiences button is clicked. The easiest way is to switch to a different screen and then come back to the screen where you are expecting the change to happen.
- Mobile preview is not supported for Android versions earlier than API-19 (KitKat).
