TrailSpark

Third-Party Intent & Field Provenance

Overview

Enrichment adds two different kinds of data, and each shows up in TrailSpark on its own terms: third-party intent is always labeled and only ever supports what your first-party data already shows, and company details always defer to your CRM.

Third-party intent is a distinct, labeled signal

Intent from a provider like Reo.dev — developer activity, research surges, and similar outside signals — is kept clearly separate from signals that came from your own product or CRM. It appears as its own labeled entry, for example:

Third-party intent (Reo.dev): developer activity High

That label is always there, so you can tell at a glance that a piece of activity came from a vendor rather than from something a real person did in your product.

In plain terms: intent from these tools supports what we see in your own product data — it never makes an account hot by itself. If an account's only activity is third-party intent, with nothing happening in your own product or CRM, that account will not score hot on the strength of the intent alone.

Because these signals aren't tied to a single named person, they also don't trigger a new evaluation on their own — they're picked up the next time the account is evaluated for its own, first-party reasons.

Enriched fields never override your CRM

Company details you get from Clay or Reo.dev — industry, employee count, region, market segment — follow one fixed rule: your CRM always wins. If a field is already set in your connected CRM, TrailSpark keeps that value no matter what an enrichment vendor sends back. Enrichment only fills in a field your CRM leaves blank.

This means enrichment is purely additive — it can only make your account data more complete, never less accurate relative to your own CRM, and there's nothing to configure to protect your CRM's values.

Next Steps