For SaaS teams

Build an affiliate programme around durable subscription identities.

Connect referred accounts, paid outcomes, renewals and refunds without making the browser or a mutable email address the source of financial truth.

01ReferralLink or code
02ConversionStable event
03CommissionRule evidence
Account-level identityRetry-safe conversionRefund-aware

Built for operating reality

Clear contracts at every boundary.

01

Use your existing account identity

Pass the stable application user ID your product already owns instead of creating another marketing identity silo.

02

Record confirmed revenue

Create conversions from the trusted system that receives checkout or billing confirmation.

03

Keep renewals and refunds coherent

Subscription and reversal events retain provider identity so repeat delivery remains one lifecycle.

SaaS acquisition

Connect the referral before the paid event arrives.

Validate or claim the referral at the product boundary, associate it with a stable account identity, then let trusted billing confirmation drive the commercial outcome.

Revenue lifecycle

Treat a subscription as a sequence, not a one-off click.

Trials, paid conversions, renewals and refunds can be tied back to provider and application identities without allowing a later URL parameter to rewrite attribution.

Questions, answered

Know where the boundaries are before you integrate.

Does AffiliateRails need customer email addresses?

Use a stable application user ID owned by your product. Marketing attribution should not depend on a mutable email address.

When should a SaaS conversion be recorded?

Record the outcome after your trusted billing system confirms the event, using its stable transaction identity.

What if the billing provider retries a webhook?

Reuse the same provider event and idempotency identity so the retry resolves to the canonical outcome.

Build the reliable path

Make every referral decision traceable from click to payout.

Request sandbox access