How can we help you?
Guides, references, and resources for integrating Wildfire's cashback and affiliate commerce platform.
Browse by product
Choose your integration surface
Shopping Portal
Launch a hosted cashback shopping experience. Auth, domain setup, and commission sync.
Desktop Extensions
Add cashback activation to your Chrome extension. Authentication, detection, and compliance.
Mobile Extensions
Implement the Safari mobile extension for iOS cashback activation.
Commissions & Payouts
Commission data, callbacks, payout models, and reconciliation workflows.
API Reference
Endpoints, JSON feeds, link creation, merchant data, and commission sync via API.
Common questions
Quick answers to frequent topics
How do I set up commission data callbacks?
Wildfire supports two models: polling the Commission API and real-time callbacks (webhooks). Set up a callback URL in your Partner Admin dashboard and Wildfire will POST commission events to your endpoint as they occur. Read the full guide →
What is a Tracking Code (TC) and how does it work?
A Tracking Code (TC) is a unique identifier you append to Wildfire-generated affiliate links to associate a purchase with a specific user or session. It is passed through as a URL parameter and returned on commission records so you can credit the right user. Read the full guide →
How do I authenticate users in my browser extension?
Extensions use a token-based flow: your backend authenticates the user, generates a short-lived Wildfire session token, and passes it to the extension. The extension stores the token and includes it on every link-creation or activation request. Read the full guide →
Why didn't my user get credit for a purchase?
The six most common causes: ad blocker interference, cookie deletion before checkout, ITP-blocked third-party cookies, a merchant affiliate program conflict, a missing or incorrect TC parameter, and checkout on a non-tracked subdomain. See all six reasons →
How do I test with sample commission data?
Wildfire provides a public sample data endpoint returning realistic commission records so you can build and test your ingestion pipeline before going live. No credentials required. View sample data →
Which authentication model should I use for the Shopping Portal?
Three models are available: SSO (recommended) for partners with authenticated users, Anonymous for unauthenticated browsing with optional later sign-in, and Embedded Token for mobile webviews. SSO gives the best tracking fidelity. Compare models →
What are the FTC compliance requirements?
FTC guidelines require clear and conspicuous disclosure whenever a material connection exists between a recommender and a merchant. Disclosures must appear before the affiliate link, be in plain language, and not be buried in footers or terms. Full compliance guide →
How do I set up a custom domain (CNAME)?
Add a CNAME record in your DNS pointing your subdomain (e.g.
shop.yourbrand.com) to Wildfire's portal host. Then enter that subdomain in Partner Admin under Domain Settings. SSL is provisioned automatically. CNAME setup guide →