Know which link, campaign and journey drove the purchase.
Validate App Store and Google Play purchases on your own servers and connect revenue to where the user came from and what you sent them.
Revenue
$96,480
+9.2%
Purchases validated
3,418
+6.4%
Trials converted
41.3%
+3.1 pts
Refunds
0.8%
| Source | Type | Purchases | Revenue | Per buyer | Trend |
|---|---|---|---|---|---|
| Referral links | Link | 1,204 | $41,820 | $34.7 | |
| Win-back journey | Journey | 688 | $22,140 | $32.2 | |
| Season launch push | Push | 912 | $18,330 | $20.1 | |
| Link | 530 | $9,870 | $18.6 |
Streamly Premium
Streamly Premium
Yearly subscription
Price$79.99 / year
Trial7 days free
Accountmaria@…
How it works.
- 1
Purchases come in
The SDK reports App Store and Google Play purchases and subscriptions.
- 2
Validated server-side
Your grovs checks each receipt with Apple or Google, so numbers can't be faked by a client.
- 3
Revenue gets a source
Each purchase is tied to the link, campaign and journey behind it.
What revenue does for you.
Revenue you can trust.
Every App Store and Google Play receipt is checked from your servers before it counts.
Purchase
premium_yearly
Your grovs
checks the receipt
Valid
$79.99 recorded
See which channels pay.
Revenue per link, channel and campaign, not just installs.
Revenue by source · 30 days
Follow every subscriber.
Trials, conversions, renewals and refunds on one timeline per user.
User 48213 · Premium yearly
Trial started
Mar 2
Converted · $79.99
Mar 9
Renewed · $79.99
Mar 9, 2027
Every feature.
Included on every grovs plan, cloud or self-hosted.
| Validation | Subscriptions | Attribution | Reporting |
|---|---|---|---|
| App StoreReceipts checked with Apple. | TrialsStarted and converted. | Revenue by linkWhich links bring paying users. | Revenue dashboardsDaily, weekly and monthly. |
| Google PlayPurchases checked with Google. | RenewalsEvery renewal recorded. | Revenue by campaignCompare campaigns by money, not clicks. | Per-buyer valueAverage revenue per paying user. |
| Server-sideRuns on your own servers. | Refunds and cancellationsKept in the purchase history. | Revenue by journeyWhat your messages earned. | ExportCSV and the event stream. |
| Fraud-resistantNo client-reported revenue. | Per-user historyEvery purchase for every user. | Revenue goalsUse purchases as a goal. | Your databasePurchases stored on your side. |
Validation
- App StoreReceipts checked with Apple.
- Google PlayPurchases checked with Google.
- Server-sideRuns on your own servers.
- Fraud-resistantNo client-reported revenue.
Subscriptions
- TrialsStarted and converted.
- RenewalsEvery renewal recorded.
- Refunds and cancellationsKept in the purchase history.
- Per-user historyEvery purchase for every user.
Attribution
- Revenue by linkWhich links bring paying users.
- Revenue by campaignCompare campaigns by money, not clicks.
- Revenue by journeyWhat your messages earned.
- Revenue goalsUse purchases as a goal.
Reporting
- Revenue dashboardsDaily, weekly and monthly.
- Per-buyer valueAverage revenue per paying user.
- ExportCSV and the event stream.
- Your databasePurchases stored on your side.
Questions about a feature?
Talk to an engineer who builds it, or read how it works in the docs.
Runs on your servers.
Revenue is part of the grovs deployment in your cloud or data center. Or start on grovs Cloud and move later.
Stays in your cloud
Purchases and revenue, in your own data stores.
What leaves
Receipts are checked with Apple and Google, the only parties who can validate them.
One SDK, five products.
Each product is one step of the same journey: bring users in, understand them, keep them, monetize and own the data.
Questions, answered.
Something else? Talk to an engineer.
Which stores are supported?
Apple App Store and Google Play, for one-off purchases and subscriptions.
Why validate purchases on the server?
A purchase reported only by the app can be faked. Your grovs deployment checks each receipt with Apple or Google, so the revenue you report is revenue you actually received.
Does this replace RevenueCat?
Not for paywall management. grovs validates purchases and connects them to the links, campaigns and journeys that drove them, inside your infrastructure.
Can we see which campaign or journey drove a purchase?
Yes. Each validated purchase is tied to the user's acquisition link and to the messages they received, so you can compare revenue by channel, campaign and journey.
Are refunds and renewals tracked?
Yes. Renewals, cancellations and refunds update the user's purchase history, so revenue figures stay accurate over time.
Your first link, live this afternoon.
Install the SDK, connect your domain and send a link that opens the right screen. Start free on grovs Cloud, or run the same stack in your own.
Compare plans$0up to 10K monthly users
- Sign up and add the SDK
- Your first link live the same day
- Flat yearly price as you grow
Flat licencea year, in your cloud, no metering
- AWS, Azure, GCP or your data center
- Deployment help from our engineers
- Your SSO, your database, your rules