Custom player metrics are numeric fields tracked individually for every player in Trackdesk. They are how you tell Trackdesk what to measure on a per-player basis — total deposits, net gaming revenue, lifetime value, plan tier, anything you can express as a number.
Custom player metrics can only be created by the Trackdesk team. Once a metric exists, its code is permanent and the metric cannot be deleted — only archived. If you need a new metric, contact Trackdesk support with a short description (see Requesting a new metric below) and we'll set it up for you. The rest of this article explains how the metrics you have are configured, where they appear, and how to manage them.
For background on what a player is and how they're registered, see Players in Trackdesk. For how values get recorded against each metric, see Recording and viewing player movements. To use a metric to pay affiliates a percentage of its value, see Player RevShare on offers. For the dashboard-to-API mapping (Player ↔ client, Brand ↔ revenue_origin), see the iGaming glossary.
What a player metric is
A player metric is a workspace-wide definition. Once a metric is created, every player in your workspace gets that metric attached automatically — there is nothing to enable per player. Each metric has a code that your integration uses to record values, and a data type that determines what kinds of numbers the metric can hold.
Metrics come in two data types:
Integer — Whole numbers only. Use for counts: number of deposits, sessions completed, tickets purchased, plan tier.
Decimal — Numbers with fractional precision. Use for monetary values, ratios, or anything that needs decimals: total deposit amount, average bet size, net gaming revenue. Only decimal metrics can be used to drive Player RevShare on an offer.
Where to find your metrics
Navigate to Settings → Players → Metrics. The page lists every metric configured for your workspace, with its name, code, and data type, along with the slot usage counters described above.
Requesting a new metric
Reach out to Trackdesk support (live chat in the dashboard, or your usual contact at Trackdesk) and tell us:
The name — a human-friendly label that will show up in reports and on the Player list. For example, "Total deposits" or "Net gaming revenue".
The code — a short machine identifier your integration will send on every API call. Use lowercase letters and digits with single hyphens between words, for example
total-deposits,ngr, orplan-tier. Pick the code carefully: once the metric is created, the code is permanent.The data type — choose Integer for whole-number counts (number of deposits, plan tier) or Decimal for money and other values with fractional precision (deposit amount, NGR, average bet).
What it represents — a one-line description of what the metric tracks and how your platform calculates it. For example, "the cumulative sum of every deposit a player has ever made, in EUR", or "the player's current loyalty tier from 1 to 5". This helps support sanity-check the choice of integer vs. decimal and avoids any surprises later.
A real-world example end-to-end: an iGaming operator might request a decimal metric called Net gaming revenue with code ngr, defined as "the player's net gaming revenue in primary currency — total bets minus total winnings minus bonus cost, sent as an absolute value after each settlement run". From this single description, support can create the metric and your integration can start sending values on the next deploy.
Coordinate with whoever owns your integration before requesting the metric — the code in your request has to match the code their code will send on every movement call.
What's permanent and what's editable
Two things are locked once a metric exists:
The code cannot be changed. The code is what your integration sends in every movement payload, and renaming it would orphan every historical movement that referenced the old code.
The data type cannot be changed. Switching a metric between integer and decimal would change the meaning of every value already recorded.
The name, on the other hand, can be edited at any time, so use it for anything that might change — translations, friendlier wording, or rebranded terminology. Renaming is the right tool when the metric still measures the same thing but you want it to read better in reports.
Managing existing metrics
From the metrics list each metric is shown with its name, code, and a data-type badge. Two actions are available:
Edit — Rename the metric. The code and data type stay as they were defined.
Archive — Hide the metric from active reports and player views while preserving every historical movement that referenced it. Use this when a metric is no longer in use but you want to keep the audit trail. Archived metrics are not removed from the workspace.
There is no delete action. If you need a metric fully removed from your workspace (rare, and only sensible during early setup), contact support.
Next steps
Once a metric exists, your integration can start recording values against it for any player. Each value sent becomes a movement, and Trackdesk maintains a running balance per player per metric on top of those movements. If the metric is a decimal, you can also configure an offer to pay affiliates a percentage of it via Player RevShare.
Continue with Recording and viewing player movements to see the payload structure, the difference between absolute and relative values, and how to inspect the movement history in the dashboard. To turn a metric into ongoing affiliate revenue, see Player RevShare on offers.