Now it's time to bring everything together and create the personalized experiences. An
Activityis 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:
- Build Activities in Adobe Target
- Validate the Activities in the sample App
Create Activities in Adobe Target
Learn how to create Engage Users and Contextual Offers activities.
First Activity - "Engage Users"
Here is a summary of the activity we'll build:
New Mobile App Users
Home: Engage New Users, Search: Engage New Users
Returning Mobile App Users
Home: Returning Users, default_content
In the Target interface do the following:
- SelectActivities>Create Activity>Experience Targeting.
- ClickMobile App.
- Select theForm 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 toEngage Users.
- Select theellipsis>Change Audience.
- Set the audience toNew Mobile App Users.
- Change the location towetravel_engage_home.
- Select the dropdown arrow next to Default Content and selectChange HTML Offer.
- Select theHome: Engage New Usersoffer.
- SelectAdd Location.
- Select thewetravel_engage_searchlocation.
- Change the HTML offer.
- Select theSearch: Engage New Usersoffer.
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:
- SelectAdd Experience Targetingon the left.
- Select the AudienceReturning 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:
- ClickNextto advance to theTargetingscreen.
- Use the default settings for Targeting. If you had experiences for audiences that overlapped (e.g.New York UsersandFirst Time Users) you could arrange the priority order on this screen.
- ClickNextto advance toGoals & Settings.
Now let's complete the activity setup:
- Set thePrimary GoaltoConversion.
- Set the action toViewed 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.
- ClickSave & Closeto save the Activity.
- Activate theActivityon the next screen.
Our first activity is now live and ready to test!
Second Activity - "Contextual Offers"
Here is a summary of the second activity we'll build:
Destination: San Diego
Promotion for San Diego
Destination: Los Angeles
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:
- Under theReporting Settings, set thePrimary GoaltoConversion.
- Set the action toViewed an mbox>wetravel_context_dest(in this activity, this metric is basically meaningless since this is also the same location which delivers the experience).
- ClickSave & Close.
Activate the Activity on the next screen.
Now our second activity is live and ready to test!
Validate the Home Offer
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 backoffer displayed. If you're a new user (less than 5 app launches), you should see the
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
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
Validate the Search Offer
San Joseas your
San Diegoas your
Find Busto search for available buses.
On the results screen, you should see the
use filtersmessage. 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):
Validate the Contextual Offers on the Thank You Screen
Now continue through the booking process:
- Select a bus on the results screen.
- Select a seat on the checkout screen.
- SelectCredit Cardon the payment screen (leave the payment info blank - no actual booking will take place).
Since San Diego was selected as the destination, you should see the
DJ SAMoffer banner on the confirmation screen:
Doneand try another booking with Los Angeles as the destination. The confirmation screen should display the
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.