Revenue Per Visitor for Mobile Apps: The Paywall Metric Conversion Rate Misses
Use revenue per visitor to compare mobile app paywalls, pricing tests, annual plans, trial offers, and conversion quality.
Summary
A paywall analytics guide that shows why revenue per visitor is often more useful than conversion rate alone.
RPV combines impressions, conversion, and purchase value.
High conversion can still lose if average revenue is low.
Use RPV with refunds and renewal metrics for durable decisions.
What revenue per visitor measures
Revenue per visitor is total revenue divided by paywall visitors. If 1,000 users see a paywall and the variant generates $3,000, the RPV is $3.00.
The metric is useful because it captures both conversion and price. A monthly plan may convert well but earn less than an annual plan offer with lower conversion and higher revenue.
How to instrument RPV
Track Paywall.viewed for the denominator and Purchase.completed for the numerator. Both events need variant, placement, source, and productId so the dashboard can group results correctly.
For subscription apps, first-purchase RPV is only the start. Renewals, refunds, and cancellations should refine the picture when provider webhook data is available.
Avoid false winners
A variant can look strong on first-purchase RPV but produce more refunds or weaker trial retention. Treat early RPV as a fast signal, not the final answer.
For durable decisions, compare RPV with trial conversion, refund rate, cancellation rate, and week-one retention.
FAQ
Common questions
Is revenue per visitor the same as ARPU?
No. RPV is scoped to paywall visitors, while ARPU usually averages revenue across a broader active user base.
Can RPV be used for trial offers?
Yes, but trial-heavy funnels should also track trial conversion and renewal events because revenue may arrive later.