Wildfire APIs

Tracking Code (TC) Parameter

2min

Wildfire Systems generates a “device ID” as a way to keep track of which client software generated a given sale/commission. But if you'd prefer to pass along your own attribution reference (i.e., an encoded user ID) you can add a TC parameter to any URL.

The following shows an example of a short/vanity URL with a TC parameter appended to it:

Text


The Wildfire platform will take the value sent to us in the TC parameter and store it. Wildfire then generates a compliant value to pass along to the affiliate network. Every affiliate network has different requirements and limitations for what are allowed values for attribution IDs.  Wildfire removes this restriction, so you don't have to worry about it. You can pass any value of any length in the TC parameter (the only limit is a browser's character limit for the entire URL, which is about 2000 characters).

The same value you send in this TC parameter will be returned as part of the commission record (via the callback or API), described as TrackingCode. If no TC parameter was sent as part of the original link, then the TrackingCode value in the commission record will be omitted.

Note: The TrackingCode (TC) value can contain multiple key-value pairs so long as this value is encoded properly.



For example, a valid URL may look something like this: https://wild.link/walmart/abc123?tc=user:123,promo:abc where a user and a promo value have been encoded into a single TC value. The pairs are separated by a , in this case, but they could be separated by a / or any other character that doesn't have a special meaning in the URL scheme. You cannot use an & for separating the key-value pairs, for example, as this character has a special meaning for separating query parameters.



The following is not a valid encoding: https://wild.link/walmart/abc123?tc=user:123;promo:abc as the semicolon ; has a special meaning in URLs (acting like a & to separate query parameters).