Company-domain enrichment turns a known website into a candidate account record. The important step is proving which business the domain represents before accepting its company name, professional-network profile or employee data. A parent company, subsidiary, product brand and regional business can share names without being the same CRM account.
Use this guide when the starting point is a company domain or website. For ongoing field updates and account operations, see account enrichment.
Normalize the website without losing evidence
Preserve the submitted value and extract the hostname with a URL parser. Separate paths and tracking parameters from the company identifier. A product page such as https://example.com/products/widget may identify the same website as its homepage, but it does not prove which legal entity or sales account owns the product.
Keep meaningful subdomains until your identity policy establishes that they can be collapsed. Do not derive the registrable domain by taking the final two labels: domain suffix structures vary. Use a maintained domain parser when that distinction matters.
Reject consumer mailbox domains as employer evidence when they came only from an email address. For trial signups with uncertain employers, use the signup enrichment workflow.
Ask for the company entity you need
Write an explicit target such as “the operating company associated with this website” or “the parent account already used in our CRM.” Without that instruction, two plausible providers can return different entities and both appear correct.
People Data Labs' company enrichment API describes matching an input company to a company profile. Treat the returned record as evidence to evaluate against your target entity, rather than letting a filled response settle every identity question.
| Evidence | What to compare | What remains uncertain |
|---|---|---|
| Website | Candidate domain and actual company website | Redirects can follow acquisitions or rebrands |
| Company name | Trading name, aliases and supplied name | Similar names can belong to different entities |
| Company profile URL | Website and organizational context on the profile | A parent profile may not represent a subsidiary |
| Location | Country or region needed by the workflow | Headquarters is not every operating location |
| Provider record ID | Stable reference within that provider | It is not automatically your CRM account ID |
Find a company profile URL by domain
Use the domain as the search or enrichment input, then inspect the candidate company profile's associated website and context. Prefer an explicit provider field when the contract supplies one. If research is required, retain the source URL and the evidence that connects the profile to the website.
Do not build a professional-network URL by guessing a slug from the business name. A plausible URL is not an identity match. Return unresolved when the evidence cannot distinguish two candidates.
If the provider returns no profile URL, search for the company name and domain together, then check the candidate profile’s website field. Record an unresolved result when no candidate establishes the connection. A search-result snippet alone is insufficient when similarly named companies remain plausible.
Interpret employee counts before using them
An employee count needs a definition. Ask whether the field represents an estimated total, a size range, profiles associated with a company, or another documented measure. Preserve that definition with the source and observation time.
Do not turn a range into an exact number or a missing value into zero. When two providers disagree, compare entity scope and freshness before calculating anything. Averaging parent-company and subsidiary counts produces a number with no clear meaning.
For a threshold-based routing rule, define how a range that crosses the threshold is handled. A range spanning two sales segments should go through the team's ambiguity rule, not whichever segment happens to be evaluated first.
Worked account: accept the profile, hold the segment
A fictional CRM account represents the operating company Example Labs at example.com. A lookup returns a profile with that website and the same operating-company name. It also returns an employee range of 51–200. Your routing policy assigns companies below 100 employees to one team and companies at or above 100 to another.
| Proposed field | Decision | Reason |
|---|---|---|
| Company profile | Accept after checking website and entity | Candidate matches the intended operating company |
| Employee range | Retain as 51–200 with source date | This is the reported value |
| Exact headcount | Leave unknown | The range does not supply an exact count |
| Sales segment | Review | The range crosses the 100-employee threshold |
| Existing account owner | Preserve | Enrichment does not authorize reassignment |
Choosing the midpoint, 125.5, would invent precision and route the account using a number nobody reported. A second result of 1,400 employees for a parent company does not resolve the ambiguity either; it describes a different entity.
Store identity acceptance separately from field acceptance. That lets a correct profile link proceed without forcing an unsupported segment decision. Before writing, resolve the existing CRM account ID and apply its field-ownership rules.
Pilot with ambiguous companies
After setting up Deepline, have the agent inspect company-enrichment tools and propose the identity contract. Use an internal sample containing an ordinary domain, a parent/subsidiary pair, a rebrand, a consumer mailbox domain and a no-match case. Show both the accepted rows and the review reasons.
Measure defensible matches and usable fields separately. A high fill rate is not useful if a regional subsidiary is repeatedly attached to the wrong global account. Use account prioritization only after the identity and field definitions are settled.
Questions operators ask
Is the company domain a unique account ID?
It is useful evidence, but businesses can operate several domains and one domain can represent several organizational units. Preserve a stable CRM ID once the target account has been resolved.
Can I get an exact employee count from a domain?
A provider may return a count or range. Its documented definition and observation time determine what the value means; do not present it as an audited headcount without supporting evidence.
Sources
People Data Labs company enrichment documentation was checked September 14, 2026. The matching policy and pilot are proposed workflow designs. For downstream updates, use HubSpot enrichment workflows.