51ºÚÁϲ»´òìÈ

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

Select Add Service and select 51ºÚÁϲ»´òìÈ 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.

{modal="regular"}

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 > > 51ºÚÁϲ»´òìÈ Experience Platform screen, ensure that Offer Decisioning, Edge Segmentation, and Personalization Destinations are selected. If you also follow the Journey Optimizer lessons, you select 51ºÚÁϲ»´òìÈ Journey Optimizer. See 51ºÚÁϲ»´òìÈ Experience Platform settings for more information.

To save your datastream configuration, select Save .

{modal="regular"}

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

Select Extensions.

Select Catalog.

Search for the Offer Decisioning and Target extension.

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

{modal="regular"}

Navigate to Data Collection interface and select Schemas from the left rail.

Select Browse from the top bar.

Select your schema to open it.

In the schema editor, select Add next to Field groups.

In the Add field groups dialog, search for proposition, select Experience Event - Proposition Interactions and select Add field groups.

{modal="regular"}

To save the changes to your schema, select Save.

Go to the Assurance UI.

Select Configure in left rail and select next to Validate Setup underneath OFFER DECISIONING AND TARGET.

Select Save.

Select Validate Setup in the left rail. Both datastream setup is validated and the SDK setup in your application.

{modal="regular"}

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. 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.
{modal="regular"}

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 Content and select Create JSON Offer from the context menu.

3. In the Create JSON Offer dialog, paste the following JSON.

   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" }

   {modal="regular"}

   Select Create.

4. Select + next to Experiences to add Experience B.

5. Repeat step b and c for experience Experience B, but instead use Aim Analog Watch as the title and paste 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" }

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

{modal="regular"}

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.

   {modal="regular"}

Back in the All Activities screen:

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

{modal="regular"}

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 OFFER DECSIONING AND TARGET.

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.
{modal="regular"}

You can explore Simulate and Event List tabs for additional functionality that helps you to validate your Target offers setup.