Devices
Open Journal -> Advanced analytics -> Devices. This report compares accounts with a successful login during the selected period and their payments. The examples use fictional training data.
Filters
| Field | Behavior |
|---|---|
| Project | All accessible projects or one project. Accounts from different projects count separately. |
| Game server | Available after selecting a project. Restricts both logins and payments. All servers also includes events without a server. |
| Period | Last 30 days by default, another preset, a calendar year or custom dates within available history. |
| From / Through | Both dates are included, using UTC. |
| Group by | Device type, browser or operating system. |
| Payment currency | All currencies or one currency with its precision. Different currencies and precisions are never added together. |
| Rows per page | 10, 25, 50 or 100 groups; 25 by default. |
Apply changed filters with the refresh button. Reset restores the defaults. Filters stay in the page address and are restored when reopening it.
Grouping
Device type groups computers, phones, tablets, other devices and declared automation. Declared automation means the client identified itself as an automated program. It does not verify a bot or justify automatically restricting the account.
Browser compares families such as Chrome, Firefox, Edge and Mobile Safari. Different versions within a family do not create separate rows.
Operating system compares recognized families such as Windows, Linux, Android and iOS. Versions are grouped together here as well.
Account Attribution
An active account has at least one successful login in the selected dates, project and server. Its last qualifying login determines the group. Earlier visits do not increase the account count or duplicate receipts. Rejected attempts and attempts without an identified account are excluded.
An unrecognized value in the last login places the account in Unknown, even if an earlier login had a known value. Browser privacy settings can limit recognition.
Payments are attributed to the account and then its group. This does not identify the device used at checkout, or establish that device type causes an account to pay.
Cards and Measures
Cards summarize the entire result, not only the current page. Unrecognized environment is included in active accounts, not added on top.
Several device types, Several browsers or Several operating systems counts accounts with more than one recognized value of the selected dimension during the period. An unknown observation alone is not a change. This is not a physical-device count: someone can use several browsers on the same computer.
| Table measure | Calculation |
|---|---|
| Accounts | Active accounts assigned to this row by their last successful login. |
| Payers | Accounts in the row with at least one eligible payment under the selected conditions. |
| Conversion | Payers / accounts in the row x 100%. |
| Gross receipts | Confirmed positive payment amounts before fees and refunds. Not net revenue, wallet balances or game coin quantities. |
| ARPU | Receipts in a currency / all active accounts in the row, including non-payers. |
| ARPPU | Receipts in a currency / accounts in the row that paid in that currency. |
Test operations and administrative credits do not increase receipts. Bonuses do not replace the amount paid. Reprocessing a payment does not add its amount again.
Selecting a currency preserves active accounts and groups, while payers, conversion and monetary measures change. With all currencies selected, do not add per-currency payer counts: an account can pay in more than one currency.
Rows without payments display No payments. Rows sort by account count descending. Next and Previous preserve traversal order; changing filters starts from the first page.
Payment Attribution
The lower table shows each currency separately:
- Attributed to active accounts: amounts included in the comparison, including the Unknown row.
- Guests: payments without a registered account.
- Accounts without a qualifying login: payments from accounts without a successful login in the selected dates and scope.
The last two categories do not contribute to conversion, ARPU or ARPPU. They remain visible rather than disappearing. The example includes 225 USD paid by guests and 84.5 EUR paid by an account without a qualifying login.
Empty Results and Errors
New information appears after a short delay. No rows means that the available history contains no qualifying successful logins. It does not necessarily mean no payments.
Refresh if the data changed or the page expired. For an oversized result, select a project or a shorter period. When the report is unavailable, a warning replaces the old rows until a successful refresh.
Inspect individual attempts in the login journal and period totals in payment statistics.