Choose From Product Economics, Not a Global Benchmark
An earlier version of this guide used unsupported revenue, conversion, and market-share statistics. They have been removed. The correct model depends on how often the user receives value, what it costs to deliver that value, how long users retain, and whether payment is tied to a durable entitlement, recurring service, or attention.
| Product value | Model to test first | Primary risk |
|---|---|---|
| Permanent feature or content pack | One-time in-app purchase | Revenue does not recur while support costs do |
| Ongoing service or refreshed content | Subscription | Weak recurring value produces churn and refund pressure |
| High-frequency free usage | Advertising or rewarded ads | Ad load damages retention and trust |
| Specialized tool with clear pre-purchase value | Paid download | Upfront price reduces trial and acquisition volume |
| Different user segments value different outcomes | Carefully bounded hybrid | Complexity, confusing entitlements, and duplicated monetization pressure |
One-Time In-App Purchases
Use one-time products for durable entitlements, finite content, or consumable value. Define whether a purchase is consumable, non-consumable, restorable, transferable across devices, and available after reinstall.
- Map every product ID to a server-side entitlement rule.
- Handle pending, cancelled, refunded, and revoked purchases.
- Explain what the user receives before the billing flow begins.
- Model future support cost for permanent purchases.
Subscriptions
A subscription is defensible when the app delivers recurring value: maintained infrastructure, regularly updated content, active analysis, synchronization, or an ongoing service. Do not use a recurring charge to repackage a static feature without a clear continuing benefit.
Questions the model must answer
- What new or maintained value does the subscriber receive each billing period?
- Which event shows that the user reached value before seeing the offer?
- What are the renewal, cancellation, grace-period, pause, and account-hold states?
- How are access and data handled after cancellation or expiry?
- Which price, trial, and plan changes require a new experiment or user consent?
Advertising
Advertising can support a free product with frequent usage, but revenue depends on geography, format, demand, session depth, consent, and retention. Do not forecast it from a generic eCPM table.
- Choose formats around natural pauses in the task.
- Measure retention, session completion, crashes, and review sentiment alongside revenue.
- Implement consent and age-appropriate controls for the target markets.
- Use rewarded ads only when the reward is clear and the choice is genuine.
- Prevent accidental taps and layouts that interfere with primary controls.
Paid Download
An upfront price can fit a focused professional tool, a trusted niche product, or an app with a strong demonstration outside the store. The listing must carry more of the sales burden because the user cannot experience the core value before paying.
Model refunds, upgrade strategy, support horizon, regional pricing, taxes, and whether a future paid major version is operationally acceptable.
Hybrid Models Need Explicit Boundaries
A hybrid model is useful when it serves distinct segments, not when every surface asks for money. Examples include a free ad-supported tier with an ad-free purchase, or a subscription with separately priced consumable credits that fund a real variable cost.
User-understanding gate
Build a First-Party Unit Economics Model
Use your own cohorts and keep assumptions visible. At minimum, model acquired users, activated users, payers or ad-eligible users, gross revenue, refunds, platform fees under the program that actually applies, taxes, infrastructure, support, content, and acquisition cost.
| Input | Source | Decision it supports |
|---|---|---|
| Activation and retention by cohort | Product analytics | Whether users reach recurring value |
| Offer views and purchase outcomes | Billing and analytics events | Price, placement, and eligibility tests |
| Refunds, cancellations, renewals | Play Console and backend records | Net revenue and product-quality risk |
| Platform fee | Google's current service-fee documentation | Net proceeds under the applicable program |
| Variable delivery cost | Cloud, content, support, and vendor records | Contribution margin and plan limits |
Validate Before Scaling Acquisition
- Instrument offer view, billing start, purchase result, entitlement activation, renewal, cancellation, and refund.
- Choose one audience and one monetization hypothesis.
- Define a primary metric and guardrails for retention, support load, and user trust.
- Run the test long enough to observe the relevant value and billing cycle.
- Review net proceeds and retention, not only gross purchases.
- Record the decision and rejected alternatives before increasing traffic.
For a billing architecture and measurement review based on your actual product, use the contact form or review the billing setup service.
Evidence standard
Primary references
These first-party sources support the changeable platform requirements in this guide. Your current Play Console notice remains authoritative for account-specific steps.
Review your next Play Console step
Tell us what the account shows, where the release is blocked, and what has already been submitted. We will scope the work around the evidence in your case.
Discuss Your Release