Attributes

Attributes are the data points attached to each user in Jimo. They power segmentation, targeting, personalization, and analytics. This page is the reference for the different types of attributes.

Dashboard path: Users & Segments > Usersarrow-up-right > [click a user] > Data tab > Attributes


What is an attribute?

An attribute is a named data point on a user, like a key-value pair:

Name
Value

plan

Pro

language

fr

hasInstalled

true

signup_date

2024-06-15

Attributes are used in three places across Jimo:

The more attributes you push, the finer your segmentation and personalization can be.


Attribute sources

Every attribute has a Source that tells you where the data comes from. The Source column in the user profile makes this explicit.

Attributes collected and managed automatically by Jimo, either by the snippet or through default SDK methods. You do not need to configure them, but you can enrich some of them via identify.

Attribute
Description
How to set

Jimer ID

Unique ID assigned by Jimo to every detected user (replaced by User ID if there's one)

Automatic

User ID

Your own internal user identifier

Pushed via identify

Name

User display name

user:name

Email

User email address

user:email

Language

User language

user:language

First seen

First session date

Automatic

Last activity

Most recent session date

Automatic

Sessions

Count of sessions recorded

Automatic

Created

Account creation in Jimo

Automatic

Tags

Tags assigned manually

Via dashboard


The Source column in the profile

When inspecting a user's profile, the Source column tells you where each attribute was set:

  • Native label: core Jimo field, automatic or set via default SDK methods

  • Jimo logo: custom attribute pushed via user:attributes

  • Integration logo (HubSpot, Salesforce…): synced from that integration

This is useful when troubleshooting: if an attribute value looks wrong, the Source tells you where to go fix it.


Identify is the prerequisite

Before pushing any attribute, you need to identify the user. Without identification, Jimo cannot attach attributes to a persistent profile.

1

Load the snippet

Install the Jimo snippet on your product. See Installing Jimoarrow-up-right.

2

Call identify on login

Assign a stable user ID as soon as the user authenticates.

3

Push default attributes in the callback

Set name, email, and language alongside the identification.

4

Push your custom attributes

Add the fields that matter for your segmentation (plan, role, signup date, feature flags, etc.).

For full implementation, error handling, and advanced options (refetchBoosted, removeUnspecified), see the SDK methods referencearrow-up-right and the SDK segmentation setup guidearrow-up-right.


If you are just getting started, here is a minimal set that unlocks most use cases:

Attribute
Type
Why it matters

user:id

String

Prerequisite for persistent profiles

user:email

String

Readable identification + integrations matching

user:name

String

Personalization in experiences

plan

String

Segment by subscription tier

role

String

Segment by permission level

signup_date

ISO date

Cohort analysis, tenure-based targeting

language

String

Multi-language targeting

last_active_days

Number

Re-engagement segments

feature_usage

Array

Adoption tracking and progressive onboarding

circle-info

See the full recommended custom attributes guidearrow-up-right for more examples and implementation patterns.


Last updated