Player Feature - First Deposit Amount
Let's take an in-depth look into the First Deposit Amount Player Feature: how it can be used, the objective of using it and the logic of how it has been set up.
First Deposit Amount 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: First Deposit Amount 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.
π Objective
The objective of the First Deposit Amount Player Feature is to be able to classify players based on the amount of their first deposit. This allows you to understand how attractive or influential your welcome offer is by monitoring first deposit amount trends.
Possible outcomes (Classes)
The possible outcomes (Feature Type Classes) that a player can belong to are:
- β¬0 - β¬10
- β¬10 - β¬25
- β¬25 - β¬50
- β¬50 - β¬100
- β¬100 - β¬500
- β¬500 - β¬1000
- β¬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:
For First Deposit Amount, there are two Active Processes, or movements, that have been set up to manage player movements between states:
1. On Successful Deposit, for all classes, assign the right class depending on deposit amount
- This movement is a Real-Time movement, based on real-time player events.
- When a player makes a successful deposit they will be moved to the relevant qualifying class (amount bracket) that corresponds with the amount of the first deposit.
- As this is the first deposit, the player will not belong to a class, and therefore no qualifying classes are eligible in the movement.
- As soon as a player matches the segment rule, they will be moved into that class. For example:
- Players with a first deposit amount less than β¬10 will be moved into class β¬0 - β¬10, and so on.
π§ A player will be moved into the corresponding class as soon as they fullfil a segment's criteria.
Therefore it is important that the segments are created ensuring that players can only belong to one segment.
2. Evaluate First Deposit Amount
- This movement is a Time-Based Query that is set to run at a set time of 'Everyday at 03:00 UTC'.
- This query makes a historical check of all players' first deposit amount to ensure they belong to the correct qualifying class.
- Blocked and excluded players are also included.
π§ Important to Note
The amounts in this player feature are predefined.
The first deposit amount is 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.
π 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:
Segmentation
Following this, you can use First Deposit Amount when creating segments for Activities and Lifecycles. You will be able to find First Deposit Amount amongst the segment fields when youβre creating a segment.