> For the complete documentation index, see [llms.txt](https://help.usejimo.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.usejimo.com/docs/analyze/users-and-segments/audience/users.md). # Users **Dashboard path:** [Users & Segments > Audience > Users](https://i.usejimo.com/users) (`/users`) *** ## Understanding a user The Users tab is your entry point to explore, filter, and inspect every user detected by Jimo. It is the first tab of [Users & Segments](https://help.usejimo.com/docs/analyze/users-and-segments) and the go-to view whenever you need to find a specific user, check their activity, or build an audience on the fly.
### Anonymous vs identified users Every user who loads a page with the Jimo snippet is recorded, but not all users are equal. * **Anonymous users** appear with the label "Anonymous" and a short Jimer ID (e.g. `Jimer hONp`). Jimo detected them but they were never linked to a real identity. * **Identified users** appear with their display name, email, and a persistent user ID. You can link their sessions across devices, segment them by any attribute, and personalize content. The difference is one SDK call: `identify`. Until that call runs, Jimo has no way to attach persistent data to the user. {% hint style="warning" %} The earlier you identify users, the richer their profiles become over time. See [Installing Jimo](https://help.usejimo.com/docs/getting-started/installing-jimo) and the [identify users guide](https://help.usejimo.com/docs/for-developers/for-developers/sdk-guides/identify-users). {% endhint %} ### What data is attached to a user Once identified, a user profile accumulates four types of data: * **Attributes** — native fields (name, email, sessions) plus [custom attributes](https://help.usejimo.com/docs/analyze/users-and-segments/users/attributes) you push (plan, role, language, etc.) * **Experience interactions** — which Jimo experiences the user has seen, completed, dismissed, or answered * **Events** — in-app actions tracked by Jimo or received from integrations * **Segment membership** — which dynamic segments the user currently belongs to All of this becomes visible in the [user profile side panel](#user-profile) and usable as conditions in the [filter builder](#filtering-the-user-list). *** ## Components of the Users tab ### The two counters at the top
They look similar and they measure very different things. Reading them wrong is the most common mistake on this page. #### Identified users from Jimo SDK How many users your app has **identified** to Jimo, over time. This is the size of the population you can actually target with your own data. If this number is flat while your product is growing, your `identify` call is not running everywhere it should. See [Identify users](/docs/for-developers/for-developers/sdk-guides/identify-users.md). #### Reached by Jimo Experience How many users **actually saw** one of your experiences, with the variation over the last 30 days. This one moves with your publishing activity, not with your traffic. A drop here usually means an experience ended, not that users left. {% hint style="info" %} **These two are not a funnel.** A user can be reached without being identified: anonymous visitors see experiences too. The counters answer two independent questions. {% endhint %} ### The user list | Column | What it shows | | ----------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **User** | Display name, or **Anonymous** if your app never identified them. The line underneath is the internal ID: your own user ID once identified, a `Jimer` code otherwise. | | **Email** | The `email` attribute. `No email` when it was never pushed. | | **Last activity** | When Jimo last saw this user. | | **First seen** | When Jimo first detected them. Not their signup date in your product, unless you push it as an attribute. | | **Tags** | Manual labels. Add one inline with **+ Add tag...**. | The last column deletes a user.
{% hint style="warning" %} **First seen is not signup date.** Jimo only knows what happened after it was installed. If you need the real signup date, push it as a [custom attribute](/docs/analyze/users-and-segments/data-management/attributes/create-a-custom-attribute.md). {% endhint %} #### Anonymous users
A user shows as **Anonymous** when your app has not called `identify` for them. They still count, they can still be reached by experiences, but you cannot attach your own data to them and you cannot target them by attribute. If most of your list is anonymous, that is an identification problem, not a Jimo problem. See [Identify users](broken://pages/335eea73df78be5b21072467123ff18821e4d35a), and the **Force Identify** option in [Installation](broken://pages/7665fd78de2dd5f911d447a49dfda75b3b81e281). #### Search and sort
The search bar matches users names or emails. Two sort options: * **Recently active**: last seen first. The default. * **Recently created**: newest first. ### Filtering The **Filter** button opens a rule builder above the list. It is the same engine that powers segments, and a filter you like can be saved as one in a click.
See [Filter users](/docs/analyze/users-and-segments/audience/users/filter-users.md). ### Importing **Import from CSV** brings in users and their custom attributes.
See [Imports](/docs/analyze/users-and-segments/data-management/imports.md). ### In this section * [**Filter users**](/docs/analyze/users-and-segments/audience/users/filter-users.md): build rules to narrow the list, and save them as a segment * [**User details**](/docs/analyze/users-and-segments/audience/users/user-details.md): inspect one user ### Related pages * [Segments](/docs/analyze/users-and-segments/audience/segments.md): save an audience for reuse * [Attributes](/docs/analyze/users-and-segments/data-management/attributes.md): the data behind the columns * [Tags](/docs/analyze/users-and-segments/data-management/tags.md): manual labels