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 merchant ids can be found in the merchants and domains docid\ dqtk9k9qdr e76dt0g9zy article 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 https //wild link/e?c=5483936\&d=54321\&tc=123e4567 e89b 12d3 a456 426614174000\&url=https%3a%2f%2fwww walmart com see also tracking code (tc) parameter docid\ pl3 phzaubmp4kwtmqukx 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