ο»Ώ

The Iterable integration is available on the [Pro](πŸ”—ο»Ώ) plan.

Iterable can be a helpful integration tool in understanding what stage a customer is in and reacting accordingly. Iterable is a cross-channel platform that powers unified customer experiences and empowers marketers to create, optimize and measure every interaction taking place throughout the customer journey. With Iterable, brands create individualized marketing touch points that earn engagement, solidify trust and galvanize loyal consumer-brand relationships.

With our Iterable integration, you can:

  • Create an event to track unsubscribes that automatically triggers an email to users who cancel.

  • Start a campaign to send users who have been with you for over a certain length of time a discount code for being a loyal customer.

With accurate and up-to date subscription data in Iterable, you’ll be set to turbocharge your users’ engagement ⚑️

# Events

The Iterable integration tracks the following events:

RevenueCat Event TypeIterable Event TypeDefault Event NameDescriptionApp StorePlay StoreAmazonStripePromo
Initial PurchasePurchaserc_initial_purchase_eventA new subscription has been purchased.βœ…βœ…βœ…βœ…βŒ
Trial StartedPurchaserc_trial_started_eventThe start of an auto-renewing subscription product free trial.βœ…βœ…βœ…βœ…βŒ
Trial ConvertedPurchaserc_trial_converted_eventWhen an auto-renewing subscription product converts from a free trial to normal paid period.βœ…βœ…βœ…βœ…βŒ
Trial CancelledCustomrc_trial_cancelled_eventWhen a user turns off renewals for an auto-renewing subscription product during a free trial period.βœ…βœ…βœ…βœ…βŒ
RenewalPurchaserc_renewal_eventAn existing subscription has been renewed or a lapsed user has resubscribed.βœ…βœ…βœ…βœ…βŒ
CancellationCustomrc_cancellation_eventA subscription or non-renewing purchase has been cancelled. See [cancellation reasons](πŸ”—ο»Ώ) for more details.βœ…βœ…βœ…βœ…βœ…
UncancellationCustomrc_uncancellation_eventA non-expired cancelled subscription has been re-enabled.βœ…βœ…βœ…βŒβŒ
Non Subscription PurchasePurchaserc_non_subscription_purchase_eventA customer has made a purchase that will not auto-renew.βœ…βœ…βœ…βœ…βœ…
Subscription PausedCustomrc_subscription_paused_eventA subscription has been paused.βŒβœ…βŒβŒβŒ
ExpirationCustomrc_expiration_eventA subscription has expired and access should be removed. If you have [Platform Server Notifications](πŸ”—ο»Ώ) configured, this event will occur as soon as we are notified (within seconds to minutes) of the expiration. If you do not have notifications configured, delays may be approximately 1 hour.βœ…βœ…βœ…βœ…βœ…
Billing IssueCustomrc_billing_issue_eventThere has been a problem trying to charge the subscriber. This does not mean the subscription has expired. Can be safely ignored if listening to CANCELLATION event + cancel_reason=BILLING_ERROR.βœ…βœ…βœ…βœ…βŒ
Product ChangeCustomrc_product_change_eventA subscriber has changed the product of their subscription. This does not mean the new subscription is in effect immediately. See [Managing Subscriptions](πŸ”—ο»Ώ) for more details on updates, downgrades, and crossgrades.βœ…βœ…βŒβœ…βŒ

For events that have revenue, such as trial conversions and renewals, RevenueCat will automatically record this amount along with the event in Iterable.

# Setup

## 1. Set Iterable User Identity

In order to associate RevenueCat data with the Iterable User Profile, either the RevenueCat `$email` or `$iterableUserId` [Subscriber Attributes](πŸ”—ο»Ώ) should be set in RevenueCat. The preferred method is to send the `$email` attribute. If neither of these fields exist, RevenueCat will fallback to the RevenueCat app user ID. You can read more about Iterable user profiles in Iterable's [Identifying the User](πŸ”—ο»Ώ) documentation.

$iterableUserId character limit

The `$iterableUserId` can be up to 52 characters long.

## (optional) Set Iterable Campaign ID and/or Template ID

To attribute an event to an Iterable Campaign ID and/or Template ID, set the `$iterableCampaignId` and/or `$iterableTemplateId` subscriber attributes through the RevenueCat SDK or [REST API](πŸ”—ο»Ώ).

ο»Ώ

## 2. Send RevenueCat Events to Iterable

After you've set up the Purchase SDK and Iterable SDK to have the same user identity, you can "turn on" the integration and configure the event names from the RevenueCat dashboard.

  1. Navigate to your app in the RevenueCat and find the _Integrations_ card in the left menu. Select **+ New**

ο»Ώ

  1. Choose **Iterable** from the Integrations menu

  2. Add your Iterable [Server-side API key](πŸ”—ο»Ώ) to the **API key** field in RevenueCat

  3. Enter the event names that RevenueCat will send or choose the default event names

  4. Select whether you want sales reported as gross revenue (before app store commission), or after store commission and/or estimated taxes.

Iterable configuration page
ο»Ώ

Iterable configuration page

Iterable sandbox environment

Iterable recommends having a production and sandbox project to separate live and testing environments. You can input both keys in the RevenueCat Iterable settings page.

# Testing the Iterable integration

## Make a sandbox purchase with a new user

Simulate a new user installing your app, and go through your app flow to complete the [sandbox purchase](πŸ”—ο»Ώ).

## Check that the Iterable event delivered successfully

While still on the Customer View, select the purchase event in the [Customer History](πŸ”—ο»Ώ) page and make sure that the Iterable integration event exists and was delivered successfully.

ο»Ώ

## Check Iterable dashboard for the delivered event

Navigate to your Iterable dashboard > Insights > Logs. To find Purchase events navigate to 'Purchases' and to find Custom events navigate to 'Events'. You will see events RevenueCat has dispatched to the Iterable under 'Purchase Log' and 'Events log' respectively.

ο»Ώ

ο»Ώ

# Sample Events

Below are sample JSONs that are delivered to Iterable for events.

ο»Ώ
ο»Ώ

# Considerations

## Refunds

Revenue for Iterable campaign reporting will not be accurate due to refund events. You can build custom workflows around a "refund" event and independently calculate the total revenue refunded for your campaigns.