Creating links - Wildfire Support Center
Creating links
Overview
With Wildfire, you can create tracking links that ensure commissions are attributed to you and your users. All such links use the same standard format described below.
Creating a Link
Creating a Wildfire tracking link does not require an API call. You simply construct the URL using two required parameters:
- Merchant ID (c) – The Wildfire Merchant ID.
- Device ID (d) – The attributed Wildfire Device ID.
You can create a Device ID via the Wildfire API (see the Postman collection for details).
Example:
https://wild.link/e?c=MERCHANT_ID_HERE&d=WF_DEVICE_ID_HERE&url=https%3A%2F%2Fwww.walmart.com
Required Parameters
| Parameter | Description |
|---|---|
| c | Wildfire Merchant ID |
| d | Wildfire Device ID (attributed device). If your product isn’t client-side (e.g. you're building an offer wall), you may reuse any of your device IDs for this value. |
Optional Parameters
Optional parameters add enhanced functionality to links. Keep in mind that most browsers only accept URLs up to 2048 characters, so the deep link URL (if included) should always appear last.
1. Tracking Code (tc)
A Tracking Code parameter can store additional metadata or identifiers related to the purchase or user. It is strongly recommended to include a user reference that is consistent across platforms.
Example:
See also: Tracking Code (TC) Parameter . While TC values can be used for tracking anything you want, it's important to include a user reference that consistently represents your user across all your platforms. Using a UUID value to represent a user across platforms allows Wildfire to help with performance analysis and unit economic analysis while keeping your user's personal information private. You should not pass an email address, phone number, etc. in the TC value as this is private information that Wildfire does not want access to.
Unique User Identifier
Best Practice: Use a UUID format to represent the user rather than personal data (email, phone, etc.). This ensures privacy while allowing for accurate performance and economic analysis.
UUID Format Example:
123e4567-e89b-12d3-a456-426614174000
For further information on UUIDs, consult this resource.
2. URL Parameter (url)
You can include a url parameter to direct users to a specific product or page at the merchant. The domain must match the merchant referenced in the c parameter and should be URL-encoded.
If omitted, the link will default to the merchant’s default URL (usually the merchant's homepage).
3. Preferred Country (pc)
A Wildfire application has a default country associated with it, but you can override this by including a pc parameter to specify the merchant country.
This is useful for global partners or multi-country applications (e.g., showing Walmart.ca to Canadian users).
Example:
https://wild.link/e?c=5483936&d=1912282&pc=CA&url=https%3A%2F%2Fwww.walmart.com%2Fcp%2Fca
Notes:
- The pc value is not case sensitive.
- Use only valid ISO 3166-1 alpha-2 country codes.
- If an invalid code is provided, Wildfire will automatically select the program with the highest available commission, which may not match the desired country.
Summary
To create a Wildfire tracking link:
- Start with the base domain: https://wild.link/e
- Add the c (Merchant ID) and d (Device ID) parameters.
- Optionally include:
- tc for tracking user (UUID recommended) or campaign data
- url for deep linking to a specific page
- pc for country override
Following this format ensures commissions are properly attributed and user journeys are tracked accurately across all platforms.
Updated29 Jun 2026