Understand channel demand
Use channel and status metadata to compare incoming support work across the customer journey.
Integrations Segment
SegmentPlanned
See support in the customer journey.
Plan your Segment integration with Message. Build a controlled event pipeline from Message to Segment. Measure support activity alongside your own product events without exporting whole conversations.
Native connector planned. This is a developer-built workflow. It does not provide automatic revenue attribution, historical backfill or a native analytics dashboard.
Analytics
What we’re planning to connect.
- 01Message metadata
- 02Your event mapper
- 03Segment
Follow task outcomes
Map agent.completed and agent.failed webhooks into events for operational reporting.
Keep metrics interpretable
Use a stable event ID, timestamp and naming convention. Treat status changes as events, not additional customers.
The right context
Be precise about what connects.
Define the data, permissions and destination before putting the workflow in front of customers.
Available from polling
Conversation ID, channel, status, site ID and update time.
Task events
Agent completion and failure events, after signature verification and field selection.
Excluded from the polling feed
Customer email, transcript, IP address and internal notes.
Prepare for the connection
Define your first workflow.
- 01
Define the event
Choose a question to measure and a minimal event schema. A developer builds this workflow; there is no native Segment installation.
- 02
Map and deliver
Choose an HTTP source and explicitly select which destinations receive support events. Use Message automation polling for conversation metadata or signed task-outcome webhooks.
- 03
Check the numbers
Run one test event, replay it and confirm it is counted once. Verify consent rules and destination access before enabling the pipeline.