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 > Users > [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:
Attributes are used in three places across Jimo:
Segmentation and filtering: conditions in the filter and segment builder
Experience targeting: Who conditions to show or hide an experience
Content personalization: dynamic variables in the content builder (e.g. "Hello {firstName}")
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.
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
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
Attributes you define yourself and push from your own database via the SDK. They are the foundation of meaningful segmentation.
Typical examples:
plan(Free / Starter / Growth / Enterprise)role(admin / member / viewer)language(if different from native)signup_datehasInstalled(boolean for feature adoption)team_sizecountry
Supported types: strings, numbers, arrays, booleans (700 characters max per attribute)
How to push them:
Custom attributes must be pushed inside the callback of the identify method to be correctly linked to the user. See the SDK segmentation setup guide for full implementation details.
Attributes synced automatically from a third-party tool connected to Jimo. The Source column shows the integration logo (HubSpot, Salesforce, Segment…).
Common integrations that push attributes:
Contact, Company, and Deal fields (via object mappings)
Salesforce record fields (via object mappings)
Identify traits
User properties from Amplitude
User properties from Mixpanel
Person properties from PostHog
Integrations are the easiest way to enrich Jimo profiles without building custom SDK calls. If your source of truth is a CRM or CDP, start there before writing SDK pushes.
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:attributesIntegration 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.
Load the snippet
Install the Jimo snippet on your product. See Installing Jimo.
For full implementation, error handling, and advanced options (refetchBoosted, removeUnspecified), see the SDK methods reference and the SDK segmentation setup guide.
Recommended attributes to push
If you are just getting started, here is a minimal set that unlocks most use cases:
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
See the full recommended custom attributes guide for more examples and implementation patterns.
Related pages
Users: Back to the user list and profile overview
Segments: Use attributes as conditions in the segment builder
Installing Jimo: Snippet installation
Identify users: Full guide to the
identifySDK methodSetup the segmentation: Detailed setup for custom attributes
SDK methods reference: Full list of SDK methods
Integration Setup: How to connect third-party sources for auto-synced attributes
Last updated