Using TelemetryDeck with RevenueCat

RevenueCat is a service that helps you process payments and in-app purchases on iOS, Android, and the web. It’s a great way to add monetization to your app.

RevenueCat pairs excellently with TelemetryDeck – use TelemetryDeck to improve your users’ flow through your application, and then present them with convenient In-App-Purchase offers.

With this integration, you can import your RevenueCat events into TelemetryDeck, and see everything on one dashboard. We’ll be using RevenueCat’s Webhooks feature to pass on their data to TelemetryDeck.

Installing RevenueCat and TelemetryDeck

First, we have to integrate both TelemetryDeck and RevenueCat into your app. You can find guides for both here:

1. Install and set up TelemetryDeck
2. Install and set up RevenueCat

Configuring the RevenueCat SDK

RevenueCat has a concept of user attributes. Our goal is to set two new user attributes for our RevenueCat users that will make TelemetryDeck recognize them as the same users it is already managing.

• $telemetryDeckAppId: This attribute should be set to your TelemetryDeck App ID, the same one you pass into the TelemetryDeck SDK for initialization.
• $telemetryDeckUserId: This attribute needs to be the already-hashed user identifier that TelemetryDeck is using.

iOS

Here’s how to set up TelemetryDeck and RevenueCat on iOS. The setup process is similar for other platforms.

// 1.
// Initialize TelemetryDeck with your app ID
let telemetrydeckAppID = "AAAAAAAA-BBBB-CCCC-DDDD"
let telemetryDeckConfig = TelemetryDeck.Config(
    appID: telemetrydeckAppID,
    salt: "MY_SECRET_SALT" // optional but recommended
)
TelemetryDeck.initialize(config: telemetryDeckConfig)

// 2.
// Manually set a default user for TelemetryDeck
// We're using IFV here, but you can also use
// e.g. an email address or any other identifying property
let myUserID = UIDevice.current
    .identifierForVendor?.uuidString
    ?? "unknown user"
TelemetryDeck.updateDefaultUserID(to: myUserID)

// 3.
// Set up RevenueCat with your TelemetryDeck App ID
// and the pre-hashed TelemetryDeck User ID
Purchases.configure(withAPIKey: "my_revenuecat_api_key")
Purchases.shared.attribution.setAttributes([
    "$telemetryDeckUserId": TelemetryManager.shared
        .hashedDefaultUser
        ?? "no-user",
    "$telemetryDeckAppId": telemetrydeckAppID
])

Here’s what’s going on in the above example

1. First we set up TelemetryDeck as described in the setup guide. If you already have set up TelemetryDeck, you can leave your setup unchanged.
2. We then manually set a default user for TelemetryDeck. This allows us to later retrieve a hashed version of the user identifier.
3. Finally, we configure RevenueCat and set up the necessary user attributes.

Setting up the Webhook

Now we need to tell RevenueCat to send copies of all events over to TelemetryDeck. We’re using a Webhook Integration to do this.

• Navigate to your RevenueCat Project
• In the left sidebar, click Integrations
• Select Webhooks
• Select Add new Configuration
• Give the new WebHook a name like Send to TelemetryDeck
• Set the Webhook URL to https://nom.telemetrydeck.com/v2/webhooks/revenuecat/
• Leave all other settings as the default and click Save

And you’re done. RevenueCat events should now arrive and be mixed in with your TelemetryDeck signals. Note that we’re automatically marking RevenueCat Sandbox events as “Test Mode”.