# 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

# Ad Consent

Report advertising consent from your Expo app to Google Ads and Meta, using provider options or runtime updates on iOS and Android.

Ad consent tells Superwall whether a user allows advertising data use and personalized advertising. Use it when sending conversions to Google Ads or Meta.

## Requirements

Use Expo SDK v1.6.0 or later on iOS and v1.8.0 or later on Android. Connect your advertising integration in the Superwall dashboard.

## Set consent

On iOS and Android, `adConsent` reports whether the user has consented to ad data use and personalized
advertising. Superwall passes these values with conversions it uploads to Google Ads and Meta.
If you omit `adConsent`, Superwall uses a stored IAB TCF consent when GDPR applies and otherwise
defaults to granted. Apps serving users in the EEA, UK, or Switzerland without a TCF banner should
set consent from their own consent flow. A value you set overrides the TCF answer. The SDK also
reports both purposes as denied when `eventTrackingBehavior` is `"none"`, and, on iOS, reports
personalization as denied when App Tracking Transparency has not been allowed unless you set it
yourself.

Set consent in provider options when it is already known at startup, or update it at runtime with
[`setAdConsent`](/docs/expo/sdk-reference/hooks/useSuperwall):

```tsx
import { Button } from "react-native";
import { useSuperwall } from "expo-superwall";

function ConsentSettings({ userConsent }) {
  const { setAdConsent } = useSuperwall();

  async function saveConsent() {
    await setAdConsent({
      adUserData: userConsent.adUserData ? "granted" : "denied",
      adPersonalization: userConsent.adPersonalization ? "granted" : "denied",
    });
  }

  return <Button title="Save consent" onPress={saveConsent} />;
}
```

On Android, the SDK reports the consent values as `adUserDataConsent` and
`adPersonalizationConsent` device attributes, and their source as `adConsentSource`.

`AdConsent` accepts these optional fields. If you omit a purpose, Superwall treats it as granted.

<TypeTable
  type="{
  adUserData: {
    type: '&#x22;granted&#x22; | &#x22;denied&#x22;',
    description: &#x22;Whether the user consents to sending ad-related user data to advertising networks.&#x22;,
  },
  adPersonalization: {
    type: '&#x22;granted&#x22; | &#x22;denied&#x22;',
    description: &#x22;Whether advertising networks may use that data for personalized advertising.&#x22;,
  },
}"
/>

The compatibility API exposes the same runtime method as `Superwall.shared.setAdConsent(consent)`.

## Limitations

Setting a consent value overrides the stored TCF answer. Update both purposes when the user's consent changes; omitted purposes are granted.

## Related

* [Configuring](/docs/expo/guides/configuring)
* [useSuperwall](/docs/expo/sdk-reference/hooks/useSuperwall)