Loading Persona Data

As individuals interact with your Rules, we gather useful information on the decisions made by the Rule, the location of the rule and details on the individual interacting.

Journey Analytics uses this information to show your users Journeys across various interaction points, these could be viewing various pages on a website, an interaction with a call centre or clicking through an email.

The question our customers come up with most is “Why” was that Journey followed or “Why” was that offer the one that generated a conversion?

The more information we know about a Individual during the journey the better we understand why these things occurred.

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.

Personas

Personas are an extension of the Customer Attribute functionality. They differ from the the standard Customer attribute data in the following ways:

• Customer attribute data is predominately a single value. For example your age band will always have a single results as would your churn risk band. For a Persona you could be a “Red Wine Lover” and a “White Wine Lover”at the same time. Either Persona could be relevent for an offer you want to show or either could be a influence on the Journey the user may choose to take. As a result for the standard persona field we support the use of a delimited array field.

• The Standard Persona field is called “AlterianCX_Persona” and this is how the Persona values are loaded into your Customer Attribute table. As a delimited pipe string.

Example Persona value