Provider dashboard and content metrics

1) Purpose and principles

• Daily content funnel management: releases, performance, localization, certification.
• Quality control: build stability, delays, drops, download speed, compatibility.
• Monetization: GGR/NGR, ARPDAU, game-to-bet conversion, revenue by market and partner.
• Growth: A/B tests, ficheflags, UX telemetry, identifying "hidden gems."
• Compliance and availability: licenses, RTP profiles, certification, responsible practices.

• "Signals> data": by default - statuses and anomalies; granularity - by click.
• Roles and Context - Each role sees its KPIs, filters, and recommendations.
• Time to insight <10 sec: filter presets, quick search, important widgets pin.
• Stable refresh intervals, fixed timezone, explicit date/analysis window.

2) Roles and key scenarios

Product Manager (PM): release prioritization, performance tracking, A/B, feature flags.
Content manager: coverage with locales and currencies, catalogs, positions in operator stores.
Commercial/BD: Revenue by Operator and Region, Contracts, Promo Windows, Catalog Deals.
Tech/DevOps: uptime endpoints, latency, build versions, crashes/eliminations, CDN.
QA: build regression, release stability, thermal map bug.
Compliance: RTP/certification/age restrictions, responsible game features.
Support/CS: incidents by operator/guide, frequent complaints, FAQs, quick action.

3) Interface framework (information architecture)

1. Top panel: global filters (period, operator (s), geo, product line, release wave, build version).
2. Main tab "Today": summary of KPI + alerts/anomalies.
3. Content: rating of games, release, "content coverage" (locales, currencies, devices).
4. Commerce: GGR/NGR, ARPDAU, Rev/Operator, margin, rates funnel.
5. Product/UX: sessions, hold, hit rate, volatility, time-to-fun, tutorials.
6. Quality/Technique: uptime API, error rate, FPS/CPU for WebGL, TTFB/TTI, crushes.
7. Compliance: market certification, rate limits, RTP profiles, self-exclusion events.
8. A/B and experiments: goals, sections, confidence intervals, risk/effect.

9. Tools: exports, webhooks, alert subscriptions, "Saved views."

4) KPIs and formulas (recommended minimum)

4. 1 Commercial

Bets = number of bets.
Stake Sum = sum of bets.
Payout Sum = payout amount.
GGR = Stake Sum − Payout Sum.
Promo Cost = bonuses + freespins (cash equivalent).
NGR = GGR − Promo Cost − Platform Fee − PSP Fee.
ARPDAU = NGR/DAU (by game/portfolio).
Take Rate = GGR / Stake Sum.
Conversion to Bet = unique bettors/unique game starters.

4. 2 Product and behavior

DAU/WAU/MAU и Stickiness = DAU/MAU.
Retention D1/D7/D30.
Avg Session Length = total time/number of sessions.
Sessions/User per period.
Hit Rate = (number of wins )/( number of spins) - for slots.
Volatility Index: variance of payments/average rate (normalized).
Time to First Spin/Bet (TTFS): UX friction.
FTUE Completion: Proportion of trainees/tutorial (if any).

4. 3 Quality/Technique

API Uptime (SLA/SLO), p95/p99 Latency by Crete. endpointam.
Crash Rate = (crash sessions )/( all sessions).
JS Error Rate (web), Client Exception Rate (mobile).
TTFB/TTI/TBT (web performance).
Asset Load Success (CDN 200/206/304).
Version Adoption: The share of players on the latest version.
Device/OS Compatibility: Top Problem Bundles.

4. 4 Content and compliance

Localization Coverage = covered locales/target locales.
Currency Coverage = supported currencies/target currencies.
Certification Coverage (by market): Certified/target markets.

5) Recommended widgets (ready-made set)

Home (Today)

Anomaly map: list of incidents (criticality, segment, operator, game).
Top 5 growing games (by GGR, by retention) and top 5 sagging.
"Revenue Pulse": NGR today vs yesterday/week, p-significance of trend.
Error & Crash Pulse: p95 delay, error budget burn-down.

Content

"Release line": release calendar, certification status, locale/currency checklist.
Games rating: positions by GGR/ARPDAU/Retention, geo/operator filters.
"Hidden Gems": Games with low traffic but high ARPDAU/Retention.
"Content Coverage": thermal map of locales/currencies/certifications.

Commerce

NGR by Operator/Geo (treemap + table).

Funnel: "game launch → bet → re-bet → hold D7."

Periodic reports: week/month/quarter, seasonality, promotional effect.

Product/UX

Sessions and retention by cohort (first run = T0).
TTFS, FTUE, session depth, betting frequency.
Frequency heat map feature (free spins, bonus pick, gamble).

Quality/Technique

SLO dashboard: Uptime, Latency, Error budget.
Crushes according to version/device/OS, top stacks.
CDN/Resource Performance Showcase: TTFB/TTI/TBT.

Compliance

Certification by markets, deadlines, audit statuses.
RTP monitor: observable vs theoretical with trust corridors.
Age/responsible features: Reality Check, Limits, Self-Exclusion events.

A/B and experiments

Select a target metric (e.g. ARPDAU, Retention D7).
Status of experiments: duration, power, confidence interval, risk.

Segments: Geo, Operator, Device, Newcomers/Veterans

6) Data and events (minimum telemetry contract)

• `session_start`, `session_end` (user_id, device, geo, operator_id, game_id, version, ts).
• `game_load_start`, `game_load_complete` (timings, assets_count, CDN POP).
• `spin_start`, `spin_result` (stake, win, balance_before/after, bonus_flags).
• `crash` (error_code, stack, device/OS, build, memory/CPU).
• `ab_exposure` (exp_id, variant, ts).
• `feature_flag` (flag_name, on/off, cohort).
• `cert_check` (market, status, ts).
• `localization_check` (locale, coverage_state).

Storage: raw events → streaming (Kafka/Kinesis) → DWH (BigQuery/Snowflake/Redshift) → storefronts.
Справочники: `games`, `operators`, `markets`, `locales`, `builds`, `flags`, `promotions`.

7) Diagram of calculations and shop windows

Fact_Bets (grain: user-game-spin): stake, win, net, flags.
Fact_Sessions (grain: user-game-session): duration, device, crushes.
Fact_Revenue (grain: operator-game-day): GGR, PromoCost, NGR.
Dim_Game/Operator/Market/Locale/Build.
Aggregates: 'Daily _ KPI', 'Release _ Perf', 'AB _ Results', 'Tech _ SLO'.

8) Data quality and trust

Data Contracts: schema versions, backward compatibility, forward alerts when drifting.
Validation: required fields, range control (for example, stake> 0), deduplication.
Observability: ETL job monitor, lags, lot omissions.
Metrics versioning: metrics catalog (owner, formulas, modified date).

9) Alerts and anomalies (example rules)

p95 Latency> SLO (X minutes in a row) - Pager for Tech.
Crash Rate ↑> Y% to the previous day's median - QA/Dev.
RTP Observed extends beyond the corridor [theor − δ; theor + δ] on N spins - Compliance/PM.
NGR by operator ↓ by Z% without promotional events - Commercial.

Failed Certification deadline <7 days - red banner in "Today."

The game did not reach the DAU/Stake threshold after release - PM task with recommendations.

10) A/B tests and decision making

Experimental design: hypothesis → impact on the target metric → risks.
Minimum duration and power (MDE count, α, β).
Traffic layering: by operator and geo for stability.
Report: uplift, confidence interval, probability of superiority (Bayes/freq).
Guardrail metrics: bet stability, crushes, latency.

11) Compliance and responsible practices

RTP profiles, observed RTP control, market reporting.
Age restrictions, betting limits, Reality Check, self-exclusion signals.
Storage and access: RBAC, user_id aliasing, retention policies.

12) RBAC, Tenancy and Privacy

Multi-tenant: separate spaces by operator/partner.
RBAC: roles and scopes (view financials, view PII - prohibition; tech-only - no commerce).
Audit: who viewed/exported, activity log.
PII minimization: user_id - hash/pseudo-ID, prohibition of re-identification in UI.

13) UX patterns and microinteractions

KPI cards with trends and trust "corridors."

Heat maps and rank tables with a fixed header, quick filter.
"Explain this change": pop-up decoding of the anomaly (contribution of regions/operators).
"Pinned views" and sharing presets within the team.
Uniform status color scale (success/warning/critical), dark/light theme.
Mobile companion: summary + alerts + acknowledge only.

14) Implementation checklist (by sprints)

Sprint 1: events, connectors, basic showcases (Daily_KPI, Release_Perf).
Sprint 2: home "Today," games ranking, NGR/GGR, Retention, SLO.
Sprint 3: anomalies, alerts, AB-module.
Sprint 4: Compliance tab, RTP monitor, coverage cards.
Sprint 5: RBAC/Tenancy, Audits, Exports, Saved views.
Sprint 6: UX optimization, mobile summary, auto recommendations.

15) Glossary (brief)

GGR/NGR - gross/net revenue.
ARPDAU - revenue per active player per day.
Hit Rate - winning rate.
Volatility Index - relative variability of winnings.
SLO/SLA - target/contract service indicators.
TTFB/TTI/TBT - web performance metrics.
Coverage - coverage of locales, currencies, certifications.

16) Antipatterns

Mixing roles on one screen (overloading and leaking contexts).
Free metric formulas without definition catalog.
Deep nested filters without presets.
Lack of "explainers" for anomalies and complex schedules.
Opaque A/B reports (no MDE/power/guardrails).

17) The bottom line

1. shows where the situation is changing,

2. explains why,

3. suggests what to do next (experiment, fix, promo, release shift),

4. protected by RBAC and held by SLO,

5. understood by all roles through personalized views.