Activity logs overview.
Review recorded transactions, account activity, and changes to loyalty programs.
Activity logs help administrators and partners review recorded changes and transactions. Open an entry to see what happened, when it happened, and the available account and resource details.
What gets logged
Recorded events include program changes, member and staff management, transactions, redemptions, tier changes, sign-in events, and privacy actions. The details vary by event. A background task may have no acting user; an event without a web request may have no IP address.
For a specific problem, use Viewing logs to filter the records by date, event, or resource.
Key features
- Event details: Inspect the recorded action and related resource.
- Change history: Review old and new values when the event records them.
- Filters: Narrow the list by category, event, user type, or resource.
- Analytics: See trends and event breakdowns in Activity analytics.
Log entry language and format
Event identifiers such as stamp_earned, otp_login, and tier_upgraded stay in English in storage and the Agent API. Dashboard exports keep their existing translated category and event labels.
The log viewer and analytics translate event and category labels into the viewer's language. Changing that language does not change the stored record.
Privacy & security
The application excludes credential fields from activity records. Logs can still contain personal information, such as account identifiers and IP addresses. Limit access and check exported records before sharing them.
The application provides a read-only log viewer. That does not make the database tamper-proof against someone with server or database access.
Global compliance frameworks
Activity records can support an investigation or review. The feature does not certify your installation against a legal or audit framework. Set access and retention to match your organization's requirements.
Who can access activity logs
| Role | Access |
|---|---|
| Administrator | Installation-wide logs, analytics, and the old-record purge |
| Partner | Its own business logs when its plan or administrator grants access |
| Staff or member | No activity-log viewer |
Partner access is a plan feature and a business permission. Removing viewer access does not stop the application from recording events.
Monetary pass records
The Prepaid passes category includes monetary issues, spends, reversals, refund steps, unclaimed sales, setup changes, and oversight. Partner views follow the current issuing business relationship, so a removed member identity does not erase the business's retained financial history. Financial events use pseudonymous actor and record IDs; they omit member names, payment references, and request content.
An idempotent retry adds no second business event. Administrators can also review denied monetary attempts under Authentication. A denial records a security outcome, not a completed sale or spend.
Ordinary log cleanup only removes the activity copy. The application does not automatically delete monetary journals or financial claims based on age, including closed records. The Health center provides separate delivery and integrity tasks; the retained monetary-retention task does not delete financial records.
Managing activity log size
The configured retention period defaults to 365 days. The administrator purge uses that period, with a minimum of 90 days. This is an application safeguard, not a statement about legal retention requirements.
How to purge old logs
- Open Activity logs as an administrator.
- Select Purge old logs.
- Review Records to delete, the cutoff date and Breakdown by category. Category names follow the selected language.
- Select Purge [count] records if you no longer need those entries.
- Select Delete in the confirmation dialog. Choose Cancel to keep the records.
If no records qualify, the page shows No old records to purge and hides the purge button.
Permanent deletion: A purge removes old records. Export any records you must retain before confirming. The application records the purge action itself.
Minimum retention period
The dashboard purge keeps records from the most recent 90 days even if the configured period is shorter. A longer configured period takes precedence.
What gets purged
The confirmation page lists the affected categories and counts. Only records older than the displayed cutoff date are eligible.
Related topics
- Viewing logs: Find and inspect an event.
- Activity analytics: Review trends and event categories.