# Users & Segments

Understand who uses your product and build the audiences that will receive your experiences. This section is the data foundation behind all targeting, personalization, and measurement in Jimo.

**Dashboard path:** [Users & Segments](https://i.usejimo.com/users) (`/users`)

***

## Dashboard structure

<figure><img src="/files/7JcSPNHUZYHsxQT762dP" alt=""><figcaption></figcaption></figure>

The page has three tabs:

| Tab          | Content                                                                                               |
| ------------ | ----------------------------------------------------------------------------------------------------- |
| **Users**    | All detected users. Click any row to open the profile side panel. Filter with the **Add...** builder. |
| **Segments** | All saved segments with a live count badge on the tab label (e.g. "Segments 12").                     |
| **Imports**  | History of CSV imports with status badges (Draft / Done) and row counts.                              |

Two action buttons in the top-right corner:

| Button                    | Behavior                                                                  |
| ------------------------- | ------------------------------------------------------------------------- |
| **Import users from CSV** | Opens the CSV import flow. Visible on all tabs.                           |
| **+ New Segment**         | Opens segment creation. Visible on Users and Segments, hidden on Imports. |

{% hint style="info" %}
There is no global search bar. Filtering users is done through the condition builder (**Add...** button) on the Users tab.
{% endhint %}

***

## Core concepts

{% tabs %}
{% tab title="Users" %}
A **user** is anyone who visits a page where the Jimo snippet is installed. Each user gets a unique **Jimer ID** automatically.

Once [identified via the SDK](https://help.usejimo.com/docs/for-developers/for-developers/sdk-guides/identify-users), a user profile accumulates over time:

* **Attributes** : native fields (name, email, sessions) + custom fields you push (plan, role, language...)
* **Experience interactions** : which Jimo experiences the user has seen, completed, or responded to
* **Events** : in-app actions tracked by Jimo or imported from integrations
* **Segment membership** : which segments the user currently belongs to
  {% endtab %}

{% tab title="Segments" %}
A **segment** is a dynamic group of users defined by conditions. It updates automatically: users enter when they match, leave when they don't.

Segments are reusable across Jimo:

* [**Experience targeting (Who)**](https://help.usejimo.com/docs/publish/target-right-people-who) : show a tour only to "Trial users"
* **Filtering** : narrow the user list to a specific audience
* **Analytics** : compare experience performance across cohorts
* **Composition** : use a segment as a condition inside another filter
  {% endtab %}

{% tab title="Attributes" %}
Attributes are the building blocks of segments and filters. They come from four sources:

| Source          | Examples                                        | How they arrive                                                                                                                                                                                 |
| --------------- | ----------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Native**      | Name, Email, Last activity, Sessions, Tags      | Automatic (snippet + SDK identification)                                                                                                                                                        |
| **Custom**      | Plan, role, language, signup date               | Pushed via [SDK](https://help.usejimo.com/docs/for-developers/for-developers/sdk-guides/setup-the-segmentation) or [integrations](https://help.usejimo.com/docs/integrations/integration-setup) |
| **Experiences** | Seen Tour X, Completed Survey Y, Answered "Yes" | Automatic when users interact with experiences                                                                                                                                                  |
| **Events**      | Clicked "Upgrade", Visited /settings            | Created in [Success Tracker](https://help.usejimo.com/docs/analyze/success-tracker) or imported                                                                                                 |

{% hint style="success" %}
The more you enrich user profiles, the more precise your segments become. Start with plan + role + language for quick wins.
{% endhint %}
{% endtab %}
{% endtabs %}

***

### Why identification matters

[Identification](https://help.usejimo.com/docs/for-developers/for-developers/sdk-guides/identify-users) (`user:id`, `user:email`, `user:name`) is the prerequisite for everything in this section.

{% tabs %}
{% tab title="Without identification" %}
Jimo sees anonymous sessions. It can show experiences to everyone, but cannot:

* Build persistent profiles across sessions or devices
* Use custom attributes for segmentation
* Track individual journeys over time
* Personalize content (e.g. "Hello {name}")
  {% endtab %}

{% tab title="With identification" %}
Jimo links every session to a known user. This unlocks:

* Cross-session profiles with full attribute history
* Dynamic segments that update in real time
* Precise targeting by plan, role, behavior, or any custom data
* Cohort analytics in [Success Tracker](https://help.usejimo.com/docs/analyze/success-tracker)
* Personalized content using [variables in the builder](https://help.usejimo.com/docs/build/builders)
  {% endtab %}
  {% endtabs %}

{% hint style="warning" %}
Configure identification as early as possible in your setup, ideally right after [installing the snippet](https://help.usejimo.com/docs/getting-started/installing-jimo). The earlier you [identify users](https://help.usejimo.com/docs/for-developers/for-developers/sdk-guides/identify-users), the more data Jimo accumulates for targeting and analytics.
{% endhint %}

For implementation details, see the [SDK segmentation guide](https://help.usejimo.com/docs/for-developers/for-developers/sdk-guides/setup-the-segmentation). If you use a CDP or CRM, check [HubSpot](https://help.usejimo.com/docs/integrations/hubspot), [Segment.io](https://help.usejimo.com/docs/integrations/segment.io), or [Salesforce](https://help.usejimo.com/docs/integrations/salesforce) to automate attribute syncing.

***

### How Users & Segments connects to Jimo

<details>

<summary><strong>Experience targeting (Who)</strong></summary>

Every experience has a [Who](https://help.usejimo.com/docs/publish/target-right-people-who) section in Target & Publish. Select a saved segment or build conditions on the fly. Both use the same condition builder.

</details>

<details>

<summary><strong>Content personalization</strong></summary>

User attributes are accessible as dynamic variables in the [content builder](https://help.usejimo.com/docs/build/builders) (e.g. "Hello {firstName}"). Combined with [Multiple Languages](https://help.usejimo.com/docs/build/multiple-languages), you can create contextual variants of a single experience.

</details>

<details>

<summary><strong>Analytics and measurement</strong></summary>

Experience [analytics](https://help.usejimo.com/docs/analyze/analytics) can be filtered by segment. The [Success Tracker](https://help.usejimo.com/docs/analyze/success-tracker) measures adoption by cohort, answering questions like "Did paying users adopt this feature faster than trial users?"

</details>

<details>

<summary><strong>Automation and triggers</strong></summary>

[Triggers & Conditions](https://help.usejimo.com/docs/build/triggers-and-conditions) use attributes and events to fire experiences at the right moment. [Actions](https://help.usejimo.com/docs/build/actions) can be conditioned by segment membership. The [Agent](https://help.usejimo.com/docs/experiences/agent) uses knowledge triggers that reference user context.

</details>

***

## Getting started

{% stepper %}
{% step %}

#### Identify your users

Push `user:id` + `user:email` + `user:name` via the SDK right after login. This is the prerequisite for everything else.

→ [Installing Jimo](https://help.usejimo.com/docs/getting-started/installing-jimo) · [Identify users guide](https://help.usejimo.com/docs/for-developers/for-developers/sdk-guides/identify-users)
{% endstep %}

{% step %}

#### Define your key custom attributes

Pick 5-10 attributes that matter for segmentation: plan type, user role, language, creation date, trial status.

→ [Setup the segmentation](https://help.usejimo.com/docs/for-developers/for-developers/sdk-guides/setup-the-segmentation) · [Initial Setup](https://help.usejimo.com/docs/getting-started/initial-setup)
{% endstep %}

{% step %}

#### Create your first segments

Start with 3 to 5 essential groups: new users (created < 7 days), paying users, inactive users (last activity > 30 days), trial users, power users.

→ [Segments](https://help.usejimo.com/docs/analyze/users-and-segments/segments)
{% endstep %}

{% step %}

#### Connect your integrations

If you use a CDP or CRM, set up the integration to auto-sync events and attributes.

→ [Integration Setup](https://help.usejimo.com/docs/integrations/integration-setup) · [HubSpot](https://help.usejimo.com/docs/integrations/hubspot) · [Segment.io](https://help.usejimo.com/docs/integrations/segment.io)
{% endstep %}

{% step %}

#### Iterate

Refine your segments based on [analytics](https://help.usejimo.com/docs/analyze/analytics) data and support feedback. Add segments as your adoption strategy matures.
{% endstep %}
{% endstepper %}

<details>

<summary><strong>Practical tips</strong></summary>

* Name segments explicitly: prefer "Paying users, active last 30d" over "Segment 1"
* Do not over-segment early. 5 well-defined segments beat 30 vague ones.
* Use **tags** for manual, one-off categorization. Use **segments** for automated, dynamic targeting.
* Test your segments with the builder preview before applying them to live experiences.
* Use the [Troubleshooting Tool](https://help.usejimo.com/docs/settings/troubleshooting) to debug segment membership issues.

</details>

***

## In this section

<table data-view="cards"><thead><tr><th>Section</th><th>What is it?</th><th>Includes</th><th data-hidden data-card-target data-type="content-ref">Target</th></tr></thead><tbody><tr><td><h4><strong>Users</strong></h4></td><td>Browse, filter, and inspect your full user base</td><td><p><em>· User list</em> </p><p><em>· Condition builder</em></p><p><em>· User profile side panel</em></p></td><td><a href="/pages/ADUZ9IR8ofuNf0v3tAgf">/pages/ADUZ9IR8ofuNf0v3tAgf</a></td></tr><tr><td><h4><strong>Segments</strong></h4></td><td>Create dynamic audience groups </td><td><p><em>· Segment list</em></p><p><em>· Segment builder</em> </p><p><em>· Survey responses</em> </p></td><td><a href="/pages/d8v9R2bGwuDtvnAYXHLr">/pages/d8v9R2bGwuDtvnAYXHLr</a></td></tr><tr><td><h4><strong>Import</strong></h4></td><td>Bulk-upload users and attributes via CSV</td><td><p><em>· 3-step import flow</em></p><p><em>· Auto-segment creation</em></p><p><em>· Import history</em></p></td><td><a href="/pages/hbqHM3grh3tvGYPJUVl7">/pages/hbqHM3grh3tvGYPJUVl7</a></td></tr></tbody></table>

***

### Related pages

* [Target right people (Who)](https://help.usejimo.com/docs/publish/target-right-people-who) : Use segments to control who sees each experience
* [Installing Jimo](https://help.usejimo.com/docs/getting-started/installing-jimo) : Snippet installation and user identification setup
* [Setup the segmentation](https://help.usejimo.com/docs/for-developers/for-developers/sdk-guides/setup-the-segmentation) : Developer guide for custom attributes via the SDK
* [Initial Setup](https://help.usejimo.com/docs/getting-started/initial-setup) : Recommended first steps for attributes and imports
* [Analytics](https://help.usejimo.com/docs/analyze/analytics) : Experience-level metrics and CSV export
* [Success Tracker](https://help.usejimo.com/docs/analyze/success-tracker) : In-app event tracking for goal-based measurement
* [Troubleshooting](https://help.usejimo.com/docs/settings/troubleshooting) : Debug segment membership and experience visibility issues


---

# Agent Instructions: 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:

```
GET https://help.usejimo.com/docs/analyze/users-and-segments.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
