> 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/segments.md).

# Segments

Saved, reusable audiences built from rules rather than lists. Find them, read their live count, and understand why it moves without you touching anything.

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

***

## Understanding segments

Segments are dynamic groups of users defined by conditions. They update automatically as users match (or stop matching) your criteria, and are reusable everywhere Jimo lets you target an audience: experience targeting (Who), analytics, and even as conditions inside other segments.

#### What makes a segment

A segment is defined by three things:

* **A name and description** so you and your team can find it later and understand its purpose at a glance
* **A set of conditions** built using the same condition builder as the Users tab filter
* **An audience** (the current list of users matching the conditions, updated live)

Conditions combine native attributes, custom data you push, experience interactions, events, and even other segments, all connected with AND/OR logic groups.

#### Dynamic by design

Segments are **not static lists**. They do not store users. They store conditions, and Jimo evaluates them on the fly whenever needed.

In practice:

* A user who matches the conditions is considered part of the segment, automatically
* When a user's attributes or activity change, their segment membership updates
* You do not need to "refresh" a segment. It is always up to date.
* Updating a segment's conditions instantly changes the audience everywhere the segment is used, including live experiences. No republish required.

{% hint style="warning" %}
Changing a segment's conditions affects every experience using it, in real time. Be careful when editing segments attached to production experiences.
{% endhint %}

#### Where segments are used

Once saved, a segment is available in these places:

* **Experience targeting (Who)**: show a tour, survey, or banner only to a segment
* **Users tab filter**: narrow the user list to a segment's audience
* **RC block conditions**: show a block only if the user belongs to a specific segment
* **Analytics**: compare how segments adopt an experience, through your assistant
* **Nested segments**: use a segment as a condition inside another segment

{% hint style="info" %}
**From your assistant.** With the Jimo MCP connected, ask "Which segments exist, and how big is Trial Users?". Sizes are approximate and refreshed in the background, so a segment you just edited can lag for a moment.
{% endhint %}

***

## User segments and company segments

The Segments page has two tabs, **User Segments** and **Company Segments**. **+ New Segment** asks which one to create: **New User Segment** or **New Company Segment**.

<figure><img src="https://2794860263-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FKzAcDWQbK1gKbpra7bkb%2Fuploads%2FIdE0UJyHXbMqo44aWgex%2FP-s12-segments-company-tab.png?alt=media&amp;token=39204e14-2c5d-418a-bb66-dc69871588ce" alt="The Segments page on the Company Segments tab, with one company segment, its audience, creation and last update"><figcaption></figcaption></figure>

|           | User segment                                                                                                         | Company segment                                                                                     |
| --------- | -------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------- |
| **Holds** | Users                                                                                                                | Companies                                                                                           |
| **Rules** | Tags, User Attributes, Company Attributes, User Segments, Company Segments, Experiences, events and integration data | Tags, Company Attributes (with Membership role and Membership team), Experiences and No-Code Events |
| **Count** | Users                                                                                                                | Companies                                                                                           |

The rules of a company segment work as on the Companies page: company attributes check the company, a membership rule matches a company when at least one of its users matches it.

A company segment lists the companies that match, with the same columns as the Companies page. After you save or edit one, the count and the list can take a few seconds to fill.

<figure><img src="https://2794860263-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FKzAcDWQbK1gKbpra7bkb%2Fuploads%2FO7rai2zAGMXqrdqBQkDM%2FP-s13-company-segment-details.png?alt=media&amp;token=7e9f4364-a448-473f-a910-6d5659256889" alt="Details of a company segment: the rule Company plan is Enterprise Plus, and the one company it holds with its domain, last activity and first seen date"><figcaption></figcaption></figure>

To reach the users of those companies, add a **Company Segments** rule to a user segment, or to the on-the-fly rules of an experience: it keeps the users whose company is in that company segment. The **Company Segments** section of the rule window appears once the project has at least one company segment.

<figure><img src="https://2794860263-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FKzAcDWQbK1gKbpra7bkb%2Fuploads%2Fb5178hDxIPaoDT9oh9Fl%2Fusing-segments-user-vs-company-v01.png?alt=media&#x26;token=7d389d0b-96e7-4754-98d8-eae18c39770e" alt="A user segment holds users, a company segment holds companies, and a Company Segments rule turns a company segment back into users"><figcaption></figcaption></figure>

***

## Components of the Segments tab

<figure><img src="https://2794860263-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FKzAcDWQbK1gKbpra7bkb%2Fuploads%2F6ogGI1IbB1dQwaqPtGdq%2Fimage.png?alt=media&#x26;token=6f38875a-4cc3-46c0-a4b8-a382a2acdb72" alt="Segments page: components of the Segments tab"><figcaption></figcaption></figure>

The page is organized into two zones:

| Zone    | Component      | What it does                                                                                                                      |
| ------- | -------------- | --------------------------------------------------------------------------------------------------------------------------------- |
| **(1)** | Header actions | **Import** and **+ New Segment** buttons, top-right. **Updated just now** tells you when the audience counts were last refreshed. |
| **(2)** | Segments list  | The list of saved segments with search, sorting, badges, audience sizes, and metadata                                             |

Clicking any segment row opens its **detail page** where you can edit conditions, preview the audience, and save changes.

***

### The segments list

<figure><img src="https://2794860263-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FKzAcDWQbK1gKbpra7bkb%2Fuploads%2FMprpuB8kwqtpyTx4qwY0%2Fimage.png?alt=media&#x26;token=24da6b1a-f7ac-4073-ad42-df7eb8c6bd23" alt="Segments page: the segments list"><figcaption></figcaption></figure>

The list displays every segment saved in the project.

#### List columns

| Column                 | Content                                                                                        |
| ---------------------- | ---------------------------------------------------------------------------------------------- |
| **Badge**              | Optional visual marker: emoji or icon with a colored label (e.g. "NEW" in blue, "VIP" in gold) |
| **Name / Description** | Segment name with its description below                                                        |
| **Audience**           | Live count of users currently matching the segment's conditions                                |
| **Created**            | Creation date with author name                                                                 |
| **Last updated**       | Most recent modification date with author name                                                 |

**Finding a segment**

Search matches on the segment name. Five sort options:

| Sort                   | Use it to                          |
| ---------------------- | ---------------------------------- |
| **Default**            | the standard order                 |
| **Name (A-Z)**         | find one you know the name of      |
| **Audience (largest)** | see what actually covers your base |
| **Recently created**   | find what you just made            |
| **Recently updated**   | find what someone changed          |

<figure><img src="https://2794860263-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FKzAcDWQbK1gKbpra7bkb%2Fuploads%2Fg0xucFceyP8A1Yb1upg6%2Fimage.png?alt=media&#x26;token=9eda3a30-cce6-40d5-a150-2b56f5f6f375" alt="Segments page: list columns"><figcaption></figcaption></figure>

{% hint style="success" %}
**Name segments for the next person.** `Test`, `test` and `seg on seg` are real segment names in a real workspace. Six months later nobody knows what they hold. The description field exists for that: use it.
{% endhint %}

#### Row interactions

* **Click** a row: opens the segment detail page
* **Hover** a row: a red trash icon appears at the end of the row for deletion

{% hint style="warning" %}
**No templates, no presets.** Jimo does not ship with pre-built segments or a gallery of suggestions. Every segment starts blank from your own conditions. Think about which audiences matter to your product and build them from there.
{% endhint %}

***

## Creating a segment

**+ New Segment** opens the builder. See Create a segment.

You can also get there sideways: build a filter on the Users page and hit **Save**. Same result, less typing.

<figure><img src="https://2794860263-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FKzAcDWQbK1gKbpra7bkb%2Fuploads%2F2Xa6iLRwW2BEQRipLtYp%2Fimage.png?alt=media&#x26;token=277d6d7f-435c-4cb7-949f-b1b902635fab" alt="Segments page: creating a segment"><figcaption></figcaption></figure>

**Import** creates a segment from a CSV of users. That segment has one rule: the tag the import put on every user of the file. See Imports.

***

### In this section

<table data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th><th data-hidden data-card-cover data-type="files"></th></tr></thead><tbody><tr><td><strong>Create a segment</strong></td><td>The builder, its condition categories, AND/OR groups and two worked examples</td><td></td><td></td></tr><tr><td><strong>Segment details</strong></td><td>Edit, duplicate, delete, and use a segment for targeting</td><td></td><td></td></tr></tbody></table>

***

## Related pages

* [Users & Segments overview](https://help.usejimo.com/docs/analyze/users-and-segments/audience.md): Core concepts, identification, and getting started
* Users: Browse the user list and inspect individual profiles
* Companies: The accounts your users belong to, and what company segments hold
* User attributes: Reference for attribute types, sources, and setup
* Import: Bulk-upload users and attributes via CSV, with auto-segment creation
* Who: target the right users: Use segments to control who sees each experience
* [Setup the segmentation](https://help.usejimo.com/docs/for-developers/for-developers/sdk-guides/setup-the-segmentation.md): Developer guide for pushing custom attributes
* Success Tracker: Create no-code events that unlock the Events category in the builder
* Integration Setup: Connect Segment.io, Posthog, Amplitude, and more to unlock their categories in the builder
