PERSONALISATION | Use Customer / Decisioning Data to Personalise Retail

Modified on Mon, 12 May at 12:24 PM

Below are the steps to set-up an internal POC/Demo of how you can support Personalisation in Retail

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 some Test Campaigns

> 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.

STEP 1: Create a REST API Key (as per Steps in Linked Article)

STEP 2: Download a REST API Client App onto the Demo Mobile Phone.

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

STEP 3: If your instance of Personalisation Hub Platform sits behind IP-Restrictions & the Demo Mobile Phone is not connected to a White-Listed Network, you'll need to white list the IP address that you use for the Demo

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

STEP 5: Triggered Campaign Running on a Connected Display (Validate Customer/Decisioning Data is being received)

REST API APP Settings should be as follows:

Request Method = POST

URL = https://your-platform-domain.com/location-api/visitor/feed

Headers = Content-Type = application/json

apikey = see Steps below to Create a New API Key

Body = raw

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

To Stop Campaign Playback, simply replace the {Data} that you sent through with Blank Values. This will clear the data.

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:

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