| Metric | Definition |
|---|---|
| App Revenue | Superwall Proceeds by purchase date: revenue after refunds, store fees, and taxes. |
| New Customers | Superwall New Users by install date. |
| New Trials | Superwall New Trials: trials started during the selected period. |
| New Paid Subs | Superwall New Subscriptions: paid subscriptions started during the selected period. |
Integrations
Superwall integration
Connect Superwall to attribute app revenue, new users, trials, and paid subscriptions to your projects.
The Superwall integration connects your Superwall organization to viral.app so analytics can show subscription outcomes next to creator performance. viral.app reads Superwall's charts with a read-only API key and attributes them to the projects you map.
Connect Superwall
Open Superwall integrations and click Connect Superwall. The connection uses an organization API key that you create in Superwall:
- In Superwall, click your organization name (top left), then Organization access, API keys, and Create API key.
- Untick All, then tick Read for Projects and Charts only. Keep project access on all projects, or pick the apps viral.app should track.
- Copy the key. Superwall shows it once, and it starts with
sk_.
Paste the key into viral.app. viral.app checks the key and its two scopes when you connect and tells you what to fix if something is missing. The pk_ SDK key from your app does not work here.
With these two scopes viral.app reads your project and app list plus aggregated chart data, not individual users or transactions. To rotate the key, use Replace API key on the Connections tab and revoke the old key in Superwall.
If Superwall stops accepting the key (it was revoked or deleted, or it lost read access to Projects or Charts), the sync stops and the workspace's owners and admins get an email. Replacing the key resumes it, with your apps, mappings, and history in place.
Map apps to projects
Metrics only sync for apps that are mapped to a viral.app project. Map each Superwall app to the project that tracks the matching creator content. You can change mappings later on the Apps tab. Each mapped app shows its last 30 days of revenue, new customers, trials, and paid subscriptions there, so you can check the right app sits on the right project.
- Mapping an app for the first time starts a full-history backfill, so charts include data from before you connected.
- Remapping an app to a different project re-attributes its full history to the new project.
- Unmapping an app removes its Superwall data from analytics.
What syncs and when
viral.app refreshes Superwall metrics roughly hourly and re-reads a trailing window of about 35 days on every sync, so refunds and late purchases are picked up automatically. You can also trigger a sync manually with Sync Now on the Connections tab, and Sync History shows every run.
All amounts are Superwall proceeds: revenue after refunds, store fees, and taxes, in USD. Only production data counts, so sandbox purchases never reach your analytics.
Metric definitions
With Superwall connected, the Analytics Overview reads these Superwall charts. App Revenue and New Customers are cards; all four are metrics in the chart.
If numbers look different from the Superwall dashboard, check the selected date range and remember that viral.app only counts the apps you mapped, filtered to the projects you selected. How filters apply to app metrics lists which filters change these numbers.
The Superwall integration page shows the same four metrics for the last 30 days: as tiles for the whole workspace, and per app on the Apps tab.
How Superwall and Apple data combine
When an app also has the deprecated Apple App Store integration, analytics prefer Superwall and use Apple data only for the days before Superwall has data:
- App Revenue uses Superwall proceeds from the first day Superwall reports revenue for the app, and Apple App Store revenue before that, so nothing is counted twice.
- New Customers works the same way: Superwall new users from the first day Superwall reports one, Apple first-time installs before that.
- New Trials and New Paid Subs come from Superwall only; the App Store integration has no equivalent.
Using Superwall and RevenueCat together
You can connect both Superwall and RevenueCat to the same workspace. Each project takes app data from one of them.
Apps that run Superwall paywalls on top of RevenueCat report the same purchases to both. A project fed by both would count its revenue twice, so viral.app keeps the two apart:
- In the project picker, projects that already use the other provider are listed but cannot be selected.
- Projects linked to the same Apple app count as one project for this rule.
- Different apps can use different providers. One project can run on RevenueCat while another runs on Superwall.
- Map each app through one provider. The same app mapped through both, even to different projects, counts its purchases twice in workspace totals.
To switch a project from one provider to the other, unmap its apps in the first integration, then map them in the second. The newly mapped apps bring their full history with them.