Now it’s time to bring everything together and create the personalized experiences. An Activity is the Target mechanism that links the locations, audiences, and offers together, so that when the request is made from the app, Target responds with the personalized content. We’ll build two personalization activities in Target and validate that personalized content is displays to the right user at the right time and in the right location.
At the end of this lesson, you will be able to:
Learn how to create Engage Users and Contextual Offers activities.
Here is a summary of the activity we’ll build:
|New Mobile App Users||wetravel_engage_home, wetravel_engage_search||Home: Engage New Users, Search: Engage New Users|
|Returning Mobile App Users||wetravel_engage_home, wetravel_engage_search||Home: Returning Users, default_content|
In the Target interface do the following:
Select Activities > Create Activity > Experience Targeting.
Click Mobile App.
Select the Form composer.
Select your workspace (the same workspace you used in previous lessons).
Select your Property (the same property you used in previous lessons).
Change the activity title to Engage Users.
Select the ellipsis > Change Audience.
Set the audience to New Mobile App Users.
Change the location to wetravel_engage_home.
Select the dropdown arrow next to Default Content and select Change HTML Offer.
Select the Home: Engage New Users offer.
Select Add Location.
Select the wetravel_engage_search location.
Change the HTML offer.
Select the Search: Engage New Users offer.
You’ve just connected an audience to locations and offers, creating the personalized experience for the New Mobile App Users! The experience should now look like this:
Now create an experience for Returning Mobile App Users:
Now use the same process we used earlier to configure the new experience. The configuration for the Returning Mobile App Users experience should look like this:
Let’s continue to the next screen in the setup:
Click Next to advance to the Targeting screen.
Use the default settings for Targeting. If you had experiences for audiences that overlapped (e.g. New York Users and First Time Users) you could arrange the priority order on this screen.
Click Next to advance to Goals & Settings.
Now let’s complete the activity setup:
Set the Primary Goal to Conversion.
Set the action to Viewed an mbox > wetravel_context_dest (Since this location is on the confirmation screen, we can use it to measure conversions).
Keep all other settings on the screen to the defaults.
Click Save & Close to save the Activity.
Activate the Activity on the next screen.
Our first activity is now live and ready to test!
Here is a summary of the second activity we’ll build:
|Destination: San Diego||wetravel_context_dest||Promotion for San Diego|
|Destination: Los Angeles||wetravel_context_dest||Promotion for Los Angeles|
Repeat the same process as above for the next Activity - “Contextual Offers”. The Final configuration for both experiences are shown below:
On the Goals & Settings step, we’ll change the Primary Goal to the location on booking confirmation screen:
Activate the Activity on the next screen.
Now our second activity is live and ready to test!
Run the Emulator and watch for the first offer to display at the bottom of the home screen. If you’re a returning user with 5 or more app launches, you would see the welcome back offer displayed. If you’re a new user (less than 5 app launches), you should see the new user message:
If the new user offer doesn’t display, try wiping the data for your emulator. That will reset the app launches to 1 the next time you launch. This is done under Tools > AVD Manager. You might need to restart Android Studio, too, if Logcat does not work properly:
You can also validate the response in Logcat by filtering for wetravel_engage_home:
Select San Jose as your Departure and San Diego as your Destination and click Find Bus to search for available buses.
On the results screen, you should see the use filters message. If you’re a returning user with 5 or more app launches, no message will appear here since default content is set for this location (which is blank):
Now continue through the booking process:
Since San Diego was selected as the destination, you should see the DJ SAM offer banner on the confirmation screen:
Now select Done and try another booking with Los Angeles as the destination. The confirmation screen should display the Universal Studios banner:
Congratulations! This concludes the main portion of the Adobe Target SDK 4.x for Android Tutorial. You now have the skills to implement personalization in Android apps! You can refer to this documentation and demo app as a reference for your future projects.
Next: Feature Flagging is another feature that can be implemented with Adobe Target in Android. To learn about feature flagging, check out the next lesson.