Click Append Parameters (Campaign > Tracking > Rules) are parameters that are added to the end of your target URL when an affiliate sends traffic to your website. If you specify a parameter here that is already part of your campaign URL, or which the affiliate has added in to the target URL, the value here will replace it.
Click Append Parameters are typically used for:
- Dynamically Adding UTM tags to affiliate links
- Tracking & De-duplication
- Pushing data to third party systems e.g. Doubleclick, channel measurement tools etc
Click Append Parameters:
Shortcodes
The following shortcodes can be used in your Click Append Parameters, and will be replaced on-the-fly with appropriate values for each click:
SHORTCODE |
DESCRIPTION |
DATA TYPE |
EXAMPLE |
[AffiliateCode] |
A unique code that you have specified on the affiliate profile page. Useful if you want to match up an affiliate to an ID number in your system. |
String |
ABC123 |
[AffiliateId] |
The affiliate's Commission Factory user ID. |
Integer |
12345 |
[CampaignName] |
The name of your campaign as specified under the Campaign Profile settings page. |
String |
Example Campaign |
[ClickId] |
A unique code that identifies each individual click sent to your campaign. Used for server-to-server conversion reporting. |
String |
0123456789abcdef0123456789abcdef |
[CreativeId] |
The ID of the creative that generated the click, or your user ID if the creative was a text link or QR code. |
Integer |
12345 |
[CreativeName] |
For banners, widgets, and videos, the name of the creative. For coupons, the coupon code. For data feed items, the SKU. For QR codes and text links, this will be blank. |
String |
Summer Sale Leaderboard |
[CreativeType] |
The type of the creative that generated the click, such as "Banner", "Coupon", "Dynamic Tool", "Video", "QR Code" or "Text Link". |
String |
Banner |
[SourceChannel] |
The channel of the traffic source that generated the click, such as "Comparison", "Content", "Display", "Email", "Loyalty", "Network", "Offer", "Recovery", "Search", "Social", or "Software". |
String |
Content |
[SourceDomain] |
For social media pages and websites, the domain name of the traffic source. For behavioural retargeting, email lists, and pay per click - and for traffic sources that could not be determined - this will be blank. |
String |
www.example.com |
[SourceDomainOrName] |
For social media pages and websites, the domain name of the traffic source. For email lists, the name of the email list. For behavioural retargeting, and pay per click - and for traffic sources that could not be determined - this will be blank. |
String |
www.example.com |
[SourceName] |
For email lists, social media pages, and websites, the name of the traffic source. For behavioural retargeting and pay per click - and for traffic sources that could not be determined - this will be blank. |
String |
Example Website |
[SourceType] |
The type of the traffic source that generated the click, such as "Behavioural Retargeting", "Email List", "Pay Per Click", "Social Media Page", or "Website". |
String |
Website |
[SourceUrl] |
For social media pages and websites, the full URL of the traffic source. For behavioural retargeting, email lists, and pay per click - and for traffic sources that could not be determined - this will be blank. |
String |
https://www.example.com/page |
[SourceUrlOrName] |
For social media pages and websites, the full URL of the traffic source. For email lists, the name of the email list. For behavioural retargeting and pay per click - and for traffic sources that could not be determined - this will be blank. |
String |
https://www.example.com/page |
Example of UTM Click Append Parameters suitable for use with Google Analytics:
utm_source=CommissionFactory&utm_medium=Affiliate&utm_content=[SourceName]&utm_Affiliate=[AffiliateId]
Format of Click Append Parameters
Click Append Parameters must be formatted like query string parameters, where each key/value pair is written like "key1=value1", and each key/value pair is separated by an ampersand like "key1=value1&key2=value2". You should not put a leading question mark.
Static values that you enter (i.e. values that will be the same every time) should be Percent Encoded (also known as "URL Encoded"). For example, a key or value like "AAA?BBB#CCC=DDD%EEE" would be encoded as "AAA%3FBBB%23CCC%3DDDD%25EEE". Dynamic values (i.e. values that may be different every time) that are inserted via a shortcode are automatically encoded.