Get CXID Example Configurations - Archive
- Ben Clark
Following the GET CXID changes in January 2023 these are no longer accurate
Fields Required by Get CXID | Commonly mapped Fields | What is required | Mandatory or Not? |
AlterianCX_channelagentid1 | AlterianCX_channelagentid1 | First identification value | Mandatory* |
AlterianCX_channelagentid2 | AlterianCX_channelagentid2 | Second identification value | Not Mandatory* |
AlterianCX_channelagentid3 | AlterianCX_channelagentid3 | Third identification value | Not Mandatory* |
AlterianCX_isknown | AlterianCX_isknown | Is this identification value for a person known to the brand? | Mandatory |
AlterianCX_referrer | AlterianCX_referrer | The referer for the Invocation of this Rule | Not Mandatory |
AlterianQueue_location | urlPath | Where the Rule is being called from. For website tracking rules it’s often the urlPath taken from the page URL that should be used. | Mandatory |
Is Control | Is Control | Identifies whether the individual is in the Control Group for this Rule. | Automatic |
AlterianQueue_channel | AlterianQueue_channel | What Channel is using this Rule in this specific call | Mandatory |
AlterianQueue_position | AlterianQueue_position | Where within the Location the rule is being used. Top Banner, Hero banner, Footer banner all on the home page using the same rule. Rule Position identifies which one was using the Rule in this specific call. | Not Mandatory |
Notes:
At least one Channelagentid should be populated. If you do not provide a Channelagentid the Get CXID Tile will generate its own random value to provide a conversation metric. This will have an impact on the number of conversations generated, increasing numbers significantly and therefore providing an accurate identification value should be a focus.
Example Website Browsing
Fields Required by Get CXID | What is required | Value |
AlterianCX_channelagentid1 | First identification value | Cookie ID |
AlterianCX_channelagentid2 | Second identification value |
|
AlterianCX_channelagentid3 | Third identification value |
|
AlterianCX_isknown | Is this identification value for a person known to the brand? | N |
AlterianCX_referrer | The referer for the Invocation of this Rule | |
AlterianQueue_location | Where the Rule is being called from. For website tracking rules it’s often the urlPath taken from the page URL that should be used. | /SalesProcess/Confirmation |
Is Control | Identifies whether the individual is in the Control Group for this Rule. |
|
AlterianQueue_channel | What Channel is using this Rule in thei specific call | Web |
AlterianQueue_position | Where within the Location the rule is being used. Top Banner, Hero banner, Footer banner all on the home page using the same rule. Rule Position identifies which one was using the Rule in this specific call. |
|
Notes
Cookie ID is provided and fed into the Rule. This does not identify the user so the is known flag is N for unknown.
Web referer is provided in the call as a field
Example Website Login
Example Website Login | What is required | Value |
AlterianCX_channelagentid1 | First identification value | Email Address |
AlterianCX_channelagentid2 | Second identification value | Phone Number |
AlterianCX_channelagentid3 | Third identification value | Cookie ID |
AlterianCX_isknown | Is this identification value for a person known to the brand? | Y |
AlterianCX_referrer | The referer for the Invocation of this Rule | |
AlterianQueue_location | Where the Rule is being called from. For website tracking rules it’s often the urlPath taken from the page URL that should be used. | /lCustomerlogin/loginsuccess |
Is Control | Identifies whether the individual is in the Control Group for this Rule. |
|
AlterianQueue_channel | What Channel is using this Rule in thei specific call |
|
AlterianQueue_position | Where within the Location the rule is being used. Top Banner, Hero banner, Footer banner all on the home page using the same rule. Rule Position identifies which one was using the Rule in this specific call. |
|
Notes
User logs in to website, as part of process they provide an Email Address and on login the website can pass through Customer ID and also the Cookie ID.
Both Email Address and Customer ID highlight fields that adequately identify a person so the is known flag is set as Y for each.
Example Call Centre
A Customer Calling in with a known Phone Number allows the Call Centre user to trigger a Rule. This provides back various elements of information for the Call Centre Operative to utilise.
When the call centre Operative confirms the known email address and sends a confirmation email the Phone and Email address will again be passed through as channelagentids.
Example Call Centre | What is required | Value |
AlterianCX_channelagentid1 | First identification value | CustomerID |
AlterianCX_channelagentid2 | Second identification value | Phone Number |
AlterianCX_channelagentid3 | Third identification value |
|
AlterianCX_isknown | Is this identification value for a person known to the brand? | Y |
AlterianCX_referrer | The referer for the Invocation of this Rule | |
AlterianQueue_location | Where the Rule is being called from. For website tracking rules it’s often the urlPath taken from the page URL that should be used. | /lCustomerlogin/loginsuccess |
Is Control | Identifies whether the individual is in the Control Group for this Rule. |
|
AlterianQueue_channel | What Channel is using this Rule in thei specific call |
|
AlterianQueue_position | Where within the Location the rule is being used. Top Banner, Hero banner, Footer banner all on the home page using the same rule. Rule Position identifies which one was using the Rule in this specific call. |
|