# 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 in Campaigns Learn how to create audiences based on demand score ranges to run targeted experiments and improve conversion. Once you understand your demand score distribution, you can act on it by creating targeted audiences in your campaigns. Superwall provides a quick-start flow and manual options for building demand-score-based experiments. > **Note:** Using Demand Score in campaign audience filters requires the **Scale** plan. Viewing Demand Score insights is available on all plans. ### Launching an experiment from Demand Score The fastest way to get started is the **Launch Experiment** button at the bottom of the Demand Score page: ![](https://2a2314a4-superwall-docs.staffbar.workers.dev/docs/images/demand-score-launch-experiment.jpg) When you click it, Superwall handles the setup automatically: 1. **If you have no campaigns**, Superwall creates a new one called "Demand Score Campaign." 2. **If you have one campaign**, Superwall uses it directly. 3. **If you have multiple campaigns**, a dropdown appears so you can choose which campaign to use. Superwall then creates a new audience named **"Demand Score 80-100"** with the filter rule `demandScore >= 80 AND demandScore <= 100`. The audience starts disabled so you can configure your paywall and settings before going live. You'll be taken to the campaign page with the new audience ready for configuration. From there, you can [attach paywalls](/docs/dashboard/dashboard-creating-paywalls/paywall-editor-overview), [adjust the score range](/docs/dashboard/dashboard-campaigns/campaigns-audience), and enable the audience when ready. ### Creating a custom demand score audience You can also build demand score audiences manually in any campaign. This gives you full control over the score ranges and combinations: 1. Navigate to your campaign and click to add a new **audience**. 2. In the audience filter settings, add a filter using the `demandScore` property. 3. Set the operator and value to define your target range. For example, to target mid-intent users: * `demandScore` **is greater than or equal to** `40` * **AND** `demandScore` **is less than or equal to** `79` You can combine demand score filters with any other audience filters (country, platform, app version, etc.) to create precise segments. For full details on audience configuration, see [Audiences](/docs/dashboard/dashboard-campaigns/campaigns-audience). ### Choosing your score ranges Every app's demand score distribution is different. Rather than using fixed tiers, use the [Demand Score charts](/docs/dashboard/dashboard-demand-score/demand-score-insights) to find natural breakpoints in your own data. Look for where conversion rate jumps or where user volume is concentrated, then define ranges that match your audience. For example, if the Conversion Rate chart shows a clear uplift starting at score 65, you might define: * **High intent:** 65–100 * **Mid intent:** 30–64 * **Low intent:** 1–29 > **Tip:** The right ranges depend on your app. Start with what the charts show you, run an experiment, and refine from there. ### Experiment strategies Here are a few approaches to get started with demand score experiments: **Target high-intent users with premium offers** Create an audience for your highest-scoring users and show them your strongest paywall with premium pricing, annual plans emphasized, and minimal distractions. These users are already likely to convert, so reduce friction and let your best offer do the work. **Use softer approaches for lower intent** For lower-scoring users, consider delaying the paywall, offering a free trial with a longer duration, or using introductory pricing. These users may need more time to see value before committing. **A/B test by score range** Run parallel experiments where different score ranges see different paywalls. For example: * High-scoring users see a direct purchase paywall with annual pricing. * Lower-scoring users see a trial-first paywall with monthly pricing and a "cancel anytime" message. Compare conversion rates across the ranges to learn what resonates with each segment. **Act on placement-specific insights** If the [Breakdown by Placement](/docs/dashboard/dashboard-demand-score/demand-score-insights#breakdown-by-placement) chart shows a placement with high demand but low conversion, that's a sign the paywall at that placement isn't matching user intent. Create a demand-score-filtered audience specifically for that placement and test a different offer. > **Tip:** Use the [AI Analysis](/docs/dashboard/dashboard-demand-score/demand-score-insights#ai-analysis) suggestions as a starting point. They're tailored to your actual data and often highlight the highest-leverage experiments to run first.