RevenueCat integration

Carry subscription events into one idempotent referral lifecycle.

Connect RevenueCat app-user and subscription identities to AffiliateRails so purchases, renewals and refunds retain provider-backed event evidence.

01ReferralLink or code
02ConversionStable event
03CommissionRule evidence
Raw-body verificationProvider event dedupeSubscription timeline

Built for operating reality

Clear contracts at every boundary.

01

Verify the source event

Authenticate inbound webhook material before trusting the application user, subscription or transaction fields it carries.

02

Retain provider identities

Provider event, transaction and subscription IDs stay attached to the canonical commercial lifecycle.

03

Process redelivery safely

Repeat delivery of the same event resolves through dedupe and idempotency instead of creating a second conversion.

Connection model

Map the provider user to the product user you already trust.

Use a stable app-user identifier shared by the product and RevenueCat. AffiliateRails keeps the provider event and subscription timeline environment-scoped.

Lifecycle handling

Keep purchases, renewals and refunds connected.

The integration translates authenticated provider events into the explicit conversion and reversal operations used by commission and reporting workflows.

Questions, answered

Know where the boundaries are before you integrate.

Which user identity should be shared?

Use the stable app-user identifier that your product and RevenueCat already agree on, rather than an email or device fingerprint.

What happens on webhook redelivery?

The same provider event identity is reused, allowing the integration to return or retain the canonical recorded result.

Are RevenueCat test events isolated?

Provider connections and accepted events remain bound to the selected AffiliateRails application environment.

Build the reliable path

Make every referral decision traceable from click to payout.

Request sandbox access