Conversion State 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: Conversion State is created based on the Feature Type: Conversion State (Lifestage).

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 Conversion State Player Feature is to be able to segment players based on where they are in the conversion journey. This covers all steps in the conversion funnel. A Player is considered fully converted when they have made their 4th deposit.

Possible outcomes (Classes)

The possible outcomes (Feature Type Classes) that a player can belong to are:

Registered
Freeplay (bet without deposit)
1st Deposit
2nd Deposit
3rd Deposit
Converted

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 Conversion State, there are seven Active Processes, or movements, that have been set up to manage player movements between states:

Active Processes

1. On Registration set "Registered"

This movement is a Real-Time movement, based on a real-time player event.
Anytime a new player registers on your site, they will be moved to the Registered class.
None of the classes qualifies for this movement. Only new players, who have not been classified before, are eligible to be classified as Registered.

Set to registered

2. Game round from "Registered" change to "Freeplay"

This movement is a Real-Time movement, based on a real-time player event.
When a registered player plays a game round or makes a casino bet, they will be moved to the Freeplay class.
Only players from the Registered class are eligible for this movement.

Registered to Freeplay

3. Successful deposit from "Registered" or "Freeplay" set to "1st Deposit"

This movement is a Real-Time movement, based on a real-time player event.
When a registered or Freeplay player makes a successful deposit, they will be moved to the 1st Deposit class.
Only players from the Registered and Freeplay classes are eligible for this movement.

Registered or Freeplay to 1st Deposit

4. Successful Deposit from "1st Deposit" set to "2nd Deposit"

This movement is a Real-Time movement, based on a real-time player event.
When a player classed as 1st Deposit makes a successful deposit, they will be moved to the 2nd Deposit class.
Only players from the 1st Deposit class are eligible for this movement.

1st to 2nd Deposit

5. Successful Deposit from "2nd Deposit" set to "3rd Deposit"

This movement is a Real-Time movement, based on a real-time player event.
When a player classed as 2nd Deposit makes a successful deposit, they will be moved to the 3rd Deposit class.
Only players from the 2nd Deposit class are eligible for this movement.

2nd to 3rd deposit

6. Successful Deposit from "3rd Deposit" set to "Converted"

This movement is a Real-Time movement, based on a real-time player event.
When a player classed as 3rd Deposit makes a successful deposit, they will be moved to the Converted class.
Only players from the 3rd Deposit class are eligible for this movement.

3rd deposit to converted

7. Evaluate Conversion State

This movement is a Time-Based Query that is set to run at a set time of 'Everyday at 03:00 UTC'.
The purpose of this computation is to review all players and evaluate where they should be classified. The query is looking at the player deposit count and bet count.
This query works by checking the player deposit count and count of bets. It ensures that players are classified the correct way.
Blocked and excluded players are also included.

Evaluate Conversion State

🧠 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 Conversion State

🏁 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:

Player Distribution - Conversion state

Segmentation

Following this, you can use Conversion State when creating segments for Activities and Lifecycles. You will be able to find Conversion State amongst the segment fields when you’re creating a segment.

Conversion State segment fiel

Player Feature - Conversion State