Page body
What this page shows
Gaming Performance is the grouped gameplay analytics report.
It aggregates gaming activity by dimensions such as:
- game
- game type
- country
The report is used to compare gameplay quality and revenue behavior rather than banking movement.
When to use it
- compare game or provider performance over the same date window
- inspect grouped GGR and NGR by gaming dimension
- review RTP, house edge, sessions, and player activity
- compare legacy and analytics-backed views when schema mode matters
How to read it
The summary cards give the headline report totals for the current query:
Distinct GamesActive PlayersTotal WageredTotal GGRTotal NGR
The main table is grouped according to the selected Group By dimensions. Operators can combine more than one grouping dimension at the same time, for example Game Title + Country or Game Type + Country. Important reading rules:
Game Typeis backend category-based grouping, not only the FE crash/slot labelActual RTPis calculated from grouped won versus grouped wageredTheoretical RTPis a weighted average using wagered volume only where a configured RTP exists
Filters that change the result
- start date
- end date
- interval
- game identifier
- provider
- country
- game type
- group by
- order by
- show only active
- use new schema
Country and Game Type are immediately applied when the selector changes. The remaining filters are applied through Refresh or by pressing Enter in the text inputs.
Order By is also immediately applied when the selector changes. Provider, Group By, the date range, Active Only, and Use New Schema stay staged until Refresh is used.
Action and filter behavior
Refreshapplies the staged filter state and resets pagination to page 1.Reset Filtersrestores the default grouped query:Group By = Game Title,Order By = Total Wagered,Active Only = OFF, andUse New Schema = ON.Export CSV / Excelis only a CSV action in the current FE despite the mixed label. The button calls the CSV export hook only.- The date pickers stay visible until an interval value has been applied. Choosing
MTD,YTD, orLTDin the UI does not immediately hide the custom date inputs untilRefreshupdates the active interval.
Why this page can differ from other gaming reports
This page is gameplay-performance focused. It groups wagering and win data by game-facing dimensions.
It is not the same as Gaming Revenue, which combines banking movement and gaming totals on a time axis.
Known caveats
- A custom range that starts and ends on today forces the legacy path even when
Use New Schemais enabled. - The visible
New SchemaorLegacy Schemachip mirrors the current FE toggle state; it is not an independent backend source badge. Game Typegrouping is driven by backend category and sub-category mapping, not only by text labels.- The standalone page does not expose a
Sub-categoriescontrol even though the shared hook and dashboard consumer can still passsubCategoryIds. Progressive Contributionis an estimated derived value based on identifiers containingprogressive.Funds in Incomplete Gamesis currently hardcoded to0in the grouped output.- The table can show
No data foundwhile the summary cards still reflect the last successful query if a new request fails and the hook keeps previous data until the next successful response.
Verification status
- status:
verified_backend - FE route, filters, grouping, export, and summary cards are mapped
gs-admin-backendowns the grouping, aggregation, and schema-selection logic- no explicit
nx-workspacedependency is required for the current report semantics