Loading
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.
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.
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.