> 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).
# Who: target the right users
Choose which users see an experience: everyone, saved segments, or conditions built for this experience only, and check the reach before you publish.
**Who** decides which users see an experience: everyone, one or more saved segments, or conditions you build for this experience only. With No automatic trigger, Who does not apply: the panel no longer shows it.
**You will have at the end:** an audience you can explain in one sentence, checked against the live count before you publish.
***
## Who should see your experience?
Under *Users that will see this experience*, two options.
#### All users
*Show this to every users.*
No condition, no filter. Everyone who loads a page where Jimo runs is eligible, anonymous visitors included. This is the default of a new experience.
{% 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.*
Picking this option opens the **Select User Segments** modal, which offers two paths: saved segments, or a segment built on the fly.
## Use 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.
{% 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.
{% 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 %}
## Build 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.
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.
**+ 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.
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…).
**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.
## Target on what users already did
The **Experiences** category of the condition builder reads how each user interacted with your experiences: seen, completed, answered with. It is what you use to sequence experiences without code.
| You want | Condition in Who |
| ---------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------- |
| A second experience only for users who saw the first one | The first experience, seen |
| To show an experience again to users who did not finish it | This experience, not completed, with a recurrence other than once in [When](/docs/publish/trigger-at-the-right-time-when.md#frequent-combinations) |
| A follow-up for detractors of an NPS | The survey, answered with the scores you pick |
Users leave a "not completed" audience on their own once they complete the experience. The full pattern for two experiences in a row is in [Chain experiences](/docs/build/actions/chain-experiences.md).
{% hint style="info" %}
Conditions on attributes need the data first. Send them with the identify call, see [Identify your users](/docs/getting-started/install-jimo/identify-your-users.md) and [Attributes and events](/docs/getting-started/install-jimo/attributes-and-events.md).
{% endhint %}
## Check 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.
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.
{% 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.
## From your assistant
Ask: *"Target the Welcome modal at VIP User and Example. How many users does that reach?"* The preview shows the current and the new audience with the number of users each reaches, before anything changes. More in [What to ask?](/docs/integrations/mcp/what-to-ask.md)
## Verify
* The live count matches the audience you described in one sentence.
* In the Troubleshoot tool, the user panel lists the segments your own account belongs to. If you are not in the audience, the experience is **Ineligible** for you. See [Why my experience does not show](/docs/getting-started/publish-your-first-experience/why-my-experience-does-not-show.md), cause 4, and the [Troubleshooting](/docs/settings/troubleshooting.md) reference.
## Go further
* [Users & Segments](/docs/analyze/users-and-segments.md): explore your base and manage segments.
* [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.
* [Identify your users](/docs/getting-started/install-jimo/identify-your-users.md): the identify call carries the user id and attributes your conditions read.
* [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 you define an audience.
* [In-app tour of Who](https://i.usejimo.com/tours?jimo_poke=d351502b-da6d-45ba-aeff-00be3b581a1d): opens a guided tour of the section in your Jimo dashboard.
**Next page:** [When: schedule and frequency](/docs/publish/trigger-at-the-right-time-when.md)
