Destinations Overview
What Destinations Do
Destinations push lead evaluation results from TrailSpark to your CRM, marketing automation, or analytics platforms. After a lead is evaluated, TrailSpark writes the score, reasoning, evaluation date, and — optionally — buying-group coverage data to the configured fields in each active destination.
Available Destinations
| Destination | Objects | Notes |
|---|---|---|
| Salesforce | Lead, Contact, Account | Supports buying-group fields |
| HubSpot | Contact, Company | Supports buying-group fields |
| Airtable | Contacts, Companies | Supports buying-group fields |
| Segment | Identify traits | Evaluation results as user traits |
Marketo is no longer available as a new destination. Existing Marketo webhook configurations remain active but cannot be reconfigured through this interface.
Destinations vs Integrations
Integrations pull data into TrailSpark (signal sources). Destinations push data out of TrailSpark (evaluation results). You can use the same platform for both — for example, Salesforce as both a signal source and a score destination.
Core Fields Sent to Destinations
Every destination push includes these fields:
| Field | Description |
|---|---|
| Score Field | Lead evaluation score: hot, warm, or cold |
| Reasoning Field | AI-generated evaluation reasoning |
| Evaluation Date Field | When the evaluation occurred |
| Propensity score | Account-level propensity: high, medium, or low (written to the account or company object; Salesforce, HubSpot, Airtable) |
Results are sent after each evaluation completes — whether triggered by new signal activity, a manual re-evaluation, or the staleness cycle.
Buying-Group Fields (Optional)
When you enable the Push buying-group fields toggle in a destination, TrailSpark can also push account-level coverage data and contact-level role assignments. All of these are optional — they only write to your CRM if you map them to a field.
Account-level fields
| UI Label | What it contains |
|---|---|
| Buying-group stage | Where the group stands: Dormant, Forming, or Complete |
| Engagement completeness (%) | Share of required roles with an actively engaged person |
| Known completeness (%) | Share of required roles with any person assigned |
| People still needed | Count of additional people needed to complete the group |
| Missing roles | Role names not yet filled (semicolon-separated) |
| Engaged roles | Role names currently active (semicolon-separated) |
| Propensity as-of date | Date the propensity score was last evaluated |
| At-risk status | "At Risk" when high propensity meets stalled engagement; otherwise "Current" |
| Renewal health | Health signal for accounts in a renewal ICP: Healthy, Cooling, Fading, Cold, or Pending |
Contact-level field
| UI Label | What it contains |
|---|---|
| Buying-group roles | The contact's assigned buying-group roles, semicolon-separated (e.g., "Champion;Economic Buyer") |
Salesforce also supports a CRM Role Source Field on the Contact object — a field TrailSpark reads from your CRM to use as the authoritative role assignment when set.
For a full explanation of what these values mean, see Account coverage.
Configuration
Go to Settings > CRM Integration > Destinations tab to see all available destinations. Each card shows whether the destination is currently active.
All destinations follow the same setup pattern:
- Select the connected integration to use
- Toggle Send Evaluations on
- Map the core TrailSpark fields to your platform's fields
- Optionally enable Push buying-group fields and map any coverage or role fields you want
- Save
The platform must be connected as a CRM integration first (Settings > CRM Integration > Connect tab). Only Owner or Admin roles can configure destinations.
Multiple Destinations
You can enable multiple destinations simultaneously. All active destinations receive the same evaluation data with their own independent field mappings.
Destination-Specific Guides
Related
- Evaluation Rules — scoring rules are now configured per ICP in the ICP builder; this page covers the legacy global Rules page