Identification Field Mapping
- Ben Clark
The GET CXID Template needs to understand who is interacting with the rule so we can track the activity against an individual and in some cases create the conversations, anda update the cutomer details. To do this we need to provide the GET CXID with the fields that will provide the identification values.
We provide the fields that contain the identification values within a parameter inside the GET CXID called
AlterianCX_identificationFields
This parameter has been given a default value so we will still support the old and new default identification fields.
For the GET CXID - Bulk Optimised public Template we will use only the top identifier that has been provided and has been populated of the following in order of priority where the value is populated.
Default Values
Priority | Fields | Origin / Use |
|---|---|---|
1 | AlterianCX_emailhash | Used in Email Tracking, we know this is a good identifier as it is derived from Email Address |
2 | dderh | Used in Email Tracking, we know this is a good identifier as it is derived from Email Address |
3 | customerid | Default field to allow a customerid to be mapped. New default value to allow our Public Rules and Templates to function without changes |
4 | emailAddress | Default field to allow an emailAddress to be mapped. New default value to allow our Public Rules and Templates to function without changes |
5 | mobileNumber | Default field to allow a mobileNumber to be mapped. New default value to allow our Public Rules and Templates to function without changes |
6 | visitorId | Default field to allow a vistorid to be mapped. New default value to allow our Public Rules and Templates to function without changes |
7 | AlterianCX_channelagentid1 | Old default - This will allow older rules using channelagentids to continue to work wiht no changes. |
8 | AlterianCX_channelagentid2 | Old default - This will allow older rules using channelagentids to continue to work wiht no changes. |
9 | AlterianCX_channelagentid3 | Old default - This will allow older rules using channelagentids to continue to work wiht no changes. |
Adding new Identifier fields
When you are creating your rules you may have alternative identification fields to provide to the GET CXID. You may for example pass through fields called ‘email’ or ‘CookieID' or 'LoginID’.
How do you change the GET CXID to use these?
Firstly we need to create a new Global Parameter
AlterianCX_identificationFields
Simply create an ordered list Global Parameter called ‘alteriancx_identificationfields’ this will allow the changes made to this Global Parameter to cascade down to the same named parameters in the Rules.
Set the Parameter as Forced and Visible - This will allow the users to see the values being used in the Rule and allows the value cascade to work.
Set the Global Parameter as Data Type 'Ordered List'.
In ‘Values’ provide the superset of the identification fields you may use in any of your Rules. It’s okay to include all of them, the GET CXID will only use the top three based on priority where populated.
Edit the order of the identification fields for each target. The fields on the far left has the highest priority so ensure your best identifiers are included here.
If you are using Alterian Email Tracking ensure ‘AlterianCX_emailhash' and 'dderh’ are included as high priority Identifiers
Once the Global Parameter has been set you will find that the AlterianCX_identificationFields parameter in the rule now has your selected fields.
The GET CXID will now use these fields to identify an individual and work through them in priority order. We only use the top one that is populated.
Providing the Identifiers in priority order will help when merging the data. For example if you have available:
Cookie ID
Customer Number
Email Address
We would recommend
Priority | Identifier |
|---|---|
1 | Customer Number |
2 | Email Address |
3 | Cookie ID |
With this ordering we will look to merge any information with the Customer number if matches occur.
If you do not provide a populated Identifier field the Get CXID Tile will generate its own random value.