Our All-Inclusive Solution is perfect for mobile games with large player bases and will increase your ARPU. It is safe (through A/B testing) and hands-off, unlocking double-digit growth for your mobile game.
It is difficult to talk at any length about the subject of growing a mobile game, without touching on player LTV, or ‘lifetime value’.
The term ‘LTV’ refers to the amount of revenue a player is estimated to generate over the course of their ‘lifetime’ within a given game. The higher the LTV is for a particular player of your game, the greater the value of that player will be for you over their whole relationship with the game.
So, if you are to scale your mobile game, you will need to keep track of player LTV. But what else do you need to know as you seek to use LTV to help power your game’s growth?
It might seem obvious enough as to why you would want to aim for higher LTV for your mobile game. Making more money from each and every player – both the most committed players and those who might play much more casually – will give you greater financial resources to invest back into the further scaling of your game.
But while player LTV might be just one metric, it is a crucial one for determining the approach you take to the marketing and growth of your mobile game.
LTV can help you with:
LTV, then, can give you a wealth of information and insights into your game. That, in turn, can help give you a better idea of what you need to do in order to maximize revenue and realize your game’s full growth potential.
This is a more complicated question to answer than you might think, as there isn’t just one way to calculate player LTV.
The simplest way would be to divide your game’s total lifetime revenue by the total number of players your game has had since it was launched. That would give you an extremely approximate figure for how much each player of your game is worth, on average.
So if, for example, a user spends 10c a day on average on your game, and plays your game for 60 days, their lifetime value would be 0.10 x 60 = $6. But as we said above, there can be a lot more to calculating player LTV than that – not least because the above formula is based on the assumption of you already having a good amount of historical data on your game. Even then, it can only ever be a rough estimate.
Your business model, as well as the data you have available, might lead to you using a range of variables and formulas for calculating LTV. Metrics often taken into account when calculating monetization include the likes of average revenue per user (ARPU) and average revenue per daily active user (ARPDAU).
Knowing your game’s expected customer LTV will help you determine how much money you can afford to spend on user acquisition campaigns, while still being profitable.
In short. you don’t want the amount of money you spend on acquiring a given user to exceed the amount of money you generate from that user over their ‘lifetime’ of playing your game (their LTV).
The average amount of money that it costs you to acquire a user for your game is known as the customer acquisition cost, or CAC. When it comes to mobile gaming, this measure also refers to cost per install, or CPI. You can calculate it by dividing total ad costs by the number of new players you acquired for your game through those ads.
So, you can probably begin to see that whilst LTV is a key metric, it isn’t a metric that you should be looking at in isolation. It needs to be considered as part of a broader picture.
To give just one very simple calculation as an example, if your game’s average player LTV is 50c ($0.50), but your CPI is 70c ($0.70), this indicates you’re losing 20c ($0.20) for each user you acquire, which is of course, not the desired goal – and requires you to rethink how you’re marketing your game. Remember that we’re talking about how much it costs you to get the user to install the app, including the associated marketing, not how much it costs them to install it.
But when you achieve an average player lifetime value that is higher than the average customer acquisition cost, you will be on a path to a positive return on investment (ROI).
That, in turn, will give you more revenue that can be spent on further user acquisition efforts, thereby helping to achieve growth for your game.
We have written a complete LTV checklist that will help you discover LTV growth opportunities and go into more detail around some of the topics covered previously.
Everything previously discussed is really just the tip of the iceberg when it comes to player LTV, but we hope its importance in achieving sustained growth has been conveyed. Given the complexities of increasing LTV, it is often difficult for publishers to choose the right approach without using a large amount of internal resources, which even then, does not guarantee success.
From our experience, there are always LTV growth opportunities within the metagame, monetization and/or ad monetization. So, please do reach out to us for a 15-minute call that would enable us to explore together how we could help you achieve your LTV objectives for your mobile game.
We’re the games growth specialists, using a combination of data and services to help publishers and owners grow their games. Get in touch for a free performance evaluation and find out how to get more revenue from your game while saving time and costs.
For technical issues and general inquiries, please contact our support.
SKY PARK Offices
Bottova 2622/2
Bratislava, 811 09
Slovakia
Beyond, Aldgate Tower
2 Leman St
London, E1 8FA
United Kingdom
We use cookies on our website.
By clicking “Accept All”, you consent to the use of all the cookies. You may click “Manage cookies” to provide a controlled consent or decline cookies. More information in Cookie Policy.
Cookie | Duration | Description |
---|---|---|
__cfruid | session | Cloudflare sets this cookie to identify trusted web traffic. |
cookielawinfo-checkbox-advertisement | 1 year | Set by the GDPR Cookie Consent plugin, this cookie is used to record the user consent for the cookies in the "Advertisement" category . |
cookielawinfo-checkbox-analytics | 1 year | Set by the GDPR Cookie Consent plugin, this cookie is used to record the user consent for the cookies in the "Analytics" category . |
cookielawinfo-checkbox-functional | 1 year | The cookie is set by the GDPR Cookie Consent plugin to record the user consent for the cookies in the category "Functional". |
cookielawinfo-checkbox-necessary | 1 year | Set by the GDPR Cookie Consent plugin, this cookie is used to record the user consent for the cookies in the "Necessary" category . |
cookielawinfo-checkbox-others | 1 year | Set by the GDPR Cookie Consent plugin, this cookie is used to store the user consent for cookies in the category "Others". |
cookielawinfo-checkbox-performance | 1 year | Set by the GDPR Cookie Consent plugin, this cookie is used to store the user consent for cookies in the category "Performance". |
elementor | never | This cookie is used by the website's WordPress theme. It allows the website owner to implement or change the website's content in real-time. |
viewed_cookie_policy | 1 year | The cookie is set by the GDPR Cookie Consent plugin to store whether or not the user has consented to the use of cookies. It does not store any personal data. |
Cookie | Duration | Description |
---|---|---|
__cf_bm | 30 minutes | This cookie, set by Cloudflare, is used to support Cloudflare Bot Management. |
visitor_id971653 | 10 years | Used by Pardot to provide protection against hackers. |
visitor_id971653-hash | 10 years | Used by Pardot to provide protection against hackers. |
Cookie | Duration | Description |
---|---|---|
_calendly_session | 21 days | Calendly, a Meeting Schedulers, sets this cookie to allow the meeting scheduler to function within the website and to add events into the visitor’s calendar. |
_gaexp | 1 month 6 days 9 hours 24 minutes | Google Analytics installs this cookie to determine a user's inclusion in an experiment and the expiry of experiments a user has been included in. |
Cookie | Duration | Description |
---|---|---|
_ga | 2 years | The _ga cookie, installed by Google Analytics, calculates visitor, session and campaign data and also keeps track of site usage for the site's analytics report. The cookie stores information anonymously and assigns a randomly generated number to recognize unique visitors. |
_ga_PSXVCB6R9N | 2 years | This cookie is installed by Google Analytics. |
_gat_UA-173282740-1 | 1 minute | A variation of the _gat cookie set by Google Analytics and Google Tag Manager to allow website owners to track visitor behaviour and measure site performance. The pattern element in the name contains the unique identity number of the account or website it relates to. |
_gid | 1 day | Installed by Google Analytics, _gid cookie stores information on how visitors use a website, while also creating an analytics report of the website's performance. Some of the data that are collected include the number of visitors, their source, and the pages they visit anonymously. |
CONSENT | 2 years | YouTube sets this cookie via embedded youtube-videos and registers anonymous statistical data. |
pardot | past | The pardot cookie is set while the visitor is logged in as a Pardot user. The cookie indicates an active session and is not used for tracking. |
Cookie | Duration | Description |
---|---|---|
uuid | never | MediaMath sets this cookie to avoid the same ads from being shown repeatedly and for relevant advertising. |
VISITOR_INFO1_LIVE | 5 months 27 days | A cookie set by YouTube to measure bandwidth that determines whether the user gets the new or old player interface. |
YSC | session | YSC cookie is set by Youtube and is used to track the views of embedded videos on Youtube pages. |
yt-remote-connected-devices | never | YouTube sets this cookie to store the video preferences of the user using embedded YouTube video. |
yt-remote-device-id | never | YouTube sets this cookie to store the video preferences of the user using embedded YouTube video. |
yt.innertube::nextId | never | This cookie, set by YouTube, registers a unique ID to store data on what videos from YouTube the user has seen. |
yt.innertube::requests | never | This cookie, set by YouTube, registers a unique ID to store data on what videos from YouTube the user has seen. |