Trackdesk's iGaming product uses native iGaming terminology in the dashboard — Player, Brand, Player movement, Player RevShare. When you integrate with the Trackdesk API, the underlying field names use a generic client_* naming scheme. The data model and behavior are identical; only the label changes.
This glossary lists each iGaming-facing term first, with the corresponding Trackdesk API/data-model concept and a short explanation. Use it as a quick reference when reading the other player-management articles or when integrating with the API.
Core entities
Player — API concept: Client.
The end-customer of your iGaming platform: the person who signs up, deposits, and plays. Each player is a long-lived record in Trackdesk that aggregates everything happening for that user over time, linked to the affiliate that originally referred them. API field names use client (for example client_id, external_client_id), while the dashboard shows "Player" throughout.
Brand — API concept: Revenue origin.
The operating brand or billing entity a player belongs to — for example, "Acme Casino" or a specific white-label site. A brand is modeled in Trackdesk as a non-login advertiser entity with its own name, billing details, and status. The same external player ID can exist under different brands without colliding. In the API the field is named revenue_origin_id.
Conversion source — API concept: same name.
The link between a player and the affiliate who referred them, established by the original tracking click at signup. Every later movement on that player keeps paying revshare to the affiliate identified by this link.
Tracking and movements
Player movement — API concept: Client metric movement.
A timestamped record of one or more player metric values being updated. Every deposit, withdrawal, wager settlement, or NGR adjustment your platform reports becomes a movement. Trackdesk uses the movement history to maintain running balances and to calculate revshare.
Player metric — API concept: Client metric.
A custom numeric field you track per player — total deposits, net gaming revenue, lifetime wager, plan tier. Metrics are workspace-wide definitions; once created, every player automatically has every metric. Metric codes are permanent. Player metrics can only be created by the Trackdesk team — contact support to request a new one.
Balance — API concept: same name.
The current running total for a single player on a single metric, kept up to date by every movement. Reports and revshare calculations read the balance instead of re-summing the full movement history.
Absolute value — API concept: Absolute.
A movement value that replaces the current balance. Use when your platform reports the total state — for example, "the player's lifetime deposits are now 1240.50".
Relative value — API concept: Relative (sometimes called a delta or incremental value).
A movement value that's added to the current balance. Use when your platform reports an event in isolation — for example, "the player just deposited 50" or "refund of -10 processed".
Request ID — API concept: same name (also known as an idempotency key).
An optional identifier you attach to a movement to prevent the same update from being applied twice. If your integration retries a failed call with the same request ID, Trackdesk recognises the duplicate and skips it.
External client ID — API concept: same name.
Your platform's own identifier for the player — typically the user ID, account number, or player ID in your database. Trackdesk does not generate it; you send it on every API call so Trackdesk knows which player you mean. The dashboard sometimes shows this as the player's external identifier.
Affiliate revenue
Player RevShare — API concept: Client RevShare.
A configuration on an offer that pays the referring affiliate a percentage of a chosen player metric — typically NGR or total deposits — on every movement recorded for the player. Where a conversion commission rewards the affiliate once at signup, Player RevShare keeps rewarding them for the full lifetime of every player they referred, in proportion to that player's activity.
Open balance (Player RevShare) — API concept: Client RevShare open balance.
The sum of every revshare contribution from movements that have not yet been included in a settlement. It sits alongside the affiliate's conversion and commission open balances and is paid out the next time you create a settlement for that affiliate.
Settlement — API concept: same name.
A payout cycle that flushes an affiliate's open balance into a paid line item. Once a movement is included in a settlement it is "spent" and no longer counts toward the open balance; only later movements feed the next cycle.
Other concepts
Primary currency — API concept: same name.
Your Trackdesk workspace's base currency. All decimal metric values are interpreted as amounts in primary currency; your integration is responsible for converting before sending if your platform earns in a different currency. Revshare totals are converted from primary currency into the affiliate's payout currency at settlement time.
Self-exclusion — API concept: self-excluded flag.
A flag on a player record indicating that the customer has opted out of further activity, common in regulated iGaming markets. Self-excluded players remain in the data set so historical reporting stays intact but can be filtered out of active reports.