| Metric | Definition |
|---|---|
| App Revenue | Total net revenue from app purchases and subscriptions during the selected period. Uses RevenueCat or Superwall proceeds where connected and Apple App Store revenue otherwise. |
| New Customers | New customers from RevenueCat or Superwall during the selected period. Falls back to Apple first-time installs where neither is connected. |
| New Trials | New trials started during the selected period, from RevenueCat or Superwall. |
| New Paid Subs | New paid subscriptions started during the selected period, from RevenueCat or Superwall. |
Integrations
RevenueCat integration
Connect RevenueCat to attribute app revenue, new customers, trials, and paid subscriptions to your projects.
The RevenueCat integration connects your RevenueCat account to viral.app so analytics can show subscription outcomes next to creator performance. One connection covers the App Store and Google Play, and it replaces the Apple App Store integration, which is deprecated.
Connect RevenueCat
Open RevenueCat integrations and click Connect RevenueCat. You authorize viral.app on RevenueCat's site; viral.app never sees your RevenueCat password and you can revoke access in RevenueCat at any time.
After you authorize, viral.app loads the projects and apps from your RevenueCat account. Connection status, discovered apps, and recent syncs are all visible on the integration page.
Map apps to projects
Metrics only sync for apps that are mapped to a viral.app project. Map each RevenueCat app to the project that tracks the matching creator content. The Apps tab also shows each mapped app's last 30 days of revenue, new customers, trials, and paid subscriptions, so you can check the right app sits on the right project.
- Mapping an app for the first time starts a full-history backfill for its connection, 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 RevenueCat data from analytics.
A RevenueCat project can contain several apps (for example an iOS and an Android app). You can map them to the same project or to different projects. New Customers is reported by RevenueCat per project, so it can only be attributed when all mapped apps of a RevenueCat project point to the same viral.app project; revenue, trials, and paid subscriptions attribute per app either way.
What syncs and when
viral.app refreshes RevenueCat metrics roughly hourly and re-reads a trailing window of about 35 days on every sync, so late-arriving receipts and refunds are picked up automatically. You can also trigger a sync manually from the integration page.
All amounts are RevenueCat proceeds: revenue net of store commission, converted to USD, bucketed by calendar day in UTC.
Metric definitions
These definitions match the dashboard tooltips on the Analytics Overview.
With RevenueCat connected:
Workspaces that still rely on the Apple integration see the same two cards fed by Apple data. New Customers then equals Apple first-time installs.
Data timing notes, as shown on the dashboard: RevenueCat data can update as receipts are processed, and Apple App Store analytics data typically has a 2-3 day processing delay.
How filters apply to app metrics lists which Analytics filters change these numbers.
How RevenueCat and Apple data combine
When an app has both integrations, analytics prefer RevenueCat and use Apple data only where RevenueCat has no coverage:
- For each app and day, App Revenue uses RevenueCat proceeds when they exist for that day and Apple App Store revenue otherwise, so nothing is counted twice.
- New Customers works the same way per day: RevenueCat new customers where covered, Apple first-time installs on uncovered days.
- New Trials and New Paid Subs come from RevenueCat only; the App Store integration has no equivalent.
If numbers look different from the RevenueCat dashboard, check the selected date range and remember that viral.app reports proceeds in USD by UTC day, filtered to the projects you selected.
Using RevenueCat and Superwall together
You can connect both RevenueCat and Superwall 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.