GitHub Start free

Integration · Product analytics

Send subscription events to Superwall

RevenueDot sends subscription events to Superwall as a webhook, because Superwall publishes no event API for it. It POSTs RevenueCat's webhook body to the URL Superwall gives you, with the Authorization header value you enter. Every event type goes out except experiment enrollments, so Superwall's revenue tracking sees purchases, renewals, cancellations and refunds.

Start free on Cloud Setup guide →

What teams do with it

  • See what each Superwall paywall earned, using purchases from RevenueDot as the revenue source.
  • Keep Superwall's revenue tracking running while your purchase backend is RevenueDot.
  • Send sandbox events to Superwall as well, marked environment: SANDBOX, or keep production only.

What RevenueDot sends

  • RevenueCat's webhook body, unchanged: {"api_version":"1.0","event":{...}} as JSON in a POST, with the Authorization header value you saved.
  • Every event type except EXPERIMENT_ENROLLMENT, such as INITIAL_PURCHASE, RENEWAL, CANCELLATION, EXPIRATION, BILLING_ISSUE and PRODUCT_CHANGE.
  • Revenue fields as in any RevenueCat-format webhook: price in US dollars (negative for refunds), price_in_purchased_currency, currency, product_id, store and transaction_id.
  • Identity: app_user_id, original_app_user_id and aliases. The Superwall SDK reads the same app user ID.
  • Sandbox events carry environment: SANDBOX and are sent when the integration's Environment includes sandbox.

Setup

How to connect Superwall to RevenueDot

  1. 01

    Get the webhook URL from Superwall

    Superwall's Settings → Revenue Tracking → RevenueCat shows an integration token, not a URL. Ask Superwall support for the URL that receives RevenueCat webhooks.

  2. 02

    Open the integration

    In RevenueDot, open Integrations → Superwall.

  3. 03

    Enter the URL

    Paste the Superwall webhook URL. It is checked when you save (https only on RevenueDot Cloud) and again before each send.

  4. 04

    Add the token if Superwall asks

    Enter the integration token as Authorization header value. It must be one line.

  5. 05

    Connect and test

    Click Connect Superwall, then Send test event and check the delivery log.

The Superwall integration page in the RevenueDot dashboard, with its settings form
Captured from the RevenueDot dashboard with demo data.

Why Superwall connects through a webhook

Superwall's own guide asks RevenueCat customers for an integration token and documents no public event URL behind it (Superwall: revenue tracking, checked October 2026). So RevenueDot does not guess an API. It sends the same body a RevenueDot webhook gets to the URL Superwall support gives you.

Superwall also sells paywalls. This page covers only the revenue feed that RevenueDot sends to Superwall. RevenueDot has its own paywalls too, and you can use either or both.

How Superwall deliveries are retried, logged and replayed

  • Retries: timeouts, 408, 425, 429 and 5xx answers retry after 5, 10, 20, 40 and 80 minutes. Any other 4xx fails at once, because sending the same request again cannot work. Fix the setting, then replay.
  • Delivery log: each delivery shows the request with every secret replaced by [redacted], the partner's answer, the HTTP status, the time taken and the number of attempts.
  • Skipped, with the reason: when there is nothing to send, such as a missing device ID, the delivery is marked skipped and says why. Retry sends it after your app sets the attribute.
  • Replay: Replay failed resends failed and skipped deliveries in bulk.
  • Sealed credentials: keys and tokens are encrypted with AES-256-GCM on the server and never shown again. The dashboard shows only the last four characters.
  • The URL is secret: it may carry a private key, so it is sealed like a credential and scrubbed from the delivery log.

FAQ

Superwall and RevenueDot

How do I connect Superwall to RevenueDot?

Ask Superwall support for the URL that receives RevenueCat webhooks, then paste it under Integrations → Superwall in RevenueDot as Superwall webhook URL. If Superwall gives you a token, enter it as Authorization header value. Click Connect Superwall.

Does Superwall need a RevenueCat account to get revenue from RevenueDot?

No. RevenueDot sends the RevenueCat-format webhook body itself, so the revenue arrives without RevenueCat. The app_user_id in the body must match the user ID your Superwall SDK uses.

Are sandbox purchases sent to Superwall?

They are when the integration's Environment includes sandbox. Each carries environment: SANDBOX in the body, so Superwall can tell them apart.

Is there a RevenueCat Superwall integration alternative?

Yes. RevenueDot sends the same webhook shape that Superwall's RevenueCat setup expects, from an open source backend you can self-host. Superwall's own steps are in its revenue tracking guide, checked October 2026.

Sources: Superwall · Superwall: revenue tracking settings. Superwall is a trademark of its owner, used to describe compatibility. RevenueDot is not affiliated with or endorsed by it.

Get started

Send Superwall every subscription event.

Start free on RevenueDot Cloud, free up to $10,000 a month in tracked revenue. Integrations are included on every plan.

Start free on Cloud Migrate from RevenueCat →

Already have an account? Sign in · Prefer your own servers? Self-host free