AI Lead Scoring for RudderStack
Send the group calls RudderStack already collects, and each workspace's plan, seats, MRR, and trial status land on the account it belongs to. Every evaluation reads them.
What syncs between Trailspark and RudderStack
Two Webhook destinations in RudderStack: one sends group calls to the product org webhook, the other sends user events to the signal webhook. Trailspark does not write back to RudderStack directly.
RudderStack sends to Trailspark
- From RudderStack
Product org ID
The group call's groupId. Trailspark keeps one record per workspace and links it to the account it belongs to.
- From RudderStack
Plan & revenue
Plan name and ID, MRR, and trial status from the group traits you map. Each evaluation reads them as part of the account.
- From RudderStack
Usage
User count, last active date, and feature flags, so a busy workspace on a small plan looks different from a quiet one.
- From RudderStack
Custom fields
Any other group trait you map, stored on the workspace record.
- From RudderStack
User events
Track, page, and identify calls sent to the signal webhook. They become signals once mapped, and events that include the workspace ID link each person to it.
Want scores in the tools RudderStack feeds?
Trailspark writes scores and reasoning to your CRM. If your CRM syncs to your warehouse, RudderStack Reverse ETL can send those fields to the rest of your stack.
A typical setup
RudderStack sends workspace data and user events in. Trailspark reads your CRM, evaluates the account, alerts the team in Slack, and writes scores back to the CRM. If your CRM syncs to a warehouse, RudderStack Reverse ETL can route those scores back out.
- RudderStack sends group calls and user events to Trailspark.
- Trailspark sends actionable alerts to Slack.
- Trailspark reads records from your CRM and writes scores and reasoning back to it.
- Optionally, your CRM data reaches RudderStack through your warehouse and RudderStack Reverse ETL.
Use cases
Give every evaluation the plan and seat count
Plan, users, MRR, and trial status sit beside the product, marketing, and CRM evidence Trailspark reads, so a trial with ten users is judged differently from a paid workspace with one.
Connect users to the workspace they share
Signals that carry the same product org ID link each person to the same account, so activity from everyone in a workspace counts toward one account story.
Keep a record of plan changes
Trailspark records a workspace's plan history only when a value actually changes, so resending the same group call writes nothing new.
Setup
Configuration in RudderStack and Trailspark only. Check the result under Settings > Org Management.
- 1
Create a Product Org Updates API key
Map groupId to the product org ID and the traits you want, like plan and MRR, in the key's payload template.
- 2
Add a Webhook destination in RudderStack
Point it at your Trailspark webhook URL and send JSON. Add the secret header if your key has one.
- 3
Keep only group calls on that destination
RudderStack's Webhook destination sends every call type by default. A short transformation passes group calls and drops the rest.
- 4
Send user events to the signal webhook
A second Webhook destination sends track, page, and identify calls. Events that include the same workspace ID link each person to their workspace and its account.
Connect RudderStack with Trailspark step by step
Our docs walk through the Product Org Updates API key, the payload template, the Webhook destination in RudderStack, and the transformation that keeps only group calls.
How the RudderStack integration works: common questions
Other integrations and pages
See Trailspark and RudderStack on your own data.
Start free. Add a Webhook destination in RudderStack and see plan and usage data on every account Trailspark evaluates.