Trackdesk's Players feature lets you track individual end-customers over their entire lifecycle, alongside the affiliate that originally referred them. Each player carries their own custom metrics — deposits, wagers, plan tier, NGR, anything you can express as a number — and a complete history of how those metrics changed over time. The Players feature is available on iGaming payment plans.
Throughout the dashboard you'll see Player, Brand, Player movement, and Player RevShare. When integrating with the Trackdesk API, the underlying field names use client_* (for example client_id, external_client_id, revenue_origin_id) — see the iGaming glossary for the full dashboard-to-API mapping.
This article explains what a player is in Trackdesk, how players fit into the conversion-tracking model, and how they are registered. Three companion articles cover defining custom player metrics, recording and viewing player movements, and paying affiliates with Player RevShare.
What is a player?
A player is a long-lived record that represents one of your end-customers in Trackdesk. Where an affiliate's conversion captures a single event — a signup, a first deposit, a first wager — a player aggregates everything that happens for that customer over time so you can attribute lifetime activity back to the affiliate who introduced them and reward affiliates on an ongoing basis.
A player is identified by two things together:
External client ID — Your own identifier for the customer, such as their user ID, account number, or player ID in your database. Up to 255 characters. (The "client" in the name comes from the underlying API model; on the dashboard this field is simply your player's external identifier.)
Brand — The operating brand or billing entity the player belongs to. The same external ID can exist under different brands without colliding. In the API this field is named
revenue_origin_id.
Each player is also linked to a standard Trackdesk click generated by your tracking integration. This link ties the player back to the affiliate who referred them, which is what allows every later event on that player to keep paying the right affiliate.
Brands
A brand in Trackdesk is the operator entity that owns a player — typically the operating casino brand or a specific white-label site, for example "Acme Casino". A single external player ID can exist under multiple brands (the same person on two of your sites) without colliding.
Each brand has its own name, billing details, contact email, and status, and lives in Trackdesk as a non-login advertiser entity used for conversion tracking and attribution. In the API and the underlying data model the brand identifier is sent as revenue_origin_id.
How players are registered
Players can only be created by integrating the Trackdesk API with your platform. The recommended pattern is to call the player-creation endpoint whenever your platform creates a new account that should be tracked, sending the following data in the payload:
The external client ID from your system.
The revenue origin ID — the UUID of the brand the player belongs to.
The click ID of the original tracking click that referred the player.
A given external ID can only exist once per brand. If your integration tries to register the same external ID a second time under the same brand, Trackdesk returns an error so you don't create duplicates. If the brand ID in the payload doesn't match any known brand in your workspace, the API rejects the call with revenue origin not found.
Once a player exists, your integration can record any number of player movements against it to track how the player's custom metrics evolve over time.
Player status and self-exclusion
Each player has one of two statuses:
Active — The default. Movements are accepted and the player contributes to revenue-share calculations and reports.
Inactive — The player is preserved but excluded from active processing. Use this when an account is closed, suspended, or otherwise no longer relevant.
Players also carry a self-excluded flag, used in regulated markets to mark customers who have opted out of further activity. Self-excluded players are kept in your data so historical reporting stays intact, and the flag is surfaced as a filter and a column on the Player list so they can be excluded from active reports.
Viewing players in the dashboard
Players have their own top-level menu in the dashboard: Players → Player list. The list includes columns for:
Registration date, internal Player ID, External client ID, and Conversion source ID
Source (the click/affiliate that referred the player)
Brand (the operator entity the player belongs to)
Offer, Country, Status, and Self-Exclusion
Any custom player metrics you have configured, shown as their own columns
Filters mirror the columns: Player ID, External client ID, CID, Sources, Brands, Offers, Locations, Status, and Self-Exclusion.
Where players are used
Once players exist in Trackdesk, three downstream features start working:
Custom player metrics — Define per-player numeric fields (such as total deposits, net gaming revenue, or plan tier) and track them per player.
Player movements — Every change to a player's metric values is recorded as a timestamped movement, giving you a full audit trail and idempotent updates.
Player RevShare on offers — Configure a percentage on an offer and every player movement turns into ongoing affiliate revenue, so affiliates earn on the lifetime activity of every player they referred — not just on the original conversion.