> For the complete documentation index, see [llms.txt](https://help.twinr.dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.twinr.dev/app-analytics/acquisition-and-retention/daily-active-users.md).

# Daily Active Users

Track the total number of users who engage with your app on a daily basis. This is a fundamental metric that provides insights into the app's daily usage.

<figure><img src="/files/Ew6ziMto1ISrIrjjPNKk" alt=""><figcaption></figcaption></figure>

Here in the image, we can see:

* daily active users for current period(5 Dec to 3 Jan) are 361. The selected timeframe here is 30 days.
* 261% shows the comparison of previous period from current one.
* Dark blue shows the current period and light blue shows previous period. Please see below image for more clear example.

<figure><img src="/files/rQhrS4XFEIPvfaSwKzLi" alt=""><figcaption></figcaption></figure>


---

# 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 current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://help.twinr.dev/app-analytics/acquisition-and-retention/daily-active-users.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.