PERSONALISATION | Trigger Campaign(s) based on Customer/Decisioning Data

To leverage customer/decisioning data in retail requires that your selected customer/decisioning vendor provides an API that can be used to retrieve customer/decisioning data for the store visitor

The Key Questions that need to be answered:

• 1. Identifier required to retrieve Customer Data from the API
• 2. What Customer Data/Insights do you want to leverage/surface in Retail

1. Identifier required to retrieve Customer Data from the API

The Platform supports a variety of mechanism (Store-Queueing, QR-Control, Appointments, etc) that can be used to Identify Customers as they approach/enter Stores.

Typically clients would use a hashed-email-address or a hashed-mobile-number as the Identifier that gets used to securely retrieve Customer Data from their CDP Platform's API. 

The key requirement here is to ensure that the required Identifier can be captured.

2. What Customer Data/Insights do you want to leverage/surface in Retail

The Next Question is what Customer Data/Insights (Product Holdings, Purchase History, Purchase Intent, etc) would you like to be able to use in Retail. This data can then be used to further Personalise a Customers Experience as they walk through a Store, however can also be surfaced to Retail Staff when they pick Customers up from the Queue.

Please Raise a ticket with the team if you would like support in getting your Customer/Decisioning Data connected to the platform.