Users & Segments
Your user base in one place. Browse users, build audience segments, and import data via CSV.
Understand who uses your product and build the audiences that will receive your experiences. This section is the data foundation behind all targeting, personalization, and measurement in Jimo.
Dashboard path: Users & Segments (/users)
Dashboard structure
The page has three tabs:
Users
All detected users. Click any row to open the profile side panel. Filter with the Add... builder.
Segments
All saved segments with a live count badge on the tab label (e.g. "Segments 12").
Imports
History of CSV imports with status badges (Draft / Done) and row counts.
Two action buttons in the top-right corner:
Import users from CSV
Opens the CSV import flow. Visible on all tabs.
+ New Segment
Opens segment creation. Visible on Users and Segments, hidden on Imports.
There is no global search bar. Filtering users is done through the condition builder (Add... button) on the Users tab.
Core concepts
A user is anyone who visits a page where the Jimo snippet is installed. Each user gets a unique Jimer ID automatically.
Once identified via the SDK, a user profile accumulates over time:
Attributes : native fields (name, email, sessions) + custom fields you push (plan, role, language...)
Experience interactions : which Jimo experiences the user has seen, completed, or responded to
Events : in-app actions tracked by Jimo or imported from integrations
Segment membership : which segments the user currently belongs to
A segment is a dynamic group of users defined by conditions. It updates automatically: users enter when they match, leave when they don't.
Segments are reusable across Jimo:
Experience targeting (Who) : show a tour only to "Trial users"
Filtering : narrow the user list to a specific audience
Analytics : compare experience performance across cohorts
Composition : use a segment as a condition inside another filter
Attributes are the building blocks of segments and filters. They come from four sources:
Native
Name, Email, Last activity, Sessions, Tags
Automatic (snippet + SDK identification)
Experiences
Seen Tour X, Completed Survey Y, Answered "Yes"
Automatic when users interact with experiences
The more you enrich user profiles, the more precise your segments become. Start with plan + role + language for quick wins.
Why identification matters
Identification (user:id, user:email, user:name) is the prerequisite for everything in this section.
Jimo sees anonymous sessions. It can show experiences to everyone, but cannot:
Build persistent profiles across sessions or devices
Use custom attributes for segmentation
Track individual journeys over time
Personalize content (e.g. "Hello {name}")
Jimo links every session to a known user. This unlocks:
Cross-session profiles with full attribute history
Dynamic segments that update in real time
Precise targeting by plan, role, behavior, or any custom data
Cohort analytics in Success Tracker
Personalized content using variables in the builder
Configure identification as early as possible in your setup, ideally right after installing the snippet. The earlier you identify users, the more data Jimo accumulates for targeting and analytics.
For implementation details, see the SDK segmentation guide. If you use a CDP or CRM, check HubSpot, Segment.io, or Salesforce to automate attribute syncing.
How Users & Segments connects to Jimo
Experience targeting (Who)
Every experience has a Who section in Target & Publish. Select a saved segment or build conditions on the fly. Both use the same condition builder.
Content personalization
User attributes are accessible as dynamic variables in the content builder (e.g. "Hello {firstName}"). Combined with Multiple Languages, you can create contextual variants of a single experience.
Analytics and measurement
Experience analytics can be filtered by segment. The Success Tracker measures adoption by cohort, answering questions like "Did paying users adopt this feature faster than trial users?"
Automation and triggers
Triggers & Conditions use attributes and events to fire experiences at the right moment. Actions can be conditioned by segment membership. The Agent uses knowledge triggers that reference user context.
Getting started
Identify your users
Push user:id + user:email + user:name via the SDK right after login. This is the prerequisite for everything else.
Define your key custom attributes
Pick 5-10 attributes that matter for segmentation: plan type, user role, language, creation date, trial status.
Create your first segments
Start with 3 to 5 essential groups: new users (created < 7 days), paying users, inactive users (last activity > 30 days), trial users, power users.
→ Segments
Connect your integrations
If you use a CDP or CRM, set up the integration to auto-sync events and attributes.
Iterate
Refine your segments based on analytics data and support feedback. Add segments as your adoption strategy matures.
Practical tips
Name segments explicitly: prefer "Paying users, active last 30d" over "Segment 1"
Do not over-segment early. 5 well-defined segments beat 30 vague ones.
Use tags for manual, one-off categorization. Use segments for automated, dynamic targeting.
Test your segments with the builder preview before applying them to live experiences.
Use the Troubleshooting Tool to debug segment membership issues.
In this section
Related pages
Target right people (Who) : Use segments to control who sees each experience
Installing Jimo : Snippet installation and user identification setup
Setup the segmentation : Developer guide for custom attributes via the SDK
Initial Setup : Recommended first steps for attributes and imports
Analytics : Experience-level metrics and CSV export
Success Tracker : In-app event tracking for goal-based measurement
Troubleshooting : Debug segment membership and experience visibility issues
Last updated