Skip to main content
Customer Data Platform Integration

AI Lead Scoring for Segment

Your tracking stays as it is. Add Trailspark as a Segment destination and the track, page, and identify calls you already send become scored signals. No code deploys.

What syncs between Trailspark and Segment

Segment forwards the events you choose through a Webhooks destination. Scores can go back to Segment too, through a separate destination you turn on.

Segment
Trailspark

Segment sends to Trailspark

  • From Segment

    Track events

    Each track call becomes a signal named after its event, with its properties available to your Signal Mapping rules.

  • From Segment

    Page views

    Page calls arrive as page view signals, with the URL and page name available for mapping. Send the pages that signal intent, like pricing.

  • From Segment

    Identify calls

    Connect anonymous activity to a person's email and add traits like name, company, and title to their record.

Trailspark writes to Segment

  • To Segment

    Scores & reasoning

    Optional: Hot, Warm, or Cold, the reasoning, and the evaluation date, sent to Segment as a track event or identify traits. ICP and score status go too if you map them.

Use cases

Score the events you already track

Segment already collects what people do on your site and in your product. Trailspark scores those events against your ICP with enrichment and CRM data, so adding it is a change in Segment, not an engineering project.

Credit the whole buying group, not just one user

Map Segment events to buying-group roles in Signal Mapping, so activity from every person at an account counts toward that account's buying-group coverage and score.

Send scores to the rest of your stack

Turn on the Segment destination, and scores, reasoning, and evaluation dates flow back into Segment, where the tools already connected to it can use them.

Setup

Configuration in Segment and Trailspark only. Test events show up in Signal Explorer within a few seconds.

  1. 1

    Create an API key

    One key authenticates the Segment destination. Nothing to install in your product.

  2. 2

    Add a Webhooks destination in Segment

    Point it at Trailspark and choose which events to forward with Segment's destination filters.

  3. 3

    Turn events into signals

    Map each event once in Signal Mapping, and it's scored alongside your CRM and product data from then on.

Connect Segment with Trailspark step by step

Our docs walk through creating an API key, adding the Webhooks destination in Segment, Signal Mapping rules, verifying the connection, and sending scores back.

Read the Segment setup guide (opens in a new tab)

How the Segment integration works: common questions

Yes. Every Trailspark plan is the full platform, Free included. Plans differ only in how many accounts Trailspark evaluates each month; see pricing for the tiers, or talk to us about custom volume.

No. Trailspark reads the track, page, and identify calls you already send. You add a destination in Segment; nothing changes in your product.

Track and page calls become signals, and identify calls connect them to a person. Each person is then matched to an account by domain or account ID.

Yes, each signal counts against your plan limits. Send identify calls plus the high-intent events that matter for scoring, and use Segment's destination filters to keep it to that list.

They're held in the staging queue until a lead match is available, usually from an identify call, or until the event ages out.

Yes, once you turn on the separate Segment destination. Scores, reasoning, and evaluation dates go to Segment as a track event or identify traits. Buying-group fields go to your CRM.

Other integrations and pages

Marketo

Marketing and CDP · Evidence in

Clay

Enrichment · Evidence in

PQL scoring

All users at the account, not one busy user

See Trailspark and Segment on your own data.

Start free. Add Trailspark as a destination in Segment and watch your events score. Results can flow back to Segment for your downstream tools, too.