Wildfire’s shopping portal is a hosted website presence that partners can point their users to - wherein the user will be able to browse and discover savings at merchants they like to shop. Users who shop inside this webpage will earn cash back rewards that can be tracked and redeemed either directly through the partners reward platform, or via Wildfire's hosted earnings dashboard.

When a user visits the shopping portal, we need a way to identify the user to affiliate when they activate cash back through the portal, in order to attribute them properly when the sale completes its lifecycle. 

Wildfire supports several variations of implementation:

Authentication details can be found here:

https://kb.wildfire-corp.com/shopping-portal-authentication-guide

The shopping portal can be hosted on a domain or subdomain owned by the partner, or we can provide a domain for you.

For a partner provided sub domain, please see the CNAME implementation guide below:

https://kb.wildfire-corp.com/cname-implementation-guide

Once your users start generating sales, you'll want your system to sync the associated data so that you can show these sales to your users, send push notifications, etc.  

There are two ways to get this commission data: pull them from our API or receive callbacks from our system.  In most cases, you'll want to receive callbacks to keep your system in sync as closely as possible, but you'll also want to hit the API to pull batches of commission in case a callback wasn't successful.  At this time, we do not re-attempt failed callbacks.

https://kb.wildfire-corp.com/article/kfgi-syncing-commission-data-via-api-and-callbacks

In the commission data we provide back to our partners, they will find the user uuid attached to each commission record. If the partner chooses to host the earnings dashboard themselves, they can use the commission data feed to populate earnings data into their own earnings dashboards using the user uuids provided in the feeds to map earnings to each user’s earnings dashboard.

https://kb.wildfire-corp.com/public-commission-sample-data

If you need a set of sample commission data to test against, there are a few options available:

If you already have a Wildfire Application ID and Secret, you can request sample commissions be created for your application.  These sample commissions include a very small set of data with a single record in each possible status.

Alternatively, if you need a larger, more diverse set of data, or if you don't have an application created yet, you can use a sample set of commission data.

Shopping Portal Onboarding Guide

partner_name

partner_name_123

Shopping Portal Authentication Guide

Wildfire Support Center

Main Product KB

CNAME Implementation Guide

Commission History

Performance Summary

Detecting Presence of your Chrome Extension

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