Two ways to create links that will attribute commissions to you and your users: Vanity URLs and Expanded URLs
With Wildfire there are a couple of ways to create links that will give credit for commissions to you and your users. There are two main use cases we support:
- Your user wants to share a link to a merchant (any page at a merchant, like a product page) so they can earn when their shared link is used to make a purchase. These links are usually shortened, so they're easy to add to an email, text message, etc. We call these Vanity URLs.
- Everything else, including when users want to earn cashback on their purchases, click through a cashback appeal in search results for products, etc. We call these Expanded URLs.
Note: Once you have a URL of either type you may add a TC parameter to it for tracking other information you want associated with purchases through these links. Learn more about Tracking Code (TC) Parameters.
Note: Both types of URLs assume a branded domain that has been set up for your application like acme.link that points to Wildfire's servers, so we can handle the redirect, tracking, etc. Our default domain name is wild.link and if you haven't set up a branded domain with us yet, you can use wild.link for testing. A branded domain is not required to launch your product, but most of our partners want to brand every part of their product's experience, including redirect URLs.
Because Vanity URLs are shortened, they need to be created "as needed" and so they require making a call against our APIs. You can learn about how to use our API to create a Vanity URL as part of our Postman collection.
If you want to create an Expanded URL, there's no API hit required. You'll build this URL yourself using a couple pieces of data. You just need to know the associated merchant ID and your branded domain.
Here's an example of an Expanded URL that uses wildlink.me as the example domain.
- The c value in this example is the Wildfire Merchant ID.
- The d value is an attributed Wildfire Device. If your product doesn't use devices because it's not a client-side software, just choose any of your devices for this value. You can learn more about how to create a Device for your application in the Postman collection.
- For the url value it should match the Merchant ID referenced in the c value and it should be URL-encoded. Note that the url value is a deep link and not the merchant's homepage. The url parameter is optional. If no deep link is required for your use case (i.e. a user clicking through a directory of merchants) and none is specified, then the link will take the user to a default URL for the merchant (usually the homepage).
You can find more information on how to get Merchant IDs for use in building these URLs from the Merchants and Domains article.