Adobe Target is the Adobe Marketing Cloud solution that lets you customize your mobile app experience by providing different experiences to different audiences to set up an A/B test. You can then maximize revenue by comparing the results of two or more experiences to determine which one performs best with different audiences. For example, you might target promotional content A at 50% of the audience and promotion content B at the remaining audience in order to determine which promotional content is more engaging.
In an AEM Mobile app, you can set up an A/B testing in either HTML articles or dynamic banners. For example, you could create a dynamic banner with an image carousel that displays content A to one audience and content B to a different audience.
- AEM Mobile Master Admin account
- Digital Marketing Cloud license that provides access to Adobe Target
Define the Adobe Target activity that you will use to determine which content in an AEM Mobile dynamic banner or HTML article appears.
-
Sign in to the Mobile Marketing Dashboard (https://mobilemarketing.adobe.com).
-
You can manage Adobe Target Activities from either Mobile Marketing Dashboard or the Adobe Target Dashboard. See Access Target from Adobe Marketing Cloud in Adobe Target Help.
-
- Specify the activity Name.
- Set Active to On.
- Set the Start and End date.
- Set the Audience if needed. See Audiences in Adobe Target Help.
- Set the Content Location, which is the name of the Target mbox. The default mbox name is target-global-mbox. If you have a custom mbox name, specify it. See Understanding the Global mbox in Adobe Target Help.
- Specify the Test Experiences. See Experiences in Adobe Target Help. When you add an experience, you specify an Offer that includes HTML code. See Offers in Adobe Target Help.
- Set the Success Location, which is the name of a Target mbox.
- Specify the activity Name.
After you create your Adobe Target activity, you need to perform several tasks to allow the HTML content in the AEM Mobile app to use the Target activity.
-
In the SDK Target Options section of app settings, select Use HTTPS, and specify the Client Code and Request Timeout.
Make sure the Use HTTPS option is checked in the Manage App Settings page in Adobe Mobile Services. If HTTPS isn't enabled, iOS calls might be blocked unless you whitelist the Target server.
The Client Code is unique to your account or company. You can find your Client Code by looking at your Target mbox settings. Open your Target activity and choose View Reports to go to the Adobe Target Dashboard. Select the activity and choose Setup > Implementation > Edit mbox.js Settings. The Client Code for your account is listed in the mbox.js settings.
The Request Timeout option specifies the length of time, in seconds, that must elapse between app launches before the launch is considered a new session.
-
-
- In the article or dynamic banner properties, make sure that Enable extensibility features is selected.
- Include <script type="text/javascript" src="cordova.js"></script> in the HTML code to enable Cordova plugins and the Mobile Services SDK.
- Enable the Target support files that you include in your HTML article or dynamic banner. The cordova.js file is included automatically in the app. The ADB.targetLoadRequest() cannot be called until the underlying Cordova library is initialized. To do this, include a support file called index.js. This support file adds a listener and waits until the Cordova library is loaded. Once the Cordova library is ready, it calls initAdobeMC(), where the ADB.targetLoadRequest() is called or any other ADB method contained in ADB_Helper.js. This code is shown in the target.js file.
<script type="text/javascript" src="cordova.js"></script> <script type="text/javascript" src="js/target.js"></script> <script type="text/javascript" src="js/index.js"></script>
Prenos
Pridobivanje datoteketarget.js.zipPridobivanje datotekeindex.js.zipPridobivanje datotekeTarget_HTML_Example.zipFor details about the Target methods used, see PhoneGap Plug-in Methods in Adobe Marketing Cloud Help.
- In the article or dynamic banner properties, make sure that Enable extensibility features is selected.