October 2022 Release Notes (v20.0)
| Release Name | Dataset Version | Publish Date |
|---|---|---|
| October 2022 | v20.0 | 10/11/2022 |
v20.0 was released on 10/11/2022.
Welcome to our October 2022 release notes! We’re rolling out some exciting updates with this release.
Here are some of the key highlights:
- Added 4.4 million new companies to our Company Dataset!
- NEW - Check if we have specific data for a person with the Preview Enrichment API!
- NEW - Filter which data updates matter to you with the Person Retrieve API!
- NEW - Find a person’s most likely email using the new recommended personal email field!
Excited yet? Read on to learn more, or jump to a specific section using the table of contents below.
Customizable Update Logic (Person Retrieve API)
We’ve added a new feature to our Person Retrieve API! As of this release, users can filter what types of changes count as an updated record using the filter_updated parameter. The first filter we’re releasing is job_change.
The job_change filter looks at the job_company_id or job_title fields that were changed since the last data refresh.
For example, a Retrieve API user might want to keep the job history of profiles up-to-date. In its current state, the user gets charged whenever PDL adds new data to the record, even if it’s irrelevant to the job history. By setting the filter_updated parameter to job_change, any results that have not had a job change since the user’s most recent data refresh will be omitted from the response and will not result in credit usage.
| Field Name | Field Type | Field Description | Example |
|---|---|---|---|
filter_updated | Enum (String) | Filters which person data field changes count as an updated record. | “job_change” |
We are launching a new data field in our Person Dataset: recommended_personal_email. This field is generated by analyzing the emails in the personal_emails list to identify the best available email for that person.
Through testing, we’ve found that using the email identified in recommended_personal_email versus selecting a random email address from a given list of emails resulted in ~33% higher deliverability.
The recommended_personal_email field is available in its own premium field bundle. If you’d like access, please reach out to us or speak to your Customer Success Manager.
| Field Name | Field Type | Field Description | Example |
|---|---|---|---|
recommended_personal_email | String | The best available email to reach a person from their personal_emails. | “[email protected]” |
This quarter, we are excited to announce the launch of our Preview Enrichment API! This API supports our Person Enrichment API by providing a preview of what fields exist for a record.
The Preview Enrichment API is a wrapper on the Person Enrichment API, meaning it returns all of the same fields as the Person Enrichment API, but with true / false values instead (true meaning we have a value for that field and false meaning we do not have a value for it).
We’ve heard from many of our users in the lead/candidate search platform market that they often “tease” their users with previews of contact information for a person to incentivize them. We’re excited to launch the Preview Enrichment API to help solve this problem.
The Preview Enrichment API is purchasable by enterprise Person Enrichment customers. If you’d like access, please reach out to us or speak to your Customer Success Manager.
This quarter, we updated millions of jobs and locations in our Global Resume Dataset. See below for details:
| Dataset | Geography | Field | Records Updated |
|---|---|---|---|
| Resume | Global | experience | 152,859,024 |
| Resume | Global | location | 140,752,248 |
| Resume | United States | experience | 55,087,011 |
| Resume | United States | location | 60,014,643 |
| Linkage | Coverage in v19 | Coverage in v20 | Increase (%) |
|---|---|---|---|
total_records | 716,378,665 | 723,056,672 | 0.93% |
name_aliases | 19,876,481 | 29,358,048 | 47.70% |
job_onet_minor_group | 158,277,253 | 215,446,535 | 36.12% |
job_onet_major_group | 158,277,253 | 215,446,535 | 36.12% |
job_onet_specific_occupation | 158,277,253 | 215,446,535 | 36.12% |
job_onet_broad_occupation | 158,277,253 | 215,446,535 | 36.12% |
job_onet_code | 158,277,253 | 215,446,535 | 36.12% |
job_onet_specific_occupation_detail | 71,235,983 | 84,891,836 | 19.17% |
| Linkage | Coverage in v19 | Coverage in v20 | Increase (%) |
|---|---|---|---|
email <> street_address | 411,671,368 | 430,785,819 | 4.64% |
| Linkage | Coverage in v19 | Coverage in v20 | Increase (%) |
|---|---|---|---|
id | 18,537,883 | 22,937,026 | 23.73% |
- We added 4.4 million new companies to our Company Dataset.
- We added 4.9 million new experience objects to our Person Dataset from these new companies.
- O*NET field coverage increased by ~36% across all datasets. If you’d like beta access to our O*NET title tagging, please reach out to us or speak to your Customer Success Manager.
email <> street addresslinkages increased by 4.64% in our API dataset