Fits into your existing stack. Not the other way around.
Connect your CRM, your marketing tools, your product analytics, and your data warehouse. Trailspark resolves it all into one account story, evaluates that story against the definition of good that applies, and writes the result back to where your team already works. No rip-and-replace. No six-month implementation.
Signals In
Give Trailspark the evidence.
Most evaluation tools only see what lives inside one system. Trailspark accepts evidence from everywhere account activity actually happens, product, marketing, CRM, warehouse, web, and enrichment, so the evaluation reflects what people and accounts actually do, not just the slice one tool can see. One webhook endpoint, or a native connection: any source that can send data over HTTP can send evidence to Trailspark.
Product data
We gather the evidence most scoring tools never see: what people actually do in your product. Three ways to get it in, all landing in the same account timeline.
Your app via API
POST JSON events from your backend to one HTTP endpoint. Universal, per-source, batch, and bulk-backfill routes, with Node and Python examples.
JavaScript tracker
One script tag for page, track, and identify calls from your web app. Same endpoint as the API, no backend work.
BigQuery
Scheduled SQL syncs for product events, users, and accounts from the warehouse you already trust. Hourly or daily, no webhook code.
CRM
Firmographics, pipeline stage, and prior touches come in as context. The score and its reasoning go back to the records your reps already open.
Salesforce
Reads account and contact context, then writes scores and reasoning back to Lead, Contact, and Account fields.
HubSpot
Reads Contacts and Companies, then writes scores and reasoning to properties your Workflows can trigger on.
Airtable
For teams that run their pipeline in Airtable. Map your Contacts, Companies, and Deals tables and Trailspark treats it like any other CRM, scores written back included.
Marketing and CDP
Form fills, email engagement, program status, and website behavior from the tools already sending webhooks. No new instrumentation.
Marketo
Program status changes, form fills, and email engagement arrive as marketing evidence through Marketo webhooks.
Segment
Identify, track, and page events through a webhook destination, with results optionally sent back to Segment.
RudderStack
Sync product orgs and account traits through a RudderStack webhook destination. Same event spec as Segment.
Hightouch
Sync product orgs and account traits from your warehouse through a Hightouch HTTP destination, on the schedule you already run.
Any webhook
Zapier, Make, Webflow, Typeform, or anything that can send an HTTP request. Trailspark detects the source from the payload.
Enrichment
Bring your own provider to fill gaps in accounts you already track. Enrichment never creates accounts, and your CRM's values win any conflict.
Clay
Bring your own Clay account to fill in company details your CRM doesn't hold. Enrichment adds detail to accounts you already track and never creates new ones.
Reo.dev
Developer-activity buying signals from your own Reo.dev account, weighed alongside your first-party evidence.
PredictLeads
Company news as buying signals. PredictLeads spots hiring, funding, launches, and new tech adoption at accounts you already track, and fills in company details your CRM is missing.
Then Trailspark resolves it into one account story.
Before any of it gets evaluated, every piece of evidence has to be tied to the right person and the right account, in a shape the evaluation can actually use.
Identity resolution
Product users and CRM contacts often don't overlap cleanly. Trailspark joins product workspaces to CRM accounts automatically, so every product user's activity factors into the account-level evaluation, even if they never filled out a form or exist as a contact in your CRM. For individual-level matching, Trailspark connects records when a shared identifier exists across systems, like a matching email or a CDP user ID.
Normalization
You don't need to standardize your data before sending it. Each source sends data in its own format. Trailspark's mapping layer normalizes everything into a unified account timeline, so your marketing team's Marketo webhooks, your product team's Segment events, and your backend's server-side calls all feed into the same evaluation without anyone rewriting their instrumentation.
Judgments Out
Put every evaluation to work.
An evaluation only matters if it changes what happens next. Trailspark writes the propensity and the reasoning behind it back into the systems your team already works in.
See what every destination receives (opens in a new tab)CRM fields & workflows
Bi-directional CRM sync
Trailspark connects to your CRM in both directions. It pulls account and contact data for enrichment, so the evaluation has the firmographic and role context it needs. Then it writes the propensity and reasoning back to the fields your team already uses, so reps never have to open another tool.
What you get
Setup is OAuth, or a token for Airtable, field discovery is automatic, and you control which fields Trailspark reads and writes. In Salesforce, a person is written to a Contact when their account is already linked to a Salesforce Account, and to a Lead otherwise.
A score on its own is a number reps ignore. Trailspark writes the reasoning beside it, so reps see why an account is hot and what changed.
Alerts & data destinations
Beyond the CRM
The same score and reasoning, pushed to the channel a rep is working in and to the tools downstream of your CDP. Nothing gets a different answer than the CRM does.
Notifications
Evaluations pushed to the channel where the right rep will see them, routed per ICP, with the reasoning attached.
Slack
Alerts for propensity changes, newly eligible accounts, quiet accounts, and buying-group progress, each routed per ICP to the channel you choose.
Mattermost
For teams that self-host their chat. The same per-ICP alerts on propensity, eligibility, and buying-group progress, delivered inside your own Mattermost deployment.
Microsoft Teams
For Microsoft 365 shops. The same per-ICP alerts on propensity, eligibility, and buying-group progress, in the Teams channels your reps already live in.
Data destinations
The score and its reasoning written downstream, so every tool behind your CDP or your tables sees the same judgment.
Segment
Score and reasoning sent back as a track event or identify traits, so every tool downstream of your CDP sees them.
Airtable
Scores, reasoning, and buying-group fields written to your Contacts and Companies tables.
How it all fits together
Ingest
Every format, every source
Resolve
Match people, accounts & context
Evaluate
The whole account against your lens
Activate
Back to where your team works
Evidence flows in from any source. Trailspark resolves identities and firmographic context, evaluates the account against the lens that applies, and activates the result, writing the propensity and reasoning back to where your team works. Every step is visible and configurable.
Connect the tools you already use.
Connect your CRM and your first evidence source. Most teams have evaluations landing in their CRM within the first week.