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 destination is in Beta
Partner Owned
- This integration is partner owned. Please reach out to the partner's support for any issues.
Jimo 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
- From your workspace’s Destination catalog page search for “Jimo (Actions)”.
- Select Jimo (Actions) and click Add Destination.
- Select an existing Source to connect to Jimo (Actions).
- Open your Jimo dashboard, find and copy your project id.
- Return to Segment and open the destination settings for the Jimo (Actions) destination that you just created. Enter your Jimo project id.
Destination Settings
| Setting | Description |
|---|---|
| Initialize only for identified users | 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. |
| Id | Required. Id of the Jimo project. You can find the Project Id here: https://i.usejimo.com/settings/install/portal |
| Refetch experiences after traits changes | 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. |
Available Presets
Jimo (Actions) has the following presets:
| Preset Name | Trigger | Default Action |
|---|---|---|
| Send Track Event | Event type = "track" |
Send Track Event |
| Send User Data | Event type = "identify" |
Send User Data |
Available Actions
Build your own Mappings. Combine supported triggers with the following Jimo-supported actions:
Mapping limits per destination
Individual destination instances have support a maximum of 50 mappings.
Send User Data
Send user ID and email to Jimo
Send User Data is a Web action. The default Trigger is: type = "identify"
| Field | Description |
|---|---|
| User ID | Type: STRINGThe unique user identifier |
| User email | Type: STRINGThe email of the user |
| User Traits | Type: OBJECTA list of attributes coming from segment traits |
Send Track Event
Submit an event to Jimo
Send Track Event is a Web action. The default Trigger is: type = "track"
| Field | Description |
|---|---|
| Message Id* | Type: STRINGThe internal id of the message. |
| Timestamp* | Type: STRINGThe timestamp of the event. |
| Event Name* | Type: STRINGThe name of the event. |
| User ID | Type: STRINGA unique identifier for the user. |
| Anonymous ID | Type: STRINGAn anonymous identifier for the user. |
| Event Properties | Type: OBJECTInformation associated with the event |
Settings
Segment lets you change these destination settings from the Segment app without having to touch any code.
| Setting | Description |
|---|---|
| Initialize only for identified users | boolean, defaults to FALSE . 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. |
| Id (required) |
string. Id of the Jimo project. You can find the Project Id here: https://i.usejimo.com/settings/install/portal |
| Refetch experiences after traits changes | boolean, defaults to FALSE . 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. |
This page was last modified: 07 Aug 2024
Need support?
Questions? Problems? Need more info? Contact Segment Support for assistance!