Browser Extension Authentication

overview before we get started, it's important to understand what a tracking code(tc) is and why it is used when a user installs your extension, we need a way to identify the user to affiliate when they activate cash back through your extension, in order to attribute them properly when the sale completes its lifecycle this is done at wildfire by attaching a tc query parameter at the end of your affiliate url once the sale completes its lifecycle, you can retrieve the value within the tc parameter by going in to the admin tool, and posting the data to your callback url example of a vanity url with a tc parameter https //wild link/lovepop/aiul ai?tc=ee5f1a61 a2f1 4cde be78 293fa339e592 example of an offline vanity url with a tc parameter https //wild link/e?d=0\&c=0\&tc=2d4109a6 c5f6 4028 a206 c26b1379ea82\&url=https //example com authentication details many extensions use different models, whether it's an oauth flow, or logging in directly through the extension they all serve the purpose of having the user identify themselves, and saving that identifier in the extension's storage for this method we will leverage your existing authentication system the extension will send the user to the partner's login page with a uri included as a query parameter example of login url https //www example com/login?uri=chrome extension%3a%2f%2fextensionidhere%2fauth html after the user is successfully authenticated the partner will redirect to the provided uri and include the user's uuid as a query parameter example of redirect url chrome extension //extensionidhere/auth html?uuid=uuidhere at this step the extension will store the uuid and include it as the tracking code on all affiliate link activations when passing a uuid ensure that each uuid is unique to a single user, does not change, and is a valid uuid each individual user should only have one uuid