Jimo Help Center
Using Jimo
Using Jimo
  • Introduction to Jimo
    • Welcome!
    • What is Jimo?
  • Getting started
    • Installing Jimo
    • Extension
    • Initial Setup
    • Designing Your First Experience
  • Experiences
    • Tours & Modals
      • Components
    • Surveys
      • Components
    • Banners
      • Components
    • Hints
      • Components
    • Checklists
      • Components
      • Behavior
    • Resource Center
      • Components
    • Changelog
      • Dashboard
        • Overview
        • Analytics
      • Changelog
        • Changelog Builder
        • Changelog Components
        • Changelog Navigator
        • Positionning (Trigger)
        • Changelog Preview
      • Posts
        • Post Builder
        • Post Components
        • Post Navigation
        • Multiple Languages
        • Post Preview
  • Design and manage experiences
    • Dashboard
    • Spaces
    • Builders
      • Flow Builder
      • Content Builder
      • In-app Builder
    • Navigator
    • Triggers & Conditions
      • Steps Triggers
      • Conditions
    • Theme
    • Multiple Languages
    • Positioning
    • Preview
  • Target & publish experiences
    • Overview
    • Trigger on the right spot (Show on)
    • Target specific URLs/Domains (Where)
    • Target right people (Who)
    • Trigger at the right time (When)
      • Planning Your Experience
      • Rate Limiting - Prevent overwhelming users
    • Increase visibility (Boost)
    • Mesure outcomes (Goal)
  • Monitor and analyze user data
    • Analytics
    • Users & Segments
      • Users
      • Segments
      • Import
      • Survey responses segmentation
    • Success Tracker
      • Overview
      • Trackers
      • Events
  • Admin & Settings
    • Project management
    • General Settings
    • Installation
    • Team Management
    • Environments
    • Plan and Billing
    • Notifications and Account Settings
    • MAU (Monthly Active Users)
  • Integrations
    • Integration Setup
    • Events for Analytics Integrations
    • Segment.io
    • HubSpot
    • Salesforce
    • Maze
    • Amplitude
    • PostHog
    • Mixpanel
    • Heap
    • Figma
    • Calendly, Google Calendar, Zcal
    • Intercom
    • Invision
    • Zapier
    • Slack
    • Crisp
    • Server-Side Events
    • Webhooks
Powered by GitBook
On this page
  • Quick access
  • Who should see your experience?

Was this helpful?

  1. Target & publish experiences

Target right people (Who)

Specify your audience with 'Who' to personalize experiences. Tailor interactions based on user traits and behaviors.

PreviousTarget specific URLs/Domains (Where)NextTrigger at the right time (When)

Last updated 6 months ago

Was this helpful?


Quick access


Click on this link to get an in-app tour of the "Who" options:

Effective user targeting is essential for delivering impactful experiences through Jimo. The 'Who' field is where you fine-tune your audience, ensuring that your interactions reach the specific users who will find them most relevant. Whether you’re aiming for broad visibility or a niche segment, understanding and configuring the 'Who' settings is your first step towards a successful user engagement strategy.

Who should see your experience?

All people:

Show this experience to all users in your platform.

Specific users (recommended):

You can target specific users in two different ways.

  1. To easily test your experience live in context, without annoying users, we recommend creating a Team segment.

    You'll just have to choose this segment while you're testing to be sure to keep what you do for your eyes only until it's ready.

  2. By narrowing your audience down with filters on the fly such as: Activity with previous experiences, Activity on events, Emails, etc.

    You can also add AND/OR logic groups to combine attributes.

Little advice: When you create a segment on the fly, do not forget to click on the refresh button on the right. It allows you to update and see which users are concerned.

By selecting users of the segments () in your account. We recommend segments because they allow you to create a more focused message, and you’re able to get a sense of what messages are being sent to what segments.

see here how to create segments
Launch in-app overview🚀
All People
Specific Users
Who field
All people
Specific users
Specific users settings
Testing team segment
Selected segment
On the fly attributes
Refresh button