Engagement
Open Journal -> Advanced Analytics -> Engagement. The report shows observed activity of registered players during the selected period. Players are ordered by active days, not by the amount they spend.
Report Fields
| Field | Purpose |
|---|---|
| Project | All accessible projects or one project. The same player in different projects is counted separately. |
| Game server | All servers or a server of the selected project. Cabinet logins are not assigned to individual game servers. |
| Period | A calendar preset, year or custom dates. |
| From / Through | First and last included dates, UTC. Defaults to the last 30 days. The future part of the period is excluded. |
| Activity source | Any activity, successful logins, payments, page visits or cabinet operations. Selects players with that kind of activity. |
| Minimum active days | At least this many distinct days. Defaults to 1. All qualifying activity contributes, not only the selected source. |
| Receipt currency | One currency and precision. Automatic selection uses the first available currency by code and number of decimals. Currencies are not added together or converted. |
| Rows per page | 1, 10, 30, 50 or 100. Page size does not limit the total number of players. |
After changing fields, use the refresh button. Filters remain in the address; reopening starts from the first page. Reset restores the last 30 days, all projects, any activity, at least 1 day and automatic currency selection.
Metrics and Rows
| Metric | Meaning |
|---|---|
| Active players | Players with a qualifying observation and the required minimum number of active days. |
| Active on multiple days | Players active on more than one day. This is not retention between periods. |
| Players who logged in | Players with a successful cabinet login. |
| Players with payments | Players with a qualifying receipt in any currency. |
| Players with page visits | Players with a recorded cabinet page visit. |
| Players with operations | Players with a recorded purchase or another supported cabinet operation. |
| Calendar days observed | Calendar days in the selected range up to refresh time. Today may be incomplete. |
| Received | Receipts from filtered players in the selected currency only. |
Each row shows the player and project, active days and their share of the period, successful logins and login days, payments and receipt days, page-visit and operation days, received amount, and first and last observed activity. Times use the panel's time zone; date boundaries and day counts use UTC.
A day containing a login, a visit and a purchase remains one active day. For example, 48 out of 92 days is 52.2%. Do not add days from different sources: they can overlap. The share of active days is not an artificial score out of 100 and does not measure time spent playing.
Successful Logins
Select Successful logins to keep players with a recorded cabinet login during the period. Failed attempts are excluded. Several successful logins on the same day increase the login count, not the number of days.
Payments
The Payments source selects players with a positive receipt from a real payment during the period. An unpaid payment request, a test transaction or an ordinary administrative credit is not such a payment.
Several partial receipts for one payment count as one payment. If they arrive on different days, receipt days can exceed payment count. Guest payments are not assigned to a registered player.
Page Visits
The Page visits source selects players with a recorded cabinet page view. Page errors and other technical signals are not visits. The report shows distinct visit days, not an exact count of viewed pages.
Cabinet Operations
Recorded shop and service purchases, case openings, lucky wheel spins and gift-code purchases are included. These are cabinet actions, not character movement, combat or game-session duration.
Activity on Several Days
Minimum active days helps select repeated activity. A value of 5 excludes players active on only one to four days. This condition combines with the source and other filters.
A Single Server
Select a project, then a server. Visits, operations and receipts are restricted to that server. The same player's actions on another server do not contribute.
Cabinet logins have no game-server identity, so logins and login days are shown as Not available, not zero, for a server-scoped report. Selecting both Successful logins and an individual server returns an empty list. Return to All servers to analyze logins.
Currencies and Zero Receipts
Changing currency affects amounts only. It does not change the players, payment counts, active days or row order. A player who paid in GBP still counts as a payer when viewing USD.
If an explicitly selected currency has no receipts, amounts are zero while activity remains visible. With automatic selection and no receipt currencies at all, amounts are unavailable because their currency is unknown.
Received is not profit or a balance. Refunds and fees are not subtracted, and advertising cost is not estimated. Use Payments to investigate receipts and refunds.
The Complete List
Players with more active days appear first, followed by those with more recent last activity. Project and player order break remaining ties. Next and Previous cover the entire result, not just the first 50 players.
If data changes during browsing or a page expires, refresh from the first page. Changing filters also starts a new list.
Email appears when the player is found. A profile link requires permission to view profiles. If the profile is no longer found, the row retains its identifier and an explicit missing-player label without a misleading link.
Historical Periods and Empty Results
Choose a year or custom dates from 1900 onward. There is no artificial ten-year limit; results depend on the history actually retained. First and last activity refer only to the selected period, not the account's entire lifetime.
When no observations match, the report shows zero counts and a separate message. This differs from a failed request and from zero receipts among active players.
Access and Errors
The report requires permission to view advanced analytics. Only projects and servers accessible to the staff member participate.
When loading fails, old rows are cleared, a message appears and the request can be retried. If the report is too large, select a project or shorten the period. Late observations may change the result after a refresh.
No recorded activity does not prove that a player did not enter the game. These metrics describe available cabinet observations, not the player's complete in-game activity.