# 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

# User management

Identify users, set attributes, and sign them out.

> **Warning:** **Beta**The Web SDK is in beta and its API may change between releases.

## Identify a user

Call `identify` once you know who the user is, typically right after sign-in.

```ts
await sw.user.identify("user_42");
```

Before that, the SDK tracks an anonymous **alias ID** it generates and persists itself, so placements and experiments work for logged-out visitors too.

## Restoring paywall assignments

A user who browsed logged-out already has experiment assignments tied to their anonymous identity. Once they sign in, those assignments may not be the ones their real account should see.

Pass `restorePaywallAssignments` to re-fetch config and re-run assignment for the identified user before `identify` resolves:

```ts
await sw.user.identify("user_42", { restorePaywallAssignments: true });
```

`register` calls block until the restore finishes, so the user never gets a paywall picked from their anonymous identity's stale assignments. It is best-effort. If the fetch fails, the cached assignments stay in place.

## Reading identity

Identity is exposed as reactive values. Read `.value` for a snapshot, or `.subscribe()` to react to changes.

```ts
sw.user.id.value;          // "" until identify()
sw.user.aliasId.value;     // the anonymous ID
sw.user.effectiveId.value; // id || aliasId
sw.user.isLoggedIn.value;  // boolean
```

> **Note:** `sw.user.id` is an empty string until you call `identify`. `effectiveId` returns `id` when set,
> otherwise `aliasId`.

## Sign out

```ts
await sw.user.signOut();
```

This clears the identified user and returns the SDK to its anonymous alias.

## User attributes

Attributes are values you attach to the user, and your campaign's audience rules can filter on them.

```ts
sw.user.setAttributes({
  plan: "team",
  seats: 12,
  signedUpAt: "2026-08-11",
});
```

`setAttributes` merges. It does not replace the whole set. Read the current values with `sw.user.attributes.value`.

## Integration attributes

Integration attributes carry third-party identifiers so Superwall can line its data up with your analytics tools.

```ts
sw.user.setIntegrationAttribute("amplitudeUserId", "abc123");

sw.user.setIntegrationAttributes({
  amplitudeUserId: "abc123",
  mixpanelDistinctId: "xyz789",
});
```

Pass `null` for a value to clear it.

## Resetting

`reset` clears local state (identity, attributes, and cached assignments), then resyncs.

```ts
await sw.reset();
```

Reach for `signOut` when a user logs out and `reset` when you want a clean slate, such as between tests.

Next, [gate your features](/docs/web/quickstart/feature-gating).