track-web-with-conversions - Location Tracking with Conversions
- Ben Clark
The track-web Public Rule helps our customers to understand where people are interacting and what content they are being exposed to.
The track-web-with-conversions Rule provides this same functionality but also allows the easy recording of “conversions” on your site.
Conversions are an important function in Alterian CX. Conversions let us understand whether people are purchasing, looking at the correct content on your site, signing up to your newsletter or downloading a PDF. Anything that demonstrates the successful end to a customer journey could be considered a conversion.
Conversions can be linked to Business Goals and Initiatives and ultimately these demostrate whether the Customer Experience and marketing programmes you are running actually make a difference.
The track-web-with-conversions allows the user to setup locations (pages) as conversions and trigger a Conversion event type for them. You can also pass through a Conversion value to enable you to ascertain the monetary benefit the conversion is providing.
The track-web-with-conversions Public Rule can be used throughout our customers websites and beyond. .
Simply open the track-web-with-conversions Public Rule from the Public Client and then save it into your client to start using it.
Dependencies
This Public Rule has a couple of dependencies. Like the track-web Public Rule it is dependent on a Category Management Rule. You will need to create one if one does not already exist. More information can be found in the Category Management Public Template help.
This Rule is also dependent on the track-conversion Rule. This is also available as s Public Rule. More details on how these two Rule interact can be found in the track-conversion Rule 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 to allow this Public Rule to work. In this Public Rule if a Page / location has been identified as a conversion a isconversion flag and a linked Conversion value will also be passed through into the Rule. | Dependency Category Management Rule |
5 | Update Category 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 | Switch Case | Public Template | If a Page / location has been identified as a conversion in the Category Management Tile a isconversion flag and a linked Conversion value will also be passed through into the Rule. This switch case looks for the isconversion flag and will push in one of two directions. If the location is not a conversion it passes to the Track Location tile. In effect it acts exactly like the track-web rule and generates the tracking events required. If the location is identified as a conversion it passes to the Log before calling tile (7b) and then to the invoke conversion tile 8b | |
7a | 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. | |
8a | Write to Log | Public Template | Provides logging to ensure the rule is working correctly. |
| Tile | Customer Created or Public Template | Purpose | More Information |
|---|---|---|---|---|
7b | Log Before Calling | Public Template | Provides logging to ensure the rule is working correctly. | |
8b | invoke conversion tracking rule
| Public Template | Calls the track-conversion Rule passing all the required information required to raise a Conversion event. More information on the track-conversion Rule and how it is configured can be found here. | Dependency |