Account detail

What's on this page

The account detail page is the single view for everything Trailspark knows about one account — its buying-group health, the people in the group, enrichment data, and connected records. You arrive here by clicking any account row in Companies.

Header

At the top of the page the account's name, domain, and creation date are shown alongside a Refresh button that reloads all data on the page.

Under those, one line says what the account is named by and what that means for your plan:

• Company domain — the account is named by a company's own domain. The ordinary case.
• Personal email — not counted toward your plan — the account is named by a personal email address (a free webmail domain), so it doesn't count against your plan's account allowance.
• Named by an excluded domain — counts toward your plan — the account is named by a domain on your excluded-domains list. You told us not to treat that domain as a company identity, but this is still a real account and it still counts, so it's flagged here with a Manage excluded domains link straight to the setting.
• No domain yet — not counted until a company email appears — we haven't seen a company email address on this account yet, so it isn't counted for now.

The same reading appears as the Domain column on the Companies list, where you can also filter by it.

An account's domain can move up on its own. When the first person with a company email joins an account that had no domain, a personal-email name, or an excluded-domain name, Trailspark renames the account by that company domain straight away — whether they arrived through a signal, a CRM link, a warehouse identity sync, a review decision that moved them, or a restore from the archive. A company name never changes on its own: when people on an already-named account turn out to span two company domains, the question goes to the Review tab instead, and the account keeps scoring under its current domain until you answer.

Admins also see a Re-score account button here, for queuing a fresh score on demand — for example, right after cleaning up which workspaces belong to this account (see Move out… below). Clicking it shows a Scoring queued confirmation, or Already queued if a score is already on its way.

A back link returns you to the Companies area.

Overview cards

Below the header, four summary cards give an at-a-glance read before you dig into any tab.

Buying-group hero

For accounts tracked under a buying-group ICP, a coverage hero sits between the overview cards and the tabs. It surfaces the key buying-group numbers in one read:

• % of required roles identified (known completeness) — the headline figure
• % of roles engaged — how many of those filled roles are currently active
• Stage badge — Dormant, Forming, or Complete
• ICP badge — which ICP is driving this picture
• Updated [time ago] control — shows when coverage was last computed; click it to refresh

When both the account's propensity was high and buying activity has since stalled, the hero shows a red alert strip: "Was strong — now at risk. Buying activity stalled N days ago."

For a full explanation of what these numbers mean and how coverage refreshes, see Account coverage.

Account fit and Outside activity

Below the buying-group hero (or in its place, for accounts not tracked under a buying-group ICP), two cards give a second and third read on the account, independent of propensity:

Account fit — a badge (Strong, Partial, Weak, or Unknown) for how well the account's company profile matches your ICP's own description, plus a confidence percentage and up to three factors that drove the read (for example Industry matches the ICP's target sector or Employee count is below the ICP's typical range). When Trailspark doesn't have enough company detail to judge fit, the card reads "We don't have company details for this account yet" instead of a badge. If your workspace has no enrichment provider connected, a Connect a data enrichment provider link appears alongside that sentence — see Data Enrichment Overview.

Outside activity — what has been happening at the account outside your product. The card has three parts:

• The band — Hot, Warm, Cold, or None, with the time since the most recent event next to it. This reflects the last 90 days.
• The kinds — chips naming what kind of activity was seen in the last 30 days, for example Raised funding, Hiring activity, or Started using a technology. Because the chips cover a shorter span than the band, an account can be Cold with nothing to chip: when the most recent event is more than 30 days old, the card reads "Nothing new in the last 30 days" in place of the chips, so a quiet band is never left unexplained.
• The most recent events — the individual things that happened, newest first, each with its date, the kind of event, the provider it came from, and a short headline (with a line of extra detail underneath where there is any). For example: Jul 26, 2026 · Hiring activity · PredictLeads — 3 new job openings (software development 3).

A See all in Signals link under the list opens the Signals tab, where these events appear alongside everything the people at the account did.

Neither card ever changes the account's propensity score. Account fit and Outside activity are independent reads next to propensity, not inputs to it — see Browsing accounts for the same facets on the accounts list.

Opportunities

Below Account fit and Outside activity, the Opportunities card shows what Trailspark knows about this account's CRM deals. Unlike Account fit and Outside activity above it, these facts can feed into the account's propensity score once Trailspark has a synced picture of the account's deals — see How deals affect scoring below.

• Active customer always reads Unknown unless you've set up a Plan ladder for your product data. It is a separate fact from Won business before below, and the two are never merged: "Won business before" comes from your CRM deals, while "Active customer" comes from the Plan ladder. An account can have won a deal and since churned, or be a paying customer today whose only deal closed before the window Trailspark can see.
• While Trailspark is still reading the account's deals, the card reads "We haven't finished reading this account's deals yet."
• Once deal data is complete:
  • A Won business before badge appears when the account has ever closed a deal won, with how long ago ("in the last N months") when known.
  • Last outcome: Won or Last outcome: Lost names the most recent closed deal and when it closed.
  • Open pipeline totals the value of open deals — one line per currency, if your open deals span more than one.
  • Open deals lists each open deal with its stage, pipeline, deal type, close date, and owner.
  • An All deals table (click to expand) lists every deal for the account — name, stage, pipeline, type, close date, owner, amount, and any custom deal properties you've mapped for deals in Field Mapping.
  • An account with no deals in your CRM shows "No deals in your CRM for this account." instead.

Deal type shows as one of New business, Renewal, Expansion, or Other — how your CRM's own deal data maps to these four is configured on your CRM integration page; see Connecting HubSpot or Connecting Salesforce.

Trailspark also records each deal's outcome today, to power future ICP insights.

How deals affect scoring

For accounts with a fully synced deal picture, Trailspark's evaluation also considers deal context alongside everything else it already looks at: how many deals are currently open and in which stages and deal types, how long the oldest open deal has been open, the most recent closed outcome and how recent it was, and whether the account has won business within the history window Trailspark syncs (24 months by default). Deal amounts, deal owners, and deal names are never used for scoring — only the facts above. Accounts with no synced deals score exactly as they always have.

A change to an account's synced deals can also prompt a fresh look — re-checking which ICP the account belongs to and, if the account is due for a new score, re-evaluating it. This happens at most as often as the account's normal re-evaluation cadence allows (once every 24 hours by default). When it does, the account's score reasoning shows after CRM deal activity changed as the reason.

Tabs

The page has five tabs: Buying Group, Lifecycle, Signals, Score History, and Account Details.

Buying Group tab

This tab has two sections stacked vertically.

ICP assignment card — shows which ICP the account is scored against ("Scored against") and any additional ICPs whose scope the account also satisfies ("Also matches"). If you see unexpected secondary matches, the Eligibility rules on those ICPs are broader than intended. For how the priority resolver works and how to adjust it, see Managing multiple ICPs.

When you've chosen which workspace represents the account (the Use this workspace control in the Account Details tab), the card also reads Eligible via followed by the workspace whose product data matched the Primary ICP's Eligibility rules. Usually that is the workspace you chose. If it names a different one, a note appears: This account's ICP was matched through a different workspace than the one you prioritized. That means the chosen workspace's product data didn't match any ICP's Eligibility rules, so Trailspark kept the ICP the account matches through another of its workspaces rather than leaving the account unscored. Widen the ICP's Eligibility rules, or reconsider which workspace really is the account.

Role coverage accordion — lists every role defined in the Primary ICP with its current state (Engaged, Identified, or Missing) and the people filling it. Expanding a role row shows each contributor, how they were matched, and a link to their lead record. When the account is Dormant, the accordion is replaced by a short message indicating no roles have been identified yet.

For the full reference on role states, contributor labels, and what to do about missing roles, see Account coverage.

Lifecycle tab

The Lifecycle tab shows the account's motion history — how it has moved through stages over time. This is documented separately in Account lifecycle.

Signals tab

The Signals tab holds the Signal Activity card — the account's full signal history in one place, "Recent signals across everyone at this account, newest first." Unlike the per-person timeline on a lead detail page, this feed spans everyone at the account.

Each row shows the Lead the signal belongs to (a link that opens that person's lead detail page in a new tab), the signal's Type, Source, Name, Description, and Date.

The feed also lists Outside activity — things that happened at the company itself rather than to a person, such as raised funding or hiring activity. Those rows are tagged Outside activity in the Lead column, with the kind of event below the tag (for example Raised funding), because they belong to the account rather than to anyone in particular. They are the individual events behind the Outside activity card at the top of the page, and like that card they never change the account's propensity score.

Use the Per page control to show 10, 50, or 100 signals at a time, and Previous / Next to page through the history. When the account has no signals yet, the card reads "No signal activity for this account yet."

Score History tab

The Score History tab lists every propensity score the account has received — "Every propensity score this account has received, newest first." Where the Propensity overview card shows only the current read, this tab is the full record.

Each entry shows:

• The propensity at the time (High, Medium, or Low)
• The ICP the account was scored against
• The date of the score
• The confidence percentage
• The reasoning behind the score and the contributing factors, when available

A score that no longer reflects how the account is scored today carries a No longer current badge with a short, plain-language reason — for example "The account now matches a different ICP.", "The account is between ICPs and is not currently scored.", or "The account no longer matches any ICP." These entries stay visible as history; they are never the account's current score. When the account hasn't been scored yet, the tab reads "This account hasn't been scored yet."

Account Details tab

This tab covers the data behind the account, organized into several sections.

Enrichment Data — firmographic fields pulled from your CRM or enrichment source: Industry, Employees, Region, and Market Segment. The section only appears when at least one field is populated. Your CRM always wins when a field is set in both places — see Data Enrichment for how to connect a vendor and how enriched fields defer to your CRM.

Linked Representations — the card is titled "Linked Representations (N)" on screen (CRM accounts, workspaces, and other linked identifiers). Records the system proposed automatically show a yellow Proposed badge with accept (checkmark) and reject (X) buttons. Records you've already confirmed show a Linked badge. For how proposed links are generated and what merge means, see Browsing accounts.

Product Org Details — the card is titled "Product Org Details (N)" on screen (your connected product workspace data). When one or more product workspaces are linked to the account, their details appear here: plan name, user count, MRR, trial status, last active date, and any enabled feature flags or custom fields from your product system. The section header shows how many workspaces are linked. When your system reports a last-active value, it's labeled Last Active. When it doesn't, Trailspark shows an estimate based on recent product activity it has received for that workspace, labeled Last activity (from signals).

When an account has more than one linked workspace, a notice above the card explains that scoring uses the one marked Scored workspace, and that you can choose another below if that's the wrong one. That workspace's card carries a Scored workspace badge naming why it was picked — for example matches this account's domain, most product activity, most known people, highest revenue, most users, or you chose this once you've set it yourself. Occasionally, when nothing else distinguishes the workspaces, the badge reads no clear winner — chosen arbitrarily — that's a deliberate flag that the account is worth a look, not an error. Every other linked workspace shows a Use this workspace button; click it to make that workspace the one Trailspark scores against instead, and the account is re-scored shortly after.

Choosing a workspace yourself also changes how Trailspark decides which ICP the account belongs to: the chosen workspace's product data is checked against your ICPs' Eligibility rules first, so an account whose chosen workspace is on an enterprise plan lands in your enterprise ICP even if one of its other workspaces would match a self-serve ICP higher in the priority order. If the chosen workspace matches no ICP at all, the account keeps the ICP it matches through another workspace — the ICP Assignment card on the Buying Group tab says which one ("Eligible via"). Automatic picks (badges other than you chose this) don't change ICP assignment.

Move a workspace out. When an account holds more than one workspace, admins also see a Move out… button on each workspace's row. Use it when a linked workspace actually belongs to a different company that got combined into this account by mistake. It opens a preview first — nothing changes until you confirm it:

• Where the workspace is going — back to its own existing account if Trailspark recognizes one, or a new account created for it.
• How many people move with the workspace, and how many stay on this account because they aren't tied to it.
• A note that existing scores on both accounts will be recalculated.
• Any review items that were only open because of this mix-up will close automatically.

Confirm with Move workspace out to apply it. If an account turns out to be several unrelated companies stitched together, repeat this for each workspace that's really its own company, then click Re-score account in the page header once you're done — Trailspark scores the account you moved a workspace out of only once you ask, so a multi-step cleanup doesn't trigger a fresh score after every single move.

Leads — a collapsible list of every lead associated with this account. Each row shows the person's name, title, lead score (Hot / Warm / Cold), signal count, and last-active time. Expand a row to see their recent signals inline. A View all details → link at the bottom of each row opens the lead detail page for that person.

Hierarchy — the account's parent organization (if any) and its subsidiaries. Each entry links to its own account detail page.

Next steps

• Account coverage — the full reference for coverage stages, role states, and the at-risk pattern
• Account lifecycle — how accounts move through motions over time
• Managing multiple ICPs — how Primary ICP assignment works and how to override it
• Browsing accounts — the account list, domain grouping, and suggested links
• Lead detail — activity history and score breakdown for one person
• Role corrections — override a role assignment when the match is wrong