or jump to THE NOTES
https://notion-ga.astrocket.vercel.app/collect?tid=UA-172450343-1&host=notion.so&page=resource119
<aside> 💎 #1: Chart your creatives on a X axis and check your D3/D7/D28 ROAS to quickly spot outlier creatives (both good and bad) so you can act on that (by reallocating spend for example). Example chart here. @10:15
</aside>
<aside> 💎 #2: A benchmark comparing ROAS (e.g. D7/D28) for each week (X axis) with success thresholds allows you to evaluate your UA strategies. Example chart here. @11:29
</aside>
<aside> 💎 #3: Understanding the CPI to spend relationship is a key factor in understanding UA payback and how you can scale your campaign. Example chart here. @13:54
</aside>
<aside> 💎 #4: Questions you need to ask yourself to find the most profitable players (for LAL on Android for example - changes coming to iOS):
</aside>
<aside> 💎 #5: Do not create too many groups/segments of players when looking at LTV. You need to make sure they are different so you can understand which group is better. It is not enough to segment based on how much they purchase however, you need to use other attributes too. @21:45
</aside>
<aside> 💎 #6: If your LTV curve looks like a step function with jumps, either your game is relying mainly on LiveOps offers (not ideal design) or the amount of payers/players is too low. Example chart here. @24:12
</aside>
<aside> 💎 #7: Your special offers are great if you can increase revenue per user while minimizing the discount. The value is in the personalization and showing the right offer (with a relevant content and price) at the right time. Example of special offer delivery system. @30:50
</aside>
<aside> 💎 #8: Predicting LTV is different at different game stages: soft launch, some time after global launch or when the game is at maturity. See characteristics and suggested approach here. @42:58
</aside>
<aside> 💎 #9: In soft launch we do not have the whole LTV curve but we somehow need to calculate the lifetime length so product knowledge is crucial because you're extrapolating. You have to know:
</aside>
<aside> 💎 #10: The most important step in LTV model development is your LTV model and forecast validation. Always have a validation sample to test the model against, and it also must be representative. Make sure you do not build the model to work especially well against your validation sample (i.e. "overfit"). @54:39
</aside>
<aside> 💎 #11: Some time after global launch you need different LTV models: country groups (Tier 1 vs. Tier 2 vs. Tier 3), acquisition sources and optimization types (Google Ads vs. video networks) and monetization types (in-apps vs. ad-based, or live ops vs. regular purchases). @58:10
</aside>
<aside> 💎 #12: Always think about how the LTV model will be used. Example: LTV model for the UA team needs to be working with a small sample size so decisions can be made at the campaign level vs. LTV model for strategic decisions needs to be more accurate and can be more thorough. @01:07:02
</aside>
<aside> 💎 #13: If you are encountering issues when leveraging machine learning, build a quick model with rough "soft launch techniques" for quick validation. Have a few models using very limited amount of data so you can retrain the machine learning models as soon as possible. @01:10:18
</aside>
<aside> 💎 #14: Understanding the impact of LiveOps events on LTV is difficult when only 3 or 4 LiveOps have been done. You can avoid having to wait by looking at peaks during the LiveOps event. "Slice" the LTV curve into smaller periods, define a validation cohort for each slice and calculate the impact on LTV over the period. Then normalize the impact and calculate the final improvement. Example chart here. @01:12:21
</aside>
<aside> 💎 #15: When evaluating the impact of LiveOps on LTV, do not forget to take into account the novelty effect: peaks tend to be higher during the first LiveOps events. @01:13:45
</aside>
<aside> 💎 #16: For special offers LTV prediction models start with a rule-based system, then a probabilistic system and finally machine learning system. With the rule-based system it is less risky and more transparent which also helps you identify the impact of the changes you make. @01:21:55
</aside>