> For the complete documentation index, see [llms.txt](https://docs-v3.toucantoco.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs-v3.toucantoco.com/administration/monitoring-engagement-with-toucan-analytics.md).

# Monitoring Engagement with User Analytics

### Introduction to User Analytics

The User Analytics feature helps you track user activity and engagement. With advanced analytics dashboards, you can monitor user interactions across different apps and analyze user behavior over various time periods (monthly, weekly, daily).

### Key Features:

* App and Interaction Selection: You can choose a specific app and track user interactions to get a granular view of user behavior. Each app generally has its own key interaction(s), making it easier to focus on what drives engagement within that app.
* Flexible Time Periods:
  * Monthly: Access to all months since the creation of your Toucan platform, ideal for analytical applications that should be consumed once a month.
  * Weekly: Analyze data for the last 24 weeks, ideal for analytical/operational applications that should be consumed once a week.
  * Daily: Zoom in on the last 60 days for detailed, ideal for operational applications used on a daily basis.

{% content-ref url="/pages/kXir7lmHxmuOSsGTs5Cj" %}
[How to Filter your User Analytics?](/administration/monitoring-engagement-with-toucan-analytics/how-to-filter-your-user-analytics.md)
{% endcontent-ref %}

{% content-ref url="/pages/TvTlv2uaVWNugHtHDCO5" %}
[Understanding your User Analytics Dashboards](/administration/monitoring-engagement-with-toucan-analytics/understanding-your-user-analytics-dashboards.md)
{% endcontent-ref %}


---

# 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://docs-v3.toucantoco.com/administration/monitoring-engagement-with-toucan-analytics.md?ask=<question>&goal=<user_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.