Mobile Games · Growth & Monetization

Player Value & Growth Economics

A practical field guide connecting Minnows, Dolphins, Whales, RFM, ARPU/ARPPU, LTV, CAC, ROAS, payback, and retention into one mobile-game Growth framework.

Payer segmentation Percentiles RFM scoring Mobile-game examples IAP + IAA contextLTV & PaybackROAS & CAC

1. Two different lenses on player value

Whale/Dolphin/Minnow and RFM are both segmentation tools, but they answer different questions.

FrameworkMain questionMain inputsBest use
Minnow / Dolphin / WhaleHow much does this payer spend compared with other payers?Spend / payer percentilePayer value, monetization, VIP analysis
RFMHow recent, frequent, and valuable is this player's behavior?Recency + Frequency + MonetaryLoyalty, churn risk, reactivation, value state
A Whale can be highly active or completely lapsed. RFM adds the context that a spend-only segment cannot provide.

2. Minnows, Dolphins & Whales

These are informal free-to-play monetization labels for different levels of payer value. Unity explicitly notes that the categories differ by game and genre; there is no universal dollar threshold that defines a Whale. [1]

Start with the full player base, not only payers. In mobile games, a large majority of users never make an IAP. AppsFlyer's 2024 gaming report says buyers are typically less than 5% of users. That means the payer segments below usually describe a small slice of the total audience, while the rest are non-payers who may still create value through ads, engagement, social activity, or future conversion. [AppsFlyer 2024 Gaming Report]
LOW SPEND

Minnow

A paying player who spends relatively little compared with the rest of the payer base.

Typical behavior: starter pack, remove-ads purchase, occasional cheap bundle.

MID SPEND

Dolphin

A medium-value payer who spends more consistently or at larger amounts than Minnows, but far less than the highest spenders.

Typical behavior: repeat bundles, battle pass, event purchases, periodic currency packs.

HIGH SPEND

Whale

One of the highest-spending payers in the game. Whales are usually few in number but can contribute a disproportionate share of IAP revenue.

Typical behavior: repeated high-value purchases, strong investment in progression, collection, competition, or convenience.

A useful percentile method

GameAnalytics published a historical analysis that divided monetizers using the 50th and 90th percentiles of total spend distribution. [2]

Payer percentileExample segmentInterpretation
Bottom 50%MinnowsLower-spending half of payers
50th–90th percentileDolphinsMiddle/high spenders below the top tier
Top 10%WhalesHighest-spending 10% of payers
Important: this 50/40/10 split is a useful analytical convention, not a universal industry standard. You can use different thresholds if your game's economy and payer distribution justify them.

Current industry context

AppsFlyer's 2024 gaming report describes Whales as roughly the 2–5% of big spenders who often contribute more than half of game revenue, and reports one Android cut where the top 5% of paying users generated 45.95% of average IAP revenue per app. [3]

That does not conflict with a top-10%-payer definition; it shows why the exact threshold must be defined by the analyst.

3. How payer percentiles are calculated

Percentiles are based on rank among payers, not a fixed dollar value.

Step 1 — choose the spending window

Examples:

  • 30-day IAP spend
  • 90-day IAP spend
  • Lifetime IAP spend
Use the same window for every player. A 30-day payer segment and a lifetime payer segment answer different questions.

Step 2 — sort payers by spend

RankUser30-day spend
1A$1
2B$2
3C$3
4D$5
5E$7
6F$10
7G$15
8H$30
9I$80
10J$200

Step 3 — calculate percentile rank

Percentile Rank ≈ (Rank - 1) ÷ (N - 1) × 100

For User F, Rank = 6 and N = 10:

(6 - 1) ÷ (10 - 1) × 100 ≈ 55.6th percentile

Step 4 — apply your segment thresholds

A–EBottom 50%
→
Minnows
F–I50th–90th
→
Dolphins
JTop 10%
→
Whale
The threshold is produced by your game's payer distribution. A Whale might start at $25 in one game and $250 in another.

Percentile threshold view

If your 10,000 payers have these spend percentiles:

P50 = $4Median payer
P90 = $45Top 10% starts here
P99 = $300Top 1% starts here

An example segmentation could be: Minnow < $4, Dolphin $4–$45, Whale ≥ $45, with an optional “super-whale” group above P99.

4. User share is not revenue share

A small segment can generate a very large share of revenue.

SegmentShare of payersIllustrative revenueRevenue share
Minnows50%$4,5005%
Dolphins40%$24,00027%
Whales10%$60,00068%

Illustrative example; not an industry benchmark.

Whale Revenue Share = Whale Revenue ÷ Total Payer Revenue × 100

GameAnalytics' older 2016 sample of 175M active users found that the Whale cohort generated 86.6% of revenue in that dataset; importantly, their revenue measure included both IAP and advertising. Treat this as a historical example of concentration, not a 2026 benchmark. [2]

Metrics worth tracking by payer segment

  • Payer count and payer share
  • Revenue share
  • ARPPU
  • Purchase frequency
  • Average transaction value
  • Retention
  • LTV
  • Time to first purchase
  • Minnow → Dolphin migration
  • Dolphin → Whale migration
  • Whale churn

5. Unit economics foundations

Player value → revenue → acquisition cost

Be careful with small sample sizes

Growth metrics become more reliable when they are calculated over a sufficiently large number of users. A single unusual payer can distort ARPU, ARPPU, conversion, retention, and LTV estimates when the sample is small.

Small sample

10 players: 9 spend $0, 1 Whale spends $100.

ARPU = $100 ÷ 10 = $10

The arithmetic is correct, but it would be misleading to conclude that a normal player is worth $10.

Larger cohort

With thousands of users, one unusual payer has much less influence on the average.

Always ask: How many users produced this metric?

ARPU vs LTV — the distinction that matters

ARPU and LTV are related because both express value on a per-user basis, but they answer different questions.

ARPU = value during a defined period

ARPU asks: How much revenue did the average user generate during this specific window?

ARPU = Revenue during the period ÷ Users in the population

Adjust defines ARPU as average revenue generated per user over a specified period.

Source: Adjust — ARPU
LTV = cumulative value across the user's lifetime

LTV asks: How much value will the average user generate over the full relationship with the game?

LTV = Expected cumulative value generated by a user over their lifetime

Adjust describes LTV as the value a user generates over the duration of their relationship with the app.

Source: Adjust — LTV

Why the two metrics can look similar

Imagine a cohort of 10,000 users. Their cumulative revenue per user grows as the cohort ages:

Cohort ageCumulative revenue per userHow to read it
D1$0.20The cohort has generated $0.20 per original user by D1.
D7$0.90Cumulative D7 ARPU / observed D7 value.
D30$1.70Cumulative D30 ARPU / observed D30 value.
D90$2.40The same cohort has accumulated more value.
Lifetime estimate$3.20Predicted final LTV if future value is modeled.
The easiest mental model: ARPU is a snapshot for a chosen period; an LTV curve is the accumulation of per-user value as time passes. A D30 cumulative ARPU of $1.70 is not automatically the final LTV if players will continue producing revenue after D30.

Observed LTV vs predicted LTV

Observed value

Revenue already realized by the cohort.

Observed D30 value = $1.70 / user
Predicted lifetime value

Observed value plus expected future revenue.

Predicted LTV = $3.20 / user
Why this matters for UA: a campaign can look weak at D7 but still be profitable over the player's lifetime if the LTV curve keeps growing. Always match the revenue window to the acquisition-cost decision you are making.

CPI and CAC — company working definition

Suppose acquisition spend is $6,000 and the campaign directly generates 3,000 paid installs:

CPI = $6,000 ÷ 3,000 paid installs = $2

During the same period, another 500 users arrive organically. In this company, CAC is defined using all new users acquired during the period:

CAC = Total acquisition spend ÷ Total new users
CAC = $6,000 ÷ (3,000 paid + 500 organic) ≈ $1.71
MetricDefinition used in this guide
CPIPaid acquisition spend ÷ paid attributed installs.
CACTotal acquisition spend ÷ all new users acquired in the period, including paid and organic users.

Why organic users matter — and what “incrementality” means

Organic users still generate revenue, so including them in the company's CAC can make sense for a business-level acquisition view. If $6,000 of marketing activity happens during a period in which 3,500 total users enter the game, the company can evaluate how much it spent relative to the total new audience that will generate future value.

However, there is a separate causal question:

Did the advertising actually cause those 500 organic users to appear, or would some of them have installed anyway?

Incrementality is the idea of measuring the extra users or revenue that happened because of the campaign compared with what would have happened without it. For example, brand exposure, store ranking, word of mouth, or search demand can create an organic lift—but not every organic install during a campaign should automatically be credited to advertising.

So both ideas can be true at once: (1) the company can include organic users in its CAC definition, and (2) analysts should avoid claiming that every organic user was caused by the campaign unless incrementality is measured.

LTV:CAC and ROI

These metrics answer different questions.

LTV = $4    CAC = $2
LTV:CAC = LTV ÷ CAC = 4 ÷ 2 = 2:1
ROI = (Return - Investment) ÷ Investment × 100
ROI = ($4 - $2) ÷ $2 × 100 = 100%

What LTV:CAC tells you

LTV:CAC is an efficiency ratio. It compares how much lifetime value a user generates with how much it cost to acquire that user.

  • 1:1 — lifetime value equals acquisition cost before considering other operating costs.
  • 2:1 — $2 of lifetime value for every $1 of acquisition cost.
  • A higher ratio usually gives more economic room to scale, but very high ratios can also mean you are under-spending and leaving growth opportunities unused.

What ROI tells you

ROI measures the net return relative to the investment. Unlike LTV:CAC, it explicitly subtracts the cost first.

ROI = (Return - Investment) ÷ Investment × 100

In a simplified user-acquisition example, if LTV is treated as the return and CAC as the investment:

ROI = (LTV - CAC) ÷ CAC × 100
Use comparable value definitions. If LTV is gross revenue, the ROI is not yet true profit ROI because app-store fees, taxes, payment fees, servers, royalties, and other costs may still need to be removed. A contribution-margin LTV is often more useful for serious profitability analysis.

Source: AppsFlyer — ROI metrics

The Growth objective is not just “high LTV.” It is: grow LTV relative to CAC, recover CAC fast enough, and keep enough margin to scale.

6. Target ROAS & the efficiency–scale tradeoff

Value-based user acquisition

ROAS compares attributed revenue (or conversion value) with ad spend.

ROAS = Attributed conversion value ÷ Ad spend × 100

If $100 of ad spend produces $80 of attributed conversion value:

ROAS = $80 ÷ $100 × 100 = 80%

What Target ROAS tells Google

With Target ROAS bidding, Google predicts the value of potential conversions and adjusts bids to maximize conversion value while trying to achieve the average ROAS target you set. Google also warns that setting the target too high can limit traffic; lowering it can let the strategy enter more auctions and generate more volume.

Source: Google Ads — Target ROAS bidding

Higher tROASStricter efficiency target
→
Fewer auctionsHarder to find qualifying users
→
Lower scalePotentially less spend / volume
Lower tROASMore flexible target
→
More auctionsMore candidates available
→
More scaleIf unit economics still work

Why an 80% ROAS campaign is not automatically a guaranteed loss

An 80% campaign-attributed ROAS means the ad platform is currently attributing $0.80 of conversion value for each $1 of ad spend in the measurement window. It does not necessarily mean the entire acquisition effort loses $0.20 per dollar forever.

There are two important reasons:

1. Revenue can continue after the reporting window

A D7 ROAS of 80% can become D30 ROAS above 100% if retained players keep purchasing or generating ad revenue.

D7: $0.80 → D30: $1.20 → Lifetime: $2.00

2. Organic users are entering the game too

While a paid campaign is running, organic users can also install and generate future revenue. Under the company's CAC definition, those users are part of the total acquisition base and can improve overall unit economics.

Important distinction: those organic users improve the broader business economics, but they are not automatically part of the campaign's attributed ROAS. To claim the campaign caused an organic lift, you would need incrementality evidence.

The practical decision

The right question is not simply “Is ROAS below 100% today?” It is:

Given our LTV curve, CAC, payback window, organic acquisition, and scale goal, is this ROAS target economically sustainable?

7. LTV curve & payback period

Meeting flow · notebook page 1

The LTV curve shows how cumulative average player value grows as a cohort gets older.

DayCumulative LTV
D0$0.10
D1$0.35
D3$0.85
D5$1.20
D7$1.45
D30$2.20
D90$2.80

If acquisition cost is $1.20, then:

LTV at D5 = CAC = $1.20

D5 is approximately the payback point.

Before payback
LTV < CAC

The cohort has not yet recovered acquisition cost.

After payback
LTV > CAC

The cohort has recovered acquisition cost on an average basis.

Why does the curve flatten?

As time passes, retention falls. Fewer players remain to generate IAP, ad impressions, event revenue, or battle-pass purchases. Cumulative LTV can keep increasing, but the slope normally gets smaller.

Better Retention → Longer Monetization Lifetime → Potentially Higher LTV

Payback is not the same as profitability

A cohort can pay back quickly and still have weak lifetime economics, or pay back slowly and eventually become very valuable.

CohortPaybackLifetime LTVInterpretation
AD7$1.05 on $1 CACFast payback, weak upside
BD30$4.00 on $1 CACSlower payback, much stronger lifetime value
A Growth analyst should be able to answer both: How much will this cohort eventually return? and When do we get the money back?

8. Meta Lookalike & retargeting

Targeting valuable users

Lookalike targeting

A Meta Lookalike Audience is used to find new users who resemble an existing audience. Meta describes Lookalikes as a way to reach new people who are similar to your best existing app users.

A useful real example comes from Meta's Owlchemy Labs case study. The studio created Lookalike audiences from purchasers and installers. Meta reports that purchaser-based and app-installer Lookalikes at 1–2% similarity performed strongly, and a 2% Lookalike audience combined with new creative reduced CPI from $4.46 to $3.56 in one month—about a 20% reduction.

What the case teaches: using known valuable or relevant users as the source audience can help Meta find new users with similar characteristics.

Source: Meta for Developers — Owlchemy Labs success story

Retargeting / re-engagement

Retargeting does something different. Instead of finding new similar people, it targets known users who already interacted with the app and tries to bring them back or move them to another valuable action.

Lookalike
Existing valuable users → Find NEW similar users
Retargeting
Existing / lapsed users → Bring THE SAME users back

For a game, retargeting can focus on users such as:

  • lapsed high-value payers or Whales,
  • players who stopped during a valuable progression stage,
  • former event participants,
  • users who purchased before but have become inactive.
Paid retargeting can be expensive. High-value re-engagement campaigns often optimize toward deeper CPA/revenue events rather than cheap installs, and those events can carry higher prices. AppsFlyer notes that CPA campaign rates are often priced higher than CPI because engaged users are worth more. The key question is whether the user's expected future LTV justifies the reacquisition cost.

At the same time, retargeting can still be economically attractive because the audience already knows the game and may convert more efficiently than completely cold users. So “expensive” should be interpreted as higher acceptable cost for a potentially higher-value user, not automatically poor ROI.

Source: AppsFlyer — remarketing pricing context · Adjust — mobile retargeting guide

9. What is RFM? + how to score it

RFM stands for Recency, Frequency, Monetary. It is a classic customer-value segmentation framework used to distinguish customers using only three behavioral variables. [4] [5]

R — Recency

How recently did the player perform the behavior?

Today - Last Activity Date

Raw value: fewer days is better.

F — Frequency

How often did the player perform the behavior during the chosen window?

# Activities in Period

Raw value: higher is usually better.

M — Monetary

How much monetary value did the player generate during the chosen window?

Revenue in Period

Raw value: higher is usually better.

Academic RFM literature similarly defines Recency as time since the latest behavior, Frequency as the number of purchases/transactions within a period, and Monetary as the amount spent/value contributed. [6]

RFM can be adapted to games in two main ways

ModelRecencyFrequencyMonetaryUse case
Engagement RFMDays since last sessionActive days / sessionsTotal player revenueOverall player state and value
Purchase RFMDays since last purchase# purchasesIAP spendPayer lifecycle and monetization
Do not mix definitions casually. If R means “last session” while F means “purchase count,” your model may become hard to interpret. Define the behavioral event clearly.
RFM scoring

A common implementation assigns each dimension a score from 1 to 5. Oracle documents this 1–5 convention, with 5 representing the strongest recency/frequency/value position. [4]

Quintile scoring

Population bucketR ScoreF ScoreM Score
Best 20%555
Next 20%444
Middle 20%333
Next 20%222
Weakest 20%111
Recency direction is reversed: raw Recency of 1 day is better than 30 days, so the most recent players receive the highest R score.

Worked example

PlayerDays since activeActive days (30d)Revenue (30d)RFM scoreInterpretation
A127$150555Recent, frequent, high value
B220$30544Healthy active payer
C125$0551Very engaged, low monetization
D1518$100255Historically valuable; recency risk
E352$5111Low-value / likely lapsed

Illustrative scoring example. Exact scores depend on the distribution of your own player base.

255 can be more urgent than 551: the first may be a valuable player who is disappearing, while the second is highly engaged but not yet monetized.

10. Recency, current audience & lapsed Whales

Meeting continuation · RFM in practice

The meeting emphasized that Recency comes first because it tells us whether the audience is alive right now. Historical spend is useful, but it can become stale.

Player A

Lifetime spend: $500

Last active: yesterday

RFM ≈ 555

Active Champion Whale.

Player B

Lifetime spend: $500

Last active: 90 days ago

RFM ≈ 115

Historically valuable, but currently lapsed.

Same Monetary value, completely different current business value. That is why RFM is more actionable than a spend-only label.

Purchase RFM vs Engagement RFM

ModelRFM
Purchase RFMDays since last purchasePurchase countIAP spend
Engagement RFMDays since last sessionActive days / sessionsTotal player revenue
Define the event clearly. Do not mix session recency with purchase frequency unless you intentionally design a hybrid model.

The “dead Whale” idea

The meeting shorthand was “retargeting tries to convert M to R.” More precisely:

High historical M + weak R → identify for reactivation → improve Recency if the user returns

You are not converting Monetary into Recency. You are using historical value to decide which low-Recency users deserve attention.

Why can a lapsed Whale justify a higher reacquisition cost?

UserExpected future valueReactivation economics
Normal lapsed player$0.50Very limited budget room
Lapsed Whale$50Can justify much higher reacquisition cost
This does not mean Whale retargeting is always expensive. It means high expected future LTV gives you room to tolerate a higher reactivation cost.

11. ARPPU vs payer conversion — higher ARPPU is not necessarily better

Meeting continuation · monetization quality

This was one of the strongest lessons in the meeting: a high ARPPU can look impressive while hiding a very narrow payer base.

IAP Revenue = Users × Payer Conversion × ARPPU

Two games, same revenue

Game AGame B
Total users10,00010,000
Payer conversion10%1%
Paying users1,000100
ARPPU$20$200
Total IAP revenue$20,000$20,000

Game B has 10× higher ARPPU, but it does not generate more revenue. It is simply far more dependent on a small group of spenders.

How ARPPU can improve while the business gets worse

Imagine most Minnows and Dolphins disappear and only the Whales remain.

BeforeAfter
Payers10020
Revenue$5,000$2,000
ARPPU$50$100
ARPPU doubled, but revenue collapsed. So “ARPPU went up” is not automatically good news.

Always read ARPPU with these metrics

ConversionHow many users become payers?
Payer countHow broad is monetization?
Revenue concentrationAre we dependent on Whales?
Total IAPDid revenue actually grow?

A healthy monetization improvement can be:

Conversion ↑ + ARPPU stable → Revenue ↑

That can be healthier than trying to make a very small group of Whales spend even more.

12. Retention sits underneath all of this

Meeting conclusion · full Growth chain

The meeting ends by connecting monetization back to retention:

You need the player to still exist in the game before you can convert or monetize them repeatedly.
Acquisition
→
Retention
→
Conversion
→
ARPPU / IAA
LTV
→
Recover CAC
→
Profitability
→
Scale

Better retention creates more lifetime opportunities for:

  • first purchase
  • repeat purchase
  • rewarded ads / IAA
  • LiveOps participation
  • social commitment
  • progression
  • Minnow → Dolphin → Whale development
Acquire → Keep → Convert → Monetize → Build LTV → Recover CAC → Scale profitably

13. Turning RFM scores into useful player segments

There is no single universal set of segment names. RFM segmentation should be designed around the business question; even RFM practitioners note that segment rules are subjective and domain-dependent. [7]

SegmentTypical patternGame interpretationPossible action
ChampionsHigh R, F, MActive, loyal, valuableVIP care, premium content, protect experience
Loyal PlayersHigh R/FStrong engagementLiveOps, social systems, progression
Promising Non-payersHigh R/F, low MLikes the game but generates little IAPRewarded ads, starter offers, value bundles
At RiskLow R, formerly high F/MValuable player is becoming inactiveReactivation, event return, personalized communication
Can't LoseVery low R, high historical MLapsed high-value payerHigh-priority win-back investigation
New / PromisingHigh R, low FRecently acquired; little historyFTUE, onboarding, early progression
Hibernating / LostLow R/FInactive and weak engagementLow-cost reactivation or deprioritize

14. Common mistakes

  1. Using arbitrary fixed Whale thresholds without checking your game's payer distribution.
  2. Ignoring the fact that most users are non-payers; payer segments cover only a small part of the total audience.
  3. Calling Whale/Dolphin/Minnow segments personas. They are spend/value segments, not motivation-based personas.
  4. Comparing ARPU and LTV without matching the time window or distinguishing observed from predicted value.
  5. Using CAC without stating the company definition. In this guide, CAC includes paid + organic new users in the period.
  6. Treating an 80% short-window ROAS as a guaranteed business loss without checking later LTV, payback, and organic acquisition.
  7. Forgetting that LTV:CAC is a ratio while ROI subtracts the investment first.
  8. Using RFM scores without documenting the window and the behavior used for R, F, and M.
  9. Forgetting Recency direction: fewer raw days since activity is better, but usually receives a higher R score.
  10. Celebrating higher ARPPU without checking payer conversion, payer count, revenue concentration, and total revenue.
  11. Treating RFM or payer segments as predictions instead of descriptive behavioral/value states.
  12. Ignoring segment migration over time, such as Dolphin → Whale or active Whale → lapsed Whale.

15. Cheat sheet

Minnow
Low-spending payer relative to other payers.
Dolphin
Medium-value payer.
Whale
Highest-spending payer group; usually small but revenue-heavy.
Percentile
A player's rank position within the payer spending distribution.
Recency
How long since the last relevant activity. More recent = stronger.
Frequency
How often the player performs the relevant activity.
Monetary
How much monetary value the player generates.
555
Recent + frequent + high monetary value.
115
Historically/highly valuable but currently inactive/low-frequency.
551
Highly engaged but low monetization.
ARPU
Average revenue per user during a defined period.
LTV
Cumulative/expected value an average user generates over their lifetime.
CPI
Paid acquisition spend divided by paid attributed installs.
CAC
Company definition: total acquisition spend divided by all new users in the period.
LTV:CAC
Lifetime value divided by acquisition cost; an efficiency ratio.
ROI
(Return − Investment) ÷ Investment × 100.
tROAS
Target return on ad spend used by value-based bidding.
Payback
Point where cumulative LTV reaches acquisition cost.
Short version: Whale/Dolphin/Minnow = payer size. RFM = current behavioral value state.

16. Sources & further reading

  1. Unity — The Definitive Guide to Ad Monetization
    Game/genre-specific Whale/Dolphin/Minnow segmentation and monetization treatment.
  2. GameAnalytics — How to Find the Whales in Your Mobile Game
    Historical 2016 analysis using the 50th and 90th spend percentiles across 175M active users.
  3. AppsFlyer — State of Gaming App Marketing 2024
    Modern whale concentration and payer-revenue distribution context.
  4. Oracle — Recency, Frequency and Monetary Models
    RFM definitions and 1–5 scoring convention.
  5. IBM SPSS — RFM Analysis
    RFM theory and ranking logic.
  6. Quality & Quantity (2026) — RFM Model Customer Segmentation
    Recent academic description of RFM variables and segmentation use.
  7. RFM — Introduction
    Practical examples of RFM segment construction and the importance of domain-specific rules.
  8. AppsFlyer — State of App Monetization 2026
    Current hybrid IAP/IAA monetization context.
  9. Adjust — ARPU definition
    Period-based average revenue per user.
  10. Adjust — Lifetime Value
    Relationship between ARPU, cohort value, and LTV.
  11. Google Ads — Target ROAS bidding
    How tROAS bidding uses value signals and why overly high targets can limit volume.
  12. AppsFlyer — ROI metrics
    ROI calculation and activity-metric definitions.
  13. AppsFlyer — ARPPU vs Conversion Rate
    Why payer value and payer conversion answer different questions.
  14. Meta for Developers — Lookalike case study
    Example of Lookalikes built from installers/purchasers to find similar new players.
  15. Meta for Developers — Owlchemy Labs
    Lookalike audience case study with purchaser/installer audiences and CPI improvement.
  16. Adjust — Retargeting Guide
    How mobile retargeting works for existing/lapsed app users.
  17. AppsFlyer — Remarketing pricing context
    Why deeper CPA/re-engagement events can carry higher pricing than CPI.
Source note: historical GameAnalytics and AppsFlyer findings are included as examples of observed distributions, not as universal thresholds for every game. Always calculate your own payer and RFM distributions.