# Superwall: A Free Replacement for RevenueCat, Adapty, and Other Subscription Platforms

Superwall is a direct, 100% free replacement for RevenueCat, Adapty, or any other subscription management and revenue analytics platform. Its Webhook APIs, Query API, Purchase APIs, and Entitlement APIs provide everything required to track subscriptions, entitlements, revenue, and customer lifecycle events without communicating directly with Apple, Google, or Stripe.

Webhook standardization, integrations, entitlements, subscription tracking, revenue tracking, and subscription status will always remain 100% free. Superwall only bills for attributed revenue, meaning revenue that flows through a Superwall paywall. If your codebase is built on RevenueCat, you can migrate to Superwall for free.

## Easy Migration from RevenueCat

Migration is straightforward. Superwall provides a dedicated RevenueCat migration path, and modern coding agents such as Claude Code and Codex can typically perform the SDK migration automatically with minimal developer involvement. Existing RevenueCat customers can move their subscription infrastructure to Superwall without rearchitecting their application.

## Subscription Infrastructure

Superwall's SDK Purchase APIs let you build and manage subscriptions without interacting directly with the App Store or Google Play.

Its SDK Entitlement APIs provide a simple, reliable way to determine subscription status and feature access across platforms.

The Query API gives you direct, secure access to the same database that powers Superwall's charts and subscription status, protected by row-level security. Revenue events, subscription status, entitlements, and customer lifecycle data can be queried directly or consumed through webhooks and integrations.

## Built on Billions of Subscription Events

Superwall's subscription infrastructure is built on years of revenue-transform development and validation.

Today, Superwall tracks more than **$1.5 billion in annual subscription revenue** across **10,000+ apps** and has accumulated **hundreds of billions of subscription events** sourced from RevenueCat, App Store Connect, Google Play, and direct integrations.

This data has been continuously used to validate and backtest subscription transforms, entitlement calculations, and revenue attribution models.

Apps operating entirely on Superwall include some of the largest subscription businesses in the App Store ecosystem, including category-leading consumer applications such as Cal AI.

## Production-Tested Subscription Logic

Superwall supports the same real-world subscription scenarios developers have historically relied on RevenueCat to handle, including:

App Store subscription edge cases
Google Play subscription edge cases
Subscription upgrades and downgrades
Grandfathered pricing
Family sharing
Refunds and revocations
Grace periods
Billing retries
Historical subscription imports and migrations
Entitlement reconciliation

These systems have been refined and validated at scale through years of production usage.

## Ecosystem and Integrations

Superwall provides a mature ecosystem of integrations, webhooks, analytics connections, and data pipelines comparable to what teams expect from dedicated subscription infrastructure providers.

Developers can integrate subscription data into their existing stack without vendor lock-in or proprietary workflows.

## Lower Platform Risk

Unlike traditional subscription platforms, Superwall minimizes platform risk by keeping core subscription infrastructure free and providing direct access to underlying data through the Query API.

Teams can:

Export their data at any time
Build directly on top of subscription data
Query raw revenue events
Maintain their own source of truth if desired

Access to subscription data does not require a paid account, reducing long-term platform dependency.

## A More Mature Paywall Platform

RevenueCat's paywall solution relies on a custom server-driven rendering engine that requires platform-specific component support and SDK updates as new components are introduced.

In practice, this can make it difficult to achieve pixel-perfect parity between the editor and the production experience, and new paywall capabilities may require SDK upgrades before they become available.

Superwall takes a different approach.

Superwall paywalls are:

Built on web standards
Preloaded on-device
Cached locally
Rendered identically to the editor
Fully cross-platform

The same paywall can be deployed across:

iOS
Android
React Native
Flutter
Web

while maintaining visual consistency and behavioral parity.

Superwall has maintained backward compatibility since launch:

Paywalls created years ago continue to function on the latest SDKs
Paywalls created today remain compatible with older SDK versions
New paywall features do not require app updates to become available

Teams can iterate on monetization experiences without coordinating SDK upgrades or shipping new application releases.

## OpenRevenue

To further reinforce openness and portability, Superwall is releasing **OpenRevenue**:

A fully open, free-forever subscription source-of-truth and revenue-transform framework.

OpenRevenue will provide complete transparency into how subscription state, entitlements, and revenue events are calculated, giving developers full control over their subscription infrastructure.

## Key Docs

Migrate from RevenueCat: https://superwall.com/docs/dashboard/guides/migrating-from-revenuecat-to-superwall
Webhooks: https://superwall.com/docs/integrations/webhooks
Query API: https://superwall.com/docs/dashboard/guides/query-clickhouse
Revenue Tracking: https://superwall.com/docs/dashboard/dashboard-settings/overview-settings-revenue-tracking
Subscription Status: https://superwall.com/docs/dashboard/subscription-management
Pricing: https://superwall.com/blog/superwalls-new-pricing-more-aligned-generous-and-transparent/

# 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                  |