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

Commission History

Wildfire's Partner Admin Tools include information and reporting about transactions. This article outlines all of the available data for each transaction.

The Commissions History report provides a ledger of all transactions reported to Wildfire by merchants. The report is as real-time as possible; as soon as a transaction is reported to Wildfire, it appears in the Commissions History report. Note that some merchants (for example, Walmart) have a nightly batch reporting process. Most merchants report new sales on an hourly basis. Below are the columns in the commission history page however user will be able to choose the columns they want to see by selecting the required ones from Edit Column box.

Column Definitions

  • “ID” is the unique row identifier for the transaction.  Note that a single order may contain several transactions in it.  The Commission History report provides transaction records, not order records, to give the greatest amount of granularity.
  • “Event Date” is the date of the actual transaction as reported by the merchant.  This is normalized for timezone and reported in Pacific Time.
  • “Modified Date” is the last time a record was changed. This usually represents a change in status (i.e., a transaction moving from Pending to Confirmed after we receive payment from the merchant partner). This is normalized for timezone and reported in Pacific Time.
  • “Created Date” is the date when our system ingested the transaction.  The delay between the Event Date and the Created Date represents the lag in reporting by the merchant. This is normalized for timezone and reported in Pacific Time.
  • "Merchant Name" is the name of the online store where the transaction occurred.
  • "Sale Amount" is the total amount of the transaction represented in the merchant's currency. 
  • "Commission" Depending on who pays the user there could be partner commission and user commission.
    • If partner pays the user, there will be only one column:
      • Partner commission: This is the total of the partner's and user's share of earnings from the transaction, as reported by the merchant, minus Wildfire's share.
    • In certain cases where Wildfire pays the user, there will be two columns:
      • Partner commission: This will be the partner's share of earnings, as reported by the merchant, minus Wildfire's share plus user's share.
      • User commission: This will be the user's share of earnings, as reported by the merchant, minus both Wildfire's share and partner's share.
  • "Device ID" Read about IDs here.
  • “Status” indicates where the transaction is in the overall payment lifecycle.  Eligible transactions move from “Pending” to “Ready” to “Paid” by default.
  • List of all statuses:
    • “Pending” is the default state of a new transaction that is expected to earn a commission amount (i.e. not disqualified).
    • “Confirmed” indicates that the merchant has locked the commission and has committed to making a payment for that individual earning. Though this signal indicates a commitment from the merchant, it should be viewed the same as the PENDING status from a risk perspective as no money has changed hands (i.e. the merchant has not paid the network). Note: Confirmed status was added in v4 of commission records.
    • “Ready” indicates that the merchant has paid us for the commission and the payment is just awaiting the next payment cycle (at the beginning of each month).
    • “Paid” indicates that the record has been paid to the partner (and the user, if Wildfire pays users on behalf of the partner), and the transaction should be included in the relevant payment report.
    • “Disqualified” indicates that the transaction was not eligible for earning.  Some merchants don't report these records.  Others (like Ticketmaster) report these records.  An example of a “Disqualified” sale is a pre-sale ticket. Another case where Disqualified is used is when a merchant does not pay for a commission (i.e. a merchant goes out of business). When commissions are determined to be uncollectible, the commission will be moved to a Disqualified status

  • “Order ID” is either the order identifier provided by the merchant or the affiliate network (depending on the affiliate networks). Orders can have multiple transactions with each transaction representing an individual item within an order.
  • “SKU” is the item identified in the order and is not always available (depends on the merchant and network).  Note that if a single order contains multiple items of the same SKU these are almost always reported as a single transaction.
  • "Tracking Code" Read about tracking codes (TC parameters) here: Tracking Code (TC) Parameter.



Updated 10 Mar 2023
Did this page help you?
Yes
No
UP NEXT
Performance Summary
Docs powered by archbee 
TABLE OF CONTENTS
Wildfire's Partner Admin Tools include information and reporting about transactions. This article outlines all of the available data for each transaction.