πŸš€ Objective: Use the Singularity Model to have the ability to target players with relevant content based on their game type and product preferences in order to increase campaign conversion.
Firstly, we want to specify the below segmentation capabilities:
  • Product Preference (e.g. Casino / Live Casino / Sportsbook)
  • Game Type Preference
    • Blackjack
    • Slots
With these in mind, we want to look at the game type and product preference in two different time ranges:
  • Short-term (recently = within the last 30 days)
  • Long-term (historically = within the player lifetime)
Every feature that you create should be meaningful to ensure it's relevant for your use.
BelowπŸ‘‡ we will walk you through a step-by-step guide on how to use the Data Studio and Singularity Model in order to achieve this objective.

πŸ“Š Define Segmentation in the Data Studio

Firstly, we need to clarify the definitions behind the different types of segmentation. We can do this with the help of the Data Studio, to find out the possible values for Game Type and Product that are needed to create the Feature Types.
Navigate to: Insights and Analytics --> Data Studio --> Dashboards
Dashbords in the Data Studio
Dashbords in the Data Studio
Create a Brand Dashboard Group and add a new dashboard into that group. Click to open the new dashboard and add a widget to your dashboard. For this objective, we need to select Casino Performance in order to get the relevant data.
Create dashboard
Create dashboard

Add Dimension

Once the widget is added, select Casino Game Type as the dimension. This will check the database for all values captured on the game_type field in the casino event.
Run the query to get a list of all the values that we can use later to define the product and game type preferences.
Add dimension
Add dimension

πŸ“ Map out Definitions

Using the values from the Dashboard, we can map out the definitions of Product Preference and Game Type Preference.
Product Preference
A player should be classified by the product that they have bet the largest amount on;
Product Event Key Value
Casino
Casino Event
game_type
slots
Casino
Casino Event
game_type
jackpot
Live Casino
Casino Event
game_type
baccarat-sic-bo
Live Casino
Casino Event
game_type
blackjack
Live Casino
Casino Event
game_type
first-person
Live Casino
Casino Event
game_type
game-show
Live Casino
Casino Event
game_type
poker
Live Casino
Casino Event
game_type
roulette
Game Type Preference
A player should be classified by the specific Game Type that they have bet the largest amount on;
Game Type Event Type Value Key
Slots
Casino Event
slots
game_type
Jackpot
Casino Event
jackpot
game_type
Baccarat
Casino Event
baccarat-sic-bo
game_type
Blackjack
Casino Event
blackjack
game_type
First Person
Casino Event
first-person
game_type
Game Show
Casino Event
game-show
game_type
Poker
Casino Event
poker
game_type
Roulette
Casino Event
roulette
game_type

βš™οΈ Create Feature Type

Now that we have all the information we need, we can set this up as a Feature Type inside the Singularity Model. Starting with the Product Preference we can create a new Feature Type.
πŸ“š Read about setting up a new Feature Type here.
For this objective, we need to set it up as in the image below. Set up a class for each value identified.
Feature Type: Product Preference
Feature Type: Product Preference
🧠 Note: The Slug will later be used in the computations to make sure the relevant data is connected to the Class.
Next, repeat the same by creating a Feature Type for Game Type Preference, as in the image belowπŸ‘‡.
Feature Type: Game Type Preference
Feature Type: Game Type Preference

πŸ‘©β€πŸ‘©β€πŸ‘¦β€πŸ‘¦ Create Player Feature

Now that we have the Feature Types set up, we can create the relevant Player Features.
As mentioned in the objective, we want to assess a player's preference in two different time ranges: short and long term. We should set up one Player Feature for each preference and for each time range. That will result in 4 Player Features;
  • Product Preference (short-term) - (using Feature Type Product Preference)
  • Product Preference (long-term) - (using Feature Type Product Preference)
  • Game Type Preference (short-term) - (using Feature Type Game Type Preference)
  • Game Type Preference (long-term) - (using Feature Type Game Type Preference)
🧠 Note: For these 4 player Features, we do not want to set a default value.
The default value is the value a player will be assigned if they have not yet been classified as any other value.
πŸ“š Read more about how to create a new Player Feature.
Product Preference (short-term)
Here is an example of how to set up the Player Features:
Player Feature - Product Preference (short-term)
Player Feature - Product Preference (short-term)

πŸ–₯ Add Computations (Manage Movements)

Step two of setting up the Player Features involves managing the player movements, or computations. This will calculate and assign players to the features we have created.
🧠 Note: The type of Action will define when the calculation takes place.
This is similar to how an activity can fire actions on either a real-time event specifically for the player or a set time for all players.
For this objective, we want the computation to run on a time-based query and ideally during low traffic, therefore we have set it to trigger at 03:00 UTC.
πŸ“š Read more about Computations.
From the Player Feature page, click Manage Movements.
Add a new time based query
Add a new time based query
Set up your time-based query with a computation trigger set to 03:00 UTC. To do this, you will need to create the query against the database where the computation will be done. Here you need to identify certain tables, fields and statements.
πŸ™‹β€β™€οΈ Please reach out to Fast Track in case you need assistance with the query.
Once the query is completed, simply decide a name for the computation and click Update.
Manage Movements
Manage Movements
Repeat this step for each of the 4 Player Features.

Segmentation

After the computation trigger has fired (03:00UTC in our example), you'll be able to see that players have now been assigned to one of the classes of your Player Feature.
You can see this happen in the Player Distribution dashboard inside the Player Feature:
Dashboard: Player Distribution Dashboard
Dashboard: Player Distribution Dashboard
Following this, you will be able to find the Product Preference and Game Type Preference in the standard segmentation list to be used for activities and lifecycles.
Segmentation fields
Segmentation fields