> For the complete documentation index, see [llms.txt](https://help.smartico.ai/welcome/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.smartico.ai/welcome/products/gamification-basics/activity-log.md).
# Activity Log
The Activity Log provides a complete trail for all user currencies, including points, gems, and diamonds. By giving users a clear view of their transaction history, you reduce support inquiries regarding "missing" rewards and provide a more transparent experience.
#### Key Log Features
In the Activity Log, users can monitor their balance dynamics through four primary data points:
* Activity & Source: Each entry displays the type of action (e.g., "Points awarded") and its specific origin (e.g., Raffle, Leaderboard, or Marketing).
* Amount: A clear indicator of the value added or deducted during that specific event.
* Balance Snapshot: The "Balance" column shows the exact total remaining in the user's wallet immediately following that transaction.
* Time: A precise timestamp for every movement, organized under daily headers for better readability.
#### Filtering & Customization
To help users find specific data quickly, the log includes two primary filtering mechanisms located at the top right of the interface:
* Type: Users can toggle between Points, Gems, or Diamonds.
* **Note:** The Type filter dropdown is only displayed if multiple wallets (Gems & Diamonds) are enabled for your account.
* Time Period: Users can narrow their view to Today, This Week, or the Previous Week. For these filters, a week is defined as Monday through Sunday.
{% hint style="info" %}
**Note:** To maintain a clean and user-friendly interface, several backend processes are consolidated under the Marketing label. This category encompasses:
{% endhint %}
* Manual adjustments made by administrators.
* Automated rules triggered by the system.
* Specific promotional campaigns.
### Back-Office Configuration
In the Back-Office, navigate to your label or brand settings and locate **Section visibility**. Toggle **Activity Log** on to make it visible in the widget menu. You can then set its position in the navigation order relative to other widget sections.
### Back-Office Player Audit & Export
You can also review and extract the activity log information in the Back-Office:
* **User Profile:** Navigate to \*\*CRM → Users → \[User Profile] → **Points History** to view all balance changes, exact timestamps, and linked entity IDs for that specific user.
* **Data Export:** Operators can export filtered activity logs to CSV or Excel directly from the Back-Office for reporting and auditing.
### Frequently Asked Questions
**Q: Can users click on an entry to view the specific mission or mini-game?**
A: No. The widget Activity Log displays high-level source categories (such as Mission, Tournament, or Store) and balance changes. Operators can look up the exact entity ID and campaign details in the Back-Office User Profile.
**Q: Why do some transactions show as "Marketing" instead of a campaign name?**
A: Manual adjustments by administrators, automation rule triggers, campaign journeys, and API transactions are consolidated under the "Marketing" category to keep the player interface clean and maintain backend operational privacy.
**Q: How far back can players view their transaction history in the widget?**
A: Players can choose between Today, This Week (Monday through Sunday), or Previous Week. Operators can view lifetime historical records in the Back-Office under **Gamification → Activity log**.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://help.smartico.ai/welcome/products/gamification-basics/activity-log.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
.png?alt=media)