Apprvd.app

Put revenue next to the behaviour behind it.

Bring purchase revenue from Google Analytics and subscription numbers from RevenueCat onto the same view as your funnels and experiments, so pricing and paywall decisions are made on one set of numbers.

At a glance
RevenueGoogle Analytics purchases, in USD
SubscriptionsRevenueCat, as KPIs
Purchase eventsYours, set per app
TestsRevenue for each version
The challenge

Why it's hard today

1
Revenue and behaviour live apart
You watch conversion in one tool and monthly recurring revenue in another, and the two never meet.
2
Paywall tests judged on taps
A version that gets more trial starts but fewer paying customers looks like a win on the wrong number.
3
Purchases logged your own way
Your app logs purchases with its own event names. Default reports can quietly miss them.
How Apprvd helps

What changes with Apprvd

Your purchase events

Tell Apprvd which events count as revenue; until you do, it uses Firebase's defaults.

RevenueCat alongside

Connect RevenueCat and put monthly recurring revenue or active subscriptions next to everything else.

Revenue for each version

Experiments report revenue in US dollars for each version, compared with your current one.

Price changes as releases

Mark a price change and compare the two weeks either side.

How it works

From connection to decision

Step 1
Connect
Set your purchase events and, if you use it, connect RevenueCat.
Step 2
Test
Try a paywall or price change on part of your users.
Step 3
Decide
Ship the version that earns more, not the one that gets more taps.
Related

Keep exploring

FAQ

Questions, answered

Small app. Bigger picture.
Building an app business under $10k in monthly recurring revenue? Sign up for early access to Apprvd. Hands-on integration support included.