Prop Firm Affiliate Program Setup: Tracking & Commission Checklist

Set up a prop firm affiliate program by defining which purchases earn commission, how the referring partner is selected, how adjustments are handled and what evidence releases a payment. Put those decisions into written terms, then test the same order journey in your checkout, CRM and affiliate system before recruiting partners.

This guide is for operators building their own firm’s program. It offers a proposed requirements and test checklist, with synthetic examples. Confirm the supported behaviour in your own implementation; these are evaluation requirements rather than a list of verified PropFirmsTech features. For referring founders to PFT itself, see the separate PropFirmsTech referral partnership.

Write the commission policy before choosing the software

Start with an operating brief covering the products, markets, sales channels, payment services and partner types you intend to support. Include evaluation purchases, resets, retries, subscriptions and Instant Funding products where applicable. Decide which are eligible individually.

Use one versioned policy for each campaign. Ask the commercial owner and the people who reconcile orders to resolve the following questions together.

There is no universal commission rate or cookie window that this checklist can establish. Calculate the offer using your own retained order revenue, acquisition costs and programme obligations. A more generous rate can increase the amount owed without proving that the referred sales were incremental or profitable.

Record who can approve a rate change and whether a tier affects only future orders or also recalculates earlier ones. Keep the applicable terms beside each calculation so support can explain a commission months later.

Specify how referral links and coupon codes interact

A trader may click one partner’s link and later enter another partner’s code. Choose the rule before that happens: for example, code priority, eligible last referral, or manual review of a conflicting claim. These are policy options to evaluate, not defaults every affiliate product supports.

Test the actual journeys you expect:

• A referral click followed by purchase in the same browser.
• A return visit before and after the agreed attribution window.
• An eligible code with no earlier tracked referral.
• A different partner’s code after an earlier link click.
• A repeat purchase, reset or renewal under the agreed eligibility rule.
• A customer moving between the marketing site, checkout and account portal.
• Missing tracking permission or unavailable browser storage, handled under your applicable consent policy.

Document which journeys can be recognised and which remain unattributed. Do not promise cross-device or cross-browser attribution without a supported, authorised method and a reproducible test. Define a controlled correction process for disputed referrals; a support note should not silently replace the original evidence.

Keep campaign reporting and commission records connected

Use campaign parameters to analyse acquisition. Google’s campaign URL guidance explains how utm_source, utm_medium and utm_campaign identify traffic in Analytics; utm_content can distinguish placements. Agree a consistent naming convention for partner campaigns.

Use a separate operational record to decide the commission owed. Link the partner, qualifying order, applied policy and adjustments through stable IDs. An acquisition report and a commission statement answer different questions, and their totals may differ because of attribution settings, consent, eligibility and refunds. Record and investigate the difference rather than overwriting either history.

A synthetic campaign URL might contain utm_source=partner_example, utm_medium=affiliate and utm_campaign=launch_example. These are planning labels, not an integration contract. Keep customer contact details and payment credentials out of public tracking URLs.

Follow one order into the commission ledger

Require a supplier demonstration that follows a synthetic order through the complete proposed workflow. Use a test environment or another explicitly authorised test method, and agree expected results before running it.

The commission record should let an authorised reviewer find:

1. The order reference, eligible product, payment confirmation and currency.
2. The selected partner and the referral/code evidence used to select them.
3. The terms version, calculation base, rate and calculated commission.
4. Any refund, dispute, manual adjustment or review hold.
5. Approval, payment-batch membership and the required payment outcome evidence.

Ask how duplicate notifications, delayed results and a retried integration request affect the record. The acceptance result should show one intended commission for one qualifying purchase, with subsequent adjustments linked to it. A retry should be distinguishable from a new eligible order.

State names vary between products. For example, Rewardful’s commission API exposes pending, due, paid and voided states, with links to the associated sale. Use that as an example of fields to inspect, then map the actual states in the product being evaluated. It does not establish provider eligibility or the features of a PFT deployment.

A worked commission calculation

The figures below are synthetic arithmetic, not market rates, a PFT offer, tax guidance or a recommended commission. Assume the written example policy uses the discounted order amount as its commission base, excludes tax and uses a 10% rate.

The outcome depends on the agreed commission base and refund rule. If USD 18 was already paid, record the USD 6 difference and the authorised resolution separately. Do not make a second cash movement or change a partner’s future statement without the agreed process.

Refund handling also depends on the integration and payment state. Rewardful’s documented example recalculates unpaid commissions for partial refunds, while an overpayment after a commission has been paid needs merchant handling. Ask your supplier to demonstrate both cases and explain which changes are automatic and which need review. This is an implementation example, not a recommendation that a particular payment provider accepts your business.

Test software with the same acceptance checklist

Compare products against your operating brief and the required CRM workflows. Record whether each requirement is included, requires configuration or custom work, depends on another service, or is unavailable. Keep evidence references beside the answer.

Use the CRM evaluation scorecard for broader supplier selection. Keep affiliate commission testing as a defined workstream within it, with its own reviewer and acceptance evidence. A claimed feature or a dashboard screenshot alone does not complete a test.

Separate commission approval from payment completion

Agree the evidence required before staff mark an affiliate payment complete. Preserve the approved commission items, currency, batch reference, provider instruction and supported outcome. Investigate missing or conflicting results in an exception queue with a named owner.

Check the selected product and plan: some workflows export a payment file; others provide an additional managed payment service. Rewardful’s payment help page describes an export-and-pay workflow in which the merchant sends the funds and then marks the selected payouts paid. Confirm the settlement responsibility in your own agreement.

Keep affiliate commissions identifiable separately from trader rewards, merchant settlement and provider fees. The payout reconciliation guide provides a related approach to stable references and exceptions for trader rewards; adapt the fields to the obligation being paid.

Give partners an accurate publishing kit

Prepare current product descriptions, programme rules, eligible markets, approved brand assets, working destination links and the agreed offer. Explain how partners report a broken link, expired code, changed rule or disputed commission. Assign an owner to update or withdraw outdated materials.

Provide clear instructions for disclosing the commercial relationship. The US FTC’s endorsement guidance says affiliate relationships should be disclosed clearly and conspicuously near the recommendation; the label “affiliate link” alone may not explain that the publisher earns commission. Review the requirements that apply in your own markets and channels. Disclosure also does not make an unsupported earnings or product claim accurate.

Choose partners by audience relevance, accuracy of previous work and willingness to follow the agreed publishing rules. Start with a manageable pilot, review the actual referred orders and support issues, then decide whether more recruitment is justified. Audience size and clicks alone do not establish sales quality.

Review the program using retained orders and owned exceptions

Use a recurring review that keeps acquisition reporting, the commission ledger and payment evidence visible together. Define each metric before comparing partners:

• Eligible orders and the associated retained revenue, with currency treatment stated.
• Pending, approved/due and paid commissions, plus open adjustments.
• Refunds, disputes and support issues associated with the referred orders.
• Unattributed or conflicting referrals awaiting review.
• Payment exceptions and the time taken to resolve them.

Treat an unusual pattern as a reason to investigate, not automatic proof of fraud. Retain the relevant evidence and apply the published review and appeal process. Evaluate a rate or campaign change against a comparable period and its actual costs; commission payments alone cannot establish incremental acquisition.

Evaluating an affiliate workflow for your firm? Bring your commission policy, one order journey and the unresolved test cases to a PropFirmsTech demo. Confirm the proposed implementation, provider dependencies, permissions and export scope in writing before launch.