Three dataset types
| Dataset | Overview | How to read it |
|---|---|---|
| Online | Records derived from online sources, including co-registration, submitted forms and publisher relationships. | Review contact, company, intent and freshness fields for the intended use. Source type alone does not establish permitted channel use. |
| Offline / skiptrace | Additional offline data matched to records to support contact and identity workflows. | Examine the matched fields and quality/suppression signals before calling or postal activation. |
| Scrape-trace | Offline matching combined with checks against public web information. | Confirm available fields and freshness in the actual export. |
Online field catalog
The published catalog lists the fields below. The grouping is for navigation; it does not imply that every field is populated or available in every export.
| Group | Published field names |
|---|---|
| Person and online contact | FIRST_NAME; LAST_NAME; DIRECT_NUMBER; MOBILE_PHONE; PERSONAL_ADDRESS; PERSONAL_CITY; PERSONAL_PHONE; PERSONAL_STATE; PERSONAL_ZIP; PERSONAL_ZIP4; SOCIAL_CONNECTIONS |
| Consumer attributes | AGE_RANGE; CHILDREN; GENDER; HOMEOWNER; MARRIED; NET_WORTH; INCOME_RANGE |
| Business email | BUSINESS_EMAIL; BUSINESS_EMAIL_VALIDATION_STATUS; PROGRAMMATIC_BUSINESS_EMAILS; BUSINESS_EMAIL_LAST_SEEN |
| Personal email and hashed identifiers | PERSONAL_EMAIL; ADDITIONAL_PERSONAL_EMAILS; PERSONAL_EMAIL_VALIDATION_STATUS; PERSONAL_EMAIL_LAST_SEEN; SHA256_PERSONAL_EMAIL; SHA256_BUSINESS_EMAIL; LAST_UPDATED |
| Company | COMPANY_ADDRESS; COMPANY_DESCRIPTION; COMPANY_DOMAIN; COMPANY_EMPLOYEE_COUNT; COMPANY_LINKEDIN_URL; COMPANY_NAME; COMPANY_PHONE; COMPANY_REVENUE; COMPANY_SIC; COMPANY_NAICS; COMPANY_CITY; COMPANY_STATE; COMPANY_ZIP; COMPANY_INDUSTRY; COMPANY_LAST_UPDATED |
| Professional context | DEPARTMENT; JOB_TITLE; LINKEDIN_URL; PROFESSIONAL_ADDRESS; PROFESSIONAL_ADDRESS_2; PROFESSIONAL_CITY; PROFESSIONAL_STATE; PROFESSIONAL_ZIP; PROFESSIONAL_ZIP4; SENIORITY_LEVEL; JOB_TITLE_LAST_UPDATED |
Offline and scrape-trace field catalogs
Both published catalog tables list the same fields. Confirm the selected dataset and matching process separately from the field names.
| Published field name |
|---|
| SKIPTRACE_MATCH_BY |
| SKIPTRACE_PERSON_TITLE_OF_RESPECT |
| SKIPTRACE_NAME |
| SKIPTRACE_ADDRESS |
| SKIPTRACE_CITY |
| SKIPTRACE_STATE |
| SKIPTRACE_ZIP |
| SKIPTRACE_LANDLINE_NUMBERS |
| SKIPTRACE_WIRELESS_NUMBERS |
| SKIPTRACE_CREDIT_RATING |
| SKIPTRACE_EXACT_AGE |
| SKIPTRACE_ETHNIC_CODE |
| SKIPTRACE_CARRIER_ROUTE |
| SKIPTRACE_LANGUAGE_CODE |
| SKIPTRACE_IP |
Terminology
| Term | Meaning in the source documentation |
|---|---|
| Online data | Data obtained from online sources or publishers. |
| Offline data | Data obtained from offline-source datasets. |
| Skip trace | Matching records against additional online and offline sources. |
| Skip scraped / scrape-trace | Combining additional-source matching with public-web checks. |
| B2C | Consumer-oriented records. |
| B2B | Business-oriented records and company context. |
| B2B2C | Business context connected to a person-level record. |
| Co-reg | Co-registration data associated with publisher collection. Confirm the recorded permissions for the intended use. |
Selected field definitions
| Field or related fields | Definition |
|---|---|
| FIRST_NAME; LAST_NAME | Names associated with the online record. |
| SHA256_PERSONAL_EMAIL; SHA256_BUSINESS_EMAIL | Fields containing hashed email identifiers. Treat them as matching identifiers, not readable email addresses. |
| PERSONAL_EMAIL; BUSINESS_EMAIL | Personal and business email-address fields. Use the appropriate validation and recency fields for the channel. |
| PERSONAL_EMAIL_VALIDATION_STATUS; BUSINESS_EMAIL_VALIDATION_STATUS | Validation labels attached to the respective email fields. |
| PERSONAL_EMAIL_LAST_SEEN; BUSINESS_EMAIL_LAST_SEEN | The most recent email signal recorded for the respective field. |
| SKIPTRACE_MATCH_BY; SKIPTRACE_B2B_MATCH_BY | The fields used to match the source record to additional data. |
| SKIPTRACE_PERSON_TITLE_OF_RESPECT; SKIPTRACE_NAME | Honorific and name fields in the offline append. |
| SKIPTRACE_ADDRESS; SKIPTRACE_CITY; SKIPTRACE_STATE; SKIPTRACE_ZIP | Postal fields in the offline append. |
| SKIPTRACE_LANDLINE_NUMBERS; SKIPTRACE_WIRELESS_NUMBERS | Appended landline and mobile phone fields. |
| DNC | A National Do Not Call Registry tag. It is one input to suppression review, not a complete authorization check. |
| COMPANY_NAME; COMPANY_DOMAIN | Company identity fields associated with the record. |
| COMPANY_DESCRIPTION | An AI-generated company description. |
| SKIPTRACE_B2B_ADDRESS | Appended business address. |
| SKIPTRACE_B2B_LANDLINE_PHONE; SKIPTRACE_B2B_WIRELESS_PHONE | Appended business phone fields. Check the aliases used by the export. |
| SKIPTRACE_B2B_SOURCE | The source of the additional business information. |
| SKIPTRACE_B2B_WEBSITE | Business website, generally its root domain. |
| LINKEDIN_URL | Profile URL associated with the person. |
Phone data and match quality
- Use the skiptrace phone fields for the documented calling workflow.
- Review SKIPTRACE_LANDLINE_NUMBERS, SKIPTRACE_WIRELESS_NUMBERS and DNC with the applicable channel checks.
- For B2B calling, resolve the B2B-specific field names shown in the field guide.
- Evaluate quality on the records selected for your own workflow.
Email verification tiers
Use BUSINESS_EMAIL or PERSONAL_EMAIL with its corresponding validation and last-seen fields. Refresh cadence depends on the ingestion batch; check the timestamp on the record you intend to use.
| Published label | How to interpret it |
|---|---|
| Valid (Catch-all) | A catch-all signal for the domain. Do not assume a specific mailbox has been confirmed. |
| Valid (Digital) | A signal associated with digital/programmatic use; it is not by itself an assurance for direct email sending. |
| Valid (ESP) | An email-service-provider activity signal. This is the tier used in the outbound-email field guidance. |
Tighten the match for the job
SKIPTRACE_MATCH_BY describes which fields supported the match. Requiring agreement across relevant identifiers, such as address and email, is one way to narrow a candidate set. Confirm how the field is encoded in the actual export.
For postal or calling workflows, review the match criteria and permitted channel fields together. A richer record does not mean every attribute should be sent to every destination.