Player RevShare pays affiliates an ongoing percentage of a chosen player metric — for example, a share of net gaming revenue, of total deposits, or of any other decimal metric you track per player. Where a standard conversion commission rewards the affiliate once at signup, Player RevShare keeps rewarding them for the life of every player they referred, in proportion to that player's activity.

This article explains how Player RevShare works in Trackdesk, how to configure it on an offer, and how the resulting revenue flows into affiliate balances and settlements.

For background on the building blocks, see Players in Trackdesk, Custom player metrics, and Recording and viewing player movements. For the dashboard-to-API mapping (Player RevShare ↔ client_revshare), see the iGaming glossary.

Player RevShare is configured per offer. On the offer, you pick:

From that point on, every player movement recorded against a player that came in through this offer is processed in two passes:

The movement's revshare contribution is owed to the affiliate that originally referred the player (resolved through the conversion source on the player). All of an affiliate's unsettled revshare contributions sum to their Player RevShare open balance, which is paid out the next time you create a settlement for that affiliate.

Player RevShare is an additional commission type on top of the offer's existing conversion-based commissions — not a replacement. The same offer can have CPA, CPL, or any other conversion commission configured under Revenue & payouts → Conversions, and Player RevShare configured under Revenue & payouts → Player RevShare, both active at the same time. In that setup an affiliate earns the conversion commission once when the player signs up, and then keeps earning Player RevShare on every movement for the lifetime of that player.

If you only want one or the other on a given offer, simply leave the other configuration blank.

The numeric value your integration sends for a decimal player metric is treated as if it were already expressed in your workspace's primary currency. Trackdesk does not attach a currency to the metric itself — the metric is just a decimal number — so it is up to your integration to send values that are already in the primary currency.

When the rate is applied, the resulting revshare contribution is also in primary currency. At settlement time, Trackdesk converts the affiliate's revshare total from primary currency into the currency of the affiliate's default payment method using the exchange rate at that moment.

In practice this means: if your platform earns and reports values in a currency other than your Trackdesk primary currency, your integration is responsible for converting before sending. Sending a "raw" value in another currency will silently produce the wrong revshare amount.

At least one decimal player metric must already exist in your workspace. Integer metrics cannot be used for revshare — only decimal metrics appear in the metric selector. If the dropdown is empty, you need to request a decimal metric from Trackdesk support first; see Custom player metrics.

You also need players to actually exist on the offer and an integration that records movements against them. Without movements, there is nothing for the rate to apply to. See Players in Trackdesk for how players are registered.

Open the offer detail page for the offer you want to configure, then in the left-hand menu open Revenue & payouts → Player RevShare.

The form has two fields:

Click Save to apply. The new configuration takes effect immediately for any movement recorded from that point onwards — see "Changing the rate later" below for what this means in practice.

Each offer can have one revshare configuration — a single metric paired with a single rate. To stop awarding revshare for an offer entirely, open the form and clear the selection, then save; movements recorded after that will not generate any revshare.

Player RevShare rates are set per offer only. There is currently no way to override the rate for a specific affiliate, affiliate group, country, or other targeting dimension — every affiliate on the offer earns at the same rate on the same metric.

If you need different rates for different affiliates, the cleanest workaround is to clone the offer and assign each group to a separate offer with its own Player RevShare configuration. The underlying tracking integration stays the same; only the affiliate routing changes.

The rate is applied to the change the movement makes to the metric, not to the player's full running balance. This works the same for both value types described in Recording and viewing player movements:

In aggregate, the totals match: across the full life of a player, the sum of all the per-movement revshare contributions equals the player's final metric balance multiplied by the rate. Per-movement accounting is what makes settlements clean — once a movement has been included in a settlement it is "spent", and only later movements feed the affiliate's open balance going forward.

An affiliate's Player RevShare open balance is the sum of every revshare contribution from every movement on every player they referred — across every offer they were on — that has not yet been included in a settlement. It sits alongside the affiliate's conversion and commission open balances and combines with them into the affiliate's overall open balance shown in their account.

When you create a settlement that includes the affiliate, every unsettled movement contributing to that affiliate's revshare is attached to the new settlement. The total revshare amount is converted from primary currency into the affiliate's default payment method currency at the current exchange rate, becomes a Player RevShare line item on the affiliate's settlement, and is paid out alongside their conversion and commission earnings.

After the settlement is created, the included movements are no longer counted in the open balance. Any new movements that come in afterwards start accumulating toward the next settlement.

The Player RevShare open balance can drop below zero — for example, if a relative movement reports a refund or chargeback that contributes a negative revshare amount, or if an absolute movement lowers the metric below where it was. Trackdesk handles a negative revshare balance with three rules that protect both you and the affiliate:

There is no automatic time-based reset, no monthly "forgiveness" rule, and no in-app button to zero out a negative balance. The negative amount carries forward until positive movements bring it back above zero on their own. If you have a specific business reason to write off a negative balance (for example, a contract change or a one-off concession to an affiliate), reach out to Trackdesk support — there is no self-serve option for this today.

A simple example. With a 5% revshare:

Updating the metric or the rate on an offer affects only future movements. Movements that were already recorded keep the revshare contribution they were calculated with at the time, including any that have not yet been settled.

In practice this means:

If you need a clean cut-over (for example, a contract change that takes effect on a specific date), the simplest approach is to update the configuration at that moment and create a settlement first to flush everything earned under the old rate.