# 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 # Campaigns Campaigns are logical groupings of paywalls to show when certain _events_ are registered and _conditions_ are met. They are an incredibly powerful tool for creating experiments and managing best-in-class monetization flows. View **Campaigns** by clicking them over on the left-hand **sidebar**: ![](https://claude-centralize-agent-preamble-superwall-docs.staffbar.workers.dev/docs/images/campaign-sidebar.png) Campaigns consist of three main concepts: 1. [Placements](/docs/sdk/quickstart/feature-gating) 2. [Audiences](/docs/dashboard/dashboard-campaigns/campaigns-audience) 3. [Paywalls](/docs/dashboard/dashboard-creating-paywalls/paywall-editor-overview) Campaigns are the centerpiece of Superwall. You can use one, or several, campaigns that can run concurrently. To understand campaigns, think of them like this: * In a campaign, you add **placements** — which are actions you want to result in a paywall, or might someday want to result in a paywall(i.e. `loggedCaffeine`, `addedEntry`, etc). * Then, as users take actions in your app, those placements are **registered** in the Superwall SDK. * When a placement is registered, it's then evaluated by Superwall. Superwall looks at your campaign **[filters](/docs/dashboard/dashboard-campaigns/campaigns-audience#configuring-an-audience)**, and may or may not show a matching **paywall**. With this setup, you can be incredibly simple or make in-depth, complex filters which determine when (and what) paywall is shown. You can set the percentage of new users that see each paywall, or even configure no paywall (a.k.a. a holdout) to be shown for certain placements. ### Toggling campaigns by status You can toggle between campaigns by their status using the tabs at the top (above the campaigns): ![](https://claude-centralize-agent-preamble-superwall-docs.staffbar.workers.dev/docs/images/campaigns-tabs.png) * **All:** The default view. This shows all of your campaigns, regardless of their status. * **Active:** Campaigns being used in production and serving up paywalls. * **Inactive:** Campaigns that are not serving paywalls in production, but can be quickly re-enabled. * **Archived:** Campaigns that have been archived, and not attached to any campaign. These can be restored. ### Viewing campaign top-level metrics Each campaign will also display its active placements and top-level metrics (if any are available). In this example, the campaign at the top has data, while the one below it doesn't: ![](https://claude-centralize-agent-preamble-superwall-docs.staffbar.workers.dev/docs/images/campaigns-inline-metrics.png) Metrics shown include: * **Opens:** The amount of time any of the campaign's placements resulted in a paywall being presented. * **Conversions:** The number of conversions produced from any paywall attached to the campaign. * **Conversion Rate:** The conversion rate of the current campaign. > **Note:** If the campaign isn't currently serving any paywalls because none have been attached to it, you'll > see a wanting indicating that in this view. In the image above, that's the case for the campaign > at the bottom, called "Survey". ### Toggling campaigns by date To toggle the date range that the metrics previously mentioned should display within, use the date toggle at the top-right side: ![](https://claude-centralize-agent-preamble-superwall-docs.staffbar.workers.dev/docs/images/campaigns-date-toggle.png) ### Viewing campaign details To view more about any campaign, to set up filters, edit placements, paywalls and more — simply **click** on any campaign listed in the table. Then, campaigns details will be presented. More on that in the next [page](/docs/dashboard/dashboard-campaigns/campaigns-structure).