Player Feature - Predicted Deposit Bracket

Let's take an in-depth look into the Predicted Deposit Bracket Player Feature: how it can be used, the objective of using it and the logic of how it has been set up.

Predicted Deposit Bracket is a system Player Feature.
✅ This means that it has been created by FT and is available to use as part of the Singularity Model.
🧠 Please note that system Player Features cannot be edited or deleted. If you want to make changes, you must create your own version of the Player Feature.

⚙️ Feature Type

All Player Features must be connected to a Feature Type. Think of the Feature Types as the settings that define the language that we use to talk about important pieces of information. The Player Feature uses these settings and relates them to a player.
The Player Feature: Predicted Deposit Bracket is created based on the Feature Type: Deposit Bracket.
The classes and slugs that are required by the Player Feature, are created and defined in the Feature Type.
📚 Further reading:
​Feature Types​
​Setting up Player Features​
​Movements​

🚀 Objective

The objective of the Predicted Deposit Bracket Player Feature is to be able to predict, based on a player's lifetime depositing history, which deposit bracket they are most likely to fall into in the future. By predicting the future value of a player you can target them with offers that are likely to be more attractive and suitable for the players.

Possible outcomes (Classes)

The possible outcomes (Feature Type Classes) that a player can belong to are:
  1. €0 - €10
  2. €10 - €25
  3. €25 - €50
  4. €50 - €100
  5. €100 - €500
  6. €500 - €1000
  7. €1000 or More
Let's look more closely at how these classes are calculated and how players can qualify to belong to a certain class 👇.

↔ Movements

Movements define the way in which players can be moved from one state to another.
They can either be real-time movements, that occur when a real-time action occurs (such as a payment or registration), or a time-based query. Time-based queries occur at a set time of the day and evaluate the player base to determine if a player should move class.
​
📚 Read more:
​Movements​
​Real-Time Movements​
​Time-Based Queries ​
For Predicted Deposit Bracket, there is one Active Process or movement that has been set up to manage player movements between states:
Active Processes
Active Processes

Evaluate Predicted Deposit Bracket

  1. This movement is a Time-Based Query that is set to run at a set time of 'Everyday at 03:00 UTC'.
  2. We must use a query in this instance as we cannot use any real-time events to help predict future deposit amounts.
  3. The query looks at lifetime deposits and groups players based on the amount of each deposit.
  4. We then count how many deposits were made in each class. The class with the highest number of deposits, or the most common deposit bracket, is selected as the predicted value of the next deposit.
  5. Blocked and excluded players are also included.
Evaluate Predicted Deposit Bracket
Evaluate Predicted Deposit Bracket
Important to Note
The amounts in this player feature are predefined.
The deposit amounts are in your base currency. If you use a different base currency from €, you will need to set up your own version of this Player Feature.

🧠 Queries

Most of the Player Features in the Singularity Model make use of time-based queries. Queries are good for determining states of player inactivity, something a real-time movement is unable to determine.
Our queries are created using ClickHouse and are included in the Singularity Model for you to use.
🧠 Please note that the slug from the Feature Type class must match inside the query.
If you want to write your own queries, you can use the Query Editor or ask Fast Track for assistance. You can find the query editor in: Insights & Analytics menu - Data Studio - Query Editor.
Evaluate Predicted Deposit Bracket computation
Evaluate Predicted Deposit Bracket computation

🏁 What's Next

Dashboards

After some time, once the computation triggers have fired, you'll be able to see that players have now been assigned to one of the classes of Player Feature. You can see this happen in the Player Distribution dashboard inside the Player Feature:
Player Distribution - Predicted Deposit Bracket
Player Distribution - Predicted Deposit Bracket

Segmentation

Following this, you will be able to find Predicted Deposit Bracket in the segment field list to be used for Activities and Lifecycles.
Predicted Deposit Bracket Segment field
Predicted Deposit Bracket Segment field