Apprvd.app
Join the waitlist

Put revenue next to the behaviour that drives it.

Apprvd.app brings purchase revenue from Google Analytics and subscription metrics from RevenueCat onto the same board as your funnels and experiments — so pricing and paywall decisions are made on one set of numbers.

At a glance
RevenueGA4 purchase revenue, USD
SubscriptionsRevenueCat KPIs
EventsYour purchase events, per app
TestsRevenue per variant
The challenge

Why it's hard today

1
Two sources of truth
Product looks at conversion, finance looks at MRR, and the two dashboards never meet.
2
Paywall tests judged on clicks
A variant that raises trial starts but lowers paid conversion looks like a win on the wrong metric.
3
Non-standard purchase events
Your app logs its own purchase events. Default reports quietly miss them.
The Apprvd.app approach

How Apprvd.app handles it

Your purchase events

Define which events count as revenue for each app. Unset, Apprvd.app uses Firebase's defaults.

RevenueCat alongside

Connect RevenueCat as a source and bind MRR or active subscriptions to KPIs.

Revenue per variant

Experiments report revenue in USD per variant, against the control.

Release impact on revenue

Pricing changes are releases too — compare fourteen days either side.

How it works

From connection to decision

Step 1
Define
Set each app's purchase events and connect RevenueCat.
Step 2
Test
Run paywall and pricing variants through Firebase A/B Testing.
Step 3
Decide
Ship the variant that wins on revenue, not on taps.
Related

Keep exploring

FAQ

Questions, answered

Take the first reading.
Connect a Firebase project and the board fills itself — dashboards, funnels, experiments and push, from data you already have. Apprvd.app opens to the waitlist first.