Dievio
Key points
- A profile URL, a name with a domain and an account domain each support a different operation.
- Review matches, empty fields and no-match responses separately.
- Keep the original source value before updating a CRM.
Choose a B2B data enrichment tool by the identifier already in your file and the field you need next. A public LinkedIn profile URL, a person’s name with a company domain, and a list of company domains give you three different starting points. Keep the source column so you can review what was matched.
Pick a tool based on the input you already have
| Your input | Operation | Output to review |
|---|---|---|
| Public LinkedIn profile URL | Dievio LinkedIn Lookup | Matching contact with available fields |
| First name, last name and company domain | Email Permutator for candidates or Hunter Email Finder for a lookup | Possible email formats or a lookup result, followed by a separate review |
| Company domains | Company enrichment for account fields, or role search for contacts at those accounts | Company attributes or new person records, depending on the operation |
If you still need to decide between a new contact database, an account data source or an intent provider, start with the B2B data provider guide.
Example 1: enrich a public LinkedIn profile URL
Make a one-column input with a public profile URL on each line. The sample input file shows the format. Keep the full source table separately so you can review the response against the original row. Sign in to use the dashboard, or send the URLs in linkedinUrls through the Lookup API.
For an API test, send one URL with includeWorkEmails: true, includePersonalEmails: false and onlyWithEmails: false. A matched profile can have an empty work email. Keep an empty response and a match with a missing field as separate outcomes.
DievioYour next customer starts here.
Find decision-makers by role, company and location. Build your next prospect list in Dievio.
Find my leadsFree audience preview · No credit card
Example 2: start with a name and company domain
Open the free Email Permutator and enter Jane, Doe and example.com. The tool generates possible addresses such as jane.doe@example.com and jdoe@example.com. It labels them as candidates. Check the company’s actual pattern and the address before using it.
If your workflow needs an email lookup service, Hunter documents Email Finder for a name and domain. Review the returned match and the available evidence before writing it back to your CRM. Hunter API reference.
Example 3: work from a list of company domains
For account fields such as industry and size, test a company enrichment API on each website and review the matched company. People Data Labs documents a website input for that operation. Keep your original account ID so you can compare the source and matched companies. People Data Labs company input reference.
For people at those accounts, submit the domains in company_websites and add role filters to POST /api/public/search. This one-row example pairs a known domain with a reserved test domain. Use your own authorized list for a real run.
{
"company_websites": ["stripe.com", "dievio-qa-secondary.example.invalid"],
"job_titles": ["Founder"],
"include_emails": true,
"include_phones": false,
"_page": 1,
"_per_page": 1,
"max_results": 1
}This is a combined people search. To record a separate outcome for each input domain, run one request per domain and keep that domain alongside its result. Search requests with an API key use the API balance. A returned record uses one credit.
If your input is a list of companies, the Clearbit and Dievio comparison separates adding company attributes from finding people who match a target role.
Keep the review before the CRM update
Save the source value, the returned fields, a review status and the date checked. Review uncertain matches and leave unknown values blank. If your input has mixed header names, use CSV Mapper to prepare the file before enrichment. For field mapping, retries and handoff, use the enrichment workflow guide.
