Ctrlk
For the complete documentation index, see llms.txt. This page is also available as Markdown.

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 section is organized in two groups, plus imports:

Group
Pages
What it is for

Audience

Users, Segments

The people you can reach, and how you group them

Data Management

Attributes, Tags, Variables

The data your audiences are built on, and how it reaches your content

Imports

Bulk-upload users and attributes via CSV

In the dashboard, Imports sits on its own below the two groups. In this documentation it lives under Data Management, because importing a CSV is how you get data in, just like the SDK or an integration. Same feature, one click away either way.

The split is meaningful:

  • Data Management decides what you are able to say about a user.

  • Audience decides what you do with it.

Each page carries its own actions:

Page
Actions

Users

Import from CSV, Filter

Segments

Import, Export, + New Segment

Attributes

+ New Attribute, Install Attributes

Tags

+ New Tag

Imports

Import users from CSV

Users, Segments and Attributes each have their own search bar. Search finds an existing item by name. To narrow the user list by data instead, use the Filter builder on the Users page.

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

  • Export : reuse segments externally via static user list file download

Attributes are the building blocks of segments and filters. They come from five sources:

Source
Examples
How they arrive

Jimo SDK

Name, Email, Last activity, Sessions, Created

Automatic (snippet + SDK identification)

Custom

Plan, role, language, signup date

Defined in Attributes, pushed via the SDK

Integrations

Any field from your CRM or analytics tool

Synced from HubSpot, Salesforce, Segment.io, PostHog...

Experiences

Seen Tour X, Completed Survey Y, Answered "Yes"

Automatic when users interact with experiences

Events

Clicked "Upgrade", Visited /settings

Created in Success Tracker or imported

Tags are the sixth ingredient, and the only one that comes from no system at all: you apply them by hand.

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

1

Identify your users

Push user:id + user:email + user:name via the SDK right after login. This is the prerequisite for everything else.

→ Installing Jimo · Identify users guide

2

Define your key custom attributes

Pick 5-10 attributes that matter for segmentation: plan type, user role, language, creation date, trial status.

→ Attributes · Setup the segmentation · Initial Setup

3

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

4

Connect your integrations

If you use a CDP or CRM, set up the integration to auto-sync events and attributes.

→ Integration Setup · HubSpot · Segment.io

5

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

Audience

The people you can reach, and how you group them

· Users

· Segments

Go to
Audience

Data Management

The data your audiences are built on, and how it gets in

· Attributes

· Tags

· Variables

· Imports · Exports

Go to
Data management

Related pages

PreviousA/B Test
NextAudience

Last updated