# 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

# Priority Placements

Preload your most important campaign's paywalls before the rest of your app's campaigns.

By default, Superwall's SDK preloads every paywall attached to your campaigns when the app launches. For most apps, this works seamlessly. But if you have a paywall that needs to appear *immediately* — like an onboarding paywall shown right at first launch — you can tell the SDK to preload that campaign's paywalls first.

That's what **Priority Placements** do. This feature is also referred to as **prioritized placements** or **prioritized campaign preloading**. When you mark a campaign as prioritized, the SDK fetches and caches that campaign's paywalls before anything else. Other campaign paywalls are still preloaded afterward in the background.

> **Note:** Only **one campaign per app** can be prioritized at a time. If you prioritize a new campaign, the previously prioritized one is automatically deprioritized.

## When to use it

Prioritizing a campaign is most useful when:

* **You show a paywall on first launch or during onboarding** — the paywall needs to be ready the moment the user hits the placement, with zero loading delay.
* **A placement is triggered very early in a session** — such as `session_start` or `app_open` — and you want to guarantee the paywall appears instantly.
* **You have many campaigns** and want to ensure one specific campaign's paywalls take precedence during preloading.

If your app only has a few campaigns, preloading happens quickly enough that you likely won't need this. It's most impactful when you have several campaigns and want to control the order they load.

## How to prioritize a campaign

In the campaign editor, look for the **flag icon** next to the **Placements** header:

![](https://2a2314a4-superwall-docs.staffbar.workers.dev/docs/images/campaigns-prioritize-placements.png)

Click the flag to prioritize the campaign. The flag turns green to indicate the campaign is now prioritized. The dashboard describes this action as prioritizing campaign preloading.

To deprioritize, click the green flag again — it will revert to its default state.

### Switching between campaigns

If another campaign is already prioritized and you click the flag on a different campaign, a confirmation dialog will appear:

> **Switch prioritized campaign?**
> "\[Other campaign name]" is currently prioritized. Only one campaign can be prioritized at a time. Switching will deprioritize it.

Confirm to switch, or cancel to keep the current priority.

## How it works under the hood

When the SDK fetches its configuration and sees a prioritized campaign:

1. **Phase 1 — Prioritized preload:** The SDK identifies all paywalls belonging to the prioritized campaign and preloads them first.
2. **Phase 2 — Remaining preload:** After a 5-second delay, the SDK preloads all remaining campaign paywalls in the background.

This two-phase approach ensures the most important paywalls are cached and ready before others, without skipping preloading for the rest of your campaigns. The prioritized campaign's paywalls will be ready to present with no loading time, while other paywalls continue loading in the background.

> **Tip:** Prioritization only affects *preload order* — it does not change how placements, audiences, or experiments work. Your campaign logic stays exactly the same.

## SDK version requirements

Priority Placements require the following minimum SDK versions:

| SDK          | Minimum version     | Notes                                                                                                       |
| ------------ | ------------------- | ----------------------------------------------------------------------------------------------------------- |
| iOS          | **4.14.0**          | Full support.                                                                                               |
| Android      | **2.7.10**          | Full support.                                                                                               |
| Flutter      | **2.4.12**          | Full support via bundled iOS SDK 4.14.2 and Android SDK 2.7.11. iOS-only support started in Flutter 2.4.11. |
| Expo         | **1.0.11**          | Full support via bundled iOS SDK 4.14.1 and Android SDK 2.7.11. iOS-only support started in Expo 1.0.8.     |
| React Native | *Not yet supported* | The current React Native SDK bundles native SDK versions that predate prioritized campaign preloading.      |

> **Note:** Priority Placements are fully backward-compatible. Older SDK versions ignore the prioritization flag and preload all paywalls in the default order.