Skip to main content
TrailsparkDocs

Data Enrichment Overview

Overview

Data enrichment connects a third-party data vendor to your workspace so Trailspark can add two things your own product and CRM data might not have:

  • Company details — industry, employee count, region, and market segment — for accounts where your CRM is thin or missing that information.
  • Third-party buying intent — outside signals of research or engagement, like developer activity picked up by Reo.dev, or hiring, funding, and expansion activity picked up by PredictLeads.

You'll find it under Settings > Integrations, in the Data enrichment section below your main integrations. If you don't already have an account with a vendor, every enrichment card offers a sign-up link right on its Connect screen — you don't need to leave Trailspark to get started.

Bring your own key

Every enrichment connection uses your own account with that vendor — Trailspark never resells or shares access to Clay, Reo.dev, or PredictLeads. You connect with a webhook or API key you control, and any usage is billed by the vendor directly to your own vendor account, in that vendor's own credit units. See Enrichment Rules & Budget Caps for the caps you can set on top of that.

Accounts only — enrichment never prospects for you

Trailspark is built around accounts you already have a relationship with, and enrichment follows the same rule: it only adds detail to accounts you already track. If a vendor sends back information for a company that isn't already one of your accounts, Trailspark ignores it — it's never saved, and no new account or lead is created from it. In short: accounts you don't already track are ignored.

What you can connect

ProviderWhat it adds
ClayFills in company details from your own Clay tables and enrichment providers
Reo.devSpots developer buying intent and fills in company details for accounts you already track
PredictLeadsSpots accounts that are hiring, raising money, launching, or expanding — and fills in company details — for accounts you already track

Each one connects and runs differently:

  • Clay is a two-sided round trip, where Trailspark and your Clay table exchange data.
  • Reo.dev is a one-way daily sync you scope with segments.
  • PredictLeads connects with an API key and an API token from your PredictLeads account. Every PredictLeads request spends one of your PredictLeads credits, and its activity is pulled on demand for the accounts that are about to be evaluated.

See Connecting Clay, Connecting Reo.dev, and Connecting PredictLeads for each setup.

Your CRM data always wins

When an enriched field and your CRM disagree, your CRM wins. Enrichment only fills in gaps — a blank industry, a missing employee count — it never overwrites a value your CRM already has. See Third-Party Intent & Field Provenance for the full precedence rule and how intent signals are labeled.

Keeping vendor spend under control

Because enrichment spends real vendor credits, every connection has its own rules for which accounts qualify and, where the vendor meters usage, monthly and daily caps. Any change to those rules shows you an estimate — priced in the vendor's own credits — before it takes effect. See Enrichment Rules & Budget Caps.

Enrichment follows scoring, not a fixed schedule

Company details and third-party activity are only pulled for accounts that are actually about to be evaluated — not your whole account list on a timer. How often Trailspark checks an account for new activity follows that account's own ICP: an ICP that only looks back 90 days doesn't need activity refreshed more often than that. An account that keeps coming back with no new activity is checked less often, and picks back up to its normal refresh rate as soon as it's active again. Company details, which change more slowly, refresh on their own longer cycle regardless.

Next Steps