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

# Filter users

## Filter users

Filtering is how you explore. You stack conditions, the list narrows, and the header tells you how many people are left.

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

### Build a rule

The builder opens on **Filter the users who...**, and each rule reads as a sentence: an attribute, an operator, a value.

```
Created          is not within the last (days)    30 days
externalEmail    is not empty
```

Rules stack with **AND**: a user must match all of them.

**+ Add rule** adds one. The **...** menu on a rule removes or duplicates it. **Clear** wipes everything.

### Pick what to filter on

Clicking the attribute opens a picker, organized by **where the data comes from**:

| Category                                                | What is in it                                                      |
| ------------------------------------------------------- | ------------------------------------------------------------------ |
| **From Jimo SDK**                                       | Native attributes: Email, Last activity, Created, Sessions, Active |
| **Custom Attributes**                                   | The ones you defined and your app pushes                           |
| **Experiences**                                         | Conditions on what a user did with your experiences                |
| **No-Code Events**                                      | Conditions on events a user performed                              |
| **Tags**                                                | Manual labels                                                      |
| **Segment.io Traits, Hubspot, Salesforce, Posthog,...** | Attributes synced from a connected integration                     |

<figure><img src="/files/GxMESMF0HW4znmfxX4c9" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
An attribute only shows up here once Jimo has received a value for it. A **Pending** attribute is invisible in this picker. See [Attributes](/docs/analyze/users-and-segments/data-management/attributes.md).
{% endhint %}

### Read the count

<figure><img src="/files/3pDWSmFl8vFhfDMyCWa3" alt=""><figcaption></figcaption></figure>

The header of the list turns into **N users found** as soon as a rule applies. It recomputes as you edit.

That count is the whole point of filtering before saving: you see the audience before you commit to it.

### Save a filter as a segment

<figure><img src="/files/6wXTpIwiS4UDG1rYpgM6" alt=""><figcaption></figcaption></figure>

This is the shortcut most people miss. **Save** turns the filter you just built into a reusable [segment](/docs/analyze/users-and-segments/audience/segments.md), without retyping the rules in the segment builder.

{% hint style="success" %}
**When to save.** If you built the filter to answer a question once, do not save it. If you built it to target an experience, or you will rebuild it next month, save it. A segment you never reuse is noise in the library.
{% endhint %}

### Filter versus segment

|                      |             Filter            |     Segment    |
| -------------------- | :---------------------------: | :------------: |
| **Lives**            | on this page, until you leave | in the library |
| **Reusable**         |               no              |       yes      |
| **Targetable**       |               no              |       yes      |
| **Group conditions** |               no              |       yes      |

### Related pages

* [Create a segment](/docs/analyze/users-and-segments/audience/segments/create-a-segment.md): the full builder, with groups and OR logic
* [Attributes](/docs/analyze/users-and-segments/data-management/attributes.md): what you can filter on
* [User details](/docs/analyze/users-and-segments/audience/users/user-details.md): inspect one of the users you found