track-web - Standard Location Tracking Rule
- Ben Clark
One of the common customer use cases we explore is the ability to trigger CX actions based on the user’s activity or our understanding of their context while browsing on a brands website.
Are they looking for help information? Can we provide tailored suggestions on other products they may like or upgrades or complimentary products to ones they already have? Can we provide a smoother process through the website to achieve the goals they came to the website today to achieve?
Knowing what they are doing and experiencing now helps us to understand what they are trying to do.
To meet this goal, we have created a Public Rule that can be used throughout our customers websites and beyond that identifies the Categories being looked at, update the engagement score based on the content they were exposed to and provided page movement information for Journey Analytics.
Simply copy the track-web Rule from the Public Client into your Client to start using it.
Dependencies
This Public Rule has a dependency on a Category Management Rule. You will need to create one if one does not already exist. More information can be found in the Catergory Management Public Template help.
| Tile | Customer Created or Public Template | Purpose | More Information |
|---|---|---|---|---|
1 | Parse Webdata | Customer Created or Public Template | Provides an API endpoint that allows the Category Management System (Or a website Javascript tag) to call the Rule. Simply provide the fields the Parse Webdata tile requires. This would be required if you needed fiedls not provided by the Realtime Input Public Template below. |
|
1 | Realtime Input | Public Template | Provides an API endpoint that allows the Category Management System (Or a website Javascript tag) to call the Rule. Provides just the key fields required for a Tracking Rule to work. | |
2 | Identify Email Clickthough | Public Template | This Template when used in our standard page tracking Rules looks for an Email recipient arriving on the page through one of our tracked links. It pulls out the identification value we provide in the URL, in this case a parameter called “DDERH”, and we use this value to identify who it is. | |
3 | Get CXID | Public Template | Identifies the individual browsing | |
4 | Category Lookup | Public Template | Identifies the current page Category against a list of Categories previously configured in a Category Management Rule. It passes back information on the Category of this page and any linked engagement scores. The Tile and this Public Rule is dependent on the the Category Management Rule, a centralised location where Categories can be configured. You will need to create this Rule separately to allow this Public Rule to work.
Once the Category Management Rule has been ceated you can configure the Parameters to link this tile to the Management Rule. | Dependency Category Group Management Rule |
5 | Update Category Group Count | Public Template | Takes the Category information provided by the Category lookup and updates the Category activity results for this individual based on the information passed in. | |
6 | Update Engagement Score | Public Template | Takes the Engagement score from the Category Lookup (Based on the Category Group visited) and increments or decrements the individuals Engagement score based on the given value. Over time this will provide a clear indication on how engaged the Individual is with the Brand. | |
7 | Track Location | Public Template | Identifies the location and passes this into the event data so the Journey analytics solution can understand how Individuals are moving through the Website and look to understand that they may be trying to achieve. The Track Location Event queue identifies this Rule as a Tracking Rule. | |
8 | Write to Log | Public Template | Provides logging to ensure the rule is working correctly. |