Jimo Destination

Destination Info

Jimo enables product teams to connect with end-users in any step of the product lifecycle from ideas, shaping to release, multiplying by 5 users’ engagement and loyalty over a product.

Jimo maintains this destination. For any issues with the destination, contact the Jimo Support team.

Getting started

  1. From the Destinations catalog page in the Segment App, click Add Destination.
  2. Search for Jimo in the Destinations Catalog, and select the Jimo destination.
  3. Choose which Source should send data to the Jimo destination.
  4. Go to the Jimo dashboard and find and copy the API key.
  5. Enter the API Key in the Jimo destination settings in Segment.

Supported methods

Jimo supports the following methods, as specified in the Segment Spec.


Send Identify calls to enrich your end-users data to help you target the right users based on their traits. For example:

analytics.identify("userId123", {
  email: "john.doe@example.com",

Segment sends Identify calls to Jimo as an identify event.


Send Track calls to help you target your end-users based on their behavior on your app. For example:

analytics.track("Login Button Clicked");

Segment sends Track calls to Jimo as a track event.


You can send computed traits and audiences generated using Engage to this destination as a user property. To learn more about Engage, schedule a demo.

For user-property destinations, an identify call is sent to the destination for each user being added and removed. The property name is the snake_cased version of the audience name, with a true/false value to indicate membership. For example, when a user first completes an order in the last 30 days, Engage sends an Identify call with the property order_completed_last_30days: true. When the user no longer satisfies this condition (for example, it’s been more than 30 days since their last order), Engage sets that value to false.

When you first create an audience, Engage sends an Identify call for every user in that audience. Later audience syncs only send updates for users whose membership has changed since the last sync.

Real-time to batch destination sync frequency

Real-time audience syncs to Jimo may take six or more hours for the initial sync to complete. Upon completion, a sync frequency of two to three hours is expected.


Segment lets you change these destination settings from the Segment app without having to touch any code.

Setting Description
string. You can find your API key in your integrations page after you linked Segment to your Jimo account

This page was last modified: 17 Aug 2022

Get started with Segment

Segment is the easiest way to integrate your websites & mobile apps data to over 300 analytics and growth tools.
Create free account