> For the complete documentation index, see [llms.txt](https://developers-apps-in-toss.toss.im/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developers-apps-in-toss.toss.im/guide/en/analytics/dashboard.md).
# Dashboard
In the App in Toss console dashboard, **you can see the key metrics of your mini app at a glance, including DAU, gender, age, and retention.** \
The dashboard is a strategic tool that accelerates the growth of partners’ mini apps, and it is a core feature you must use for the growth and success of your mini app. \
If you continuously check the data and use it to make improvements, you can experience tangible benefits such as increased traffic and higher conversion rates.
Once the mini app is launched and logs are collected, you can view the dashboard from **‘Analyze’** tab in the console home menu. Before checking the data, please make sure to review the following.
* **SDK 0.0.26 or later**Only mini apps with this applied can have their data checked.
* Data from the sandbox or launch-preparation stage is not provided, and **only data after the actual launch** can be checked.
* Data is available **starting the day after the service launch** can be checked.
{% hint style="info" %}
**Features planned for future release**
SDK **0.0.36 or later**If applied, you can check the mini app’s **dwell time data**. This data is planned to be provided in the dashboard later.
{% endhint %}
***
### Data available in the dashboard
You can set the period in the top right, such as daily, weekly, or monthly, and view it or download it as an Excel file.
* Dashboard data can be checked for the previous day every day after 9:00 a.m.
* For DAU daily data, you can view data up to 2 hours before each hour, and weekly and monthly data are updated as well.
* Example: at 17:00, data up to 15:00 can be checked
**DAU (Daily Active Users)**
* This is a core metric that most intuitively shows the service’s growth trend.
* You can check the number of users who used the app on a daily basis over the past 4 weeks.
* It is measured based on logs that can determine that a user ‘used the service’ after accessing the mini app.
**OS, Toss app version**
* You can view Android and iOS users separately over the past 4 weeks.
* You can also check users by Toss app version.
* This can be used to establish optimization strategies for each operating system.
**Gender distribution**
* You can check the number of male and female users over the past 4 weeks.
* This is essential data for planning content tailored to your target audience, such as segment composition.
**Age distribution**
* You can check the number of users by age group over the past 4 weeks, from their teens to those in their 60s and older.
* It can be used to identify the main customer base and design marketing strategies, such as segment composition.
**Traffic source**
Traffic source refers to the path through which a user entered the service within the Toss app. \
Each traffic source shows that the user acquisition method and user expectations are different, and these differences can affect subsequent service continuity (retention).
The types of traffic sources you can check in the console dashboard are as follows.
* All tab (traffic from Toss app > All at the bottom right)
* Search (traffic from the search function at the top right within the All tab)
* Benefits tab (traffic through this path when a promotion is displayed in the Benefits tab of the Toss app)
* Push/notification (traffic through promotional or functional push notifications)
* Game home (traffic through the game menu within the All tab)
* Contacts module (traffic through the contact sharing link)
* Other (all other traffic)
To see all traffic sources, please refer to the traffic source referrer document.
**Retention and retention by traffic source (repeat visit rate)**
You can check the rate at which users used the app again within a certain period after their first visit. \
This is a key metric for measuring service loyalty and satisfaction. \
If you click ‘View by traffic source’ in the top right, you can also see retention (repeat visit rate) by traffic source.
If you check retention by traffic source, you can gain the following insights.
**① You can identify the traffic sources that actually contribute to the service.**
* Traffic sources with low volume but high retention → **Users well suited to the service**
* Traffic sources with high volume but low retention → **Short-term responsive users**
**② You can identify which exposure methods lead to long-term use and which only contribute to short-term activation.**
* Exploratory traffic: All tab, Benefits tab, Game home
* Goal-oriented traffic: Search
* External stimulus traffic: Push/notification, promotion
---
# 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://developers-apps-in-toss.toss.im/guide/en/analytics/dashboard.md?ask=&goal=
```
`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.