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 
6min

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:

Text
|
https://wild.link/lovepop/AIuL-AI?tc=ee5f1a61-a2f1-4cde-be78-293fa339e592


Example of an offline vanity URL with a TC parameter:

Text
|
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

Text
|
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

Text
|
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.

Sequence Diagram
Sequence Diagram




Updated 03 Mar 2023
Did this page help you?
Yes
No
UP NEXT
Implementing Wildfire Coupons into an existing Chrome Extension
Docs powered by archbee 
TABLE OF CONTENTS
Overview
Authentication Details