Jimo Cloud (Actions) Destination
Jimo lets you create powerful in-app experiences—such as AI Copilots, onboarding tours, marketing modals, hints, and more, improving your product adoption and without needing to involve your developers.
This destination is maintained by Jimo. For any issues with the destination, contact the Jimo support team.
- From your workspace's destination catalog, search for Jimo Cloud (Actions).
- Select Jimo Cloud (Actions) and click Add Destination.
- Select an existing source to connect to Jimo Cloud (Actions).
- Go to the Jimo dashboard, find and copy the API Key.
- Paste the API Key in the Jimo Cloud (Actions) destination settings in Segment.
Your Jimo API key.
Build your own Mappings. Combine supported triggers with the following Jimo Cloud (actions)-supported actions:
Mapping limits per destination
Individual destination instances have support a maximum of 50 mappings.
Send user profile details to Jimo
Send User Data is a Cloud action. The default Trigger is type = "identify"
The unique user identifier
Optional
The email of the user
Optional
User attributes coming from segment traits
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 Cloud (Actions) may take six or more hours for the initial sync to complete. Upon completion, a sync frequency of two to three hours is expected.