Player Feature - Previously Played Products

An in-depth look into Previously Played Products, a system Player Feature: how it can be used, the objective of using it, and the logic of how it has been set up.

Previously Played Products 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: Previously Played Products is created based on the Feature Type: Product.
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 Previously Played Products Player Feature is to be able to identify all the product verticals that the player has placed a bet on historically. This will allow you to breakdown and target players based on the verticals they play on your website.

Possible outcomes (Classes)

The possible outcomes (Feature Type Classes) that a player can belong to are:
  1. Casino
  2. Live Casino
  3. Sportsbook
  4. Lottery
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 Previously Played Products, there is one Active Process, or movement, that has been set up to manage player movements between states:
Active Processes
Active Processes

Previously Played Products

  1. This movement is a Time-Based Query that is set to run at a set time of 'Every day at 03:00 UTC'.
  2. The query analyses all the bets that a player has placed historically on the website and identifies in which categories those bets were placed. The categories are then added to the list of Previously Played Products of that player.
  3. Blocked and excluded players are also included.
Previously Played Products
Previously Played Products

🧠 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.
Previously Played Products
Previously Played Products

🏁 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 Current Player Distribution dashboard inside the Player Feature:
Player Distribution
Player Distribution

Segmentation

Following this, you can use Previously Played Products when creating Segments for Activities and Lifecycles. You will be able to find Previously Played Products amongst the Segment Fields when you’re creating a Segment.
Segment Field
Segment Field