Solutions by app
Segment collects and routes user events, including track calls, page views, identify calls, and group associations, into sources, destinations, and profiles that power every team's analytics and activation work. Tray connects Segment so behavioral signals trigger workflows across your stack, and agents can query profile traits, act on audience membership, and write results back to the tools that need them.
Segment is where customer behavioral data lives: events, traits, computed audiences, and the sources and destinations that move data between your product and your stack. What it doesn't do is act on that data outside its own pipeline. It won't open a ticket, alert a rep, update a CRM record, or kick off an approval when something changes.
Tray bridges the gap, turning track events, identify calls, and audience changes into multi-step workflows that read profile traits from Segment, apply logic, and write to every system that needs to act.
See how different teams use Tray to take action from Segment.
Marketing
If you work in marketing, these are common ways teams use Tray with Segment to activate audience data and keep campaigns in sync with behavioral signals.
Product and engineering
If you work in product or engineering, these are common ways teams use Tray with Segment to connect behavioral data to experiments, onboarding, and activation flows.
Data and analytics
If you work in data or analytics, these are common ways teams use Tray with Segment to govern tracking plans, manage warehouse syncs, and maintain data quality.
Revenue operations
If you work in revenue operations, these are common ways teams use Tray with Segment to turn product usage signals into pipeline and account intelligence.
Support
If you work in customer support, these are common ways teams use Tray with Segment to surface behavioral context and respond faster when issues arise.
IT
If you work in IT or security, these are common ways teams use Tray with Segment to manage workspace governance, access, and compliance obligations.
Tray listens to Segment source events, including page views, track calls, and identify calls, and triggers workflows when configured behavioral conditions are met. Workflows can also run on schedules to poll Segment for profile trait updates, delivery metric changes, or workspace audit events.
Once triggered, workflows apply branching logic against event properties and profile traits, call external systems to enrich or act on the data, and write results back, updating records in CRMs such as Salesforce or HubSpot, creating tasks in Asana, sending alerts in Slack, or firing track and identify calls back into Segment to keep the event stream consistent. They can also be exposed as agent tools.
Segment sits at the center of your behavioral data layer, collecting events from web, mobile, and server sources and routing them to the destinations and warehouses your teams depend on. Tray extends that layer outward: workflows respond to Segment events and carry logic into CRMs, marketing platforms, data warehouses, customer support tools, and any system that needs to act on what users did.
Integrate Segment with 700+ applications plus any system with an API using our HTTP connector. These domains reflect how teams work in Segment.
Tray agents turn Segment behavioral data into action. They ground on approved profile context such as traits, computed audiences, and event histories, then call governed tools across your stack to update records, trigger workflows, and answer questions about user behavior in real time. Every outcome writes back to Segment and connected platforms, so teams can ask, act, and audit in one continuous flow.
Find answers to common questions about our products and services.
Tray connects using a workspace API token generated in your Segment workspace settings, scoped to the sources and operations you choose to expose.
Tray's Segment trigger listens for source events, including track and page calls, and starts workflows when configured event types are received. Workspace-level changes like audit events or delivery metrics are picked up via scheduled checks.
The connector supports track, page, identify, alias, group, and batch calls, plus profile trait, event, and external ID reads. Workspace operations include sources, destinations, tracking plans, regulations, and audit trail events.
Yes. Track, identify, group, alias, and batch calls can all be sent back into Segment from within a workflow or agent run.
Workflows can require human sign-off before executing sensitive actions like regulation submissions or tracking plan changes, routed through Slack, email, or any connected channel.
Most teams start with a single track or identify trigger and connect it to one downstream system, such as a CRM update or support ticket, then expand from there.
Tray's Segment trigger listens for source events, including track and page calls, and starts workflows when configured event types are received. Workspace-level changes like audit events or delivery metrics are picked up via scheduled checks.
Whether your systems, data, or models run in the cloud or on-premises, Tray connects them in one secure platform. Every connection, workflow, and agent operates under IT governance with encryption, audit logging, and access controls built in. Security teams can trust that all integrations comply with enterprise network and authentication policies.