parse campaign tracking tags
- Ben Clark
The parse campaign tracking tags public Template works with the referrer value and the query string parameters it may hold to help identify where a user arrived from.
The referrer value and the query string parameters are provided by the Alterian RIS used in our Standard Tracking Rule.
Many outbound messaging and CX campaign tools look to track success by using the standard UTM tags that are championed and used by Google.
This Public Template will review the referrer query string parameters to see if standard UTM tags are present. If they are, we pull them out, re-name them to make them generic for Alterian and make them available as fields in the flow of the Rule.
These UTM tags provide in depth information on which campaigns and content are generating traffic.
This functionality may also provide an easy way to allow Alterian CX access to tracking information for 3rd parties without specific tagging being required. You simply turn on the automated UTM tracking functionality many venders provide out of the box.
This template will look for the following UTM tags:
utm_campaign
utm_source
utm_medium
utm_term
utm_content
At a minimum a utm_source is required. If this is not present we consider the values invalid and remove them.
Field Mapping
Input Fields
Field | Description | Example |
|---|---|---|
urlQuerystring | Takes the Query String from the referrer gathered from the RIS and breaks out the query string parameters it contains looking for commonly used UTM parameters |
|
urlDomain | Takes the URL Domain from the Referrer |
|
AlterianCX_referrer | Takes the Referrer value from the RIS |
|
Configuration
No configuration required
Field | Description | Example |
|---|---|---|
|
|
|
Output Fields
Field | Description | Example |
|---|---|---|
referrerScheme | This is http or https | HTTP or HTTPS |
referrerDomain | The domain of the referrer. This indicates where the user was when they clicked through. | |
referrerPath | The specific, location they were on before clicking through | /holidays |
referrerQuerystring | Querystring on the referrer. We review this and pull out UTM tags where they exist |
|
AlterianCX_inboundCampaignName | This is taken from the standard utm_campaign tag and renamed for Alterian CX use. | Summer2022Campaign1 |
AlterianCX_inboundSource | This is taken from the standard utm_source tag and renamed for Alterian CX use. This is the minimal subset of values we accept. If the utm_source is not present we remove any remaining UTM as these are likely to be incorrect or invalid. For a “channel source” event created at the start of a new interaction in the GETCXID Public Template we look up the AlterianCX_inboundSource to see if it is blank. If it is we use the standard channel supplied in the call to the rule. If it is populated we will use the AlterianCX_inboundSource as the LOCATION for the event. See Impact on the Channel Source event creation | |
AlterianCX_inboundMedium | This is taken from the standard utm_medium tag and renamed for Alterian CX use. For a “channel source” event created at the start of a new interaction in the GETCXID Public Template we look up the AlterianCX_inboundMedium to see if it is blank. If it is we use the standard channel supplied in the call to the rule. If it is populated we will use the AlterianCX_inboundMedium as the CHANNEL for the event. See Impact on the Channel Source event creation | |
AlterianCX_inboundTerm | This is taken from the standard utm_term tag and renamed for Alterian CX use. | holidays |
AlterianCX_inboundContent | This is taken from the standard utm_content tag and renamed for Alterian CX use. | Acadianholidayslink |