Skip to main content
TrailsparkDocs

Segment Destination

Overview

The Segment destination sends evaluation results to Segment as a track event named Lead Evaluated. After a lead is evaluated, Trailspark sends one event with the lead's score, AI reasoning, confidence, and evaluation date as event properties. You configure the property names to match your Segment schema.

This is an outbound destination — Trailspark pushes data to Segment. If you are using Segment to send activity events into Trailspark, that is the Segment integration under Settings > Integrations. For more on Segment as a signal source, see Connecting Segment.

Prerequisites

  • Segment integration connected (Settings > Integrations)
  • Admin or Owner role in Trailspark
  • A Segment source configured to receive server-side calls

Configuration

Go to Settings > Destinations.

Destination Settings

  • Send Evaluations to Segment -- Toggle to enable/disable the destination
  • Segment Integration -- Select which connected Segment integration to use
  • Use Email as User ID -- On by default. Uses the lead's email address as the userId of each event. When it is off, or the lead has no email, the userId is Trailspark's ID for the lead. Keep it on if email is your primary user identifier in Segment.

Trait Mapping

Each event carries these properties. The settings call them traits; you set the name for each:

UI LabelDefault trait nameWhat it contains
Score TraittrailsparkScoreThe lead's evaluation score: hot, warm, or cold
Evaluation Date TraittrailsparkEvaluatedAtISO 8601 timestamp of when the evaluation ran
Reasoning TraittrailsparkReasoningAI-generated evaluation reasoning
ICP Trait(none — optional)The name of the ICP the lead was scored against. Only sent when you set a trait name and the lead was scored against a specific ICP.
Score status Trait(none — optional)The account's score status: current, retired, or not_evaluated. Lets downstream tools tell a live score from a stale one — once an account leaves its ICP its status becomes retired and rides the next sync, so the last score is never mistaken for fresh. Only sent when you set a trait name.

Every event also includes confidence (a whole number) and leadId (Trailspark's ID for the lead) under those fixed names. You can rename the other properties to match your existing Segment naming conventions. The defaults use camelCase, Segment's recommended style.

What Trailspark Sends

For each evaluated lead, Trailspark sends one Lead Evaluated event. In the Segment debugger it looks like this:

json
{
  "userId": "jane@example.com",
  "event": "Lead Evaluated",
  "properties": {
    "leadId": 4821,
    "trailsparkScore": "hot",
    "trailsparkEvaluatedAt": "2026-06-30T14:05:12.000Z",
    "trailsparkReasoning": "Multiple stakeholders engaged across pricing and security pages...",
    "confidence": 85
  },
  "timestamp": "2026-06-30T14:05:12.000Z"
}

The property names shown are the defaults. The ICP and score status properties appear only when you set a name for them. Events are sent after each evaluation completes — whether triggered by new signal activity, a manual re-evaluation, or the staleness cycle.

Once the events land in Segment, you can forward them to downstream Segment destinations (ad platforms, email tools, analytics) or build Segment audiences from their properties, such as score tier and evaluation date.

Segment vs Other Destinations

Unlike Salesforce, HubSpot, and Airtable, the Segment destination does not support buying-group coverage fields. It sends individual lead evaluation properties only. Use a CRM destination if you need buying-group stage, completeness percentages, or role lists pushed alongside scores.

Troubleshooting

IssueResolution
Lead Evaluated events not appearing in SegmentVerify the destination is enabled and the Segment integration is still connected
Events arrive under a Trailspark ID, not an emailTurn on Use Email as User ID. Leads with no email always use the Trailspark ID
Property names conflict with existing propertiesRename them in the Trait Mapping section to avoid collisions
No Segment integrations availableConnect Segment first from Settings > Integrations

Next Steps