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.

Rise AI Source


Source Info
  • The Rise AI Source is an Event Cloud source. This means that it sends data as events, which are behaviors or occurrences tied to a user and a point in time. Data from these sources can be loaded into your Segment warehouses, and also sent to Segment streaming destinations. Learn more about cloud sources.
  • This source is in Beta

Rise AI(link takes you to an external page) provides AI-powered user guidance and automation, helping users accomplish their jobs-to-be-done with intelligent walkthroughs and contextual assistance.

This is an Event Cloud Source which can not only export data into your Segment warehouse, but can also federate the exported data into your other enabled Segment Destinations.

Rise AI maintains this source. For any issues with the source, contact their Support team.


Getting started

getting-started page anchor
  1. From your workspace's Sources catalog page(link takes you to an external page) click Add Source.

  2. Search for Rise AI in the Sources Catalog, select Rise AI, and click Add Source.

  3. On the next screen, give the source a name, then configure any other settings.

    • The name is used as a label in the Segment app, and Segment creates a related schema name in your warehouse. The name can be anything, but we recommend using something that reflects the source itself and distinguishes amongst your environments (for example, RiseAI_Prod, RiseAI_Staging, or RiseAI_Dev).
  4. Click Add Source to save your settings.

  5. Copy the Write key from the Segment UI.

  6. Log in to your Rise AI account, then navigate to Settings > Integrations > Segment Integration and paste the key to connect.


Rise AI uses the stream source component to send Segment event data. It uses a server-side Track method to send data to Segment. These events are then available in any destination that accepts server-side events, and available in a schema in your data warehouse, so you can query using SQL.

Rise AI includes the userId when available, along with a unique tenant_id for tenant isolation to ensure data privacy and proper attribution across different workspaces.


The table below lists events that Rise AI sends to Segment. These events appear as tables in your warehouse, and as regular events in other destinations. Rise AI includes the userId if available.

Event nameDescription
Walkthrough ProgressUser progress through AI-guided walkthroughs and onboarding flows
ChatsAI chat session creation and interactions

The table below list the properties included in the events listed above.

Property nameDescription
batch_idUnique identifier for the event batch
chat_idUnique identifier for the chat session
environmentEnvironment where the event occurred (for example, production or staging)
event_timestampTimestamp when the event occurred
tenant_idUnique identifier for the tenant/workspace
step_indexPosition of the current step in the walkthrough (walkthrough-progress only)
step_titleTitle of the current walkthrough step (walkthrough-progress only)
fulfillment_actionAction taken to fulfill the step (walkthrough-progress only)
walkthrough_job_to_be_doneThe job-to-be-done that the walkthrough helps accomplish (walkthrough-progress only)
chat_typeType of chat interaction (chats only)

Now that your source is set up, you can connect it with destinations.

Log into your downstream tools and check to see that your events appear as expected, and that they contain all of the properties you expect. If your events and properties don't appear, check the Event Delivery tool, and refer to the destination docs for each tool for troubleshooting.

If there are any issues with how the events are arriving to Segment, contact the Rise AI support team.