Cohorts are defined as groups of users that have completed a specific action within a specific period of time. A good example of a cohort would be “the players that first launched your game on April 30th, 2015”.
The GameAnalytics Cohorts is a framework build on the classical cohort table view. To define a cohort you will need:
- a completed action to identify the users by (this is automatically set by GameAnalytics to “Start game” event, and cannot be changed)
- a specific period of time for which the cohort will be computed (you can specify it in the date drop-down table).
Note: For cohorts processing we consider days, weeks and months by calendar. All events for Cohorts are calculated every day at midnight UTC, regardless of your locale settings. All custom events that you send to the GameAnalytics servers under the same user are counted for a cohort (not just their first occurrence for the period specified in the cohort).
This view of the cohort table contains:
- Granularity buttons – each metric has a preset of granularity and aggregations available. If a metric or aggregation is not available for a particular metric, it is most likely not characteristic to it.
- Metric picker – Choose any of the custom events instrumented to analyse them by cohorts. This is ideal for analysing things like time to first purchase of a specific store item to how fas users reach a certain level.
- Aggregations – For custom events you can choose to display the values by the Mean, Sum or Count aggregation methods.
Cohorts are a great way of analysing your data. One of its key advantages is being able to follow in-game behaviours such as the adoption rate of a new character or the evolution of players’ buying behaviour over a certain period of time.