> 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.md).
# Users & Segments
Your user base in one place. Browse users, build audience segments, and import data via CSV.
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
The section is organized in two groups, plus imports:
| Group | Pages | What it is for |
| ------------------- | --------------------------- | --------------------------------------------------------------------- |
| **Audience** | Users, Segments | The people you can reach, and how you group them |
| **Data Management** | Attributes, Tags, Variables | The data your audiences are built on, and how it reaches your content |
| | Imports | Bulk-upload users and attributes via CSV |
{% hint style="info" %}
In the dashboard, **Imports** sits on its own below the two groups. In this documentation it lives under **Data Management**, because importing a CSV is how you get data in, just like the SDK or an integration. Same feature, one click away either way.
{% endhint %}
The split is meaningful:
* **Data Management decides what you are able to say about a user.**
* **Audience decides what you do with it.**
Each page carries its own actions:
| Page | Actions |
| -------------- | ----------------------------------- |
| **Users** | Import from CSV, Filter |
| **Segments** | Import, Export, + New Segment |
| **Attributes** | + New Attribute, Install Attributes |
| **Tags** | + New Tag |
| **Imports** | Import users from CSV |
{% hint style="info" %}
Users, Segments and Attributes each have their own search bar. Search finds an existing item by name. To narrow the user list by data instead, use the **Filter** builder on the Users page.
{% 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
* **Export** : reuse segments externally via static user list file download
{% endtab %}
{% tab title="Attributes" %}
Attributes are the building blocks of segments and filters. They come from five sources:
| Source | Examples | How they arrive |
| ---------------- | ----------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Jimo SDK** | Name, Email, Last activity, Sessions, Created | Automatic (snippet + SDK identification) |
| **Custom** | Plan, role, language, signup date | Defined in [Attributes](https://help.usejimo.com/docs/analyze/users-and-segments/data-management/attributes), pushed via the [SDK](https://help.usejimo.com/docs/for-developers/for-developers/sdk-guides/setup-the-segmentation) |
| **Integrations** | Any field from your CRM or analytics tool | Synced from [HubSpot, Salesforce, Segment.io, PostHog...](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 |
[**Tags**](https://help.usejimo.com/docs/analyze/users-and-segments/data-management/tags) are the sixth ingredient, and the only one that comes from no system at all: you apply them by hand.
{% 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
Experience targeting (Who)
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.
Content personalization
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.
Analytics and measurement
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?"
Automation and triggers
[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.
***
## 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.
→ [Attributes](https://help.usejimo.com/docs/analyze/users-and-segments/data-management/attributes) · [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/audience/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 %}
Practical tips
* 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.
***
## In this section
***
### 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
