# Third-Party Intent & Field Provenance

> Source: https://docs.trailspark.ai/data-enrichment/how-enriched-data-shows-up

## 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 or PredictLeads — developer activity, research surges, hiring, funding, 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 (PredictLeads): receives financing — raised $12M in Series A funding
>
> Third-party intent (PredictLeads): 7 new job openings (software development 5, data analysis 2)
>
> Third-party intent (PredictLeads): started using Snowflake
>
> 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. Each PredictLeads news event gets its own entry, dated to when PredictLeads found it. Job openings are combined into one line per check, so an account with hundreds of open roles doesn't flood its activity with individual entries. A "started using" entry only appears for a technology you've added to your **Technologies to watch** list — see [Connecting PredictLeads](https://docs.trailspark.ai/data-enrichment/connecting-predictleads).

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.

## Where outside events show up on an account

Beyond the labeled entries themselves, these events roll up into the **Outside activity** read on an account — a band for how recently something happened at that company outside your product — shown on the account's own page and as a column on the accounts list. It sits next to **Account fit** — how well the account's company profile matches your ICP, which is exactly what the company details from enrichment fill in. Neither one changes the account's propensity score. See [Account detail](https://docs.trailspark.ai/accounts-dashboard/account-detail#account-fit-and-outside-activity) and [Browsing accounts](https://docs.trailspark.ai/accounts-dashboard/browsing-accounts#account-fit-and-outside-activity-columns).

## Enriched fields never override your CRM

Company details you get from Clay, Reo.dev, or PredictLeads — 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

- [Enrichment Rules & Budget Caps](https://docs.trailspark.ai/data-enrichment/enrichment-rules-and-budget-caps) — choose which accounts get enriched and set spending caps
- [Connecting Clay](https://docs.trailspark.ai/data-enrichment/connecting-clay) — set up company-detail enrichment
- [Connecting Reo.dev](https://docs.trailspark.ai/data-enrichment/connecting-reo-dev) — set up developer buying-intent enrichment
- [Connecting PredictLeads](https://docs.trailspark.ai/data-enrichment/connecting-predictleads) — set up hiring, funding, and technology-adoption activity