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.
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 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.

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

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 instead.
The segment definition block
Create opens the attribute picker. The condition you pick becomes the first rule of a Segment definition block, inline in the Who section. It is the same 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, User Segments, Experiences, No-Code Events, Tags, plus a category per connected integration (Segment.io, HubSpot, PostHog and the others).

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: Has been seen, Has been completed, Has been dismissed, their Has not been counterparts, and Answered with for surveys. It is what you use to sequence experiences without code.
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
A follow-up for detractors of an NPS
The survey, answered with the scores you pick
A reminder for users who finished a checklist a while ago
The checklist, Has been completed, more than N days ago
Users leave a "not completed" audience on their own once they complete the experience.
Completed more than N days ago
When the experience in a Has been completed condition is a checklist, a third field appears: at any time, the default, or more than N days ago. Jimo keeps the date each user completed the checklist, so you can bring back users who finished a first checklist a few days ago, without an import or an attribute of your own. The live count updates as you type the number. This time field exists for Has been completed on checklists only: tours, surveys and the other Experiences conditions have none. The full pattern for two experiences in a row is in Chain experiences.


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.

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?
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, cause 4, and the Troubleshooting reference.
Go further
Users & Segments: explore your base and manage segments.
Create a segment: the full condition builder reference.
Segment details: edit a segment, and what deleting one does to your targeting.
Identify your users: the identify call carries the user id and attributes your conditions read.
Attributes: the data your conditions read from.
Users: explore your base before you define an audience.
In-app tour of Who: opens a guided tour of the section in your Jimo dashboard.
Next page: When: schedule and frequency
Last updated