Forward Apple's Notifications from RevenueCat
Keep RevenueCat's URL in App Store Connect and have RevenueCat forward Apple's App Store Server Notifications to Superwall.
Apple sends an app's App Store Server Notifications to one URL per environment. If that URL is RevenueCat's, you don't have to give it up for Superwall to receive the same notifications. RevenueCat can forward each one to a second URL, and that URL can be your app's Superwall URL.
Use this page when App Store Connect already shows a RevenueCat URL under App Information → App Store Server Notifications. If the URL field in App Store Connect is empty, set Superwall's URL there directly instead. See Revenue Tracking.
This is not RevenueCat's Superwall integration. That integration sends RevenueCat's own subscription events to Superwall, and is covered under RevenueCat. Forwarding passes Apple's original notifications through untouched. You can use either one, or both.
Set up forwarding
- 1
Copy your app's Superwall URL
In the Superwall dashboard, open your iOS app's Revenue tracking page and copy the server notification URL. It's the same URL you would paste into App Store Connect.
From the Superwall CLI:
superwall asc notification-url --app <id>The URL contains your app's token. Treat it like a secret.
- 2
Open the iOS app in RevenueCat
In the RevenueCat dashboard, go to your iOS app under Apps, and scroll to Apple Server to Server notification settings.
- 3
Paste the URL and save
Paste the Superwall URL into Apple Server Notification Forwarding URL, then click Save Changes.
Leave the URL in App Store Connect as it is. RevenueCat keeps receiving Apple's notifications, and sends a copy of each to Superwall.
RevenueCat's documentation for this setting is Apple App Store Server Notifications. Check it for which RevenueCat plans include forwarding and which environments it covers.
If the field is already in use
The field holds one URL. If RevenueCat already forwards Apple's notifications to your own server, keep that, and forward from your server to Superwall instead. See Event Forwarding. The request your server receives through RevenueCat is still Apple's own, so forward its body unmodified.
Check that it works
After the next purchase, renewal, or cancellation, an Apple event appears under recent events on the Revenue tracking page. Sandbox purchases count.
Forwarding doesn't choose your revenue provider
Receiving Apple's notifications and choosing which source your revenue metrics count are separate settings. If RevenueCat's Superwall integration is also sending events for this app, both sources arrive and are stored. The revenue provider on the Revenue tracking page decides which one your charts count. See Choosing a revenue provider.
How is this guide?