Key takeaways
- Measure the journey from acquisition to meaningful product use, return visits and revenue.
- Compare users at the same age after acquisition, using consistent attribution and revenue definitions.
- Review contribution and product experience together before increasing spend or ad exposure.
1. Treat growth as a connected system
More installs do not automatically create a stronger app or game business. The people you acquire need to experience something useful or enjoyable, find a reason to return and generate enough value to support the cost of serving and reaching them.
Start by describing that journey. For a game, it might connect an advert, installation, tutorial completion, a satisfying first session and a later return. For a utility or creative app, the important moment may be completing a task or producing a result worth saving.
Agree the business objective and the product experience that supports it. Acquisition, retention and monetization can then share the same priorities instead of becoming separate activities that improve individual numbers while weakening the overall result.
2. Define events before building the dashboard
Create a measurement plan with events that answer decisions you expect to make. Define activation, such as completing a first meaningful task, separately from opening the app. Track the steps that lead to it, alongside relevant purchases, ad revenue and failures.
For every event, record its meaning, trigger, required parameters and owner. Distinguish a purchase attempt from a completed transaction. Check whether repeated screens or retries can create duplicate events, and test the reporting with known actions before using it to guide spending.
Agree privacy and consent requirements with the implementation team. Collect the information needed for the analysis and avoid putting personal content into event parameters. A smaller, reliable event set is more useful than a large dashboard whose numbers cannot be explained.
3. Compare users at the same point in their journey
A cohort groups users who share a characteristic, such as acquisition date. Reviewing cohorts helps you compare what happens after people arrive rather than mixing new users with people who have had weeks to generate activity or revenue.
Define your reporting windows explicitly. For example, decide whether a retention measure means returning on a particular day or returning at any time within a period. Compare revenue after the same elapsed time, and allow recent cohorts enough time to mature before drawing conclusions.
Where the sample supports it, examine acquisition source, country, platform and product version. Keep attribution rules consistent and explain discrepancies between advertising, analytics and revenue reports. Small or incomplete samples should guide further investigation rather than immediate expansion.
4. Separate revenue from contribution
Return on ad spend compares attributed revenue with advertising spend. It does not, by itself, tell you whether the product is profitable. Agree which revenue figure the report uses and which costs are already deducted from it.
A useful working view of contribution starts with the money retained after applicable refunds and transaction or platform deductions, then subtracts acquisition spend and variable delivery costs. Those costs might include paid AI generation, processing or other usage-based services. Avoid deducting a fee twice when the revenue source already reports a net figure.
This is still different from full company profit, which also needs to account for costs such as salaries and overhead. Track the timing of receipts and costs as well: a promising long-term return can still require more working capital than the business can support.
5. Review monetization alongside the experience
Ad-supported products, purchases and subscriptions create different choices for users. A rewarded placement can offer an optional benefit, while an interruption may affect the flow of a session. Paid features need a clear value proposition and a product experience that supports it.
Evaluate placement, timing, frequency and reward design together. Increasing short-term revenue per session is not enough if fewer people return, complete the core task or choose to pay. Review retention, progression or task completion alongside monetization measures.
Check the current policies of the stores and advertising services used in your implementation before changing placements or offers. Test product changes with appropriate controls and review the effect across user groups, rather than assuming that a monetization approach will work equally well everywhere.
6. Give each experiment a decision to support
Choose the most important constraint first. If people install but do not complete the first useful action, investigate onboarding and expectations. If engaged users return but revenue does not cover variable costs, review the offer, delivery costs and monetization design.
Write a hypothesis, a primary measure and guardrails before launching a test. Decide what evidence would support continuing, changing or stopping it. Avoid changing acquisition audiences, onboarding, pricing and ad frequency simultaneously when you need to understand which change caused the result.
Plan a review period that fits the behaviour being measured, with enough data to inform the decision. Record inconclusive results honestly. They can reveal a measurement problem or a question that needs a different experiment.
7. Turn reporting into a working plan
Use a recurring review to connect product and marketing decisions. Check data quality, acquisition costs, activation, retention, revenue and contribution in that order, then agree the next priority and its owner.
Keep a shared record of releases, campaigns and experiments so changes in performance have context. Increase activity in stages when the evidence supports it, while monitoring whether the result holds as the audience or spend changes.
The purpose of the growth plan is to make the next decision clearer. A team that understands both the user experience and the economics can choose more deliberately where to improve the product, invest in acquisition or investigate further.
