The Superwall integration is available on the [Pro](🔗) plan.
Superwall can be a helpful integration for optimizing pricing and understanding which paywalls are producing customers with the highest LTV. RevenueCat can automatically send billing, subscription, and revenue metrics to Superwall, a paywall SDK that lets you remotely update every aspect of your paywall.
With our Superwall integration, you can:
Create paywalls on-the-fly without shipping app updates
Determine which paywalls have high trial conversion rates
Find which product & paywall combinations have the highest LTVs
Offer discounts to users who churn
The Superwall integration tracks the following events:
|Event Type||Default Event Name||Description||App Store||Play Store||Amazon||Stripe||Promo|
|Initial Purchase||`||A new subscription has been purchased.||✅||✅||✅||✅||❌|
|Renewal||`||An existing subscription has been renewed or a lapsed user has resubscribed.||✅||✅||✅||✅||❌|
|Cancellation||`||A subscription or non-renewing purchase has been cancelled. See [cancellation reasons](🔗) for more details.||✅||✅||✅||✅||✅|
|Uncancellation||`||A non-expired cancelled subscription has been re-enabled.||✅||✅||✅||❌||❌|
|Non Subscription Purchase||`||A customer has made a purchase that will not auto-renew.||✅||✅||✅||✅||✅|
|Subscription Paused||`||A subscription has been paused.||❌||✅||❌||❌||❌|
|Expiration||`||A 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 Issue||`||There 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 Change||`||A 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.||✅||✅||❌||✅||❌|
|Transfer||`||A transfer of transactions and entitlements was initiated between one App User ID(s) to another.||✅||✅||✅||✅||❌|
## 1. Set Superwall User Identity
In order to associate RevenueCat subscription data with Superwall paywall events, the RevenueCat app user ID must match the Superwall app user ID. You can read more about how Superwall handles user ID’s in their documentation [here](🔗). You can set up a custom app user ID in RevenueCat by following the instructions in our [Identifying Users](🔗) documentation.
## 2. Send RevenueCat events to Superwall
After you've set up the Purchases SDK and Superwall SDK to have the same user identity, you can "turn on" the integration from the RevenueCat dashboard.
Navigate to your project in the RevenueCat dashboard and find the _Integrations_ card in the left menu. Select **+ New**
Choose **Superwall** from the Integrations menu
Add your Superwall Token (Superwall settings > Integrations)
Remember to select _Add Integration_
# Testing the Superwall 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 Superwall event delivered successfully
While still on the Customer View, select the purchase event in the [Customer History](🔗) page and make sure that the Superwall integration event exists and was delivered successfully.
## Check Superwall dashboard for the delivered event
Navigate to your Superwall dashboard > Users and search for the created app user ID. You will see events RevenueCat has dispatched to the Superwall under 'Recent Events'.
# Sample Events
Below are sample JSONs that are delivered to Superwall for each event type.
You've done it!
You should start seeing subscription data from RevenueCat appear in Superwall.