Most Active Day of Week 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: Most Active Day of Week is created based on the Feature Type: Day of Week.
The classes and slugs that are required by the Player Feature, are created and defined in the Feature Type.
πŸ“š Further reading;

πŸš€ Objective

The objective of the Most Active Day of Week Player Feature is to be able to understand which day of the week your players are most likely to be active. Looking at the historical data (the last 90 days), we identify which day of the week has the most active days for each player. By understanding the preferred day of the week, you can target your players when they are most likely to be active and responsive.

Possible outcomes (Classes)

The possible outcomes (Feature Type Classes) that a player can belong to are;
  1. Monday
  2. Tuesday
  3. Wednesday
  4. Thursday
  5. Friday
  6. Saturday
  7. Sunday
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 Most Active Day of Week, there is one Active Process, or movement, that has been set up to manage player movements between states;
Active Processes
Active Processes

Evaluate Day of Week

  1. This movement is a Time-Based Query that is set to run at a set time of 'Everyday at 03:00 UTC'.
  2. This query counts the number of deposits and groups them according to the day of the week they were made.
  3. The day of the week with the highest count is the most active day. Players are moved into the class that corresponds to that day of the week.
  4. Blocked and excluded players are also included.
Evaluate Day of Week
Evaluate Day of Week

🧠 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 day of the week
Evaluate day of the week

🏁 What's Next


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
Player Distribution


Following this, you can use Most Active Day of Week when creating segments for Activities and Lifecycles. You will be able to find Most Active Day of Week amongst the segment fields when you’re creating a segment.
Segment field
Segment field