Optimize and personalize with Adobe Target

In the Data Collection UI, select Datastreams, and select your datastream, for example Luma Mobile App.

Select Add Service and select Adobe Target from the Service list.

If you are a Target Premium customer and would like to use property tokens, enter the Target Property Token value that you want to use for this integration. Target Standard users can skip this step.

You can find your properties in the Target UI, in Administration > Properties. Select to reveal the property token for the property you want to use. The property token has a format like "at_property": "xxxxxxxx-xxxx-xxxxx-xxxx-xxxxxxxxxxxx"; you must only enter the value xxxxxxxx-xxxx-xxxxx-xxxx-xxxxxxxxxxxx.

Optionally, you can specify a Target Environment ID. Target uses environments to organize your sites and pre-production environments for easy management and separate reporting. The preset environments include Production, Staging, and Development. See Environments and Target Environment ID for more information.

Optionally, you can specify a Target third-party ID namespace to support profile syncing on an identity namespace (for example CRM ID). See Target Third Party ID namespace for more information.

Select Save.

In the Data Collection UI, select Datastreams, and select your datastream, for example Luma Mobile App.

Select for Experience Platform and select Edit from the context menu.

In the Datastreams > > Adobe Experience Platform screen, ensure that Offer Decisioning, Edge Segmentation, and Personalization Destinations are selected. If you also follow the Journey Optimizer lessons, you select Adobe Journey Optimizer. See Adobe Experience Platform settings for more information.

To save your datastream configuration, select Save .

Navigate to Tags, find your mobile tag property, and open the property.

Select Extensions.

Select Catalog.

Search for the Adobe Journey Optimizer - Decisioning extension.

Install the extension. The extension does not require additional configuration.

In the Target UI, select Activities from the top bar.

Select Create Activity and A/B Test from the context menu.

In the Create A/B Test Activity dialog, select Mobile as the Type, select a workspace from the Choose Workspace list, and select your property from the Choose property list if you are a Target Premium customer and specified a property token in the datastream.

Select Create.

In the Untitled Activity screen, at the Experiences step:

1. Enter luma-mobileapp-abtest in Select Location underneath LOCATION 1. This location name (often referred to as an mbox) is used later in the app implementation.

2. Select next to Default Content and select Create JSON Offer from the context menu.

3. Copy the following JSON into Enter a valid JSON object.

   code language-json
   { "title": "Luma Anaolog Watch", "text": "Designed to stand up to your active lifestyle, this women's Luma Analog Watch features a tasteful brushed chrome finish and a stainless steel, water-resistant construction for lasting durability.", "image": "https://luma.enablementadobe.com/content/dam/luma/en/products/gear/watches/Luma_Analog_Watch.jpg" }

4. Select + Add Experience.

   

5. Repeat step b and c for experience Experience B, but instead use the following JSON:

   code language-json
   { "title": "Aim Analog Watch", "text": "The flexible, rubberized strap is contoured to conform to the shape of your wrist for a comfortable all-day fit. The face features three illuminated hands, a digital read-out of the current time, and stopwatch functions.", "image": "https://luma.enablementadobe.com/content/dam/luma/en/products/gear/watches/Aim_Watch.jpg" }

6. Select Next.

   

In the Targeting step, review the setup of your A/B test. By default, both offers are allocated equally across all visitors. Select Next to continue.

In the Goals & Settings step:

1. Rename your Untitled Activity, for example to Luma Mobile SDK Tutorial - A/B Test Example.

2. Enter an Objective for your A/B test, for example A/B Test for Luma mobile app tutorial.

3. Select Conversion, Viewed an mbox in the Goal Metric > MY PRIMARY GOAL tile and enter your location (mbox) name, for example luma-mobileapp-abtest.

4. Select Save & Close.

   

Back in the All Activities screen:

1. Select at your activity.
2. Select Activate to activate your A/B test.

In Xcode, ensure that AEP Optimize is added to the list of packages in Package Dependencies. See Swift Package Manager.

Navigate to Luma > Luma > AppDelegate in the Xcode Project navigator.

Ensure AEPOptimize is part of your list of imports.

import AEPOptimize

Ensure Optimize.self is part of the array of extensions that you are registering.

let extensions = [
    AEPIdentity.Identity.self,
    Lifecycle.self,
    Signal.self,
    Edge.self,
    AEPEdgeIdentity.Identity.self,
    Consent.self,
    UserProfile.self,
    Places.self,
    Messaging.self,
    Optimize.self,
    Assurance.self
]

Navigate to Luma > Luma > Utils > MobileSDK in the Xcode Project navigator. Find the func updatePropositionAT(ecid: String, location: String) async function. Add the following code:

// set up the XDM dictionary, define decision scope and call update proposition API
Task {
    let ecid = ["ECID" : ["id" : ecid, "primary" : true] as [String : Any]]
    let identityMap = ["identityMap" : ecid]
    let xdmData = ["xdm" : identityMap]
    let decisionScope = DecisionScope(name: location)
    Optimize.clearCachedPropositions()
    Optimize.updatePropositions(for: [decisionScope], withXdm: xdmData)
}

This function:

• sets up an XDM dictionary xdmData, containing the ECID to identify the profile for which you have to present the A/B test, and
• defines a decisionScope, an array of locations on where to present the A/B test.

Then the function calls two API’s: Optimize.clearCachedPropositions and Optimize.updatePropositions. These functions clear any cached propositions and update the propositions for this profile. A proposition in this context is the experience (offer) that is selected from the Target activity (your A/B test) and which you defined in Create an A/B test.

Navigate to Luma > Luma > Views > Personalization > TargetOffersView in the Xcode Project navigator. Find the func onPropositionsUpdateAT(location: String) async { function and inspect the code of this function. The most important part of this function is the Optimize.onPropositionsUpdate API call, which:

• retrieves the propositions for the current profile based on the decision scope (which is the location you have defined in the A/B Test),
• retrieves the offer from the proposition,
• unwraps the content of the offer so it can be displayed properly in the app, and
• triggers the displayed() action on the offer which sends an event back to Platform Edge Network informing the offer is displayed.

Still in TargetOffersView, add the following code to the .onFirstAppear modifier. This code ensures the callback for updating the offers is registered only once.

// Invoke callback for offer updates
Task {
    await self.onPropositionsUpdateAT(location: location)
}

Still in TargetOffersView, add the following code to the .task modifier. This code updates the offers when the view is refreshed.

// Clear and update offers
await self.updatePropositionsAT(ecid: currentEcid, location: location)

Rebuild and run the app in the simulator or on a physical device from Xcode, using .

Go to the Personalisation tab.

Scroll down to the bottom, and you see one of the two offers that you have defined in your A/B test displayed in the TARGET tile.

{width="300"}

Review the setup instructions section to connect your simulator or device to Assurance.

Select Configure in left rail and select next to Review & Simulate underneath ADOBE JOURNEY OPTIMIZER DECISIONING.

Select Save.

Select Review & Simulate in the left rail. Both datastream setup is validated and the SDK setup in your application.

Select Requests at the top bar. You see your Target requests.

You can explore Simulate and Event List tabs for further functionality checking your setup for Target offers.