Segment Source
Deway 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.
This source is maintained by Deway. For any issues with the source, contact their Support team.
Getting Started
-
From your workspace's Sources catalog page click Add Source.
-
Search for "Deway" in the Sources Catalog, select Deway, and click Add Source.
-
On the next screen, give the Source a name and 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 (e.g.,
RiseAI_Prod,RiseAI_Staging,RiseAI_Dev). -
Click Add Source to save your settings.
-
Copy the Write Key from the Segment UI.
-
Log in to your Deway account - navigate to Settings > Integrations > Segment Integration and paste the key to connect
Stream
Deway 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.
Deway passes the userId associated with the user profile as the userId. In cases where Deway does not have an associated userId, the user's identifier will be passed in as the anonymousId.
Events
The table below lists events that Deway sends to Segment. These events appear as tables in your warehouse, and as regular events in other Destinations. Deway includes the userId if available.
| Event Name | Description |
|---|---|
walkthrough-progress | Tracks user progress through AI-guided walkthroughs and onboarding flows |
chats | Tracks AI chat session creation and interactions |
Event Properties
walkthrough-progress Event
The table below lists the properties included in the walkthrough-progress event.
| Property Name | Type | Description |
|---|---|---|
batch_id | String | Unique identifier for the event batch |
chat_id | String | Unique chat session identifier |
entity_type | String | Type of entity tracked (e.g., "walkthrough_progress") |
environment | String | Environment where event occurred (e.g., "prod", "staging") |
event_timestamp | ISO 8601 DateTime | When the event occurred |
event_type | String | Type of event (e.g., "progress_tracked") |
fulfillment_action | String | User action that fulfilled the step (e.g., "click") |
fulfillment_selector | String | DOM selector of element that was interacted with |
processed_at | ISO 8601 DateTime | When Deway processed the event |
processing_duration_ms | Number | Time taken to process the event in milliseconds |
selector | String | CSS selector of the target element |
step_index | Number | Current step number in the walkthrough (0-indexed) |
step_prompt_message | String | AI-generated guidance message for the step |
step_title | String | Human-readable title of the current step |
tenant_id | String | Unique identifier for the customer organization |
walkthrough_id | String | Unique identifier for the walkthrough |
walkthrough_job_to_be_done | String | The user's goal or job that the walkthrough helps accomplish |
chats Event
The table below lists the properties included in the chats event.
| Property Name | Type | Description |
|---|---|---|
batch_id | String | Unique identifier for the event batch |
chat_id | String | Unique chat session identifier |
chat_type | String | Type of chat interaction (e.g., "ask-me-anything") |
entity_type | String | Type of entity tracked (e.g., "chat") |
environment | String | Environment where event occurred (e.g., "prod", "staging") |
event_timestamp | ISO 8601 DateTime | When the chat was created |
event_type | String | Type of event (e.g., "create") |
processed_at | ISO 8601 DateTime | When Deway processed the event |
processing_duration_ms | Number | Time taken to process the event in milliseconds |
tenant_id | String | Unique identifier for the customer organization |
Common Properties
All Deway events include these standard Segment properties:
| Property Name | Description |
|---|---|
time | Unix timestamp of when the event occurred |
distinct_id | Unique user identifier |
$user_id | User ID when available |
$insert_id | Unique event identifier for deduplication |
Use Cases
Analyze Walkthrough Completion Rates
Track how effectively users complete onboarding flows and identify drop-off points:
SELECT
walkthrough_job_to_be_done,
step_index,
COUNT(DISTINCT chat_id) as users_reached,
COUNT(*) as step_completions
FROM walkthrough_progress
GROUP BY walkthrough_job_to_be_done, step_index
ORDER BY step_index;
Measure Chat Engagement
Understand when and how users engage with Deway:
SELECT
DATE(event_timestamp) as date,
chat_type,
COUNT(*) as chat_sessions,
COUNT(DISTINCT tenant_id) as unique_tenants
FROM chats
WHERE environment = 'prod'
GROUP BY date, chat_type
ORDER BY date DESC;
Track Job Completion Efficiency
Analyze which jobs-to-be-done are most or least efficient:
SELECT
walkthrough_job_to_be_done,
AVG(step_index + 1) as avg_steps_to_complete,
AVG(processing_duration_ms) as avg_processing_time,
COUNT(DISTINCT chat_id) as total_attempts
FROM walkthrough_progress
GROUP BY walkthrough_job_to_be_done
ORDER BY avg_steps_to_complete DESC;
Data Privacy
Deway is designed with privacy in mind:
- No PII in selectors: DOM selectors are automatically sanitized to remove any personal information
- Opt-out support: Users who opt out of tracking will not have events sent to Segment
- GDPR compliance: Supports data deletion requests
- Tenant isolation: All events include
tenant_idfor proper data segmentation