AI Lead Scoring for Salesforce
Your objects, your automations, your fields. Trailspark adds Hot, Warm, or Cold scores with written reasoning on Leads and Contacts, plus propensity and buying-group coverage on the Account.
What syncs between Trailspark and Salesforce
Trailspark reads the Salesforce fields you map and your opportunities to score each account, then writes results to custom fields you create, updated after each evaluation.
Salesforce sends to Trailspark
- From Salesforce
Account, Lead & Contact fields
Industry, employee count, market segment, region, and job title from the fields you map, used for ICP matching and role-based scoring.
- From Salesforce
Opportunities
Synced onto accounts so deal history informs scoring. On by default; limit it to the record types and opportunity types you choose.
- From Salesforce
CRM Role Source Field
Point Trailspark at a Contact field where your team records buying roles, and those assignments are treated as authoritative.
Trailspark writes to Salesforce
- To Salesforce
Trailspark Score
Hot, Warm, or Cold, written to a field you create on Lead and Contact. Updated after each evaluation.
- To Salesforce
Trailspark Reasoning
The plain-language reason behind the score, in a Long Text Area field reps can read before a call.
- To Salesforce
Evaluation Date, ICP & Score Status
When the evaluation ran, which ICP scored the record, and whether that score is current, retired, or not evaluated, so Flows can tell a fresh score from a stale one. ICP and status are optional.
- To Salesforce
Account propensity
High, medium, or low on the Account, with its ICP and score status. Unconverted Leads can take propensity as a fallback. All optional, mapped per field.
- To Salesforce
Buying-group roles & coverage
With buying-group push on: each person's roles on Lead and Contact, and Account fields for stage, engaged and missing roles, and people still needed. Only mapped fields are written.
Use cases
Prioritize inbound with the reason attached
Trailspark scores each person against your ICP using product usage, enrichment, and the Salesforce data you map, then writes Hot, Warm, or Cold with written reasoning to the Lead or Contact. Your Flows route on the score, and reps read the reason before they call.
Create records only for people worth a rep's time
When someone without a Salesforce record reaches the score levels you choose, Trailspark creates one: a Contact on the matching Account, or a Lead with company details filled in. Everyone else stays in Trailspark, out of your CRM.
See buying-group coverage on the Account
Buying Groups tracks who fills each role at an account. Push it to Salesforce and the Account shows its stage, engaged and missing roles, and how many people are still needed, next to its propensity.
Setup
Your Salesforce admin's part takes about five minutes. The rest happens in Trailspark.
- 1
Your admin creates a Connected App
A one-time step in Salesforce. OAuth with PKCE means no Client Secret is stored and there's no managed package to install.
- 2
Map your fields
Trailspark loads your Salesforce schema when you connect. Map the fields it reads and the custom fields that receive scores.
- 3
Choose what gets written
Pick the score levels that can create new records and whether buying-group fields are pushed. Everything else stays as is.
Connect Salesforce with Trailspark step by step
Our docs cover creating the Connected App, connecting a production or sandbox org, field mapping after you connect, opportunity sync, and troubleshooting.
How the Salesforce integration works: common questions
Other integrations and pages
Buying Group Intelligence
Buying roles and gaps, written to your CRM
See Trailspark and Salesforce on your own data.
Start free. Connect Salesforce with OAuth. Watch scores land in custom fields you create on the records your reps already use.