Configuring Site Settings
Accessing Scoring Configuration
Requires Owner or Admin role. Navigate to Settings > General Settings and scroll to the Lead Scoring Configuration section.
These settings control when and how TrailSpark evaluates leads. Changes take effect immediately for new evaluations; leads in cooldown follow new settings when their cooldown expires.
Signal Requirements
| Setting | Default | Range | Description |
|---|---|---|---|
| Minimum Signals | 3 | 1-50 | Total signal count required before a lead is evaluated |
| Minimum Signal Types | 2 | 1-10 | Number of distinct signal categories required (e.g., web activity AND product engagement) |
Increasing these values produces higher-quality scores but evaluates fewer leads. Decreasing them gives faster coverage with less data per lead.
Time Period
| Setting | Default | Range | Description |
|---|---|---|---|
| Lookback Days | 90 | 1-365 | How far back to consider signals when evaluating a lead |
Align this with your typical sales cycle. Longer cycles benefit from a wider window; fast-moving markets benefit from a shorter one.
Confidence Settings
| Setting | Default | Range | Description |
|---|---|---|---|
| Minimum Confidence Average | 70% | 0-100% | The AI model must reach at least this confidence for a positive evaluation |
Higher values produce fewer but more certain evaluations. Lower values increase coverage at the cost of certainty.
Cooling Off Period
Cooling off prevents leads from being re-evaluated too frequently, maintaining score stability.
Enable Cooling Off
Enabled by default. When active, recently evaluated leads must wait before re-evaluation. The wait depends on their last score.
Cooldown by Score
| Lead Score | Default Cooldown | Description |
|---|---|---|
| Hot | 168 hours (7 days) | Moderate cooldown; hot leads are already identified |
| Warm | 72 hours (3 days) | Shortest cooldown to catch leads about to convert |
| Cold | 336 hours (14 days) | Longest cooldown since rapid change is unlikely |
Profile Change Detection
Enabled by default. When active, cold leads bypass their cooldown if significant profile changes are detected (e.g., job title change, company firmographic update).
Signals from mapping rules with High Intent enabled always bypass cooldown. When a high-intent signal is received for a lead that was already evaluated, re-evaluation is triggered immediately regardless of the lead's current score or cooldown timer. You can flag rules as high intent when creating or editing them in Signal Mapping > Signal Rules. For more information see the Signal Management documentation.
Product Organization ID Fields
Configure which fields in your signal payloads identify a workspace or organization. These fields are searched in priority order to extract the product org ID for target org resolution.
By default, TrailSpark searches common fields like groupId, workspaceId, teamId, organizationId, companyId, accountId, tenantId, and nested variants (e.g., context.groupId).
You can add custom fields or reset to defaults. Changes apply to new signals only -- existing leads and target orgs are not affected.
Excluded domains
Some domains show up at a lot of your accounts without belonging to any of them: the agency that runs three of your customers' marketing, the consultancy embedded at half your enterprise base, a contractor who logs into six different workspaces. Left alone, a domain like that looks exactly like evidence that those companies are the same company — and can pull unrelated accounts together.
Excluded domains is where you name them. Add a domain here and TrailSpark stops treating it as a company identity: it will never link two accounts together, never win the contest for what an account is called, and never raise a flag in the Review tab.
What it does not do:
- People from those domains still count. They're still leads, still scored, still part of a buying group. Only the domain's role as "the company" is removed.
- It doesn't change your bill. This list has no effect on evaluated accounts or overage — see usage tracking.
- It doesn't rewrite anything by itself. If an account is currently named after a domain you exclude, TrailSpark doesn't quietly rename it. It puts an item in the Review tab proposing the new name, and waits for you.
There's one deliberate exception: if an account's people are all on an excluded domain — the agency is also a real customer of yours — the account keeps that domain and carries on as normal. Excluding a domain stops it standing for other companies; it doesn't erase the company itself.
Adding and removing domains
Under Settings > General Settings, scroll to Excluded domains.
- Type a domain into the box and press Enter (or click the add button) to turn it into a chip under Configured Domains.
- Click the × on a chip to remove it, or Clear all to empty the list.
- Under Suggestions you'll find one-click chips for domains commonly seen in this role. Nothing is excluded until you add it — the row is a shortlist, not a default.
Changes take effect when you save. Removing a domain simply stops the exclusion from that point forward: nothing that was kept separate gets merged back, and no closed review item reopens.
You can also exclude a domain straight from the Review tab, using the Exclude button on any item that names one — it's the same list.
Next Steps
- Inviting Team Members
- Browsing accounts — the Review tab, where excluded domains stop items appearing
- CRM Integration Overview
- Creating an ICP