Player Feature - Acquisition Source

Let's take an in-depth look into the Acquisition Source Player Feature: how it can be used, the objective of using it and the logic of how it has been set up.

Acquisition Source 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: Acquisition Source is created based on the Feature Type: Acquisition Source.
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 Acquisition Source Player Feature is to be able to differentiate players based on origin, whether they registered through an affiliate or not. Offering the possibility to tailor player engagement that is specific to the acquisition source.

Possible outcomes (Classes)

The possible outcomes (Feature Type Classes) that a player can belong to are:
  1. Direct
  2. Affiliated
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 Acquisition Source, there are two Active Processes, or movements, that have been set up to manage player movements between states:
Active Processes
Active Processes

1. On Registration or Login, set Affiliate Reference to either "Direct" or "Affiliated"

  1. This movement is a Real-Time movement, based on real-time player events.
  2. When a player registers or logs in, they will be moved to either Direct or Affiliated depending on their affiliate reference.
  3. On this occasion, players will be classified according to the segment rules:
    1. Players without an affiliate reference will be moved to Direct
    2. Players with an affiliate reference will be moved to Affiliated
Players without an Affiliate Reference
Players without an Affiliate Reference
Players with an Affiliate Reference
Players with an Affiliate Reference
🧠 It is important to note that the segment rules will be checked in sequence and the player will be moved as soon as they match a segment.
Therefore it is important that the segments are created ensuring that players can only belong to one segment.
Set Affiliate Reference
Set Affiliate Reference

2. Evaluate Acquisition Source

  1. This movement is a Time-Based Query that is set to run at a set time of 'Everyday at 03:00 UTC'.
  2. The purpose of this computation is to review all players and evaluate where they should be classified. Players will be classified based on their affiliate reference and regardless of any casino or sportsbook activity.
  3. The query will catch any players who did not make a deposit or log in.
  4. Blocked and excluded players are also included.
Evaluate Acquisition Source
Evaluate Acquisition Source

🧠 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 Acquisition Source computation
Evaluate Acquisition Source computation

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

Segmentation

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