Ask what happens when it fails
Every platform handles the happy path. Ask what a duplicate webhook produces, what a refund after payout does, and what a commission rule change does to commissions already accrued.
Evaluation guide
Most affiliate platforms demo identically. These are the questions whose answers differ, why each one matters, and what a good answer sounds like — useful whichever platform you end up choosing.
Built for operating reality
Every platform handles the happy path. Ask what a duplicate webhook produces, what a refund after payout does, and what a commission rule change does to commissions already accrued.
Whether payouts draw from your balance or the vendor’s changes your exposure, your reconciliation and who your affiliates are legally paid by. Ask before pricing.
Attribution history, commission evidence and affiliate identities should be exportable. A platform that cannot export the evidence behind a commission is a platform you cannot leave.
Tracking
Browser-side tracking is blocked by ad blockers and privacy defaults, and it cannot describe a renewal that happens months later with no browser present. Ask whether conversions can be recorded server-side from trusted code, and whether a later referral code can silently overwrite an existing attribution.
Testing
Test credentials, codes, conversions and commissions should be bound to a separate application environment, so a integration test can never create a real payable. Ask to see the boundary rather than the feature list.
Questions, answered
Ask what happens when the same conversion is delivered twice. The answer tells you whether the platform has an identity model or a database insert, and everything else follows from that.
Less than it used to. Browser storage is increasingly unreliable, so a long cookie window is a weaker guarantee than a durable server-side claim tied to a stable customer identity.
A rule change should apply to future decisions while existing commissions retain the rule version and monetary basis that produced them. If changing a rule silently rewrites history, the reporting cannot be trusted.
Build the reliable path