Trailspark Accounts overview
Overview
Trailspark Accounts keeps a live copy of your scored accounts inside your own CRM: Propensity, buying-group coverage, and a plain-language reasoning, next to the boards and lists you already use. It is a source, not a place to do your day-to-day work. You build your own views and automations on top of it, and Trailspark keeps the underlying rows current.
Exactly how it looks depends on the CRM you connect. On monday it is a board. This page covers what is the same everywhere; see the connect page for the CRM you use for its exact columns and setup steps.
What each field means
Every field Trailspark writes falls into one of a few kinds:
| Field | What it means |
|---|---|
| Propensity | High, Medium, Low, or Not scored: the account's current score level. |
| Score status | Current, Retired, or Merged: whether Propensity is backed by a live score right now. |
| At risk | Flagged when an account shows signs of churn or disengagement, clear otherwise. |
| Buying group | Dormant, Forming, or Complete: how filled in the people at this account are. |
| Missing roles | Which buying-group roles this account still needs someone in. |
| Account fit | Strong, Partial, Weak, or Unknown. |
| Outside activity | Hot, Warm, Cold, or None: activity Trailspark sees for this account outside your own product or CRM. |
| As of | When this row was last checked, whether or not anything changed. A freshness marker only, never a trigger. Build automations against Last changed and What changed instead. |
| Last changed | When something worth noticing last changed on this row. |
| What changed | What changed the last time this row was written. |
| Why | A plain-language explanation behind the account's Propensity. |
| Next step | A suggested next action for this account. |
| Merged into | Filled in only if this account was merged into another one. |
The names above are what every CRM Trailspark supports uses. See your CRM's own page in this section for anything specific to it, for example how it links back to your own account record.
Treat Trailspark's fields as read-only
Trailspark owns every field it creates and rewrites it on its own schedule. Typing into one won't change an account's score, and whatever you typed is overwritten the next time that row updates.
Your own fields are yours. Add anything you like next to Trailspark's: a status, a note, a person to assign, a due date. Trailspark never writes, renames, or removes anything it didn't create. The one thing it reads from your side is what you choose on the Field Mapping tab: the board and column that link each row to your own record, and, on monday, any columns of your own Accounts board you map as account fields (see Read your account fields from monday).
Where your CRM and Trailspark's row meet
Your own deals, tasks, and anything else linked to your account record stay exactly as they are. Trailspark never touches that relationship. Trailspark's row links to that same account record. That link is the one place the two meet: from Trailspark's row, you can get to your own record and everything attached to it, and depending on the CRM, sometimes the other way around too.
Next steps
- Which accounts appear, and what happens after: the rules for who gets a row, and what Score status and What changed mean
- Trailspark Leads: the optional, off-by-default list of people
- Connection health: reading the health of your connection, and what Repair and Restore all do
- Connecting monday CRM: if you use monday