What does data enrichment do in TrailSpark?

It fills in company details — like industry, employee count, and region — for accounts your CRM doesn't already cover, and it can bring in third-party buying-intent signals (like Reo.dev developer activity) alongside your own product and CRM data.

Which vendors can I connect for enrichment?

Clay and Reo.dev today, under Settings > Integrations in the Data enrichment section. Each connects with your own account for that vendor.

Will enrichment ever create new accounts or leads?

No. Enrichment only adds detail to accounts you already track. Any vendor record that doesn't match an existing account is ignored, not saved — TrailSpark never uses these connections to build a prospect list.

If my CRM and an enrichment vendor disagree on a field, which one wins?

Your CRM always wins. Enrichment only fills in company-detail fields your CRM leaves blank — it never overwrites a value you already have.

Data Enrichment Overview - TrailSpark Docs

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.

You'll find it under Settings > Integrations, in the Data enrichment section below your main integrations.

Bring your own key

Every enrichment connection uses your own account with that vendor — TrailSpark never resells or shares access to Clay or Reo.dev. 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. As the Reo.dev setup screen puts it: accounts you don't already track are ignored.

What you can connect

Provider	What it adds
Clay	Fills in company details from your own Clay tables and enrichment providers
Reo.dev	Spots developer buying intent and fills in company details for accounts you already track

Clay and Reo.dev connect differently — Clay is a two-sided round trip where TrailSpark and your Clay table exchange data, while Reo.dev is a one-way daily sync you scope with segments. See Connecting Clay and Connecting Reo.dev 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.

Next Steps

Connecting Clay — the two-sided webhook setup
Connecting Reo.dev — API key and segment setup
Enrichment Rules & Budget Caps — which accounts qualify and how spend is capped
Third-Party Intent & Field Provenance — how intent is labeled and which source wins on a field