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

# AppStance

The AppStance integration sends Superwall subscription and payment events to the AppStance platform for Apple Ads ROAS optimization. Automatically forward iOS transaction data with Apple Search Ads attribution for campaign performance analysis.

> **Note:** This integration is currently in **Beta**. Features and behavior may change. If you encounter any issues, please reach out to support.

In the **Analytics** section within **Integrations**, you can connect your AppStance account to Superwall.

AppStance (formerly Search Ads Optimization / SAO) is an Apple Ads ROAS optimization platform. This integration automatically forwards iOS subscription lifecycle events along with Apple Search Ads attribution data to AppStance, enabling you to measure and optimize your Apple Ads campaign performance.

### Required fields

Fill out the following fields and **click** the **Enable AppStance** button at the bottom right to save your changes:

* **Integration ID:** Must be set to `appstance`.
* **Anonymous User Behavior:** Whether to send or skip events for anonymous users (optional).

### Features

* **Apple Ads ROAS Optimization**: Connects subscription revenue to Apple Search Ads campaigns
* **Automatic ASA Attribution**: Forwards Apple Search Ads attribution fields (org, campaign, ad group, keyword, and more)
* **iOS-Only Filtering**: Automatically filters out non-App Store events (Play Store and Stripe events are skipped)
* **Production-Only**: Sandbox events are skipped to keep optimization data clean
* **No Authentication Required**: The AppStance endpoint is public and does not require API keys
* **Device Identifier Forwarding**: Sends IDFV and IDFA when available

### Configuration

#### Optional settings

| Field                     | Description                                | Example                  |
| ------------------------- | ------------------------------------------ | ------------------------ |
| `anonymous_user_behavior` | Whether to send events for anonymous users | `"send"` or `"dontSend"` |

#### Example configuration

```json
{
  "anonymous_user_behavior": "send"
}
```

### Event mapping

AppStance uses its own event name mapping, which differs from the standard Superwall event mapping used by other integrations.

| Superwall Event         | Period Type | AppStance Event Name |
| ----------------------- | ----------- | -------------------- |
| `initial_purchase`      | `TRIAL`     | `free_trial`         |
| `initial_purchase`      | Any other   | `initial_purchase`   |
| `renewal`               | Any         | `renewal`            |
| `cancellation`          | Any         | `cancellation`       |
| `billing_issue`         | Any         | `billing_issue`      |
| `product_change`        | Any         | `product_change`     |
| `non_renewing_purchase` | Any         | `initial_purchase`   |
| `test`                  | Any         | `test`               |

### Event payload

Every event sent to AppStance includes the following fields:

#### Core fields

| Field                 | Type    | Description                                                           |
| --------------------- | ------- | --------------------------------------------------------------------- |
| `user_id`             | string  | User identifier (uses `originalAppUserId` or `originalTransactionId`) |
| `install_timestamp`   | number  | Timestamp from `purchasedAt`                                          |
| `country_code`        | string  | Country code of the user                                              |
| `store`               | string  | Always `APP_STORE` (non-iOS events are filtered out)                  |
| `event_unique_id`     | string  | Unique event identifier                                               |
| `event_name`          | string  | Mapped event name (see table above)                                   |
| `event_timestamp`     | number  | Timestamp of the event                                                |
| `period_type`         | string  | Subscription period type                                              |
| `price_usd`           | number  | Transaction price in USD                                              |
| `proceeds_usd`        | number  | Proceeds after store fees in USD                                      |
| `is_trial_conversion` | boolean | Whether this event is a trial-to-paid conversion                      |

#### Revenue fields

| Field                  | Type   | Description                               |
| ---------------------- | ------ | ----------------------------------------- |
| `revenue_raw_amount`   | number | Price in the original purchased currency  |
| `revenue_raw_currency` | string | Currency code of the original transaction |

#### Transaction fields

| Field                     | Type    | Description                                  |
| ------------------------- | ------- | -------------------------------------------- |
| `bundle_id`               | string  | App bundle identifier                        |
| `transaction_id`          | string  | Transaction identifier                       |
| `original_transaction_id` | string  | Original transaction identifier              |
| `product_id`              | string  | Product identifier                           |
| `new_product_id`          | string  | New product identifier (for product changes) |
| `is_small_business`       | boolean | Whether the Small Business Program applies   |
| `environment`             | string  | Transaction environment                      |
| `project_id`              | string  | Superwall project identifier                 |
| `application_id`          | string  | Application identifier (currently null)      |

### Apple Search Ads attribution

AppStance extracts Apple Search Ads (ASA) attribution data from user attributes and includes it in every event payload. This is the core data that powers Apple Ads ROAS optimization.

| Field                   | Description                                  |
| ----------------------- | -------------------------------------------- |
| `asa_org_id`            | Apple Search Ads organization ID             |
| `asa_campaign_id`       | Campaign identifier                          |
| `asa_adgroup_id`        | Ad group identifier                          |
| `asa_keyword_id`        | Keyword identifier                           |
| `asa_ad_id`             | Ad identifier                                |
| `asa_country_or_region` | Country or region for the campaign           |
| `asa_conversion_type`   | Conversion type (e.g., Download, Redownload) |
| `asa_click_date`        | Date of the ad click                         |
| `asa_claim_type`        | Claim type                                   |
| `asa_impression_date`   | Date of the ad impression                    |

For ASA attribution data to be available, ensure your app has the [Apple Search Ads integration](/docs/integrations/apple-search-ads) configured and that the Superwall SDK is collecting attribution data on the client side.

### Device identifiers

AppStance includes device identifiers from user attributes when available:

| Field  | Description                                       |
| ------ | ------------------------------------------------- |
| `idfv` | Identifier for Vendor                             |
| `idfa` | Identifier for Advertisers (requires ATT consent) |

These identifiers are extracted from `userAttributes` on the event. If your app collects IDFA (after obtaining App Tracking Transparency consent), it will be forwarded automatically.

### Sandbox handling

AppStance is a **production-only** integration. Sandbox events are automatically skipped and are not sent to AppStance. This ensures that test transactions do not affect your ROAS optimization data.

Additionally, only App Store (iOS) events are forwarded. Events originating from Google Play Store or Stripe are filtered out, since AppStance is focused exclusively on Apple Ads optimization.

### User identification

The integration identifies users using the following hierarchy:

1. **Primary**: `originalAppUserId` (if available)
2. **Fallback**: `originalTransactionId` (always present)

If `anonymous_user_behavior` is set to `"dontSend"`, events for users without a resolved identity are skipped.

### Testing the integration

#### 1\. Trigger a test event

Use the `test` event type to verify connectivity. The integration maps `test` events to the `test` event name in AppStance.

#### 2\. Trigger production events

Since AppStance skips sandbox events, you will need to test with production transactions:

* iOS: Use TestFlight with a sandbox Apple ID. Note that StoreKit Configuration files do not generate App Store Server Notifications, so webhooks and downstream integrations will not fire.
* Verify that events appear in your AppStance dashboard.

#### 3\. Verify ASA attribution

Confirm that Apple Search Ads attribution fields are populated:

1. Ensure the Apple Search Ads integration is enabled in Superwall.
2. Install your app via an Apple Search Ad (or use a test campaign).
3. Make a purchase and check that `asa_campaign_id` and related fields are present in AppStance.

### Best practices

1. **Enable Apple Search Ads**: Ensure the [Apple Search Ads integration](/docs/integrations/apple-search-ads) is configured so that ASA attribution data flows through to AppStance.
2. **Collect IDFA**: Request App Tracking Transparency consent to maximize device identifier coverage for attribution matching.
3. **Set User IDs Early**: Send `originalAppUserId` to Superwall as early as possible so that AppStance can consistently identify users across events.
4. **Use Anonymous User Filtering**: Set `anonymous_user_behavior` to `"dontSend"` if you want to exclude events that lack a resolved user identity.
5. **Monitor Production Data**: Since sandbox events are filtered, verify your integration using production transactions or the `test` event type.

### Troubleshooting

#### Events not appearing in AppStance

1. **Check Platform**: Only iOS (App Store) events are sent. Play Store and Stripe events are automatically filtered out.
2. **Check Environment**: Sandbox events are skipped. Ensure you are testing with production transactions.
3. **Check Anonymous Users**: If `anonymous_user_behavior` is `"dontSend"`, events for anonymous users are skipped.

#### Missing ASA attribution data

1. **Check Apple Search Ads Integration**: Ensure the Apple Search Ads integration is enabled in Superwall settings.
2. **Check SDK Version**: The Superwall SDK must be collecting ASA attribution data on the client side.
3. **Check Timing**: There is a delay between app install via a search ad and when Apple sends attribution data. Events that fire before attribution data arrives will have empty ASA fields.

#### Events not mapping correctly

1. **Check Event Type**: Verify the Superwall event name matches one of the supported types in the event mapping table.
2. **Check Period Type**: For `initial_purchase` events, the period type determines whether the event maps to `free_trial` or `initial_purchase`.
3. **Non-renewing purchases**: These are mapped to `initial_purchase` in AppStance regardless of period type.