Loading
Data enrichment fills in missing facts about companies — legal name, registration number, industry, employee count, location and founding year — from outside sources. In Treepie Flow enrichment runs when a company arrives, stamps every value with its source and date, never overwrites a value your team typed, and leaves a field blank rather than guessing when no reliable source exists.
Because enriched fields look exactly like fields a person entered. Two years later a segment is built on employee counts that were true in 2024, and nobody can tell which numbers to trust.
Enrichment fills firmographic fields on a company record — size, industry, location, registration — and stamps each filled field with where it came from and when.
Enriched values are held with their source and date and are visibly distinct from entered ones. You choose whether enrichment may overwrite an entered value; the default is that it may not.
A campaign targeting companies over 200 staff pulled 340 accounts. Filtering to values enriched in the last twelve months left 210 — a smaller list, and one the team could defend in the review.
It does not guarantee accuracy. It records a provider's claim with its date, which is a far more useful thing to hold than an unattributed number.
Segments and lists filter on it, lead scoring can weight it, routing rules can use size or territory from it, and Growth reads industry when it groups organic performance.
| Manual research | Bulk data uploads | Treepie Flow | |
|---|---|---|---|
| When fields are filled | When someone has time | In periodic bulk uploads | On arrival, before routing |
| Where values came from | Unknown | Rarely recorded | Source and date on every field |
| Team edits | Overwritten by the next import | Often overwritten | Never overwritten |
| Missing data | Left blank or guessed | Often filled with estimates | Left blank when no source is reliable |
| Keeping it current | Never | Another upload | Refreshed every 90 days |
Whichever you connect. The field-level source stamp is Treepie's part of it, and it is provider-agnostic.
Not by default. If you allow it, the previous value is kept in the audit trail.
Yes, as a job with a diff you approve before it commits, like any other bulk change.
Legal name, registration number, industry, employee count, headquarters location and founding year. You choose which are switched on.
Within seconds of a company being created, before routing rules run.
Yes. A backfill enriches existing companies in the sandbox first, so you can check results before applying them.
The fields stay blank and the company is marked as not matched, so nobody mistakes a gap for data.
No. Values come from sources that can be named and dated. If none is reliable, the field is left empty.
Yes. Every enriched value is in the field history with its source, and refreshes that change a value are recorded too.
No. It is part of Flow; the pricing page lists which plan includes it and any usage limits.
Coverage depends on the public registries available in each country. Where no registry is available, website and filing sources are used.
Fourteen days, every module, no card. Or half an hour with someone who will run it on your own records and tell you where it does not help.