Build With RevenueCat

Build a customized mobile subscription business with RevenueCat. We do the heavy lifting of normalizing subscribers from any source and maintain a single source of truth for subscription status, so you can get back to building your app.

RevenueCat is a powerful, secure, reliable, and free to use in-app purchase server with global support. All you need to get started is an API key.

Get Started    REST API Endpoints


Integrate and collect attribution data with Purchases SDK


Attribution collection is only available on paid plans.

It’s important to know which marketing efforts are most effective at acquiring new users and keeping them engaged. RevenueCat can integrate with your attribution provider to track how much revenue was driven by each source and ad network.

Providing Attribution Data to RevenueCat

RevenueCat can help you understand precisely how much revenue your campaigns generate even if users stop opening up the app. By continuing to follow your cohorts whether they're active users or not, you'll know the long tail revenue generated by your campaigns.

Most attribution SDKs provide a way to report revenue from the device, but this completely fails to capture recurring revenue that occurs while a user is not using the app. With RevenueCat, you receive a full picture.

How does RevenueCat work with your attribution provider?

RevenueCat itself is not an attribution network, and by itself cannot inform you which ad campaigns are driving revenue. What RevenueCat does is take the subscription lifecycle events it knows about, and informs your attribution network of the users that are purchasing. It's the networks job to then tie these users back to the campaigns that drove them to install.

Supported Networks

RevenueCat can send revenue events into the following attribution networks:

If you use an attribution provider not listed here, contact us.

Updated 3 months ago


Integrate and collect attribution data with Purchases SDK

Suggested Edits are limited on API Reference Pages

You can only suggest edits to Markdown body content, but not to the API spec.