Person Attributes
These attributes represent personal and professional details for an individual, as returned by Tomba's enrichment services.
Basic Details
| Attribute | Description | Example |
|---|---|---|
email | The person's email address | m@wordpress.org |
first_name | The person’s first name | Matt |
last_name | The person’s last name | Mullenweg |
full_name | The complete name | Matt Mullenweg |
gender | Gender of the individual | male |
phone_number | Phone number if available (false if not) | false |
type | Classification type (generic, personal) | generic |
country | Country of the individual | US |
score | Confidence score (0–100) | 99 |
Professional Role
| Attribute | Description | Example |
|---|---|---|
position | Job title or role | CEO |
department | Department the person belongs to | executive |
seniority | Seniority level | senior |
Social Profiles
| Attribute | Description | Example |
|---|---|---|
linkedin | LinkedIn profile URL | https://www.linkedin.com/in/mattm |
twitter | Twitter handle or URL | null |
Verification
| Attribute | Description | Example |
|---|---|---|
verification.date | Date of last successful verification | 2021-05-25T00:00:00+02:00 |
verification.status | Status of the most recent verification | valid |
Note: Fields may return false or null when data is unavailable.
Email Type Attribute
The type field defines the nature of the email address based on the role or naming pattern used. It helps distinguish between direct contacts and role-based addresses.
Available Values
| Value | Description |
|---|---|
personal | The email address belongs to a specific individual (for example, john@company.com). |
generic | The email is a role-based address, typically not tied to one person (for example, support@, info@). |
Use Cases
- Prioritize personal emails for outreach and sales.
- Use generic emails for general notifications or customer support.
- Segment contacts by personalization level for better targeting.
Department Attribute
The department field identifies the division or function within the organization that a person belongs to. This is used to help segment, target, and understand roles within a company.
Accepted Department Values
| Department | Description |
|---|---|
engineering | Software, hardware, or technical engineers |
sales | Sales reps, account executives, closers |
finance | Finance and accounting roles |
hr | Human resources |
it | Information technology support and admin |
marketing | Marketing and branding teams |
operations | Logistics, business ops, and execution |
management | Mid-level or general management |
executive | C-level or founder-level roles |
legal | Legal team, lawyers, compliance |
support | Customer or technical support |
communication | Corporate communications or media relations |
software | Developers, software architects |
security | Information security, cybersecurity |
pr | Public relations |
warehouse | Physical product handling or logistics |
diversity | Diversity, equity, and inclusion |
administrative | Admin assistants and office managers |
facilities | Office or site facilities and maintenance |
accounting | Bookkeepers and financial accountants |
Use Cases
- Send outreach campaigns tailored to specific departments.
- Filter by function in CRMs or dashboards.
- Map personas in account-based marketing strategies.
Author Finder Attributes
These are additional fields returned if the email was discovered using Tomba's Author Finder, typically from an article or blog post. The response includes article metadata and a ranked list of author candidates.
Article Metadata
| Attribute | Description | Example |
|---|---|---|
url | URL of the article where the author was found | https://example.com/blog/post |
title | Title of the article | How to Write Cold Emails |
og_image | Open Graph image URL of the article | https://example.com/og-image.png |
description | Article description or excerpt | A guide to cold email outreach. |
article_domain | Domain where the article is hosted | example.com |
publisher_name | Name of the publication or blog | The Example Blog |
publish_date | Publication date in ISO 8601 format | 2025-08-29T19:32:47.000Z |
Candidates
The candidates array contains a ranked list of potential authors detected on the page. Each candidate includes:
| Attribute | Description | Example |
|---|---|---|
full_name | Candidate's full name | James Milsom |
first_name | Candidate's first name | James |
last_name | Candidate's last name | Milsom |
email | Discovered email for the candidate (if found on page) | james@example.com |
image | Candidate's profile image URL | https://gravatar.com/avatar/abc... |
gravatar | Whether the image is from Gravatar | true |
linkedin | LinkedIn handle | james-milsom |
twitter | Twitter/X handle | jmilsom |
facebook | Facebook handle | james.milsom |
github | GitHub handle | jmilsom |
instagram | Instagram handle | jmilsom |
youtube | YouTube handle | jmilsom |
mastodon | Mastodon handle or URL | @james@mastodon.social |
bluesky | Bluesky handle | james.bsky.social |
author_url | Author's profile page on the publication | https://example.com/blog/author/james |
website | Candidate's personal website | https://jamesmilsom.com |
job_title | Candidate's job title | Head of Content |
bio | Candidate's biography | Content marketing specialist... |
sources | Array of extraction methods that identified the candidate | ["json-ld", "meta-author"] |
name_confidence | Name confidence score (0.0–1.0) | 0.69 |
score | Composite candidate score (0.0–1.0) | 0.61 |
count | Number of times the candidate was mentioned on the page | 9 |
Extraction Sources
The sources array on each candidate indicates how the name was detected. Possible values include:
| Source | Description |
|---|---|
json-ld | Structured data (JSON-LD schema.org) |
meta-author | HTML meta author tag |
readability | Extracted via content readability analysis |
author-link-href | Author link found in HTML href attributes |
author-name-class | CSS class matching author name patterns |
twitter-data1 | Twitter card metadata |
social-slug | Inferred from social media profile URL slugs |
ner | Named Entity Recognition from article content |
Valid Email Guarantee
Tomba returns only valid email addresses when using Email Finder and LinkedIn Finder. All results are automatically verified before being returned, ensuring you receive deliverable and active email addresses. This saves you time and credits by eliminating the need for separate verification steps.