Set engagement score will apply a fixed value to the Engagement score for a user. This will overwrite any Engagement score that already exists so you should be careful in its use. The value could be defaulted or set via standard parameters.
...
We are often asked how to make CX decisions as targeted as possible. Once of the methods is to clearly understand as much as possible about the person interacting at the time of interaction. This Public Template is especially useful for our brands with an offline presence; it takes the IP address at the time of interaction and provides back into the flow of the rule various location details including country, city, latitude, and longitude. These fields can then be used in further personalisation - nearest store offers of direction information for example.
...
Input Data
Field | Description | Example | AlterianCX_cxid | CXID | engagementScore | Field automatically created by Journey Orchestration and will auto-map |
---|
Configuration
...
Parameter | Description | Example | ||
---|---|---|---|---|
engagementScore | The Value to set the engagement score to | 100 or -500 | ||
engagementScoreColumn | The name of the column where the engagement score is stored. By Default this is set to engagementScore and it should be left like this in the majority of cases. It is possible customers may want engagement scores linked to specific activities like a Sale. this functionality could allow an Sale Engagement Score to be created and stored. | engagementScoreIP | IP Address - Provided by the calling system. This would as standard be gathered in the tracking tagging. | 81.141.1.226 |
Configuration
By default the Public template calls out to the API at https://ip-api.com/ and provides back the location information. At its basic tier you can make 45 calls for free per min. Good for small usage or testing. Beyond this volume it has a competative paid for tier. Configuration for the paid for tier can be configured by adapting the Public Template and saving it in your local client.
Processing
This tile template will take the CXID IP field in the flow and write into the required engagementScoreColumn a value as set in the engagementScoregenerate a series of location fields that should identify where the person was when the call was made.
Getting geolocation data from an IP is useful but is not always 100% accurate. For identifying a closest store or local weather it’s fine. It should not be relied upon to provide important location information proximity to a forest fire for example!
Output Data
Field | Description | Example | AlterianCX_cxid | CXID | engagementScore | Field automatically created by Journey Orchestration and will auto map|
---|---|---|---|---|---|---|
city | Expected nearest City | York | ||||
country | Expected country | Great Britain | ||||
countryCode | Provides country ISO codes as described in the ISO 3166 international standard numerical | GBR | ||||
IP | IP Address | 81.141.1.226 | ||||
latitude | Measurement of distance north or south of the Equator | 51.2279 | ||||
longitude | Measurement east or west of the prime meridian | -2.5261 | ||||
postalCode | Postal district level | BA4 |