Trailspark + Salesforce Lead Scoring Integration
Scores with written reasoning on your Lead and Contact records, account propensity and buying-group coverage on the Account. Fields you map, automations you already run.
What syncs between Trailspark and Salesforce
Every field is mapped during setup and updates as each evaluation completes or Salesforce data is updated.
TrailSpark Score
→ SalesforceHot, Warm, or Cold, written to a text field you create on the Lead and Contact objects. Pushed as each evaluation completes.
TrailSpark Reasoning
→ SalesforceThe written, plain-language reason behind the score, in a Long Text Area field reps can read before a call.
TrailSpark Evaluation Date
→ SalesforceWhen the evaluation ran, as a DateTime field. Pair it with Score Status so automations can tell a fresh score from a stale one.
Account Propensity, ICP & Score Status
→ SalesforceOn the Account object: propensity (high, medium, or low), the ICP the account was scored against, and a score status of current, retired, or not evaluated. All optional, mapped per field.
Buying-group roles & coverage
→ SalesforceWith the buying-group toggle on: role names per person on Lead and Contact records, plus account-level coverage fields. Only mapped fields are ever written.
Salesforce Account Data
← SalesforceFirmographic fields from the Account object flow into Trailspark for ICP fit evaluation.
CRM Role Source Field
← SalesforcePoint Trailspark at a Contact field where your team records buying roles, and those assignments are treated as authoritative.
Use cases
Inbound lead prioritization
Marketing routes inbound form fills to Salesforce. Trailspark evaluates them against ICP fit and prior product usage, and your flows route Hot accounts to an SDR queue with the reasoning attached.
Product qualified lead (PQL) routing
Free trial signups without CRM records are evaluated at the account level first. When a trial account reaches the score levels you configured, Trailspark creates the record in Salesforce with score and reasoning; enrichment fields you map are written at the Account level.
Expansion scoring for existing Accounts
Trailspark writes scores on existing Contacts tied to your customer Accounts based on product usage signals. CSMs and expansion reps see which customer users are showing new buying signal without waiting for a renewal cycle.
Setup
From authentication to first scored contact in under an hour for most teams.
- 1
Have your Salesforce admin create a Connected App
About five minutes for a Salesforce System Administrator: a Connected App with OAuth (PKCE, so no Client Secret is stored). No managed package, no AppExchange install.
- 2
Create the Trailspark custom fields
Three fields on Lead and Contact (Score, Evaluation Date, Reasoning) and optional Account fields for propensity, ICP, and score status. Trailspark gives you the exact labels, API names, and data types to use.
- 3
Map fields from a dropdown
Trailspark loads your Salesforce field metadata automatically. Map the Lead and Contact objects independently; each shows fields by label and API name.
- 4
Choose which score levels create records
Enable Create Records if Not Found and pick which score levels (Hot, Warm, Cold) trigger creation. Low-signal trial users stay in Trailspark instead of cluttering Salesforce.
- 5
Build automations on the score fields
Use Salesforce Flow to route on score, branch on which ICP produced it, and suppress actions when Score Status reads retired. Pushes land as each evaluation completes.
Common questions
Other integrations and pages
See Trailspark and Salesforce on your own data
Start free. Connect Salesforce with OAuth. Watch scores land in the custom fields your reps already use.
Sign Up Free