Create a segment

Build an audience from rules and nested groups, combine them with AND and OR, watch the count update as you type, and save it for reuse.

Dashboard path: Users & Segments > Audience > Segments > + New Segment

---

Create a segment

Click + New Segment in the top-right corner of the Segments page to open the creation screen.

You build first, you name it last. Unlike most creation flows, the name, description and icon are not asked upfront: they come in a modal when you hit Save. Start from the audience you want, not from the label.

---

The condition builder

The builder lets you define any audience from your user data. It is the exact same tool used on the Users tab filter or in the Who section to target a specific audience on the fly.

+ Add offers two things, and the difference is the whole model.

• Add a rule: one condition. An attribute, an operator, a value.

• Add a group: a container holding several conditions, combined together, that then combines with the rest.

Available categories

The builder exposes up to 9 condition categories, but not all appear by default. Some are dynamic: they only show up when at least one attribute or event of that category exists in your project.

Always visible

Category	What it covers
From Jimo SDK	Native Jimo attributes fields: Name, Email, Last activity, Created, Sessions, Tags
User Segments	Nested segments: allow dependencies, unions and intersections between existing segments
Experiences	User interactions with Jimo experiences (seen, completed, answered with…)

Visible when data exists

Category	Appears when
Custom Attributes	At least one custom attribute has been pushed via the SDK or an integration
No-code Events	At least one no-code event or Jimo native event has been logged
Tags	At least one tag has been created
Segment.io Traits	Segment.io integration is connected and has sent identify traits
Segment.io Events	Segment.io integration is connected and has sent track events
Hubspot attributes	Hubspot integration synchronized custom attributes
Posthog events	Posthog integration is connected and has sent events
Mixpanel events	Mixpanel integration is connected and has sent events
Jimo API events	At least one event has been ingested via Jimo's server-side API

On a fresh project, only Attributes and Experiences are usable out of the box. Custom Attributes and Events unlock the real segmentation power — push them early via the SDK or integrations to expand what you can target.

Attributes vs Properties: The Users filter labels the native attribute category as "Properties". The Segments builder labels it as "Attributes". These refer to the same thing — the user's list of native attributes. See User attributes for the full reference.

Combining conditions with AND / OR

Conditions within the same group are connected by AND (green connector on the left). Separate groups are connected by OR (orange connector).

Start from the sentence, not from the builder. Write down who you want in plain language first, then reproduce it. People who build rule by rule end up with audiences they cannot explain.

To see how this comes together, walk through a concrete example.

Example — Building an AND/OR segment from scratch

Target audience:

Users with a proper Name AND a proper Id AND either a native Email OR an external_email custom attribute.

Formula:

Name AND Id AND (Email OR external_email)

Build steps:

1) Add the first condition (Name)

Click Add... and pick Attributes > Name > is not empty. The builder automatically creates the first main group around this condition with a default AND connector.

2) Add the second condition (Id)

Click Add... inside the same group and pick Attributes > Id > is not empty. The condition joins the existing group under the same AND connector.

3) Add a nested logic group

Click Add... and pick New logic group. A nested sub-group is created inside the main group.

4) Add the first alternative (Email) inside the group

Inside the new group, click Add... and pick Attributes > Email > is not empty. The condition is added under an AND connector by default.

5) Switch the group to OR connector

As new nested groups are created with a default AND connector. Click the connector and switch it to OR.

6) Add the second alternative (external_email)

Still inside the OR group, click Add... and pick Custom Attributes > external_email > is not empty. The condition joins the first one inside the OR group.

Final structure:

AND — Name is not empty
AND — Id is not empty
AND — [ OR — Email is not empty
        OR — external_email is not empty ]

All three top-level conditions must be true (Name, Id, and at least one of the two emails) for a user to match the segment.

Managing logic groups

As your segment grows, you will want to group, ungroup, and reorganize conditions. There are two levels of controls.

On a single rule, the ... menu offers:

Action	Effect
Turn into group	Promotes the rule into a container, so you can add conditions next to it
Duplicate	Copies the rule
Remove	Deletes just that rule

On a group, hovering reveals three action icons in its top-right corner.

Icon	Action	Effect
	Nest the selected conditions into a sub-group	Creates a new AND/OR layer around them
	Flatten a sub-group back into its parent	Moves the conditions up one level
	Delete the entire group	Removes all nested conditions plus the group's AND/OR connector

Do not confuse the two delete actions:

• Trash icon (on a group): wipes out the whole group — every nested condition and the AND/OR logic — in one click.

  
• X cross (at the end of a condition block): removes only that single condition, leaves the surrounding group intact.

  

Both are irreversible until you re-add the conditions manually. When in doubt, use the X cross to remove conditions one by one.

Example — Restructuring the previous segment

Continuing from the segment built in the previous section, suppose you now want a different audience.

New target audience:

Users with a proper Id AND either Name, native Email, or external_email.

New formula:

Id AND (Name OR Email OR external_email)

Starting state (from the previous example):

AND — Name is not empty
AND — Id is not empty
AND — [ OR — Email is not empty
        OR — external_email is not empty ]

Restructure steps:

1) Wrap everything in a new top-level group

• Hover the outermost group and click the Turn into a group icon

• The whole current segment becomes nested inside a new top-level AND group, giving you a place to add the Id condition separately later

2) Switch the middle group to OR

• Click the connector of the middle group (the one that used to be the main group)

• Toggle it from AND to OR

3) Move the Id condition out

• Inside the middle group, click the X cross at the end of the Id is not empty condition to remove just that condition (the group itself and the other conditions stay untouched)

• At the new top level, click Add... and re-add Attributes > Id > is not empty

After this step the structure is:

AND — Id is not empty
AND — [ OR — Name is not empty
        OR — [ OR — Email is not empty
                OR — external_email is not empty ] ]

4) Ungroup the redundant OR nesting

• The middle group now has two consecutive OR layers nested inside each other (the outer OR with Name, and the inner OR with Email/external_email)

• Since stacked ORs produce the same result, hover the innermost group and click the Ungroup icon

• The two email conditions are lifted one level up and join Name under a single OR

Final structure:

AND — Id is not empty
AND — [ OR — Name is not empty
        OR — Email is not empty
        OR — external_email is not empty ]

The segment now matches users with a valid Id plus at least one of Name, Email, or external_email.

---

Read the count

Under the builder, N users found with the matching users listed. It recomputes as you edit.

Use it as a sanity check, not just as a number: if the count is 0, or suspiciously round, or equal to your whole base, the rule does not say what you think it says.

This is how you verify that your segment catches the users you intended, before saving.

---

Save it

Save opens a modal asking for the identity of the segment.

Field
Icon	The visual marker shown next to the name in the list
Name	Required
Description	Optional, and the one people skip

Tip: Prefer explicit names like "Paying users, active last 30d" over "Segment 1". Use the description to note the intent ("For monthly activation tours") or the data sources it relies on.

The description is not decoration. It is what the next person reads in the library to decide whether to reuse your segment or build yet another one.

Once saved, you are redirected to the segments list where your new segment appears with its audience count already computed.

---

Related pages

• Segments: the library

• Segment details: edit, duplicate, delete, and target with it

• Filter users: the same engine, in exploration mode

• Attributes: define what you can filter on

• Success Tracker: create the no-code events that unlock the Events category