Affiliate tracking

Attribution that stays coherent when real systems retry.

Connect referral codes and links to conversions with explicit identity, idempotency and environment boundaries that survive duplicate delivery.

01ReferralLink or code
02ConversionStable event
03CommissionRule evidence
Stable external IDsExact replay handlingSandbox isolation

Built for operating reality

Clear contracts at every boundary.

01

Accept retries safely

Stable idempotency keys and transaction identities keep duplicate deliveries from becoming duplicate commercial outcomes.

02

Keep attribution explainable

A conversion retains the code, affiliate and rule evidence used when the decision was made.

03

Test without production risk

Publishable and secret test keys stay bound to sandbox environments and separate test activity from live activity.

How a referral becomes an approved payoutFive stages in order: a referral code carrying affiliate identity, a claim carrying the claim time, a conversion carrying an idempotency key, a commission carrying its rule version and monetary basis, and a payout statement carrying the approval identity.affiliate identity01Referral codeOne affiliate onlyclaim time02ClaimBound to an end useridempotency key03ConversionRecorded server-siderule version + basis04CommissionCalculated onceapproval identity05Payout statementApproved, then paidEach stage retains the evidence the next stage depends on.
A referral carries evidence forward at every stage, so a commission can still be explained after the rule that produced it has changed.

One path to money

Validate, attribute and record through explicit contracts.

Use browser-safe code validation where a customer enters a referral, then record the paid outcome from trusted server code. AffiliateRails resolves the authoritative attribution before commission calculation.

Failure semantics

A timeout is unknown—not permission to create another conversion.

Retry the same semantic body and key. The platform returns the original committed result or a bounded conflict when another request is still in progress.

Questions, answered

Know where the boundaries are before you integrate.

How does AffiliateRails prevent duplicate conversions?

A stable external transaction identity and idempotency key bind retries to one canonical conversion result.

Where should conversion recording run?

Record confirmed outcomes from trusted server code. Secret credentials must not be shipped in a browser or mobile bundle.

Can a later code replace an existing attribution?

An existing live attribution remains authoritative; a later supplied code cannot silently replace it.

Build the reliable path

Make every referral decision traceable from click to payout.

Request sandbox access