Player Feature - Preferred Product

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

Preferred Product 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: Preferred Product is created based on the Feature Type: Preferred 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 Preferred Product Player Feature is to identify each player’s preferred product category across five key verticals: Casino, Live Casino, Sportsbook, Poker, and Lottery.
By determining the most favoured product for each player, we aim to target players with relevant content based on their game type and product preferences in order to increase campaign conversion.

Possible outcomes (Classes)

The possible outcomes (Feature Type Classes) that a player can belong to are:
  1. Casino
  2. Live Casino
  3. Sportsbook
  4. Poker
  5. 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 class 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 Preferred Product, there is one Active Process, or movement, that has been set up to manage player movements between classes:
Active Processes
Active Processes
  1. This movement is a Time-Based Query that is set to run at a set time of 'Every day at 07:00 UTC'.
  2. The query analyses the conversion data of Activities that contained product preference classifications.
    1. This movement calculates the Preferred Product based on the player’s betting activity across different products.
    2. We look at all the bets a player has made on products like casino, live casino, sportsbook, poker and lottery. Each bet is weighted based on how recent it was and the profit margin of the product.
    3. As an example, if a player bets mostly on Casino and a little on Sportsbook, after applying the weights, Casino will have the highest score and will be assigned as the player’s preferred product.
Previously Played Products
Previously Played Products

🧮 Calculation

Preferred Product is calculated based on a player’s betting activity (e.g., number of sessions, stakes, or net revenue contribution) across different products. Each bet is weighted according to how recent it was and the profit margin of the product, and these weighted values are aggregated per product. The product with the highest total weighted contribution is identified as the player’s Preferred Product.
A product’s profit margin represents how much revenue is retained as profit from that product. Margins differ between products: higher-margin products need less betting activity to generate the same revenue as lower-margin products. By giving more weight to bets on higher-margin products, we ensure that the calculation reflects the actual contribution of each product to overall revenue.
For reference, the average profit margins used in this model are:
  1. Casino: 3%
  2. Live Casino: 3%
  3. Sportsbook: 9%
  4. Poker: 10%
  5. Lottery: 40%
These values determine the relative weight of each product when identifying a player’s Preferred Product.

🏁 What's Next

Dashboards

After some time, once the computation triggers have fired, you’ll be able to access two different dashboards with key data about your players inside the Player Feature:
  1. Current Player Distribution Dashboard: See how players have been assigned to one of the classes in the Player Feature.
  2. Last 500 Movements This Week: Track the 500 most recent player movements from one category to another.

Segmentation

Following this, you can use the Player Feature Preferred Product when creating Segments for Activities and Lifecycles. You will be able to find Preferred Product amongst the Segment Fields when you’re creating a Segment.
​
​