L2 : Understand how Target works - adobe-target/mobile-lab-emea GitHub Wiki
Level | Beginner |
---|---|
Time | 5 mins |
This lesson is informational and having a basic understanding of these concepts will help you complete the objectives easily.
Step 1 : Target Locations or mboxes
Target Location is also referred to as an mbox. It is an identified location in your app that is enabled for testing or personalization. These locations are identified and implemented during the test creation process. An mbox can be instrumented around small text field (eg: a welcome message on the screen) or an entire screen (eg: a paywall)
Success Metric is an action performed by the user that identifies if a specific activity was successful (eg: signing up, making a purchase, booking a ticket etc). A success of an activity can be measured in Adobe Target or in Adobe Analytics using Analytics for Target(A4T). We will learn more about A4T after we create our first A/B test.
In this image,
Target Location is 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 is the action performed by the user where the user taps the register button.
Step 2 : Mobile SDK and configuration
The Adobe iOS 4.x SDK lets you measure native Apple iPhone and iPad applications, deliver targeted content within your apps, and leverage and collect audience data through Audience Manager. The iOS v4.13.4 of this SDK is already installed in the app that you downloaded.
Step 3 : Target calls from the SDK
The SDK fires calls to your Target account to deliver the right content to the right user. A configuration file in the SDK determines how the calls from your user's app are routed. The calls reach the nearest server on Target's global edge network and Target returns the optimized content all within a fraction of a second.