At a glance
| Field | Detail |
|---|---|
| What | Choose the revenue basis and customer population behind an app lifetime value comparison. |
| Who it matters to | App buyers comparing acquisition costs with purchase, subscription, or ad revenue. |
| Where | Google Ads App campaigns, with supporting AppsFlyer, Adjust, and RevenueCat reporting. |
| When it applies | Before using a reported lifetime value to justify an acquisition target. |
| Action | Review deductions, customer definitions, and the value used for bidding together. |
Mobile app LTV, or lifetime value, needs a precise definition before it can support a Google Ads acquisition target. Google's documentation says target return on ad spend, or tROAS, works from the conversion values set for targeted actions. Our suggested starting point is to document how those values relate to the revenue measure used to assess acquisition economics. A dashboard label alone does not establish that relationship. Google Ads bidding documentation
Match the customer population to the acquisition cost
RevenueCat's Realized LTV per Paying Customer chart measures actual cohort revenue after refunds, per customer who became a payer within the selected lifetime. Customers who only started a free trial are excluded. Refunding a customer's first payment within that lifetime also removes that customer from the payer count. The cited page describes Charts v3. RevenueCat's paying-customer chart
Our interpretation: compare a payer-based value with a payer acquisition cost using compatible definitions. Keep a separate comparison for the cost of acquiring the broader customer population. Copying a payer metric into an install-cost decision would leave the populations unmatched.
Even similarly named reports need inspection. RevenueCat's Cohort Explorer groups New Paying Customers by first purchase date and includes customers later refunded. Its separate paying-customer LTV chart groups them by customer cohort date. Review the report definition before treating matching calendar labels as matching users. RevenueCat Cohort Explorer
Choose the revenue basis explicitly
The following options answer different questions. These are reporting definitions and suggested checks, not instructions to replace a campaign's conversion values.
| Measure or approach | Source-backed capability | Limitation | Suggested check |
|---|---|---|---|
| RevenueCat realized payer LTV | Measures actual revenue after refunds per qualifying paying customer. | Store commissions, fees, and taxes have not been deducted. | Record the deductions still needed for the intended economic comparison. |
| RevenueCat Proceeds | Estimates revenue after store taxes and commission. | It is an estimate of store proceeds. | Label it separately from gross revenue and realized LTV. |
| AppsFlyer net revenue | Uses the advertiser's supplied net-revenue value, or a store-revenue calculation after store fees and taxes. | Availability and coverage depend on the reporting setup. | Confirm the definition and supported report before comparing it with another tool. |
| Google Ads tROAS | Optimizes toward a target using conversion values for selected actions. | Automatic equivalence to a vendor's net LTV is not established by these pages. | Trace the targeted action and value back to their source. |
RevenueCat distinguishes gross revenue before refunds from revenue and Proceeds. Its Cohort Explorer deducts a refund in the period when the refund occurs. Our suggested check is to preserve that treatment when explaining differences between exports; changing the revenue basis can change the apparent result without a change in acquisition quality. RevenueCat's revenue measures
AppsFlyer adds another distinction: advertiser-supplied net revenue can follow the advertiser's own calculation. Its documented store-revenue calculation deducts store fees and taxes. The net metrics support Activity and Cohort periods, but not the LTV period, and exclude ad revenue events. They are also unsupported for SKAN and SSOT attribution sources. Our recommendation is to write those exclusions beside an export rather than treating every revenue column as interchangeable. AppsFlyer metric definitions and limits
Check collection and bidding separately
Adjust documents subscription reporting across conversions, renewals, and cancellations by channel, with subscription data stored separately from attribution data. Its Subscriptions solution requires the relevant package. Suggested check: confirm that the lifecycle events needed for your value assessment are actually collected and available. A subscription reporting capability does not establish the conversion value used by a particular campaign. Adjust Subscriptions
Automatic use of a vendor's net-revenue metric as a Google Ads bidding value is not established here. Integration-specific behavior: Not specified in the cited documentation. Review the actual integration before assuming that a reporting change also changes optimization. Our measurement data-path review provides a way to document that relationship.
What to review
- Check whether the denominator represents all customers or paying customers, and how refunds affect inclusion.
- Record whether revenue includes refunds, store deductions, and ad revenue.
- Compare the report's population and revenue basis with the acquisition cost being assessed.
- Check vendor package access and reporting exclusions before requesting a net-value comparison.
- Trace the Google Ads targeted action and conversion value separately from the lifetime-value report.
- Keep the chosen definitions with the acquisition outcome plan so later reviews use the same basis.



