Operator guideENdashboardplayersrankingstable

Dashboard / Player Statistics

Top-player table for winners, losers, and depositors, with rank, player identity, level, and amount shown in a compact comparison view.

Reader view

Clean portal guidance

This page keeps the operator explanation, field and action descriptions, and screenshots visible without exposing repo paths, raw sidecars, or editorial-only implementation details.

Narrative content

Page body

What this widget shows

Player Statistics shows ranked lists of players in three views:

  • Winners
  • Losers
  • Depositors

Use it when you need a quick answer to who is leading a particular ranking over the selected period.

How to read it

Each row shows:

  • rank
  • player identity
  • level
  • amount

For players with a user id, the email is clickable and opens the player profile.

Filters that change the result

  • Date option
  • Start date
  • End date
  • Limit

Filter apply model

  • Limit auto-submits immediately.
  • Date option auto-submits immediately.
  • Start date and End date auto-submit when changed.
  • There is no separate Apply Filters button on this widget.

Important implementation notes

The depositor dataset is transformed in the frontend before rendering:

  • actioneeName is renamed to username
  • depositAmount is renamed to amount

This means the table is not showing the raw backend field names for depositor rows.

Common questions

Why is the player column showing email instead of username?

Because the visible identity in the table is built around email and country for operator use. The frontend links the row to the player profile when userId exists.

Why can the deposited amount label differ from backend naming?

Because the frontend renames depositAmount to the common display field amount.

Known caveats

  • The current code maps the Winners tab to topTenLosers and the Losers tab to topTenWinners. Treat this as an unresolved FE mapping caveat until product or backend owners confirm that the labels are intentionally inverted.
  • Depositor rows use a frontend remap before rendering:
    • actioneeName -> username
    • depositAmount -> amount Operators should therefore read the visible table labels, not assume the raw backend field names are shown unchanged.
  • The visible refresh icon is only a FE loading animation. It does not call the data hook refetch and does not change filters on its own.
Grid columns

Columns

field

Rank

Position within the currently selected top list.

field

Player

Player identity block used by operators to open the profile or recognize the user.

field

Level

Current player level displayed as a chip.

field

Amount

Amount associated with the current ranking category.

Data Type
amount
Filter dictionary

Filters

field

Limit

Type
numeric-select
Caveat
Shared Formik helpers submit this change automatically.
field

Date option

Type
preset-range
Caveat
Shared Formik helpers submit this change automatically.
field

Start date

Type
date
Caveat
Visible only when `Date option` is `custom`.
field

End date

Type
date
Caveat
Visible only when `Date option` is `custom`.
Metric dictionary

Metrics

metric

Rank

Position within the active winners, losers, or depositors view.

Verification Status
verified_backend
metric

Amount

Amount shown for the current ranking row after FE normalization.

Verification Status
verified_backend
metric

Level

Player level shown next to the ranked identity row.

Verification Status
verified_backend
Operational notes

Notes

item

Frontend rendering is standardized around Player.amount even when backend naming differs.

item

The FE currently maps `Winners` to `topTenLosers` and `Losers` to `topTenWinners`; docs treat that as an unresolved presentation caveat rather than an intentional product guarantee.

item

Depositor rows are normalized in FE before render, including `actioneeName -> username` and `depositAmount -> amount`.

item

The visible refresh icon only controls local `isRefreshing` state in the widget component and does not call the hook refetch function.

Related references

Related pages

pageDashboard / Bonus Payouts

Shared comparison widget rendered for tournament, challenge, and no-deposit bonus payout groups.

pageDashboard / Game Reports

Deep comparison widget for Games and Providers with separate backend paths, multiple grouping options, search, and a mix of backend and frontend summary logic.

pageDashboard / GGR Chart

Revenue trend chart with frontend summary cards derived from the loaded time series.

pageDashboard / KPI Reports

Sortable KPI table for games or providers, used to compare betting and GGR-style metrics by entity rather than by time bucket.

pageDashboard / KPI Summary

Comparison table for high-level KPI rows across today, yesterday, month-to-date, and the selected period, with frontend trend chips and data-source badges.

pageDashboard / Live Player Report

Card-based snapshot of today's GGR, total players, conversion rates, active players, and merchant balance.