Ledger v1 Data Fields
This page applies to Ledger v1. For the latest fields for v2 Ledgers, see the parent page
When viewing data in your ledger, either via the UI, CSV, or API, many fields of information are provided by Live Data. The table below explains each of the fields:
| UI Field Category | UI Field Name | API Field Name | Description |
|---|---|---|---|
| N/A | <not shown> | id | The unique contact ID for this contact |
| None | Verified? | isVerified | Indicates whether Live Data has been able to verify/identify this contact on the open web |
| Last Changed (UTC) | Job | lastJobChangedAt | The last time (in UTC) Live Data updated this persons job on this ledger. A blank value indicates there has been no change from the imported data. |
| Last Changed (UTC) | Other Info | lastInfoChangedAt | The last time (in UTC) Live Data updated any of this persons information on this ledger. A blank value indicates there has been no change from the imported data. |
| Person Info | Reference ID | referenceId | The customer-provided reference ID for this contact |
| Person Info | Name | name | The customer-provided name for this contact |
| Person Info | The LinkedIn URL for this contact | ||
| Person Info | Multiple Jobs? | hasMultipleJobs | Indicates whether we've detected this person has multiple current jobs. See below for more details |
| Current Job | Company | company | The current company that employs this contact |
| Current Job | Title | title | The current job title of this contact |
| Current Job | Title Level | titleLevel | The inferred level of the current job, based on their title. See below for more details |
| Current Job | Title Domain | titleDomain | The inferred domain of the current job, based on their title. See below for more details |
| Current Job | Start Date | jobStartedAt | The date that this person started at their current job |
| Contact Info | contactInfo.email | The current email address of this contact, if known | |
| Contact Info | Email Status | contactInfo.emailStatus | The status of the email address. 'valid' denotes a valid email, 'catch-all' denotes a mail server that does not validate emails, and 'best-guess' denotes a likely email address that could not be positively confirmed. |
| Company Info | companyInfo.linkedin | The LinkedIn URL for this company | |
| Company Info | Domain | companyInfo.domain | The top-level domain name for the current company. |
| Company Info | Size | companyInfo.size | The size of the current company. |
| Company Info | Industry | companyInfo.industry | The industry of the current company. |
| Company Info | Location | companyInfo.location | The geographic location of the company headquarters. |
| Imported Data | importLinkedIn | The LinkedIn URL that this contact was imported with | |
| Imported Data | Company | importCompany | The name of the company that this contact was imported with |
| Imported Data | Title | importTitle | The job title this contact was imported with |
| Imported Data | Title Level | importTitleLevel | The inferred level of the title this contact was imported with. See below for more details |
| Imported Data | Title Domain | importTitleDomain | The inferred domain of the title this contact was imported with. See below for more details |
| N/A | <not shown> | createdAt | Date at which this contact was added to this ledger |
| N/A | <not shown> | ledgerImportId | The ID of the batch import this contact was imported from |
Multiple Jobs Flag
The multiple jobs flag is intended to provide a "heads-up" that the person has multiple jobs, but is not set to true under all conditions. Essentially, we are not able to ask the Internet "does Suzy have multiple jobs" and get a good answer. But, under certain circumstances, it may be possible for us to detect that someone does have multiple jobs and that is when the flag gets set. This usually occurs when we have multiple customers asking us about the same person at each of their jobs -- in those cases, we can ask the Internet "is Suzy at A" and "is Suzy at B" and if we get positive results for both then we set the flag to true.
Job Level Values
The potential values for the level fields in the payload are:
- C-Team
- VP
- Director
- Manager
- Senior Staff
- Staff
- Consultant
Job Domain Values
The potential values for the domain fields in the payload are:
- Banking and Wealth Management
- Business Management
- Consulting
- Education
- Engineering
- Finance and Administration
- Healthcare
- Human Resources
- Information Technology
- Legal
- Marketing and Product
- Operations
- Program and Project Management
- Publishing, Editorial and Reporting
- Quality
- Real Estate
- Risk, Safety, Compliance
- Sales and Support
Updated 3 months ago