> For the complete documentation index, see [llms.txt](https://help.openloyalty.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.openloyalty.io/implementation-guide/getting-started-1/dashboard.md).
# Dashboard
The dashboard is the first page that appears when you log in to the Admin panel. The dashboard gives an overview of the members' activity in your loyalty programs.
The Open Loyalty dashboard is an informative hub for administrators managing loyalty programs. Upon logging in, admins are greeted with a comprehensive overview of member activities and program metrics. Key features include monitoring registered and active members, tracking revenue, and analyzing average spending and transaction values. The dashboard also offers detailed insights into transactions and lets admins view data across various time frames, including daily, weekly, monthly, and yearly aggregates. Additional metrics such as points earned, used, expired, pending, and member engagement without transactions are also available.
This robust dashboard provides a clear and detailed view of loyalty program performance, aiding in effective management and strategy development.
{% hint style="info" %}
Metrics can be exported and utilized in any reporting tool you work with daily.\
To find out more, please refer to this article:
[S3 Bucket Exports](/implementation-guide/integrations-and-data-exchange/imports-exports/exports/s3-bucket-exports.md)
{% endhint %}
For a more detailed view and specific information, please refer to one of the following sub-articles:
---
# 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 dynamically by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://help.openloyalty.io/implementation-guide/getting-started-1/dashboard.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 `build a script that syncs our docs to a CMS` 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.