RevenueCat dashboard next to your web revenue
App Store and Google Play subscriptions through RevenueCat, on the same screen as the Stripe or Paddle revenue of the same product.
What Sumly reads
- Every customer's subscriptions, priced by their latest payment
- Payments without tax and less the store's commission
- Each purchase, renewal, cancellation and refund the moment it happens, by webhook
Good to know
- RevenueCat has no list of every subscription, so the full read runs when you connect and then once a day; the webhook fills in between.
- Only production events count, never sandbox ones.
Connect RevenueCat in a few minutes
- 1In RevenueCat: Project settings → API keys → New secret API key, version V2.
- 2Read only: Customer information (customers, subscriptions, purchases) and Charts & metrics → Overview. The Project ID is in the address bar after /projects/.
- 3After connecting, add the webhook it shows under Integrations → Webhooks, so payments arrive as they happen.
- 4To trace purchases to visits, set the attribute
sumly_visitor_idto the SDK's visitor id.
Trace each payment to its visit
Set the subscriber attribute sumly_visitor_id to the SDK's visitor id. RevenueCat keeps names starting with $ for itself, so the attribute has no $. How attribution works.
Questions
Can one project have RevenueCat and Stripe?
Yes. A project can take money through several providers, and Sumly adds them up.
What does the webhook need?
Sumly shows an address and a secret for each connection. Paste both into RevenueCat under Integrations, Webhooks.
Other integrations
Try it with your own projects
Sumly opens to a few founders at a time. Leave your address and what you would connect; we write when your place is ready.
Or look around first: open the live demo.