Project and server comparison
Open Journal -> Advanced Analytics -> Benchmark. Compare project or game server payments over selected dates and an immediately preceding interval of the same duration.
Filters
| Field | Selection |
|---|---|
| Project | All accessible team projects or one project. |
| Game server | All servers of the selected project or one server. Choose a project first. |
| Period | A calendar preset, year or custom dates. |
| From (UTC) | First included day. |
| Through (UTC) | Last included day. Today includes only the time elapsed at calculation. |
| Compare | Projects combines server payments within each project. Servers shows separate rows with their project names. |
| Payment currency | One currency and precision. First available currency selects the first code and precision present across either period. |
| Rows per page | 1, 5, 10, 25, 50 or 100 groups; default 25. Does not change the summary. |
Use refresh after editing filters. Reset restores the initial settings and the last 30 days. Filters are stored in the page address; reopening it starts at the first page.
Comparable periods
Dates use UTC. Exact boundaries appear below the cards: the start is included and the end is excluded. For example, 1 August through 10 September appears as 2026-08-01 00:00:00 -> 2026-09-11 00:00:00 UTC.
The preceding period ends at the start of the selected period and has the same duration. In this example it is 2026-06-21 -> 2026-08-01. It is not necessarily the previous calendar month or year. When today is unfinished, only elapsed time is compared, up to the calculation instant.
History is not limited to ten years. Choose any available year or range within the supported calendar, starting in 1900. Available dates do not guarantee that payments were recorded and retained for them. If the preceding interval falls before the calendar boundary, the report shows Previous period unavailable.
Measures
| Measure | Meaning |
|---|---|
| Projects / Servers | Groups with payments in either period. The heading count includes all pages. |
| Payments | Distinct payments with receipts in the selected period, including guests. Multiple partial receipts do not count as multiple payments. |
| Paying accounts | Unique master accounts with payments, excluding guests. Accounts in different projects are distinct. |
| Gross receipts | Positive payment receipts in the selected currency and current period, including guests. This is not a wallet balance or net profit. |
| Previous receipts | Receipts in the preceding comparable period. |
| Receipts change | Current minus previous receipts, divided by previous receipts, as a percentage. |
| Average payment | Current receipts divided by the number of payments. |
| Median payment | The middle payment amount after sorting. For an even population, the mean of the two central amounts. |
| Receipts per payer | Receipts linked to master accounts divided by paying accounts. Guest receipts are excluded from the numerator. |
Cards summarize the whole selection, not just the visible page. An account can pay on several servers, so adding server payer counts may exceed the overall distinct count. Different currencies are never added together.
The report includes positive confirmed receipts from ordinary live payments. Test payments, bonus grants and administrative credits are excluded. Processing the same receipt again does not increase totals.
When partial receipts arrive in different periods, each interval includes only its own receipts and counts that payment once. Mean and median amounts also use only receipts within the selected period.
A median can require an additional decimal place: the middle of 2.02 and 3.01 is 2.515. Missing averages are not replaced with zero.
A later refund does not erase the original payment from this comparison. Use the payment journal to inspect individual payments and refunds.
Projects, servers and pages
In Servers mode, payments without a game server appear as Without a server within their project. They are not automatically assigned to other servers. The project label helps distinguish identically named servers.
Rows are sorted by current gross receipts, largest first, with stable ordering for ties. A server with payments only in the preceding interval remains visible: zero current receipts, -100% change and unavailable current averages.
Use Previous / Next to move between pages. Editing filters disables paging until you refresh. If data changes between page requests, refresh from the first page.
Selecting one server applies to both intervals, summary cards and receipt allocation. It does not change the selected currency.
Currencies and guests
A currency code and decimal precision define a separate selection. There is no automatic currency conversion. Selecting a currency absent from both intervals produces an empty result rather than substituting another currency.
Receipt allocation below the comparison shows both periods:
| Column | Meaning |
|---|---|
| Identified account receipts | Receipts linked to a master account. |
| Guest payments | Distinct payments without a master account. |
| Guest receipts | Their total. Added to identified receipts, this equals the period's gross receipts. |
Guests contribute to gross receipts, the mean and median, but not the paying account count. The report contains no email addresses or personal payment details.
History and empty results
Select a year or custom dates to review retained history. The preceding interval is calculated automatically and displayed below the cards.
An empty result means no qualifying payments in either interval. No comparison base means the preceding amount is zero. Previous period unavailable means the preceding interval cannot be constructed within the supported calendar. These are different states.
When calculation is temporarily unavailable, a warning replaces stale results. If the selection is too large, narrow the dates or choose a project. The first page refreshes automatically while you are not editing filters.
For grouping payers by payment recency, frequency and amount, open payer segments.