Add Parameters to the Requests

Last update: October 16, 2021

CREATED FOR:

  • Intermediate
  • Developer

In this lesson we will add Adobe lifecycle metrics and custom parameters to the Target requests added in the previous lesson. These metrics and parameters will be used for creating personalized audiences later in the tutorial.

Learning Objectives

At the end of this lesson, you will be able to:

  • Add the Adobe mobile lifecycle metrics
  • Add parameters to a prefetch request
  • Add parameters to a live location
  • Validate the parameters for both requests

Add the Lifecycle Parameters

Let’s enable the Adobe mobile lifecycle metrics. This will add parameters to location requests containing rich information about the user’s device and engagement with the app. We’ll build audiences in the next lesson using data that the lifecycle request provides.

To enable lifecycle metrics, open the HomeActivity controller again and add Config.collectLifecycleData(this); to the onResume() function:

Lifecycle Request

Validate the Lifecycle Parameters for the Prefetch Request

Run the Emulator and use Logcat to validate the lifecycle parameters. Filter for “prefetch” to find the prefetch response and look for the new parameters:
Lifecycle Validation

Even though we’ve only added Config.collectLifecycleData() to the HomeActivity controller, you should see the lifecycle metrics sent with the Target request on your ThankYou screen, too.

Add the at_property Parameter to the Prefetch Request

Adobe Target Properties are defined in the Target interface and are used to establish boundaries for personalizing apps and websites. The at_property parameter identifies the specific property where your offers and activities are accessed and maintained. We’ll add a property to the prefetch and live location requests.

NOTE
You may or may not see the Properties options in the Target interface, depending on your license. If you don’t have these options, or if you don’t use Properties in your company, just skip ahead to the next section of this lesson.

You can retrieve your at_property value in the Target interface under Setup > Properties. Hover over the property, select the code snippet icon and copy the at_property value:

Copy at_property

Add it as a parameter for each location in the prefetch request like this:
Add at_property parameter
Here is the updated code for the targetPrefetchContent() function (be sure to update the your at_property value goes here placeholder text!): 

public void targetPrefetchContent() {
        List<TargetPrefetchObject> prefetchList = new ArrayList<>();

        Map<String, Object> params1;
        params1 = new HashMap<String, Object>();
        params1.put("at_property", "your at_property value goes here");

        prefetchList.add(Target.createTargetPrefetchObject(Constant.wetravel_engage_home, params1));
        prefetchList.add(Target.createTargetPrefetchObject(Constant.wetravel_engage_search, params1));
        Target.TargetCallback<Boolean> prefetchStatusCallback = new Target.TargetCallback<Boolean>() {
            @Override
            public void call(final Boolean status) {
                HomeActivity.this.runOnUiThread(new Runnable() {
                    @Override
                    public void run() {
                        String cachingStatus = status ? "YES" : "NO";
                        System.out.println("Received Response from prefetch : " + cachingStatus);
                        engageMessage();
                        setUp();

                    }
                });
            }};
        Target.prefetchContent(prefetchList, null, prefetchStatusCallback);
    }