# 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 # Acquisition Cohort Report Pull installs, trials, ad spend, CPI, and install-cohorted revenue per campaign, ad set, ad, or country through the Superwall MCP or API. The acquisition cohort report answers a single question: for the users acquired through a given campaign, ad set, ad, or country, what did they cost and what have they earned back so far? It is available through the [Superwall MCP](/docs/dashboard/guides/superwall-mcp), where you can ask your agent for something like "show me installs and D30 revenue by campaign for the last 30 days", and over the API at `POST /v2/charts/acquisition-cohort-report`. ## What it returns Each row is one value of the dimension you grouped by, plus a row for the organic/unattributed bucket. For every row you get: | Column | Meaning | | ----------------------- | ------------------------------------------------------------------------------------------------------------------------------------ | | `installs` | Installs in the window. For campaign, ad set, and ad, these come from MMP install matching; for country, from the SDK's install geo. | | `trials` | Trial starts, cohorted by install date. | | `install_to_trial_rate` | `trials ÷ installs`. | | `spend` | Ad-network spend. Campaign dimension only. | | `cpi` | Cost per install: `spend ÷ installs`. Campaign dimension only. | | `revenue` | Net proceeds per requested window, keyed by window (`d4`, `d14`, `d30`, and so on). | Revenue is **cohorted by install date**, not by purchase date: the `d30` figure for a campaign is what the users it acquired had earned you within 30 days of installing, however long ago that was. ## Choosing your windows By default the report returns `d4`, `d14`, and `d30`. You can request any combination of `d1`, `d3`, `d4`, `d7`, `d14`, `d30`, and `d90`. Shorter windows tell you sooner whether a campaign is working; longer windows tell you more accurately. A campaign that looks weak at `d4` may look very different at `d30`. ## Reading zero versus null The report distinguishes "we measured nothing" from "we could not measure": * **0** means the source was available and genuinely saw nothing. A campaign with `installs: 0` is one the MMP has no matched installs for, even though it has revenue attributed to it. * **null** means the source itself was unavailable, or a rate or cost had nothing to divide by. On the campaign, ad set, and ad dimensions, `installs` is null when the report is not scoped to production only, because MMP installs are production-only. The country dimension counts installs from SDK data instead, so it keeps its install column on any environment filter. `spend` and `cpi` are null on every dimension except campaign, and null on all rows when the window contains no spend at all, so a report never claims your installs were free just because no ad account is connected. ## Totals are blended `totals.cpi` and `totals.install_to_trial_rate` divide by **all** installs in the window, organic included. They are blended figures and deliberately are not the sum of the per-row values: a paid campaign's own CPI is typically higher than the blended CPI, because the blend is spreading the same spend across organic installs too. ## Things worth knowing Ad spend has campaign granularity only. It carries no ad set id, ad id, or country, which is why `spend` and `cpi` appear on the campaign dimension and nowhere else, and why they need a connected ad account. See [Meta Ads](/docs/integrations/meta-ads). On ad dimensions, installs are windowed by MMP match time while trials and revenue are cohorted by SDK install date. At the edges of a window those two can disagree slightly, which occasionally pushes `install_to_trial_rate` above 1. The report defaults to production only. Widening the environment filter to include sandbox makes the revenue side describe a different population than MMP installs can, so on the campaign, ad set, and ad dimensions the install column drops to null rather than comparing two different things. The country dimension is unaffected: its installs come from SDK data and follow the same environment filter as revenue.