...
We have Customer Attributes to provide this detail. We allow our customers to upload information on your customers to Alterian CX and have this information automatically available for Custom Dashboards and for filtering in Journey Analytics.
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 actioned 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.
...
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 ChannelAgent id field to create or lookup a suitable CXID. We normally suggest that your best, or most accurate ChannelAgent id is used where possible.
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
ChannelAgentid1 = 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.
ChannelAgentID1 = 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.
called ChannelAgentid data into this Rule a row at a time.
...
An example rule running in Kettle may look like this.
How Customer Attribute Data works wiht Events
Alterian provide a series of event queue Public Templates. These templates pass event data into data streams that are used by Journey Analytics, our dashboards and reporting.
The Public templates that create data streams for have been upgraded to contain a parameter (AlterianQueue_customerAttributeTable) that references a table* with our standard Customer Experience ID as the key.
Once the Customer Attribute table has been configured, each time an event is passed to Alterian Journey Analytics any data from the Customer Attribute Table linked to the corresponding Customer Experience ID will also get passed through.
As long as you keep the Customer Attribute Table up to date you will be able to understand much more clearly “who” does what and why.
For example you would be able to filter by customer value decile to see how your bigger spending users interact with your website or use customer type to identify why one offer may have been better than another.
*Please contact Alterian Support to organise the creation of this table and to discuss how to keep the information up to date in the most performant manner.
*Please note that data loads come with a cost. Please review your contract for pricingcustom dashboards and for filtering in Journey Analytics.