You added an offerwall. Revenue went up. But how much of that revenue is incremental — money you wouldn’t have earned otherwise — and how much is cannibalized from your existing IAP revenue?
This is the question every app developer should ask after integrating an offerwall. And it’s the question most can’t answer. In this guide, we’ll walk through a practical framework for measuring the true incremental LTV impact of an offerwall layer.
Why Incremental Measurement Matters
Offerwalls generate revenue from non-paying users — the 95% who never buy IAP. But if some of those users would have converted to IAP eventually, and the offerwall gives them a free alternative, you’re not adding revenue. You’re shifting it.
The only way to know the difference is to measure it. And the only way to measure it is with a controlled experiment.
The Framework: Cohort Comparison with Holdback
The gold standard for measuring incremental impact is a holdback test — sometimes called a geo-experiment or A/B test with a control group.
Step 1: Define Your Cohorts
Split your user base into two groups:
- Treatment group (90%): Sees the offerwall
- Holdback group (10%): Does not see the offerwall
Use a random assignment based on a stable user identifier (user ID, device ID, or a hashed attribute). The holdback group should be large enough to produce statistically significant results — for most apps, 10% of daily active users is sufficient.
Step 2: Track These Metrics Over 30-60 Days
| Metric | Treatment | Holdback | What It Tells You |
|---|---|---|---|
| Total revenue per user | R_t | R_h | Overall revenue impact |
| IAP revenue per user | IAP_t | IAP_h | Cannibalization effect |
| Ad revenue per user | Ad_t | Ad_h | Whether offerwall eats ad engagement |
| Offerwall revenue per user | OW_t | 0 | Direct offerwall contribution |
| Retention (D1, D7, D30) | Ret_t | Ret_h | Engagement impact |
| Session count per user | Sess_t | Sess_h | Engagement depth |
Step 3: Calculate Incremental LTV
The incremental LTV per user is:
Incremental LTV = R_t - R_h
If your treatment group earns $0.15 more per user than the holdback group over 30 days, your incremental LTV is $0.15. That’s revenue you would not have earned without the offerwall.
Step 4: Measure Cannibalization
Cannibalization is the IAP revenue lost to the offerwall:
Cannibalization = IAP_h - IAP_t
If the holdback group generates $0.08 IAP revenue per user and the treatment group generates $0.06, your cannibalization is $0.02 per user — 25% of holdback IAP.
Net incremental revenue = Offerwall revenue – Cannibalization
If offerwall revenue is $0.12 per user and cannibalization is $0.02, your net incremental revenue is $0.10. That’s the real value the offerwall adds.
Benchmarks by Game Genre
Based on aggregated data across Perkox publishers, here’s what we typically see:
| Genre | Incremental LTV | Cannibalization | Net Incremental |
|---|---|---|---|
| Hyper-casual | +$0.03-0.08 | Negligible | +$0.03-0.08 |
| Casual (match, puzzle) | +$0.05-0.15 | 5-10% | +$0.04-0.13 |
| Mid-core (RPG, strategy) | +$0.10-0.30 | 10-20% | +$0.08-0.24 |
| Hardcore (MMO, competitive) | +$0.15-0.50 | 15-30% | +$0.10-0.35 |
| Utility / non-game | +$0.02-0.10 | Negligible | +$0.02-0.10 |
Key takeaway: cannibalization is real but manageable. Even in hardcore games where it’s highest (15-30%), the net incremental revenue is consistently positive. The offerwall adds more than it takes.
Retention Impact: The Hidden Upside
Revenue isn’t the only metric that matters. Offerwalls consistently show retention improvements in holdback tests:
- D1 retention: +2-5% (users return to check for new offers)
- D7 retention: +5-12% (the “earn” loop becomes a daily habit)
- D30 retention: +8-15% (long-term engagement from non-payers who now have a reason to stay)
Higher retention compounds LTV. A user who stays 30 extra days generates more ad impressions, more offerwall completions, and — counterintuitively — more IAP conversions. The offerwall doesn’t just monetize non-payers; it extends their lifetime.
Common Measurement Mistakes
- Comparing before vs. after — without a holdback, you can’t separate offerwall impact from seasonality, updates, or market changes
- Measuring only offerwall revenue — you need total LTV (IAP + ads + offerwall) to see the full picture
- Running the test too short — 7 days isn’t enough. LTV differences emerge over 30-60 days as retention effects compound
- Ignoring segment differences — the offerwall may have high incremental LTV for casual players but negative LTV for whales. Segment your analysis.
Practical Implementation with Your MMP
If you use AppsFlyer, Adjust, Singular, or Kochava, you can track offerwall events as custom in-app events. Set up:
offerwall_shown— when the offerwall opensofferwall_completed— when a user finishes an offerofferwall_reward— the reward amount (as event value)
Then create a cohort in your MMP dashboard comparing users with vs. without offerwall events. Filter by LTV, retention, and IAP conversion to see the incremental impact.
Conclusion
Measuring incremental LTV isn’t optional — it’s the only way to know if your offerwall is truly adding value or just shifting revenue around. Run a 30-60 day holdback test, track total LTV (not just offerwall revenue), and segment by user type. The data consistently shows that offerwalls generate positive net incremental revenue across all genres — but you should verify that for your own app.
Want to set up proper LTV measurement with your offerwall? Get started with Perkox and our team will help you configure MMP postbacks for accurate incremental tracking.
