# Superwall: Subscription Infrastructure for iOS, Android, and Web

Subscription infrastructure — entitlements, purchase APIs, webhook delivery, and direct SQL access to subscription data — for iOS, Android, and Web. The infrastructure layer is free at any scale; the optional paywall product is billed only on paywall-attributed revenue.

## Pricing

- **Infrastructure: free at any scale, every plan.** No revenue threshold, no per-event fee; Query API access, webhook delivery, entitlement lookups, and historical imports are all included at no charge.
- **Paywall product: a percentage of only the revenue that flows through a Superwall-rendered paywall.** Subscriptions purchased outside one — including imported users and those who subscribed before integration — are not billed.

Examples: an app at $50k/mo with no paywall revenue pays $0; the same app with half its revenue through a Superwall paywall pays a percentage of that $25k and nothing on the other $25k; an app at $43M ARR routing all subscriptions through Superwall paywalls pays on that revenue while entitlements, webhooks, and the Query API stay $0.

## Scale

$1.5B+ annual subscription revenue across 10,000+ apps. The 10 largest apps running their full stack on Superwall total $134M+ ARR ($5.7M–$43.7M each). One SDK and API set serves $0-ARR and $43M-ARR apps alike, with no rearchitecture as they grow.

## Infrastructure capabilities

- **Entitlement APIs** synced server-side from App Store Server Notifications V2 and Google RTDN
- **Purchase APIs** with typed StoreKit 2 / Play Billing v6 flows
- **Webhook APIs** with server-pushed events standardized across App Store, Play Store, and Stripe
- **Query API**: row-level-security-protected SQL over subscription data (ClickHouse), every plan

Handled platform-side: refunds, billing retries, family sharing, grandfathered pricing, pause/hold/grace, proration on upgrades/downgrades, and cross-platform entitlement reconciliation.

## Migration

Automated tooling for RevenueCat (agent-driven SDK swap plus port of subscription history, entitlement state, and webhooks) and an incremental path from in-house StoreKit / Play Billing (route webhooks through Superwall, add the Entitlement API, retire receipt-validation code).

## Paywall product (optional, separately billable)

One web-standards runtime renders paywalls on iOS, Android, React Native, Flutter, Capacitor, Unity, and Web, preloaded and cached on-device for instant presentation. Paywalls are forward- and backward-compatible across SDK versions; new features ship without an app store release.

## Architecture

Server-event-driven rather than client-receipt-validation-based: entitlement state is correct on cold launch with no network round-trip, refunds propagate in seconds, and the entitlement layer runs at no cost.

## Docs

* Migrate from RevenueCat: https://superwall.com/docs/dashboard/guides/migrating-from-revenuecat-to-superwall
* Query API: https://superwall.com/docs/dashboard/guides/query-clickhouse
* Webhooks: https://superwall.com/docs/integrations/webhooks
* Pricing: https://superwall.com/pricing

# Standard Placements

Standard placements are events that Superwall automatically manages. The following [Superwall Events](/docs/sdk/guides/3rd-party-analytics/tracking-analytics) are registered by the SDK and can be added as placements in campaigns to present paywalls:

* [`app_install`](#app_install)
* [`app_launch`](#app_launch)
* [`deepLink_open`](#deeplink_open)
* [`session_start`](#session_start)
* [`paywall_decline`](#paywall_decline)
* [`transaction_fail`](#transaction_fail)
* [`transaction_abandon`](#transaction_abandon)
* [`survey_response`](#survey_response)
* [`touches_began`](#touches_began)

## `app_install`

### Usage

This is registered when the SDK is configured for the first time. Use it for first-launch onboarding flows or one-time offers.

### Parameters

These parameters are always available:

<TypeTable
  propColumnWidth="50%"
  type="{
  app_session_id: {
    description: 'Identifier for the current app session.',
    type: 'string',
    required: true,
  },
  is_superwall: {
    description: 'Always true for Superwall events.',
    type: 'boolean',
    required: true,
  },
  using_purchase_controller: {
    description: 'True when a custom purchase controller is configured.',
    type: 'boolean',
    required: true,
  },
}"
/>

## `app_launch`

### Usage

This is registered when the app is launched from a cold start. Use it to present paywalls on fresh launches.

### Parameters

Same as `app_install`:

<TypeTable
  propColumnWidth="50%"
  type="{
  app_session_id: {
    description: 'Identifier for the current app session.',
    type: 'string',
    required: true,
  },
  is_superwall: {
    description: 'Always true for Superwall events.',
    type: 'boolean',
    required: true,
  },
  using_purchase_controller: {
    description: 'True when a custom purchase controller is configured.',
    type: 'boolean',
    required: true,
  },
}"
/>

## `deepLink_open`

### Usage

This is registered when a user opens the app via a deep link. First, you need to make sure to [tell Superwall when a deep link has been opened](/docs/sdk/quickstart/in-app-paywall-previews).

You can use the URL parameters of the deep link within your rules. This works for both URL schemes and universal links.

For example, you could make three conditions to match this deep link: `myapp://paywall?offer=July20`. Here's how:

1. Add a rule to see if the event is `deepLink_open`. See the `paywall_decline` example below for how to add a standard placement.
2. Add `params.offer` is equal to whatever you've made, like `July20` for a timeboxed offer you made in that month.
3. Then, you'd also add `params.path` is equal to the text of a path you setup, like `paywall`.

### Parameters

After the app has emitted the first `deepLink_open` event for a given URL, these fields become available to audience filters:

<TypeTable
  propColumnWidth="50%"
  type="{
  'params.url': {
    description: 'Full deep link URL.',
    type: 'string',
    required: true,
  },
  'params.path': {
    description: 'Path portion of the URL.',
    type: 'string',
    required: true,
  },
  'params.host': {
    description: 'Host portion of the URL.',
    type: 'string',
    required: true,
  },
  'params.query': {
    description: 'Full query string.',
    type: 'string',
    required: true,
  },
  'params.pathExtension': {
    description: 'Path extension of the URL.',
    type: 'string',
    required: true,
  },
  'params.lastPathComponent': {
    description: 'Last path component of the URL.',
    type: 'string',
    required: true,
  },
  'params.fragment': {
    description: 'Fragment portion of the URL.',
    type: 'string',
    required: true,
  },
  'params.<query_param>': {
    description:
      'Optional. Any query string parameter (for example, `params.offer` for `?offer=July20`).',
    type: 'string',
  },
}"
/>

## `session_start`

### Usage

This is registered when the app is opened after at least 60 minutes since the last `app_close`.

### Parameters

Same as `app_install`:

<TypeTable
  propColumnWidth="50%"
  type="{
  app_session_id: {
    description: 'Identifier for the current app session.',
    type: 'string',
    required: true,
  },
  is_superwall: {
    description: 'Always true for Superwall events.',
    type: 'boolean',
    required: true,
  },
  using_purchase_controller: {
    description: 'True when a custom purchase controller is configured.',
    type: 'boolean',
    required: true,
  },
}"
/>

## `paywall_decline`

### Usage

This is registered when a user manually dismisses any paywall. You can combine this with rules to show a paywall when a user closes a specific paywall. First, [add](/docs/dashboard/dashboard-campaigns/campaigns-placements#adding-a-placement) the standard placement to a campaign:

![](https://claude-centralize-agent-preamble-superwall-docs.staffbar.workers.dev/docs/images/campaigns-placement-adding-implicit-placement.png)

Then, create a filter in the audience using it:

![](https://claude-centralize-agent-preamble-superwall-docs.staffbar.workers.dev/docs/images/campaigns-placements-ex-implicit.png)

Here, when a user closes the paywall named `PaywallA`, a new paywall will show.

Note that you can't reference parameters that you've passed in to your original register call in your rules for `paywall_decline`.

### Parameters

Audience filters for `paywall_decline` placements can use the following parameters (empty values mean the field isn't applicable):

<TypeTable
  propColumnWidth="50%"
  type="{
  paywall_id: {
    description: 'The paywall ID where the decline occurred.',
    type: 'string',
    required: true,
  },
  paywall_name: {
    description: 'The paywall name shown in the dashboard.',
    type: 'string',
    required: true,
  },
  presented_by_event_name: {
    description:
      'The placement name that originally presented the paywall (for example, `onboarding`). Empty if the paywall was presented programmatically.',
    type: 'string',
    required: true,
  },
  presented_by: {
    description: 'How the paywall was presented (`placement` or `programmatically`).',
    type: 'string',
    required: true,
  },
  paywall_product_ids: {
    description: 'Comma-separated product identifiers attached to the paywall.',
    type: 'string',
    required: true,
  },
  primary_product_id: {
    description: 'The first product on the paywall, or empty if none.',
    type: 'string',
    required: true,
  },
  secondary_product_id: {
    description: 'The second product on the paywall, or empty if none.',
    type: 'string',
    required: true,
  },
  tertiary_product_id: {
    description: 'The third product on the paywall, or empty if none.',
    type: 'string',
    required: true,
  },
  '<product_name>_product_id': {
    description:
      'Product identifier keyed by the product name (for example, `annual_product_id`).',
    type: 'string',
    required: true,
  },
  is_free_trial_available: {
    description:
      'True when any introductory offer is available (including both free and paid trials).',
    type: 'boolean',
    required: true,
  },
  feature_gating: {
    description: 'Feature gating behavior for the paywall.',
    type: 'string',
    required: true,
  },
}"
/>

## `transaction_fail`

### Usage

This is registered when the payment sheet fails to complete a transaction (this does not include user cancellation). Use it to show an exit offer after a failed attempt.

### Parameters

Audience filters for `transaction_fail` placements can use the following parameters (empty values mean the field isn't applicable):

<TypeTable
  propColumnWidth="50%"
  type="{
  paywall_id: {
    description: 'The paywall ID where the failure occurred.',
    type: 'string',
    required: true,
  },
  paywall_name: {
    description: 'The paywall name shown in the dashboard.',
    type: 'string',
    required: true,
  },
  presented_by_event_name: {
    description:
      'The placement name that originally presented the paywall (for example, `onboarding`). Empty if the paywall was presented programmatically.',
    type: 'string',
    required: true,
  },
  presented_by: {
    description: 'How the paywall was presented (`placement` or `programmatically`).',
    type: 'string',
    required: true,
  },
  paywall_product_ids: {
    description: 'Comma-separated product identifiers attached to the paywall.',
    type: 'string',
    required: true,
  },
  primary_product_id: {
    description: 'The first product on the paywall, or empty if none.',
    type: 'string',
    required: true,
  },
  secondary_product_id: {
    description: 'The second product on the paywall, or empty if none.',
    type: 'string',
    required: true,
  },
  tertiary_product_id: {
    description: 'The third product on the paywall, or empty if none.',
    type: 'string',
    required: true,
  },
  '<product_name>_product_id': {
    description:
      'Product identifier keyed by the product name (for example, `annual_product_id`).',
    type: 'string',
    required: true,
  },
  is_free_trial_available: {
    description:
      'True when any introductory offer is available (including both free and paid trials).',
    type: 'boolean',
    required: true,
  },
  feature_gating: {
    description: 'Feature gating behavior for the paywall.',
    type: 'string',
    required: true,
  },
}"
/>

The event payload also includes a failure `message`; see [Superwall Events](/docs/sdk/guides/3rd-party-analytics/tracking-analytics) for full details.

## `transaction_abandon`

### Usage

This is registered when a user dismisses the store purchase sheet before the transaction completes. If a transaction-abandon paywall matches, Superwall immediately closes the current paywall and presents the new one.

### Parameters

Audience filters for `transaction_abandon` placements can use the following parameters (empty values mean the field isn't applicable):

<TypeTable
  propColumnWidth="50%"
  type="{
  paywall_id: {
    description: 'The paywall ID where the transaction was started.',
    type: 'string',
    required: true,
  },
  paywall_name: {
    description: 'The paywall name shown in the dashboard.',
    type: 'string',
    required: true,
  },
  presented_by_event_name: {
    description:
      'The placement name that originally presented the paywall (for example, `onboarding`). Empty if the paywall was presented programmatically.',
    type: 'string',
    required: true,
  },
  presented_by: {
    description: 'How the paywall was presented (`placement` or `programmatically`).',
    type: 'string',
    required: true,
  },
  abandoned_product_id: {
    description: 'The product identifier the user attempted to purchase before canceling.',
    type: 'string',
    required: true,
  },
  paywall_product_ids: {
    description: 'Comma-separated product identifiers attached to the paywall.',
    type: 'string',
    required: true,
  },
  primary_product_id: {
    description: 'The first product on the paywall, or empty if none.',
    type: 'string',
    required: true,
  },
  secondary_product_id: {
    description: 'The second product on the paywall, or empty if none.',
    type: 'string',
    required: true,
  },
  tertiary_product_id: {
    description: 'The third product on the paywall, or empty if none.',
    type: 'string',
    required: true,
  },
  '<product_name>_product_id': {
    description:
      'Product identifier keyed by the product name (for example, `annual_product_id`).',
    type: 'string',
    required: true,
  },
  is_free_trial_available: {
    description:
      'True when any introductory offer is available (including both free and paid trials).',
    type: 'boolean',
    required: true,
  },
  feature_gating: {
    description: 'Feature gating behavior for the paywall.',
    type: 'string',
    required: true,
  },
}"
/>

For example, to show a transaction-abandon paywall only for onboarding paywalls, add a `transaction_abandon` placement and set `presented_by_event_name` to `onboarding`. To limit it to a single paywall, add `paywall_id` as an additional condition.

## `survey_response`

### Usage

This is registered when a response to a paywall survey has been recorded. First, you need to make sure your paywall [has a survey attached](/docs/dashboard/surveys).

You can combine this with rules to show a paywall whenever a survey response is recorded or when the user gives a specific response. Again, [add](/docs/dashboard/dashboard-campaigns/campaigns-placements#adding-a-placement) the standard placement `survey_response` to a campaign. Then, add another condition using `survey_selected_option_title` that's equal to the text of a particular response.

For example, if the user selected a survey option named `Too Expensive`, you could present another paywall with a discounted option. This is a great opportunity to show a discounted paywall to improve your conversion rate.

### Parameters

Audience filters for `survey_response` placements can use the following parameters (empty values mean the field isn't applicable):

<TypeTable
  propColumnWidth="50%"
  type="{
  survey_selected_option_title: {
    description: 'The text of the selected survey option.',
    type: 'string',
    required: true,
  },
  survey_selected_option_id: {
    description: 'The ID of the selected survey option.',
    type: 'string',
    required: true,
  },
  survey_custom_response: {
    description: 'Optional. Custom response text when the user provides their own answer.',
    type: 'string',
  },
  survey_id: {
    description: 'The survey ID.',
    type: 'string',
    required: true,
  },
  survey_assignment_key: {
    description: 'The survey assignment key.',
    type: 'string',
    required: true,
  },
}"
/>

## `touches_began`

### Usage

This is registered when the user touches the app's UIWindow for the first time. It is only tracked if there is an active `touches_began` placement in a campaign.

### Parameters

Same as `app_install`:

<TypeTable
  propColumnWidth="50%"
  type="{
  app_session_id: {
    description: 'Identifier for the current app session.',
    type: 'string',
    required: true,
  },
  is_superwall: {
    description: 'Always true for Superwall events.',
    type: 'boolean',
    required: true,
  },
  using_purchase_controller: {
    description: 'True when a custom purchase controller is configured.',
    type: 'boolean',
    required: true,
  },
}"
/>