# 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 do I extract Apple Search Ads attribution data from Superwall?

Learn how to access raw Apple Search Ads attribution data from the Superwall SDK on the client side, since ASA data is not included in webhooks or third-party integration payloads.

When the [Apple Search Ads integration](/docs/integrations/apple-search-ads) is enabled, Superwall automatically fetches ASA attribution data and stores it as user attributes on the device. This data is available in the Superwall dashboard (on user profiles, in charts, and in campaign filters), but it is **not** included in webhook payloads or third-party integration events like Mixpanel or Amplitude.

To forward raw ASA attribution data to your own backend or analytics service, you need to read it from the SDK on the client side.

## How ASA data flows through the SDK

When a user opens your app, the Superwall SDK:

1. Fetches an AdServices attribution token from Apple's `AAAttribution` API.
2. Sends the token to Superwall's servers, which resolve it into attribution details (campaign name, keyword, ad group, etc.).
3. Stores the resolved attribution data as user attributes on the device.

Because this happens automatically, you do not need to call any Apple APIs yourself. The attribution fields become available alongside your other user attributes once the process completes.

> **Warning:** There is a delay between when a user downloads your app via a search ad and when the attribution data becomes available. The data may not be present immediately on the first app launch. Avoid reading ASA attributes during app startup without checking that they exist first.

## Reading ASA data from the SDK

### Swift (iOS)

Access the `userAttributes` property on the shared `Superwall` instance. ASA fields are stored with a `$` prefix (e.g., `$asa_campaign_name`, `$asa_keyword`).

```swift
let attributes = Superwall.shared.userAttributes

// Check if ASA data is available
if let campaignName = attributes["$asa_campaign_name"] as? String {
    print("Campaign: \(campaignName)")

    // Forward to your backend or analytics
    MyAnalytics.track("asa_attribution", properties: [
        "campaign_name": campaignName,
        "keyword": attributes["$asa_keyword"] as? String ?? "",
        "ad_group_name": attributes["$asa_ad_group_name"] as? String ?? "",
        "campaign_id": attributes["$asa_campaign_id"] as? String ?? ""
    ])
}
```

You can also listen for attribute changes using the `SuperwallDelegate`:

```swift
class MySuperwallDelegate: SuperwallDelegate {
    func userAttributesDidChange(newAttributes: [String: Any]) {
        // Called whenever user attributes update, including when ASA data arrives
        if let campaignName = newAttributes["$asa_campaign_name"] as? String {
            // ASA data is now available, forward it
        }
    }
}
```

## Where ASA data is and is not available

| Channel                                              | ASA data available? |
| ---------------------------------------------------- | ------------------- |
| SDK user attributes (client-side)                    | Yes                 |
| Superwall dashboard (user profiles)                  | Yes                 |
| Campaign audience filters                            | Yes                 |
| Dashboard charts (breakdowns)                        | Yes                 |
| Webhooks                                             | No                  |
| Third-party integrations (Mixpanel, Amplitude, etc.) | No                  |