> 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/publish/target-right-people-who.md).

# Target right people (Who)

***

## Quick access

* [**All People**](#all-people)
* [**Specific Users**](#specific-users-recommended)

***

{% hint style="info" %}
Click on this link to get an in-app tour of the "Who" options:

[Launch in-app overview🚀 ](https://i.usejimo.com/tours?jimo_poke=d351502b-da6d-45ba-aeff-00be3b581a1d)
{% endhint %}

Effective **user targeting is essential** for delivering impactful experiences through Jimo. 

The **Who** block is where you fine-tune your audience, ensuring that your interactions reach the specific users who will find them most relevant. Whether you are aiming for broad visibility or a niche audience, configuring Who is your first step towards a successful engagement strategy.

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

## Who should see your experience? <a href="#id-1-who-should-see-this-content" id="id-1-who-should-see-this-content"></a>

Under *Users that will see this experience*, two options.

#### All users

*Show this to every users.*

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

No condition, no filter. Everyone who loads a page where Jimo runs is eligible, anonymous visitors included.

{% hint style="warning" %}
**All users is also the fallback.** If an experience was targeting a segment and that segment gets [deleted](/docs/analyze/users-and-segments/audience/segments/segment-details.md#deleting-a-segment), the experience reverts to showing for everyone. Check your live experiences before deleting a segment.
{% endhint %}

#### Segment of users

*Only show this to a segment of users.*

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

Picking this option opens the **Select User Segments** modal, which offers two paths.

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

***

### Using saved segments

Under **Workspace Segments**, every [segment](/docs/analyze/users-and-segments/audience/segments.md) saved in your project, with its icon, description, and current audience size. Search by name at the top.

Segments are the recommended path: they let you write a more focused message, and you keep a clear picture of which audience receives what.

#### **Selecting several**

You can tick more than one. The modal footer keeps a running count, for example **4 Segments (7 users total)**, so you know the reach before confirming.

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

{% hint style="warning" %}
The experience is shown to users belonging to **any** of the selected segments: the logic between segments is a **union**, not an intersection. To require that a user matches several conditions at once, build that as a single segment, or use an on-the-fly definition.
{% endhint %}

Once confirmed, the Who block summarizes your choice: the first segment names, *and N more*, plus the combined total.

<figure><img src="/files/0zpJqA4MG54B2LeWZmYJ" alt=""><figcaption></figcaption></figure>

{% hint style="success" icon="lightbulb-on" %}
**Create a Team segment to test live, without bothering anyone.** Build a segment matching only you and your teammates, then target it while you iterate. Your experience runs in real conditions, in context, but stays for your eyes only until it is ready. Switch to the real audience when you publish.
{% endhint %}

***

### Building a segment on the fly

**On The Fly Segment**, at the top of the modal, creates conditions that live **only inside this experience**. Nothing is saved to your Segments library.

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

Use it when the audience is specific to one experience and you will never reuse it. If you find yourself rebuilding the same conditions across experiences, save them as a [segment](/docs/analyze/users-and-segments/audience/segments.md) instead.

#### **The segment definition block**

**Create** opens a **Segment definition** block inline in the Who section. It is the same [condition builder](/docs/analyze/users-and-segments/audience/segments/create-a-segment.md#the-condition-builder) used for saved segments.

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

**+ Add** offers **Add a rule** for a single condition, or **Add a group** for an AND/OR container. Nested groups let you express combinations like *(A and B) or C*, exactly as in a saved segment.

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

Conditions come from the same attribute picker, organized by source: **From Jimo SDK**, **Custom Attributes**, **Experiences**, **No-Code Events**, **Tags**, plus a category per connected integration (Segment.io, HubSpot, PostHog…).

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

**Remove**, bottom-right of the block, deletes the on-the-fly definition entirely and returns you to the choice between All users and a segment.

***

### Checking who you are about to reach

Below the builder, a live count reports how many users currently match. It recalculates on its own as you edit, showing **Applying filters…** while it works. There is nothing to refresh.

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

<figure><img src="/files/94TOa6PR8wnYWmm8ZJhy" alt=""><figcaption></figcaption></figure>

More useful still: **the count is clickable**. Open it and a side panel lists the actual users matching your targeting, with their email, last activity and first seen. Search by name and sort by **Recently active** to check that real, recent people are in scope.

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

{% hint style="warning" %}
**Read the count before publishing.** Zero users means your conditions contradict each other, or the attribute you filtered on is [Pending](/docs/analyze/users-and-segments/data-management/attributes.md#pending-attributes) and carries no data yet. A count equal to your whole base usually means a condition is not doing what you think.
{% endhint %}

**Done** closes the Who block and keeps your targeting.

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

***

### Related pages

* [Segments](/docs/analyze/users-and-segments/audience/segments.md): create and manage the segments listed here
* [Create a segment](/docs/analyze/users-and-segments/audience/segments/create-a-segment.md): the full condition builder reference
* [Segment details](/docs/analyze/users-and-segments/audience/segments/segment-details.md): edit a segment, and what deleting one does to your targeting
* [Attributes](/docs/analyze/users-and-segments/data-management/attributes.md): the data your conditions read from
* [Users](/docs/analyze/users-and-segments/audience/users.md): explore your base before defining an audience
* [Troubleshooting](/docs/settings/troubleshooting.md): check live which segments your own account belongs to