With Tray, you build
IconAutomations
IconIntegrations
and
IconAgents
that connect Segment across your business systems and teams.
Icon

Use cases

Segment + Tray

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.

What you can do with Tray

  • Marketing

    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.

    • Sync audiences to ad platforms: Push audience membership changes to paid channels when computed traits update
    • Trigger nurture sequences from track events: Enroll users in email sequences or update lifecycle stage when page-view or checkout events fire
    • Propagate identify traits to your MAP: Auto-push updated traits to your marketing automation platform after receiving enriched identify calls
  • Product and engineering

    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.

    • Trigger onboarding steps from milestone events: Fire targeted prompts or in-app messages when users complete key track events like "First Project Created"
    • Replicate experiment cohorts to analytics tools: Sync audience membership to BI or experimentation platforms when audiences are defined or updated
    • Resolve identity merges downstream: When alias calls link anonymous IDs to known users, update CRM contact records or identity graphs automatically
  • Data and analytics

    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.

    • Alert on tracking plan violations: Route schema mismatch or blocked event notifications to the owning team for remediation
    • Orchestrate reverse ETL model runs: Trigger Reverse ETL syncs on a schedule or in response to upstream warehouse changes
    • Surface failed destination deliveries: Run scheduled checks on egress metrics and route failures to on-call queues before they compound
  • Revenue operations

    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.

    • Route PQL events to your CRM: Create or update opportunities when a user hits a product-qualified threshold based on track events and computed traits
    • Sync group traits to account records: Push updated company attributes to CRM account records when Segment receives a group call
    • Alert reps on high-intent event sequences: Notify the owning rep via Slack or email when a user's track events indicate buying intent
  • Support

    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.

    • Attach event history to support tickets: Pull profile events and traits from Segment and append them to new tickets so agents have context at open
    • Trigger escalations from error events: Open a priority ticket or page on-call when a track event signals a critical failure or repeated error state
    • Enrich cases with identity traits: When a support record is created, fetch the matching Segment profile to populate account tier, plan, and recent activity
  • IT

    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.

    • Automate write key revocation on offboarding: Remove workspace access and revoke source write keys when employee offboarding is triggered in your HR system
    • Route deletion requests to Segment regulations: Submit GDPR or CCPA deletion and suppression requests from privacy tooling into Segment's regulation API without manual steps
    • Forward audit trail events to your SIEM: Pull workspace audit events on a schedule and sync them to your security or compliance log
Slack Logo
Tray Logo
Icon

Automations

Automations with Segment and Tray

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.

Icon

Integrations

Integrations with Segment and Tray

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.

Segment integration capabilities

Integrate Segment with 700+ applications plus any system with an API using our HTTP connector. These domains reflect how teams work in Segment.

Send behavioral data into Segment from anywhere in your stack

  • Track external events in Segment: Fire track calls when orders, tickets, or billing events occur in other systems so your event stream stays complete
  • Keep profiles current from CRM data: Send identify calls with traits from your CRM so Segment profiles reflect what's true across your stack
  • Sync account traits via group calls: Push company attribute changes from your CRM into Segment when account records update
  • Backfill and replay at scale: Use batch operations to ingest historical events when sources are added or schemas change
Icon

Agents

Build agents with Segment and Tray

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.

Ground agents with the behavioral context they need to act accurately

  • Object scope: Access profile traits, computed traits, event histories, and external IDs within approved workspace and source permissions
  • Freshness: Query profile data at run time, event history can be scoped by user, time range, or event type

Frequently Asked Questions

Find answers to common questions about our products and services.

How does Tray authenticate with Segment?

Tray connects using a workspace API token generated in your Segment workspace settings, scoped to the sources and operations you choose to expose.

How does Tray detect events from Segment?

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.

Which Segment objects and operations does the connector support?

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.

Can workflows and agents write data back into Segment?

Yes. Track, identify, group, alias, and batch calls can all be sent back into Segment from within a workflow or agent run.

How do approvals work for sensitive operations?

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.

How do teams start small?

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.

FAQs

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.

What comes standard with Tray

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.

Universal connectivity

  • Prebuilt connectors: 700+ connectors plus a universal HTTP connector for any REST API
  • Custom connectors: Build custom connectors that behave like native ones
  • Connect anywhere: Cloud or on-prem systems supported

Learn more about our connectivity options

On-premises connectivity

  • Connect securely: Access on-premises systems, whether first-party or third-party
  • Meet network requirements: Connect through approved configurations that align with enterprise security policies
  • Enterprise protocols: Support multiple on-premises security standards for safe integration

Learn more about on-premises connectivity

Authentication management

  • Secure credentials: Collect and store authentications with full encryption
  • Encrypted data: Protect all data at rest and in transit
  • Role-based control: Partition credentials by workspace and access level

Learn more about authentication management

Security and governance

  • Certified compliance: SOC 2 Type II, GDPR, CCPA, HIPAA
  • End-to-end protection: Encryption, detailed audit logs, scoped connections, and OAuth scopes

Learn more about security and governance