First-Party Enrichment

First-Party Enrichment

First-party enrichment is any field Intempt fills in from data you already own. Your events, your traits, and the objects your connected platforms sync. No outside vendor sees it and there is no per-lookup charge.

Reach for this before third-party enrichment. It is free, it is always available, and it is usually more accurate about your own customers than any purchased dataset.

The two first-party services

Out-of-box source schema

Connect a platform and Intempt provisions its objects with a schema already defined, field for field. You do not write a mapping and you do not normalise the payload.

Full breakdown in Source taxonomy. This is enrichment in the sense that matters: a Stripe invoice arrives with 112 fields on the same profile as a web pageview, and you did nothing to make them line up.

Derived attributes

Computed from data already in your project, recomputed as that data changes.

Identity resolution is the one people forget is enrichment. Stitching an anonymous visitor to a known user retroactively enriches every event that visitor already sent.

What first-party cannot tell you

It cannot tell you a company's headcount, funding round, tech stack, competitors or hiring activity, because that information was never in your data to begin with. That is the line where third-party enrichment starts.

Cost

Both first-party services write into the same reserved keys as everything else, so a value's meaning does not depend on which service produced it. See user and account attributes.