# 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 # How to Start a Fresh A/B Test Learn the different ways to start a new A/B test with clean metrics, whether by resetting assignments or creating a new campaign. ## Answer When you want to run a new A/B test with clean metrics, you have two main options: **reset assignments** on an existing experiment or **create a new campaign**. Which approach to use depends on what you are testing and whether you want to preserve historical data. ### Option 1: Reset assignments Best when you want to reuse the same campaign and paywall setup but start measuring from scratch. 1. Navigate to your campaign, select the audience, and click the **Paywalls** tab to view the experiment group. 2. When editing presentation percentages, look for the **refresh icon** (circular arrow) next to where it says "X assigned" below any paywall variant. 3. Choose to **reset a single variant** to clear history for just that paywall, or **reset all paywalls** to clear history for every variant in the experiment. Resetting creates a new variant ID behind the scenes. All analytics for that variant, including conversions, ARPU, users, and trial metrics, start fresh from that point forward. The paywall configuration itself stays the same. > **Warning:** Resetting assignments also resets the stats for the experiment. Only reset when you are ready to start measuring from scratch. ### Option 2: Create a new campaign Best when you want to keep your previous test results intact for reference, or when you are testing a fundamentally different audience or placement. Create a new campaign with the paywalls you want to compare. This gives you a completely separate experiment with its own analytics, while your old campaign's data remains untouched. ### How assignments work When a user matches an audience and is assigned a paywall variant, that assignment is **sticky**. The user will continue to see the same variant regardless of percentage changes. Changing presentation percentages only affects new users. Resetting assignments clears these sticky assignments, so all users (new and returning) will be reassigned based on the current percentages. A new campaign has no prior assignments, so all users start fresh. ### Which option to choose * **Reset assignments** when you want to keep your campaign structure and do not need to reference old test data. * **Create a new campaign** when you want to preserve previous results or are changing the audience, placement, or overall test setup. > **Tip:** Avoid duplicating paywalls just to get clean metrics. Either reset assignments or create a new campaign instead. This keeps your dashboard organized.