# 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

# Using Demand Score

Demand Score is a 1-100 value assigned to each user by Superwall, indicating their likelihood to convert. Use it to understand your audience and target users with the right offers.

Demand Score helps you understand how likely each user is to convert, so you can target the right people with the right offers. To view it, click **Demand Score** in the **sidebar**:

![](https://2a2314a4-superwall-docs.staffbar.workers.dev/docs/images/ds_sidebar.jpeg)

> **Note:** Demand Score is currently in **beta**. Anyone can view Demand Score insights, but using it to target audiences in campaigns requires the **Scale** plan.

### What is Demand Score?

Demand Score is a number from 1 to 100 assigned to each user by Superwall on every app open. A higher score means the user is more likely to convert. It's generated using several signals and data points, though no first-party user attributes are used.

Some signals used include device model, OS version, device age, App Store country, connection type, number of app opens, and paywall views. The model is trained on hundreds of millions of real-world data points across the Superwall network. You can use demand score a few different ways:

* **View interactive charts** that show how conversion rate, volume, and trial outcomes vary across demand score buckets.
* **Break down performance by placement and country** to see where your offerings resonate and where they don't.
* **Generate an AI-powered analysis** that highlights key patterns in your data and recommends experiments to run.
* **Filter campaign audiences** using `demandScore` to target users based on their likelihood to convert.
* **Launch experiments directly** from the Demand Score page to create high-intent audiences with one click.

> **Tip:** Because Demand Score relies on device-level signals and not user attributes, it works out of the box. There's nothing to configure in the SDK.

### Data thresholds

If your app is new, doesn't have enough paywall activity yet, or enough data processed, the Demand Score page will display empty results:

![](https://2a2314a4-superwall-docs.staffbar.workers.dev/docs/images/ds_layout_empty.jpeg)

This happens when Superwall hasn't observed enough user sessions to generate reliable demand scores for your app. The model needs a baseline of app opens and paywall views across your user base before it can assign scores.

No action is needed on your end. As users interact with your app and encounter paywalls, Superwall will automatically begin assigning demand scores and the charts will populate.

> **Tip:** You can also try expanding the date range to **Last 90 days** or **Last 180 days** to capture a wider window of activity.

### Coverage

At the top of the Demand Score page, the **Coverage** card shows what percentage of your recent paywall viewers have been assigned a demand score:

![](https://2a2314a4-superwall-docs.staffbar.workers.dev/docs/images/demand-score-coverage.jpg)

Coverage is color-coded to help you quickly assess data reliability:

| Coverage  | Indicator | Meaning                                                                  |
| --------- | --------- | ------------------------------------------------------------------------ |
| Above 80% | Green     | Great, you can confidently segment and run demand-score-based audiences. |
| 50–80%    | Yellow    | OK, results are usable but may have gaps.                                |
| Below 50% | Red       | Low, try selecting a longer date range for more reliable results.        |

### Selecting a date range

Use the date range selector in the top-right corner to adjust the time window for all charts and breakdowns on the page. Options include **Last 7 days**, **Last 30 days**, **Last 90 days**, and **Last 180 days**:

![](https://2a2314a4-superwall-docs.staffbar.workers.dev/docs/images/demand-score-overview.jpg)

All sections on the page (coverage, charts, breakdowns, and AI analysis) update to reflect the selected range.

### Using Demand Score for targeting

The `demandScore` attribute (a number from 1 to 100) is available as an audience filter in [campaigns](/docs/dashboard/dashboard-campaigns/campaigns). Rather than using fixed tiers, use the charts on this page to understand where natural breakpoints exist in your own data, then create custom score ranges that match your app's audience.

For example, if the [Conversion Rate](/docs/dashboard/dashboard-demand-score/demand-score-insights#conversion-rate) chart shows a clear jump at score 70, you might target 70–100 as your "high intent" range. Every app's distribution is different, so let your data guide the ranges you choose.

For details on setting up demand score filters, see [Using Demand Score in Campaigns](/docs/dashboard/dashboard-demand-score/demand-score-experiments).