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

Tenjin

Integrate Purchases SDK with Tenjin for precise revenue tracking

With our Tenjin integration you can:

  • Accurately track subscriptions generated from Tenjin campaigns, allowing you to know precisely how much revenue your campaigns generate.
  • Send trial conversions and renewals directly from RevenueCat to Tenjin, 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. Send device data to RevenueCat

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

Key

Description

Required

$idfa

iOS advertising identifier UUID

✅ (iOS only)

$gpsAdId

Google advertising identifier

✅ (Android only)

$idfv

iOS vender identifier UUID

❌ (optional)

$androidId

Android device identifier

❌ (optional)

$ip

The IP address of the device

❌ (optional)

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

import AdSupport
// ...
Purchases.configure(withAPIKey: "public_sdk_key")
// ...
Purchases.shared.collectDeviceIdentifiers()
//..
Purchases.configure(this, "public_sdk_key")
//..
Purchases.sharedInstance.collectDeviceIdentifiers()

You should make sure to call collectDeviceIdentifiers() after the Purchases SDK is configured, and before the first purchase occurs. It's safe to call 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.

(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 Tenjin, 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.

Key

$mediaSource

$campaign

$adGroup

$ad

$keyword

$creative

❗️

Remove SDK 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 Tenjin SDK directly can lead to double counting of revenue in Tenjin.

2. Send RevenueCat events into Tenjin

After you've set up the Purchase SDK to send attribution data from Tenjin 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 'Tenjin' from the integrations menu
  2. Add your Tenjin developer API key
  3. Select whether you want RevenueCat to report proceeds (after app store cut) or revenue (gross sales)

Tenjin configuration screen

📘

About revenue discrepancies

RevenueCat must have the IDFA or ADID of the user at the time an event occurs in order to send it to Tenjin. This can result in drastically lower revenue metrics in Tenjin vs. RevenueCat since some users opt-out of ad tracking or don't have IDFA/ADID, which means some of your total revenue won't be tracked by Tenjin. Don't be alarmed! If events are being sent successfully in testing and for some of your users in production, then the integration is working as intended to pair subscription revenue with campaign performance.

👍

You've done it!

You should start seeing events from RevenueCat appear in Tenjin. Woohoo!

Updated about a month ago


Tenjin


Integrate Purchases SDK with Tenjin 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.