> For the complete documentation index, see [llms.txt](https://doc.batch.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.batch.com/getting-started/features/customer-engagement-platform/analytics/profile-overview.md).
# Profile Overview
The userbase tab gives you an overview of your current iOS, Android or Web userbase, allowing you to elaborate new push strategies and understand how to best engage with your users.
There are three kind of information you can see on your userbase:
* Basic statistics: Total number of users, opt-in rate, etc.
* Smart Segments: Distribution of your users in Batch Smart segments.
* Native and custom segments statistics.
## Basic statistics
There are **4 metrics** you should check to see how your app is performing:
### **Installs**
Total **number of installs** of your app since you released it with Batch SDK. This number includes users who still have your app on their device or who already uninstalled it.
{% hint style="info" %}
The number of users is updated in real time.
{% endhint %}
### **Opt-ins**
This is the percentage of users **who have opted-in** to push notifications in your app or website.
### **Number of tokens**
Appears on hover on *"Opt-ins"*. The interpretation of this metric differs from an OS to another:
**Android**
On Android, Batch retrieves automatically the token of your new users. Users who have a token are users who **still have your app** on their device.
**iOS**
On iOS, the token collection can depend on the *background refresh*. You can go in Xcode and see if *"Remote notifications"* is checked as a background mode in your app's Capabilities to see if it's enabled.
* **If enabled**: Batch collects tokens for all your users, even for those who choose not to receive push notifications. In this case, users who have a token are also users who have your app on their device.
* **If disabled**: Batch only collects tokens for users who opt-in for push notifications. In this case, users who don't have a token are users who didn't accept notifications or uninstalled your app.
Please note that users can disable background refresh for your application so these stats may be imprecise.
## Smart Segments
#### Understanding smart segmentation
Smart Segments are automatically created by Batch using **a proprietary algorithm**. They let you visualize precisely who is using your app, and who is not, who is buying your product, and who is churning away.
Our **algorithm** analyses the sessions of your users from the moment they install your app and put them in 4 different segments. Here is a short definition of every segment:
* **New**: Newcomers to your app that haven't yet established themselves as engaged, lasting users.
* **Engaged**: Congratulations! These users are actively using your app.
* **Dormant**: These promising users haven't used your app in a while. Reengage them!
* **One-time**: Users that have had your app for a while but have only opened it once.
We are also showing the predictive and intermediate Smart Segments that our algorithm calculates:
* **Risky Engaged**: Users with a high risk of becoming dormant in the next days if you don’t re-engage them with a targeted notification.
* **Promising New / Dormant** users: Users who are about to become engaged. Don’t miss the opportunity to send them a message!
Batch also shows the number of **imported tokens** who haven't been reintegrated to Batch Smart Segments yet. You will find more information on token import [here](/getting-started/features/customer-engagement-platform/profiles/import-tokens.md).
{% hint style="warning" %}
The Profile overview page provides insights on the installation base that powers **Push v1**, siloed by platform (iOS, Android, Web). For details about Push v2 Profile Analytics [go there](/getting-started/features/customer-engagement-platform/analytics/profile-analytics.md).
{% endhint %}
---
# 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://doc.batch.com/getting-started/features/customer-engagement-platform/analytics/profile-overview.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.