website logo
WildlinkWildfire-corpFeaturesNetworkCompanyPricingResourcesContact us
⌘K
Wildfire Systems Knowledgebase
Partner Admin
Commission History
Performance Summary
Desktop Solutions
Browser Extension Authentication
Implementing Wildfire Coupons into an existing Chrome Extension
How to Implement OAuth in a Chrome Extension
Direct tracking code injection to extension
Mobile Solutions
Android MCA SDK Guide
Android MCA Permission Compliance
How to implement the Mobile Safari Extension
Wildfire APIs
Country filtering and multiple applications
Public Commission Sample Data
Getting to know the Wildfire JSON Data Feeds
Creating links
Commission History
Gift Card
Merchants and Domains
Merchant Images
Tracking Code (TC) Parameter
Syncing Commission Data via API and Callbacks
Working with Wildfire Coupon Data
Getting started with the Wildfire API Postman collection
FAQ and General Resources
Jump Track
Best Practices
6 Reasons Why a User Might Not Get Credit for Earning
FTC Compliance Overview
Stand-Down Policy Compliance
Docs powered by archbee 
3min

Tracking Code (TC) Parameter

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
|
https://wild.link/walmart/abc123?tc=user12345


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.





Updated 03 Mar 2023
Did this page help you?
Yes
No
UP NEXT
Syncing Commission Data via API and Callbacks
Docs powered by archbee 
TABLE OF CONTENTS