# 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

# Data Schema

See every user attribute, device attribute and event your app sends to Superwall, with each event's properties and daily volume, and query any of them.

The **Data schema** page lists everything your app sends to Superwall: the attributes it sets on users and devices, and the events it fires, with the properties each event carries. Use it to find the exact name of an event or attribute, check that a new event is arriving, or start a query from it.

> **Note:** Data schema is in early access. If you don't see it under **Analytics**, it isn't turned on for you yet. Data schema and **Queries** are turned on together.

## Open the data schema

Open your app, then click **Analytics** in the sidebar and choose **Data schema**.

![The Data schema page for an iOS app on the Custom events tab, listing eight events with their property counts, last 30 days volume and sparklines, and when each was last seen](https://superwall.com/docs/images/data-schema/data-schema-custom-events.jpg)

The page shows production data only. Events and attributes that only ever arrived from sandbox aren't listed.

## What's on each tab

| Tab                   | What it lists                                                                                                                                                                                                                                                 |
| --------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **User attributes**   | The attributes your app sets on users with `setUserAttributes`.                                                                                                                                                                                               |
| **Device attributes** | The attributes the SDK reports about each device.                                                                                                                                                                                                             |
| **Custom events**     | Your own events: the placements you `register` and the events you track.                                                                                                                                                                                      |
| **Standard events**   | Superwall's own events, such as `paywall_open` and `transaction_complete`, and events from store and integration webhooks, such as `renewal`. See [Superwall Events](/docs/sdk/guides/3rd-party-analytics/tracking-analytics) for what the SDK's events mean. |

Each tab shows how many items it has.

**Attributes** show their key, their type, such as `String` or `Int64`, and when the key last arrived. A key that has arrived with more than one type shows each one.

**Events** show their name, how many properties they've carried, how many times they arrived in the last 30 days with a sparkline of each day, and when they last arrived. Today is still arriving, so the end of the sparkline is dashed.

Click a key or event name to copy it. Click an event's row to open it and see its properties, each with its type.

Click a column header, except **Type**, to sort by it. Long lists show 100 rows at a time, with **Show more** at the end.

## Search

The search box at the top covers all four tabs at once, and every event's property keys too. Each tab's count changes to the number of matches.

When an event matches because one of its properties does, it opens on its own and shows the matching keys, up to 50 per event.

![Searching the data schema for presented_by_event_name: the Standard events tab shows 19 matches, each event opened onto its matching property keys, with a Query button on the hovered key](https://superwall.com/docs/images/data-schema/data-schema-search.jpg)

Press Escape to clear the search.

## Query an event or attribute

Hover a row and click **Query** to open it on the **Queries** page as a chart of the last 30 days, by day:

* **An event:** how many times it arrived each day. This count is approximate, to within about 1%.
* **A property under an open event:** the event's daily count, split by the property's values.
* **An attribute:** how many times the attribute was set each day, split by its values.

A split shows the 8 most common values as their own lines and adds up the rest as `(other values)`. Events that didn't carry the key show as `(none)`.

Superwall writes the SQL for you, runs it and draws the chart. From there you can change the query, save it, or copy it as an API request for your own tools or agent.

Running a query needs the `data:read` scope with access to every project. Owner, Admin and User roles have it. Editors, Readers, Analysts and members with access to only some projects can browse the data schema, but their queries won't run. See [Access Controls](/docs/dashboard/dashboard-settings/overview-settings-access-controls).

![The Queries page opened from the data schema: a query for paywall_open split by presented_by_event_name, with its SQL and a line chart by day](https://superwall.com/docs/images/data-schema/data-schema-query.jpg)

## Limitations

* Each event tab lists at most 1,000 event names, the most recently seen. If your app has sent more, the page says so, and older names aren't listed or searched.
* Each event lists at most 500 property keys, the most recently seen. If an event has carried more, its property list says so.
* The lists can be a few minutes behind the events your app just sent.

## Get the data schema from the API

The same lists, and each event's daily volume, are available from the API. See [Find event names and property keys](/docs/dashboard/guides/query-clickhouse#find-event-names-and-property-keys) in Query ClickHouse.

## Related

* [Query ClickHouse](/docs/dashboard/guides/query-clickhouse)
* [Charts](/docs/dashboard/charts)
* [Setting User Attributes](/docs/sdk/quickstart/setting-user-properties)