Apple Retention Messaging
Configure Apple's Retention Messaging API in Superwall, including the callback URL, messages, default message mappings, and real-time configurations.
In the Retention Messaging section within Integrations, you can configure Apple's Retention Messaging API for subscribers who intend to cancel.
Apple must first approve your app for the Retention Messaging API before you can use this integration in production — Superwall cannot grant this access.
After Apple has approved your app, contact Superwall Support to enable full message configuration in the dashboard. Until then, only the callback URL is available.
Apple Callback URL
The dashboard generates a callback URL using your app's public API key:
https://retention-messaging-api.superwall.com/v1/message/<public-api-key>
Use this as the Retention Messaging URL in App Store Connect for your app.
- Copy the callback URL from Retention Messaging in Superwall.
- Request access from Apple for the Retention Messaging API.
- In App Store Connect, open your app's subscription settings and paste the URL into the Retention Messaging URL field.
- After Apple approves access, contact Superwall support to enable message configuration in the dashboard.
The callback URL does not change when you switch between Production and Sandbox in the dashboard. The environment selector applies to messages, default mappings, and real-time configurations.
Messages
Use Messages to create and manage the retention message payloads that Superwall sends to Apple.
These messages are the records referenced by Default Messages and Real-time Configurations.
Create a message
When you create a message, the dashboard asks for:
Name: internal label shown in Superwall.Environment:ProductionorSandbox.Locale: for example,en-US.HeaderBodyAlt Text(optional)Image Identifier(optional)
The messages table shows the Apple review state for each message: PENDING, APPROVED,
REJECTED, or UNKNOWN.
Create the message for the correct environment and locale before adding a default mapping or real-time configuration that references it — the message picker only shows matches for the selected environment and locale.
Default Messages
Use Default Messages to define fallback message mappings by product and locale.
Use a default mapping when you want Apple to show a specific message whenever there is no matching real-time configuration for that product.
Create a default mapping
To create a default mapping:
- Choose the environment.
- Select one or more products.
- Enter the locale.
- Choose a message. The picker only shows messages for the same environment and locale.
- Save the mapping.
The dashboard lets you create mappings for multiple products in one action.
The UI disables products that already have a default mapping in the selected environment. If a product is unavailable, delete its existing mapping before creating another one.
Real-time Configurations
Use Real-time Configurations to map product and locale combinations to the retention message behavior Apple should use at runtime.
Supported configuration types
Two real-time configuration types are supported:
Message: Apple uses the linked retention message.Alternate Product: Apple uses the linked message together with an alternate product.
Create a real-time configuration
To create a configuration:
- Enter a name.
- Choose the environment.
- Select one or more products.
- Enter the locale.
- Choose the type.
- If the type is
Alternate Product, choose the alternate product. - Choose a message. The picker only shows messages for the same environment and locale.
- Create the configuration.
The dashboard lets you create configurations for multiple products in one action.
The UI disables products that already have a real-time configuration in the selected environment. If a product is unavailable, delete its existing configuration before creating another one.
If a real-time configuration exists for a product, Apple uses that behavior instead of the default message mapping. When no real-time configuration applies, Apple falls back to the default message.
How is this guide?
Apple Search Ads
Integrate Apple Search Ads with Superwall. View details on users acquired via search ads, visualize conversions from Apple Search Ads in charts, and create powerful campaign filters to target users using search ad data. Search ad integration requires 3.12.0 of the Superwall SDK or higher.
Facebook Pixel
The Meta Conversion API integration sends subscription lifecycle events from Superwall directly to Facebook's server-side Conversion API. This enables accurate attribution for Facebook and Instagram ad campaigns, optimizes ad delivery for subscription events, and provides reliable tracking that isn't affected by browser privacy restrictions or ad blockers.