Skip to guide

See Distill in action

Request Demo

Tell us a little about yourself and we’ll follow up to schedule time.

Browse guides

Enrichment

On this page 9 sections

Enrichment adds or updates information about a person or company, such as a matched profile, an employer, or an email address. It helps turn supplied names, URLs, and other records into more useful information for research and outreach.

Matching the right identity, loading a profile, finding an email, and deciding whether an address can be used for outreach are separate checks. Research develops the broader context and evidence that can explain relevance.

Profiles: the record behind a result#

A person profile can contain:

  • Name, professional description, and available location information.
  • Current companies and positions, including role titles and dates.
  • Previous work experience and education.
  • Research highlights and relevant web sources.
  • Available company details, such as website, employee count, industry, and headquarters.
  • Contact information and relationship context where the relevant feature and access make them available.

A company profile can contain its description, website, size, industry, headquarters, funding or investment information, research highlights, and relevant sources.

The contents vary with source coverage. A missing field means the information is not present in that result, not that the underlying fact is false. A person can have multiple current roles. A placeholder such as “Stealth” or “Self-employed” is not necessarily the name of an ordinary company.

Profiles are separate from lists and campaigns. The same person can appear in several lists, while each list can retain its own notes or other context. A campaign has its own audience and messaging settings. See Lists and Campaigns and personalization.

Matching an input to the right identity#

Distill can work from supported profile URLs, company websites, existing Distill profile identifiers, and email-to-profile lookups. Lists also accept imported records that require matching.

Inputs provide different levels of certainty:

Input or outcomeWhat it establishes
A recognized profile URLIdentifies a particular profile to resolve or load. Loading can still be pending or fail.
A company websiteProvides a company identity and material that can support a company profile.
A name with company contextHelps matching, but people can share names and employment can change.
An email addressCan be looked up to associate it with a person or company. A completed lookup can still be unresolved.
An unconfirmed list entryPreserves supplied information without establishing a confirmed profile match.

Matching a person, loading their profile, researching them, and finding an address are separate outcomes. An accepted import or a successful request does not prove all four happened.

For example, a spreadsheet row for “Alex Morgan, partnerships” is less specific than a row with the intended person's LinkedIn URL. If a name matches the wrong person, adding more research about that person does not fix the identity problem. List matching and correction options are covered in Lists.

Loading and updating profile information#

A supported URL or identifier can resolve to a profile already in Distill or one that still needs loading. Some work runs in the background, so the returned profile can be partial while its load is pending.

loadStatus reports the basic profile-loading state. researchStatus reports the separate research request. A loaded profile can still have research pending or not requested. A failed load or unresolved match does not establish that the person or company does not exist.

Profile fields, deeper research, and email information have separate update rules. A source publication date is not one universal date when every profile field was verified. Research explains the standard research reuse window and observable research states.

Current employment and job changes#

Current employment is based on available role records and employment rules. Current and historical roles are treated separately, including cases where a person has more than one current affiliation. Distill also has checks that use current employers when evaluating work-email information and outreach exclusions. Detected employment changes can trigger a new screening assessment for affected campaign records.

Source records can also lag behind a job change or leave an old role open. A search result, a loaded profile, and a prepared message can therefore reflect information checked at different times.

Finding an email is different from verifying it#

Email information has several distinct questions:

  1. Identity: does the address belong to the intended person?
  2. Employment: does a work address correspond to an employer currently associated with the person?
  3. Deliverability: does the validation service return a usable result for that address?
  4. Outreach eligibility: can this campaign use it under its settings and screening rules?

Distill's email-finding paths can use existing addresses, customer-provided information, enrichment providers, and possible addresses inferred from known information. The result can include its source and other details. A suggested address is not equivalent to a confirmed, currently usable address.

Validation can return valid, invalid, ambiguous, or unknown. Unknown can mean a check did not produce a usable verdict, such as a timeout or provider failure. It is different from confirmed invalidity. Validation results can be saved and reused, so viewing an address does not necessarily trigger a new check.

The product can show an address for inspection even when it is not eligible for new automated outreach. Current-employer filtering also has explicit exceptions for user-supplied addresses and addresses already used in a campaign. Those exceptions preserve the supplied address choice or allow an existing conversation to continue; they do not independently prove current employment.

Using enriched information in lists and campaigns#

An imported row can preserve the customer’s original information and extra context while Distill matches it to a profile. Unresolved or incorrect matches can be reviewed through the supported list actions. Lists explains import outcomes, duplicate handling, and corrections.

A saved address is available information, not by itself a decision to use that address in a campaign. Identity, current-employer checks, validation, campaign screening, and sending settings determine the relevant outcome. A visible email can remain ineligible for new automated outreach.

Enriched information can also support personalization. The campaign’s message variables and AI writing context determine how it reaches a message. Campaigns and personalization explains those paths.

Working through a connected assistant#

A connected assistant can retrieve detailed profiles, retrieve basic profiles in a batch, and use email-to-profile lookup. Supported options can include additional sources or work history in a detailed response; the default response contains only a selection of available information.

Email-to-profile lookup starts with an email address already supplied. It associates that address with available person or company information and can return unresolved or pending results. This differs from finding a new address or validating whether it can receive mail.

The product’s email-finding and validation capabilities do not imply that every assistant connection exposes a dedicated action for them. The current tool set determines which parts are available directly. Using an assistant explains access and tool availability.

Common questions#

Can I start with just a name, a website, or an email address?#

Distill supports several inputs, but they offer different certainty. A recognized profile URL points to a specific profile. A name needs enough context to distinguish the right person or company. An email can be looked up, but the result may still be unresolved. A company website can support company identification and profile information.

What if Distill matches my contact to the wrong person?#

The list’s identity match can be reviewed and corrected through supported actions. More research about the wrong profile does not fix the match. Lists explains correction, confirmation, and duplicate handling.

What if someone has changed companies?#

That can affect targeting, work-email relevance, and messaging. Distill records current and past roles separately, checks employers, and can reassess outreach eligibility when it detects a change. Customer-supplied or already-used addresses have different handling from newly discovered work addresses.

If an email is verified, will my message be delivered?#

Not necessarily. Validation does not guarantee inbox delivery or a reply. Email ownership, whether an address can receive mail, current employment, and campaign eligibility are different checks. A valid address also does not establish consent or audience fit.

Why can I see an email address that a campaign will not use?#

The profile can show information for inspection while the campaign applies additional eligibility checks. Current-employer relevance, validation, screening, and campaign settings can affect whether it is used. User-supplied addresses and addresses already used in a conversation have specific exceptions.

Does an unknown email result mean the address is invalid?#

No. Unknown can mean a timeout, provider failure, or another check without a usable verdict. It differs from a confirmed invalid result. Saved validation results can also be reused.

Does the assistant find a new email when it looks up an email address?#

No. Email-to-profile lookup begins with an address you already have and tries to identify the associated profile. Finding an address and checking its deliverability are separate capabilities.

All guidesBack to top
Distill product guidesAll pages as text