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 Purchases SDK with AppsFlyer for precise revenue tracking

With our AppsFlyer integration you can:

  • Accurately track subscriptions generated from AppsFlyer campaigns, allowing you to know precisely how much revenue your campaigns generate.
  • Send trial conversions and renewals directly from RevenueCat to AppsFlyer, allowing for tracking without an app open.
  • Continue to follow your cohorts for months to know the long tail revenue generated by your campaigns.

1. Install Appsflyer SDK

Before RevenueCat can integrate with Appsflyer, your app should be running the latest Appsflyer SDK. Refer to the Appsflyer developer documentation for the latest installation instructions.

2. Send device data to RevenueCat

The Appsflyer integration requires some device-specific data. RevenueCat will only send events into Appsflyer if the below Subscriber Attributes keys have been set for the device.





Appsflyer Id. The unique Appsflyer identifier for the user

✅ (required)


iOS advertising identifier UUID

✅ (recommended)


Google advertising identifier

✅ (recommended)


Android device identifier

✅ (recommended)


iOS vender identifier UUID

✅ (recommended)


The IP address of the device

❌ (optional)

These properties can be set manually, like any other Subscriber Attributes, or through the helper methods to collectDeviceIdentifiers() and setAppsflyerId().

import AdSupport
// ...
Purchases.configure(withAPIKey: "public_sdk_key")
// ...

// Automatically collect the $idfa, $idfv, and $ip values

// Set the Appsflyer Id
Purchases.configure(this, "public_sdk_key")
// Automatically collect the $gpsAdId, $androidId, and $ip values
// Set the Appsflyer Id

You should make sure to set attributes after the Purchases SDK is configured, and before the first purchase occurs. It's safe to set this multiple times, as only the new/updated values will be sent to RevenueCat.


Device identifiers with iOS App Tracking Transparency (iOS 14.5+)

If you are requesting the App Tracking permission through ATT to access the IDFA, you can call .collectDeviceIdentifiers() again if the customer accepts the permission to update the $idfa attribute in RevenueCat.


Import AdSupport Framework (iOS)

The AdSupport framework is required to access the IDFA parameter on iOS. Don't forget to import this into your project.


Remove any client-side purchase tracking

Make sure to remove all client-side tracking of revenue. Since RevenueCat will be sending events for all revenue actions, tracking purchases with the Appsflyer SDK directly can lead to double counting of revenue in Appsflyer.

(Optional) Send campaign data to RevenueCat

RevenueCat itself is not an attribution network, and can't determine which specific ad drove an install/conversion. However, if you're able to collect this information from another source, such as Appsflyer, it's possible to attach it to a user in RevenueCat using Subscriber Attributes as well.
The below reserved key names can be used to optionally attach campaign data to a user. This data will then be sent through to other downstream analytics integrations and accessible via APIs and webhooks.








3. Send RevenueCat events into AppsFlyer

After you've set up the Purchase SDK to send attribution data from AppsFlyer to RevenueCat, you can "turn on" the integration and configure the event names from the RevenueCat dashboard.

  1. Navigate to your app in the RevenueCat dashboard and choose 'AppsFlyer' from the integrations menu
  2. Add your developer key and app Ids for iOS and/or Android
  3. Enter the event names that RevenueCat will send or choose the default event names
  4. Select whether you want RevenueCat to report proceeds (after app store cut) or revenue (gross sales)
AppsFlyer configuration screenAppsFlyer configuration screen

AppsFlyer configuration screen

4. Testing the Appsflyer integration

You can test the Appsflyer integration end-to-end before going live. It's recommended that you test the integration is working properly for new users, and any existing users that may update their app to a new version.

Add a sandbox API key in the RevenueCat dashboard

Before you test the integration, make sure you have an Appsflyer API key set in the "Sandbox developer key" field in RevenueCat. This is required if you want the integration to trigger for sandbox purchases.

Make a sandbox purchase with a new user

Simulate a new user installing your app, and go through your app flow to complete a sandbox purchase.

Check that the required device data is collected

Navigate the the Customer View for the test user that just made a purchase. Make sure that all of the required data from step 1 above is listed as attributes for the user.

Check that the Appsflyer event delivered successfully

While still on the Customer View, click into the test purchase event in the Customer History and make sure that the AppsFlyer integration event exists and was delivered successfully.


AppsFlyer reports events by install date

Under the Events view, AppsFlyer displays in-app events according to the install date of the user. This means if you select Jan 1 through Jan 8, you'll see the events that were performed by users who installed within the selected date range.

Refer to AppsFlyer's docs for more information about this.


You've done it!

You should start seeing events from RevenueCat appear in AppsFlyer

Updated 3 months ago


Integrate Purchases SDK with AppsFlyer for precise revenue tracking

Suggested Edits are limited on API Reference Pages

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