Skip to contentSkip to navigationSkip to topbar
On this page
Looking for more inspiration?Visit the
(information)
You're in the right place! Segment documentation is now part of Twilio Docs. The content you are used to is still here—just in a new home with a refreshed look.

Jimo (Actions) Destination


Destination Info
  • Accepts Page, Alias, Group, Identify and Track calls.
  • Refer to it as Jimo (Actions) in the Integrations object
  • This destination is not compatible with Destination Insert Functions.
  • This integration is partner owned. Please reach out to the partner's support for any issues.
  • This destination is in Beta

Jimo(link takes you to an external page) helps you to publish personalized product experiences to elevate adoption and user engagement without code as a layer on top of your app.

This destination is maintained by Jimo. For any issues with the destination, contact their Support team.


Getting started

getting-started page anchor
  1. From your workspace's Destination catalog page(link takes you to an external page) search for "Jimo (Actions)".
  2. Select Jimo (Actions) and click Add Destination.
  3. Select an existing Source to connect to Jimo (Actions).
  4. Open your Jimo dashboard(link takes you to an external page), find and copy your project id.
  5. Return to Segment and open the destination settings for the Jimo (Actions) destination that you just created. Enter your Jimo project id.

Property nameTypeRequiredDescription
Initialize only for identified usersboolean

Optional

If true, Jimo SDK will be initialized only after a Segment event containing a userID has been triggered. This prevents from having anonymous profile created in Jimo.


Idstring
required

Id of the Jimo project. You can find the Project Id here: https://i.usejimo.com/settings/install/portal


Refetch experiences after traits changesboolean

Optional

Enable this option if you'd like Jimo to refetch experiences supposed to be shown to the user after user traits get updated. This is useful when if you have experiences that use segment based on Segment traits.


Jimo (Actions) has the following presets

Preset NameTriggerDefault Action
Send Track EventEvent type = "track"Send Track Event
Send User DataEvent type = "identify"Send User Data

Build your own Mappings. Combine supported triggers with the following Jimo-supported actions:

(information)

Mapping limits per destination

Individual destination instances have support a maximum of 50 mappings.

Send User Data

send-user-data page anchor

Send user ID and email to Jimo

Send User Data is a Web action. The default Trigger is type = "identify"

Property nameTypeRequiredDescription
User IDSTRING

Optional

The unique user identifier


User emailSTRING

Optional

The email of the user


User TraitsOBJECT

Optional

A list of attributes coming from segment traits

Submit an event to Jimo

Send Track Event is a Web action. The default Trigger is type = "track"

Property nameTypeRequiredDescription
Message IdSTRING
required

The internal id of the message.


TimestampSTRING
required

The timestamp of the event.


Event NameSTRING
required

The name of the event.


User IDSTRING

Optional

A unique identifier for the user.


Anonymous IDSTRING

Optional

An anonymous identifier for the user.


Event PropertiesOBJECT

Optional

Information associated with the event


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

Property nameTypeRequiredDescription
Initialize only for identified usersboolean

Optional

If true, Jimo SDK will be initialized only after a Segment event containing a userID has been triggered. This prevents from having anonymous profile created in Jimo.

Default: false

Idstring
required

Id of the Jimo project. You can find the Project Id here: https://i.usejimo.com/settings/install/portal


Refetch experiences after traits changesboolean

Optional

Enable this option if you'd like Jimo to refetch experiences supposed to be shown to the user after user traits get updated. This is useful when if you have experiences that use segment based on Segment traits.

Default: false