Loading Customer Attributes to Alterian CX

Loading Customer Attributes to Alterian CX

To enable customer attributes to be used in Alterian CX we need to know the following. What fields are required by the customer, what data types they are and which should be used as filters in Journey Analytics.

Our customers provide this information through a request into the Alterian support team.

Once this request has be been completed an autoloader rule will appear in your account. This rule can be used to load your customer attribute data into your Customer attribute table, whilst at the same time looking up a Customer Experience ID (CXID) to use as the key.

Open

The rule by default is called autoloader-cat. It’s an API endpoint available to your Integrations team. You can integrate in any way that suits, whether this is row by row updates through the day from a CDP or CMS or loads each night*.

To setup a process to load customer attribute data you need to pass your stated customer attribute data into this rule as well as a Identifier field to create or lookup a suitable CXID. We normally suggest that your best, or most accurate Identifier is used.

However, as this single value is used to lookup an individual it may be beneficial to use a good but more commonly used data item instead of the very best to get more matches and therefore more customer attribute data into your solution.

For example

Identifier = Customer number

The customer number is the best identifier of an individual, but it is not available on the website and therefore we will not be able to match it to an individual.

Identifier = Login email address

The login email address is a good identifier for an individual and it available on the website and in email campaigns and therefore we will be able to match it to more individuals and therefore generate more useful data for filtering.

Customer Attribute Load Process

1. Customer to provide details of the 15 "customer attributes" they would like to setup for journey analytics filtering, Dashboards and Rule Enrichment. For each one we need:

   1. Field Type

   2. Whether it should be used as a filter in Journey analytics. See the cardinality restriction highlighted above. Some information may be used in reporting only and not used as a filter. Customer to flag those that should be filters

   3. A standard Persona Field will always be available to load data into and will alwats be available as a filter and for use in Rule Orchestration

2. Alterian create a Autoloader-cat Rule that will load the data into Alterian CX

3. Customer loads stated customer attributes to the Rule a row at a time.

   1. Customer provides a Identifier field to act as a lookup to identify previous CXIDs if not found a new one is created.