Using Monetization Stack to Analyze and Plan Game Revenue
DARPU and an Example of Monetization Stack
One of the key metrics people measure a game (or other products) is called DARPU (often just ARPU), Daily Average Revenue Per User. Depends on the type of game, and how well the game is optimized, the ARPU can be very different. Think of a monetization stack as a break down of what features/categories that contribute to the ARPU.
We’ll look at an example causal arcade game. It has ARPU of 6 cents. In the chart below, we can see how each of the features contributes to overall proportion of the revenue. Ads is self explanatory. The game has Energy, which kind of like lives, which are required to play a level in this game. It limits how many failures you can have before you have to purchase energy/lives to keep trying. The game also has Pre-Game Power-ups, which means when you select a level to play, you get a chance to purchase a power-up (think of the “Color Bomb”, “Jelly Fish” and “Striped and Wrapped” in Candy Crush Saga). In addition, the game offers In-Game Power-ups, which means while you are in middle of a game session, you can purchase additional power-ups (think of the “Lollipop Hammer” in Candy Crush Saga) to help you strategically. The game also offers continues when you don’t pass the level, and get a chance to keep playing to beat the level. In this game, these features all contribute different amount.
Research and Plan:
You can get real data for a monetization stack after your game is launched, but even before you start to design game, you need to think about how your stack will most likely looks like. When you pitch a game, you’ll often asked the question how are you going to make money. Monetization stack helps you answer that question.
The monetization stack will vary depends the genre of the game you’re working on. The monetization stack of a Card Battler (e.g. Ayakashi, Rage of Bahamut) or a 4X game (e.g. Hobbit or Kingdoms of Camelot) will be very different from an Invest and Express game (e.g. Farmville) or an Arcade Game (e.g. Candy Crush). A same game can have different ARPU by platform (web vs. iOS vs. Android) or by market (China vs. US), but often the monetization stack percentages still look the same.
While within each genre, the different games will monetize different amount, but if you looked at enough games within that genre, patterns will emerge.
Best games in each of the genres will monetize about the same range on the same platform in the same market. Experienced game producers or product managers often will know approximately what is a good ARPU for a game of certain genre. For example, best Arcade/Causal games probably will have an DARPU around 6 cents to 8 cents on iOS.
A deeper level analysis and research will reveal how much each of the major features/categories contribute to the monetization stack. Here, often there is pattern also. It is an still an estimate, but you’ll get a sense of how much a similar features will contribute to ARPU. For example, Ads will often attribute 1 cents towards ARPU. In many arcade games such as Candy Crush Saga, “Continues” will monetize much greater than In-game Power-ups, which in turn will contribute more revenue than Pre-game Power-ups. The Continue mechanism is especially powerful and proven, which will typically contribute 50% to 60% of the ARPU. (Although I don’t know the exact numbers of CCS, and I can’t reveal the exact monetization stacks of games that I managed, but I had done enough Arcade games to know that is a good estimate.)
Based on your research data, you can create your planned monetization stack, more confidently answer the question how you are going to make money, and justify the numbers.
How Stack impact Design considerations:
During your planning stages, a monetization stack (even if it is just an estimate or target) will help you prioritize features. Perhaps even drop some features. For example, if we know that In-Game Power-ups often make more money than Pre-Game Power-ups, perhaps more thoughts should be put into the “in game power-ups.”
If you knew in most Arcade games, Continue mechanism is a main contributor to revenue, then it is important to think through what does continue mean in your game. For Candy Crush Saga, that is extra moves; for Ruby Blast, that is extra time. For other games, it may not be very straightforward. This will require the design of the winning condition (what does mean to beat a level) to accommodate this mechanism. It would be much harder to try to add this after game design (especially the winning condition) is baked. I saw a lot of Causal/Arcade games that don’t have this feature, then they are leaving money on the table.
After game is launched, the monetization stack can be used as diagnose tool. For example, if your ARPU isn’t as high as comparable games, then you can dive deeper by looking at your actual monetization stack from data. Often you’ll find a category didn’t contribute as much as expected or as competition, perhaps this feature is badly designed. It would help you focus your resource to fix those features. It also may show gaps between what your monetization stack looks like vs. other game’s monetization stack. You can try to close the gap by adding the right features.
Caveats:
-
Cannibalization effect: we can’t expect to keep adding monetization features and expect the revenue to keep stack up. For example: if feature A contributes 1 cents, but feature B contributes 0.5 cents. Implementing feature A and feature B will not necessarily contribute 1.5 cents total.
-
ARPU (and monetization stack) is just one metric for indicate how good your game is. Don’t ignore other metrics such as retention. Sometimes it is a trade off. As you tighten the pinch, you increase the ARPU but sometimes you reduce the retention.
Conclusion:
1. During planning phase/pitch phase, use monetization stack as a tool to answer the question how your make money in a F2P game and set goals. Do research to find out what other games’ monetization stack look like.
-
During game design/production phase, use monetization stack to help guide your feature priorities and determine best solutions.
-
After game launch, use monetization stack as a metric to see how you stack up (pun intended) against competition and your goals.
notes
Also, this and couple other articles on monetization wrote by me was published on gamasutra.
Related Articles
API Analytics and Monitoring
Introducing AI Explain
We are thrilled to introduce our newest feature to Moesif - AI Explain - a powerful conversational tool that lets you interact with your API analytics data l...
API Analytics and Monitoring
Monitoring Cost and Consumption of AI APIs and Apps
Discover how Moesif can help manage and optimize your AI-driven APIs with powerful observability tools that track costs and usage efficiently.
API Development
Unlock Deep API Insights with Moesif’s HTTP Body Analytics
Learn how to use Moesif to analyze HTTP bodies.
API Analytics and Monitoring
How Moesif API Observability Compares to Treblle
Learn how Moesif’s API observability platform compares to Treblle.