PERSONALISATION | Use Customer / Decisioning Data to Personalise Retail

When you are ready to Start Delivering Personalised Experiences in Retail, below is a quick way to set-up an internal POC/Demo for your Executive Team. 

The POC/Demo covers how Brands can quickly demonstrate the value of integrating their Customer/Decisioning Data into the Platform to support Connected & Personalised Customer Experiences in Retail.

The Steps below cover how to connect to the Platform's 'Visitor API' & utilise any Customer/Decisioning Data within the Platform. 

Connected Customer/Decisioning Data can also be surfaced to Store Staff when they pick-up customer's up from the Queue.

What you require for this POC/Demo

> Platform REST API Key (to authenticate with the Visitor API)

> Mobile Phone with a REST API Client App installed

> Test Store/Display running a Test Channel

> Demo Use Cases (incl Defined Customer/Decisioning Data)

Please raise a support ticket if you need help at any stage in setting up the below POC/Demo. The Team will be happy to assist.

We use 'REST Api Client Android' & see section below for Settings

STEP 4: Define the Demo Use Cases and {Data} used to Trigger Personalised Campaigns

STEP 5: Test Channel Running on Display (Validate Customer/Decisioning Data is being received)

STEP 6: Create AEM Audience(s)/Segment(s) based on the Visitor {Data} that you wish to use

STEP 7: Author a Targeted Channel based on the Audience(s)/Segment(s) defined in Step 6 above

REST API APP Settings should be as follows:

USE CASE 1. 'TRIGGER CAMPAIGN' ON A SPECIFIC DISPLAY

{
    "device_id":"xxx",
    "device_type":"{Data}",
    "events":"{Data}",
    "first_name":"{Data}",
    "page_view":"{Data}",
    "product_holdings":[
       "{Data}"
    ],
    "source":"APP",
    "uuid":"{ACTUAL-STORE-CODE}",
    "uuid_type":"STORE_CODE",
"display_id":{ACTUAL-DISPLAY-ID}
 }

USE CASE 2. 'TRIGGER CAMPAIGNS' ON ALL DISPLAYS IN A SPECIFIC STORE AT ONCE

{
    "device_id":"xxx",
    "device_type":"{Data}",
    "events":"{Data}",
    "first_name":"{Data}",
    "page_view":"{Data}",
    "product_holdings":[
       "{Data}"
    ],
    "source":"APP",
    "uuid":"{ACTUAL-STORE-CODE}",
    "uuid_type":"STORE_CODE"
 }

For "device_id" > you can use any random value, however this field can't be left Blank

For "source" > you can use either "APP" or "STORE_TABLET"

For "uuid" > you must use the Actual Store Code for the Store you are Testing In

For "uuid_type" > leave as is. This must be "STORE_CODE"

For "display_id" > you must use the Actual Display ID of the Display you are Testing on. Quickest way to get this is to Login to HQ Admin, Navigate to the Display Details Page and check the URL (/hq-admin/displays-and-devices/details/{ACTUAL-DISPLAY-ID}/display-details)

Other Customer/Decisioning fields supported (see AEM ContextHub Paths below):

> Age, Gender, Product Type, Plan Type, Plan Value, Purchase History, Platform Data & Visitor Segments

Corresponding AEM ContextHub Paths used to Create Audience/Segment

Remember to ensure that the Boost Value used to create these AEM Audiences is set to a higher value than any of the existing Audiences/Segments running in the AEM Channel.

location-store/displays/0/display_segmentation/formatted_visitor_device_type

location-store/displays/0/display_segmentation/formatted_visitor_events

location-store/displays/0/display_segmentation/formatted_visitor_page_views

location-store/displays/0/display_segmentation/formatted_visitor_platform_data

location-store/displays/0/display_segmentation/formatted_visitor_product_type

location-store/displays/0/display_segmentation/formatted_visitor_plan_type

location-store/displays/0/display_segmentation/formatted_visitor_plan_value

location-store/displays/0/display_segmentation/formatted_visitor_purchase_history

location-store/displays/0/display_segmentation/formatted_visitor_segments