What this page shows
Players / Activity Log is the standalone history view for player-related activity rows. It is useful when operators need to investigate activity across many players instead of opening one player profile at a time.
The page combines:
- activity filters and extra player-segmentation filters
- a paginated, sortable activity table
- three summary cards for the currently loaded rows
- CSV export for the filtered activity result set
- a map dialog for IP-location inspection
- row-level detail blocks for descriptions, JSON payloads, and user-agent data
- special website-search row details for search query, result count, and games received
- comment-group management when the component is opened in COMMENT mode
When to use it
Use this page when you need to:
- inspect comments or operational history across players
- filter activity by date range, activity type, device, PID, or country
- narrow the result set with include/exclude tags or comment groups
- compare desktop vs mobile activity in the current result set
- inspect activity rows on a map or open row-level JSON/detail blocks
- export filtered activity rows
How to read it
This page is history-first. Operators usually set filters first, then read the resulting table, export the result, or open row-level detail for one activity.
The header count shows total records matching the current query. The summary cards below the header are different: they are calculated from the rows currently loaded into the table component.
The summary cards are:
Total ActivitiesDesktopMobile
Key visible columns include:
IDActivityMethodUserComment GroupCRM UserCRM RoleDeviceIP AddressTime
Filters
The main filter panel includes:
DescriptionActivityDeviceStartEnd
Extra filters can be revealed when needed:
CountryPIDUser IDInclude TagsExclude Tags
Important behavior:
Apply Filtersreloads the activity table and resets it to page 1.Resetreturns the form to its default values and reloads the table.- filter summary chips can clear one active filter at a time.
PIDlooks up matching players first, then returns activity rows for those players.Include Tagskeeps players with all selected tags.Exclude Tagsremoves players with any selected excluded tag.- date filtering is reliable when both
StartandEndare set.
Export
Export downloads the filtered activity rows as CSV. The export uses the same filter and sort state as the table, but export is not limited to the currently visible page.
The downloaded filename can appear as transactions.csv. The CSV field order follows the exported activity record shape, not the exact visible table column order.
Map View
Map View helps inspect IP locations for the currently loaded activity rows. It groups rows by IP and shows markers when locations can be resolved.
Map behavior depends on configuration:
- if the Mapbox API key is missing, the dialog shows
Map Not Available - if MaxMind is disabled or credentials are missing, uncached IPs may not resolve
- cached IP locations can still be used when available
- country-level location can use a country capital coordinate when exact latitude/longitude is missing
The map is a location aid for the loaded table rows. It is not a full geolocation report for every row matching the filter.
Comment mode
When the activity filter is set to COMMENT, the table changes shape:
- the main text column becomes
Comment Data - the table exposes
Comment Group,CRM User, andCRM Role - expanded row detail swaps
DescriptionandAdditional Dataordering to prioritise comment payloads
In COMMENT mode, Manage Groups opens the comment-group manager. Deleting a group only deactivates it when it is not already used by comment activity rows. Existing comments are not deleted by this action.
Known caveats
- Summary cards describe the currently loaded rows, while the header count describes the full filtered result count.
- The verified activity read/export path is authenticated, but no separate Activity Log-specific permission gate was found.
- The standalone page does not force COMMENT mode by itself; comment-specific columns and group management appear when the component is scoped to COMMENT activity mode.
WEBSITE_SEARCHrows use a special detail view when their payload can be parsed; otherwise the generic JSON detail view is used.- Map View depends on system settings and IP-location lookup availability.
- The player profile also has activity/comment tabs; this standalone page is broader and designed for cross-player filtering.