Verify the source event
Authenticate inbound webhook material before trusting the application user, subscription or transaction fields it carries.
RevenueCat integration
Connect RevenueCat app-user and subscription identities to AffiliateRails so purchases, renewals and refunds retain provider-backed event evidence.
Built for operating reality
Authenticate inbound webhook material before trusting the application user, subscription or transaction fields it carries.
Provider event, transaction and subscription IDs stay attached to the canonical commercial lifecycle.
Repeat delivery of the same event resolves through dedupe and idempotency instead of creating a second conversion.
Connection model
Use a stable app-user identifier shared by the product and RevenueCat. AffiliateRails keeps the provider event and subscription timeline environment-scoped.
Lifecycle handling
The integration translates authenticated provider events into the explicit conversion and reversal operations used by commission and reporting workflows.
Questions, answered
Use the stable app-user identifier that your product and RevenueCat already agree on, rather than an email or device fingerprint.
The same provider event identity is reused, allowing the integration to return or retain the canonical recorded result.
Provider connections and accepted events remain bound to the selected AffiliateRails application environment.
Build the reliable path