Key takeaways
- Company enrichment adds context to a correctly identified organization.
- Headquarters, operating location, parent and subsidiary are different relationships.
- Define authoritative sources and merge rules for each business attribute.
Overview
The first problem is identifying which organization the record represents. A brand, legal entity, subsidiary and local branch can have different attributes while sharing a name or website. Define the unit you need before enriching. Employee count and revenue estimates should include ranges, dates and source context rather than appearing as precise current facts without support.
How it works
Resolve the organization and distinguish parent, subsidiary and location records.
Retrieve the fields relevant to the intended segmentation or workflow.
Apply source and freshness rules before merging attributes.
Choose which organization the record represents
A brand, a legal entity and a corporate group can share a name while representing different account boundaries. Decide which one the workflow needs before adding revenue, employee count or location. A global parent’s employee total can be misleading when the sales territory is responsible for one local subsidiary.
Domains are useful identifiers but are not perfect corporate boundaries. One organization may use several domains, and a parent may host pages for many brands. Keep aliases and relationships rather than forcing every observation into one flat company record. When the entity is ambiguous, return the ambiguity instead of selecting the largest or most visible search result.
| Attribute | Definition to establish | Common confusion |
|---|---|---|
| Location | Headquarters, office or operating market | Treating an office as the only market served |
| Size | Group, entity or business-unit headcount | Applying parent size to a subsidiary |
| Industry | Classification system and business activity | Assuming one label captures every product line |
| Revenue | Period, currency and estimate or reported value | Comparing figures with different scopes |
Resolve disagreements field by field
Two sources may disagree because they observed different dates or used different definitions. An employee estimate is not necessarily comparable to a published year-end headcount. Store those qualifiers when they affect targeting. A precise-looking number without a date or method can be less useful than a documented range.
Set field-specific source precedence and preserve confirmed customer corrections. For example, a company website may clarify a trading name while a regulatory filing establishes a legal name. Do not make a single provider authoritative for every attribute merely because it matched the domain correctly. Identity confidence and field confidence answer different questions.
Validate the enriched account in its destination
Review a sample against the actual account-selection rules. If eligibility depends on operating in a supported region, verify operating coverage rather than checking that the headquarters field is populated. If it depends on size, confirm that the size refers to the right entity. Quality checks should follow the commercial definition, not just the schema.
An illustrative import enriches 500 account records but identifies 40 aliases of existing companies. Resolve those relationships before creating new accounts, then verify that ownership and history remain intact. Track newly useful accounts, corrected fields and unresolved identities separately. A higher row count after enrichment may indicate duplication rather than improved coverage.
What this looks like in practice
A regional subsidiary uses its parent’s website. The team records the relationship but avoids assigning the parent’s worldwide headcount to the local office used for territory planning.
Examples explain the concept; they are not reported customer results.What to check
Test entity resolution, hierarchy handling and the accuracy of fields used as hard filters. Sample edge cases such as rebrands, acquisitions and shared domains.
Common mistake
Using a company name as a globally unique identifier or assuming a website domain always maps to one legal entity.
Company enrichment vs. Firmographic data
Firmographic data is a category of company attributes. Company enrichment is the process that can add those attributes along with technology, events and other context.
Read the Firmographic data definition →Questions answered
What is Company enrichment?
Company enrichment adds or updates organization-level information, such as domain, industry, employee range, location, technology or ownership, on an existing company record.
Is a domain a sufficient company identifier?
It is useful but not infallible. Groups, brands and subsidiaries can share domains, and companies can change or operate multiple domains.
Why do providers report different employee counts?
They may use different sources, dates, entity boundaries and estimation methods. Preserve that context and avoid treating an estimate as an exact census.
Can a domain identify a company uniquely?
It is often a strong identifier, but shared sites, parent groups, redirects and multiple brands can complicate the relationship. Use the domain with entity context and preserve aliases. For consequential matching, verify that the account represents the intended organization rather than assuming every domain maps neatly to one legal entity.
Should estimated company revenue be used in targeting?
It can be useful if its uncertainty, period and entity scope are clear. Prefer a range when the source is approximate and test how the threshold affects inclusion. Do not present an estimate as audited revenue or let false precision determine eligibility without review.
References and further reading
Primary documentation and source material for this topic. Sources checked September 14, 2026; provider requirements can change.
Continue reading on the blog
Explore all articles and guides →Put the concept to work.
Explore the relevant AstroFabric workflow and see how the pieces connect.
Help keep this guide useful. Suggest a correction or browse the full glossary.