> ## Documentation Index
> Fetch the complete documentation index at: https://docs.peopledatalabs.com/llms.txt
> Use this file to discover all available pages before exploring further.
# April 2025 Release Notes
| Release Name | Dataset Version | Publish Date |
| :----------- | :-------------- | :----------- |
| April 2025 | `v30.0` | 04/15/2025 |
**Welcome to our April 2025 release notes!**
This month, we’re rolling out some exciting and important updates across our data products.\
Here’s what’s new:
* **🏢 New Company Insights Fields**: We just launched a whole batch of exciting [new Company Insight fields](#new-insights)!
* **❄️ Snowflake Single Listing Migration**: We’ve completed the [migration of Snowflake customers](#snowflake-migration) to a unified, single listing for their data.
* **🥷 Sunset of Skill Enrichment API**: The Skill Enrichment API is now [officially removed](#skill-enrich-deprecation).
* **🆓 Free Job Title Enrichment API Plans**: Free & Pro users now have [access to the Job Title Enrichment API](#ss-job-title-enrichment)
* **🎓 Expanded School Tagging**: Academic institutions are now [better labeled](#improvements) in our Company dataset using the `educational` company type.
* **📊 Freshness Updates**: This past quarter, we [verified 296M+ jobs](#freshness) and [detected 9M+ job changes](#job-changes) across our global dataset
Explore the full details below, or skip ahead to a specific section using the table of contents.
## 📣 Key Announcements
### Schema Changes
#### New Company Insights Fields ([Company Schema](/docs/company-schema))
| Field | Type | Short Description | Bundle |
| :------------------------------------------------------------------------------------------------------------ | :------- | :------------------------------------------------------------------------------------------------------------------------------------------------------- | :------------------------------------------------------------------------------------------------------------------------- |
| [`top_next_employers`](/docs/company-schema#top_next_employers) | `Object` | The top ten companies employees moved to, and how many employees moved there, across all time periods | [Comprehensive](/docs/company-data-field-bundles#comprehensive) |
| [`top_previous_employers`](/docs/company-schema#top_previous_employers) | `Object` | The top ten previous companies employees worked for previously, and how many current employees were previously employed by them, across all time periods | [Comprehensive](/docs/company-data-field-bundles#comprehensive) |
| [`top_next_employers_12_month`](/docs/company-schema#top_next_employers_12_month) | `Object` | The top ten next employers, counting only employee changes within the last 12 months | [Comprehensive](/docs/company-data-field-bundles#comprehensive) |
| [`top_previous_employers_12_month`](/docs/company-schema#top_previous_employers_12_month) | `Object` | The top ten previous employers, counting only employee changes within the last 12 months | [Comprehensive](/docs/company-data-field-bundles#comprehensive) |
| [`employee_count_by_sub_role`](/docs/company-schema#employee_count_by_sub_role) | `Object` | The number of current employees broken down by [Job Title Sub Role](/docs/job-title-subroles). | [Comprehensive](/docs/company-data-field-bundles#comprehensive) |
| [`employee_growth_rate_12_month_by_sub_role`](/docs/company-schema#employee_growth_rate_12_month_by_sub_role) | `Object` | The twelve month rate of change by [Job Title Sub Role](/docs/job-title-subroles) | [Comprehensive](/docs/company-data-field-bundles#comprehensive) |
| [`employee_count_by_class`](/docs/company-schema#employee_count_by_class) | `Object` | The number of current employees broken down by [Job Title Class](/docs/job-title-class) | [Premium](/docs/company-data-field-bundles#premium) [Comprehensive](/docs/company-data-field-bundles#comprehensive) |
| [`employee_growth_rate_12_month_by_class`](/docs/company-schema#employee_growth_rate_12_month_by_class) | `Object` | The twelve month rate of change by [Job Title Class](/docs/job-title-class) | [Premium](/docs/company-data-field-bundles#premium) [Comprehensive](/docs/company-data-field-bundles#comprehensive) |
This month, we’re excited to introduce eight new Company Insight fields as part of the April 2025 (v30.0) release! These enhancements provide deeper visibility into employee movement trends and organizational composition, offering our customers even more actionable insights.
These Company Data fields are currently in beta and are automatically available to customers with [Company Comprehensive](/docs/company-data-field-bundles#comprehensive) and [Company Premium](/docs/company-data-field-bundles#premium) field bundles, as indicated in the table above.
**Key Highlights**
* **Better Classification Support**: Headcount metrics are now broken down using our new Job Title Class and Job Sub Role taxonomies, providing more granularity and flexibility in workforce analysis.
* **Time-Bound Talent Flow Summaries**: New 12-month versions of the Top Previous and Top Next Employers fields allow you to isolate and analyze recent employee movements, giving a sharper view of current hiring and attrition trends.
* **Improved Data Readability**: All Top Employers summaries now include displayable company names, making analysis clearer and the data more presentation-ready.
**Availability**\
These new fields are automatically included for customers with the following Company Data field bundles:
* [Company Comprehensive](/docs/company-data-field-bundles#comprehensive)
* [Company Premium](/docs/company-data-field-bundles#premium)
See the table above for field availability across bundles. If you’re not currently seeing these fields and would like to enable access, please reach out to your Account Team for assistance.
**Deprecation Notice**\
Please note that two of these new fields will fully replace two existing Company Insights fields (now considered legacy) in July 2025 as part of the v31.0 release. Please see the full [deprecation notice](#legacy-insights) below for more information.
**We’d Love Your Feedback!**\
We’re always looking to improve. If you have thoughts on how these fields are working for you - or ideas for what insights you'd like to see next - please don’t hesitate to share your feedback with us. We would love to hear your input and ideas through our [Roadmap Feature Request Board](https://feedback.peopledatalabs.com/)!
***
## ❗Breaking Changes (Going Live This Month)
### ❗ Snowflake Listing Migration
Change expected in: **v30.0 / April 2025**\
Previous Announcements: [v29.0 / Jan. 2025](/changelog/january-2025-release-notes-v290#snowflake-migration), [v29.1 / Feb. 2025](/changelog/february-2025-release-notes-v291#snowflake-migration), [v29.2 / Mar. 2025](/changelog/march-2025-release-notes-v292#snowflake-migration)
Products Impacted: **Snowflake Listings**
| Products Impacted |
| :----------------------------------------------------------------------- |
| [Snowflake Data License Deliveries](/docs/data-delivery-using-snowflake) |
As of the April 2025 (v30.0) release, the migration of all Snowflake customers to a single listing per customer is now complete.
**Why did we make this change?**\
Previously, Snowflake customers receiving multiple data entities (e.g. Person and Company datasets) were assigned separate listings for each entity. Starting in August 2024, new customers began receiving a unified, single listing. With this release, we have completed that same transition for all existing customers.
All customers who previously had multiple listings have now been migrated to a single listing. This change simplifies data delivery and improves consistency and support across all Snowflake-based data products.
**Migration Options and Final Status**\
Prior to this release, customers with multiple listings were given the opportunity to choose how they’d like to consolidate their data:
* **Create a New Listing (default)**: PDL would set up a new, consolidated listing and retire the existing ones.
* **Merge and Deprecate**: Customers could choose to retain one of their existing listings and have the other merged into it.
With the April 2025 release now complete, all customer migrations have been finalized. In cases where no preference was shared, the default New Listing approach was applied to ensure a smooth transition.
### ❗ Sunset of Skill Enrichment API
Change expected in: **v30.0 / April 2025**\
Previous Announcements: [v29.0 / Jan. 2025](/changelog/january-2025-release-notes-v290#skill-enrich-deprecation), [v29.1 / Feb. 2025](/changelog/february-2025-release-notes-v291#skill-enrich-deprecation), [v29.2 / Mar. 2025](/changelog/march-2025-release-notes-v292#skill-enrich-deprecation)
Products Impacted: **Skill Enrichment API**
| Products Impacted |
| :------------------------------------------------- |
| [Skill Enrichment API](/docs/skill-enrichment-api) |
As of the April 2025 (v30.0) release, the Skill Enrichment API has been officially sunset and is no longer available.
**Why this change?**\
The Skill Enrichment API was originally developed to enhance the user experience alongside our Person Search API. However, based on historical usage and customer feedback, we made the decision to shift focus toward our Job Title Enrichment API and sunset the Skill Enrichment API.
If you have any questions about this change, we welcome your input and ideas via our [Roadmap Feature Request Board](https://feedback.peopledatalabs.com/)!
### ⚠️ Upcoming Breaking Changes
**Upcoming Breaking Changes**
**Upcoming breaking changes** may impact your current processes. We are announcing them here to provide ample time for you to adjust your processes accordingly.
#### ⚠️ (*New*) Deprecation of Legacy Employer Insights Fields ([Company](/docs/company-schema))
Change expected in: **v31.0 / July 2025**
Products Impacted: **Company**
As of April 2025 (v30.0), we are deprecating two fields in our [Company Schema](/docs/company-schema), which are now considered legacy. These fields will be fully replaced in July 2025 (v31.0) by the improved Company Insights fields that were released this month ([see above](#new-insights)).
**Why this change?**\
Over the past few months, we’ve made several improvements based on customer feedback requesting more display-ready and flexible insights fields. One of the key improvements is the inclusion of displayable company names, which makes it much easier to build visualizations like Sankey charts or other talent flow views without needing additional API calls. The result is a simpler implementation experience and reduced API credit usage.
To support these updates, we introduced a new set of fields rather than modifying the existing ones in order to provide an overlap period, giving users time to transition smoothly.
**Migration Plan**
* **April 2025 (v30.0)**: New fields are available.
* **April - July 2025 (v30.0 - v31.0)**: Both legacy and new fields are available in the Company Schema to support a smooth transition.
* **July 2025 (v31.0)**: Legacy fields will be removed.
**Action Required**\
If you currently use the `top_next_employers_by_role` or `top_previous_employers_by_role` fields, you’ll need to update your systems to use the new fields listed below before July 2025 (v31.0):
| Deprecated Fields (Removed in v31.0) | Replacement Fields (Released in v30.0) |
| :-------------------------------------------------------------------------------------- | :---------------------------------------------------------------------- |
| [`top_next_employers_by_role`](/docs/company-schema#top_next_employers_by_role) | [`top_next_employers`](/docs/company-schema#top_next_employers) |
| [`top_previous_employers_by_role`](/docs/company-schema#top_previous_employers_by_role) | [`top_previous_employers`](/docs/company-schema#top_previous_employers) |
The new fields capture all the value of the legacy versions - with the added benefit of being easier to use in visual tools and product interfaces.
If you have any questions or need help with the transition, please reach out to your Customer Account Team - we’re here to support you.
***
## ✨ New Products and Features
### Free & Pro plan Job Title Enrichment API Access
We are excited to announce that we have added free access to the [Job Title Enrichment API](/docs/job-title-enrichment-api) for all Free and Pro plans!
You can use the Job Title Enrichment API to enrich a job title and return the **top 5 matching job titles** in our dataset along with the **top 5 relevant skills** related to the job title. This allows you to enhance your Person Search API requests by easily broadening your search criteria without the need for complex fuzzy matching and guessing.
**What do I have access to?**\
If you have a **Pro plan for the Person Search API**, you’ll be allocated **1,000 free credits per month** or **12,000 per year** with your annual plan.
If you have a **Free plan for the Person Search API**, you have access to **10 free credits per month** to help facilitate testing.
**Where can I learn more?**
* Check out our API documentation here: [Job Title Enrichment API](/docs/job-title-enrichment-api)
* Check out our Help Center article here: [Person Search Support API - Job Title Enrichment API](https://support.peopledatalabs.com/hc/en-us/articles/36025065882907-Person-Search-Support-API-Job-Title-Enrichment-API)
* Get in touch with technical support here: [Submit a request](https://support.peopledatalabs.com/hc/en-us/requests/new)
***
## 🚀 Data Updates
### Freshness
*The number of jobs and locations verified in our datasets (based on the`job_last_verified` and `location_last_updated` fields).*
📌 **Quarterly (v29.0 → v30.0)**\
*Freshness updates over the past quarter.*
| Dataset | Geography | Field | Records Updated |
| ------- | ------------- | ------------ | --------------- |
| Resume | Global | `experience` | 296,822,089 |
| Resume | Global | `location` | 436,083,756 |
| Resume | United States | `experience` | 84,572,377 |
| Resume | United States | `location` | 108,684,741 |
📌 **Monthly (v29.2 → v30.0)**\
*Freshness updates over the past month.*
| Dataset | Geography | Field | Records Updated |
| ------- | ------------- | ------------ | --------------- |
| Resume | Global | `experience` | 85,384,126 |
| Resume | Global | `location` | 109,570,460 |
| Resume | United States | `experience` | 31,141,735 |
| Resume | United States | `location` | 35,652,759 |
#### Job Changes
*The number of person records where the primary job experience changed in our Person Dataset (based on the`job_last_changed` field).*
📌 **Quarterly (v29.0 → v30.0)**\
*Freshness updates over the past quarter.*
| Dataset | Geography | Records Updated |
| ------- | ------------- | --------------- |
| Resume | Global | 9,204,577 |
| Resume | United States | 1,764,710 |
📌 **Monthly (v29.2 → v30.0)**\
*Freshness updates over the past month.*
| Dataset | Geography | Records Updated |
| ------- | ------------- | --------------- |
| Resume | Global | 160,907 |
| Resume | United States | 68,881 |
### Coverage (Full Stats: [Person](/docs/datasets), [Company](/docs/company-stats))
#### 📌 Quarterly (v29.0 → v30.0)
**[Resume Dataset](/docs/resume-stats)**
| Linkage | Coverage in v29.0 | Coverage in v30.0 | Increase (%) |
| -------------------------------------------- | ----------------- | ----------------- | ------------ |
| total\_records | 736,325,366 | 756,205,993 | 2.70% |
| `job_title_sub_role` | 91,464,350 | 218,966,414 | 139.40% |
| `headline` | 38,462,189 | 74,745,897 | 94.34% |
| `experience.title.sub_role` | 165,187,811 | 312,906,910 | 89.42% |
| `experience.company.location.street_address` | 172,581,307 | 309,548,414 | 79.36% |
| `job_title_role` | 156,985,217 | 267,779,170 | 70.58% |
| `experience.title.role` | 238,896,469 | 357,062,928 | 49.46% |
| `experience.location_names` | 183,408,859 | 227,614,350 | 24.10% |
| `summary` | 115,792,801 | 142,664,883 | 23.21% |
| `location_locality` | 438,460,583 | 503,593,899 | 14.86% |
| `experience.summary` | 136,829,932 | 154,738,826 | 13.09% |
| `location_address_line_2` | 3,417,978 | 3,678,767 | 7.63% |
| `education.school.linkedin_url` | 242,794,815 | 256,023,067 | 5.45% |
| `skills` | 148,404,392 | 137,431,706 | -7.39% |
[API Dataset](/docs/stats)
| Linkage | Coverage in v29.0 | Coverage in v30.0 | Increase (%) |
| ------------------------- | ----------------- | ----------------- | ------------ |
| total\_records | 2,458,046,594 | 2,438,028,671 | -0.81% |
| `summary` | 135,392,275 | 164,194,016 | 21.27% |
| `location_locality` | 1,283,837,335 | 1,464,066,706 | 14.04% |
| `location_address_line_2` | 68,105,393 | 74,583,404 | 9.51% |
[Email Dataset](/docs/email-stats)
| Linkage | Coverage in v29.0 | Coverage in v30.0 | Increase (%) |
| -------------- | ----------------- | ----------------- | ------------ |
| total\_records | 634,898,506 | 598,695,608 | -5.70% |
| `experience` | 293,137,070 | 255,112,090 | -12.97% |
[Mobile Phone Dataset](/docs/mobile-phone-stats)
| Linkage | Coverage in v29.0 | Coverage in v30.0 | Increase (%) |
| :------------- | :---------------- | :---------------- | :----------- |
| total\_records | 485,553,309 | 484,854,828 | -0.14% |
[Company Dataset](/docs/company-stats)
| Linkage | Coverage in v29.0 | Coverage in v30.0 | Increase (%) |
| :------------------------ | :---------------- | :---------------- | :----------- |
| total\_records | 71,478,660 | 71,480,559 | 0.003% |
| `location.street_address` | 18,962,288 | 46,024,415 | 142.72% |
| `industry` | 45,769,144 | 53,934,583 | 17.84% |
| `location.locality` | 50,338,832 | 57,775,410 | 14.77% |
| `founded` | 13,602,870 | 15,108,123 | 11.07% |
| `location.region` | 55,680,104 | 59,910,659 | 7.60% |
| `ticker` | 27,674 | 26,226 | -5.23% |
| `affiliated_profiles` | 281,740 | 195,851 | -30.49% |
#### 📌 Monthly (v29.2 → v30.0)
**[Resume Dataset](/docs/resume-stats)**
| Linkage | Coverage in v29.2 | Coverage in v30.0 | Increase (%) |
| :----------------------------------- | :---------------- | :---------------- | :----------- |
| total\_records | 751,349,471 | 756,205,993 | 0.65% |
| `education.school.location.locality` | 196,060,230 | 242,981,350 | 23.93% |
| `job_title_sub_role` | 206,788,089 | 218,966,414 | 5.89% |
| `location_address_line_2` | 3,484,436 | 3,678,767 | 5.58% |
| `job_title_role` | 254,637,685 | 267,779,170 | 5.16% |
[API Dataset](/docs/stats)
| Linkage | Coverage in v29.2 | Coverage in v30.0 | Increase (%) |
| :------------------ | :---------------- | :---------------- | :----------- |
| total\_records | 2,473,230,064 | 2,438,028,671 | -1.42% |
| `skills` | 163,076,220 | 145,686,456 | -10.66% |
| `location_locality` | 1,337,713,215 | 1,464,066,706 | 9.45% |
| `emails` | 685,747,622 | 649,474,773 | -5.29% |
[Email Dataset](/docs/email-stats)
| Linkage | Coverage in v29.2 | Coverage in v30.0 | Increase (%) |
| :------------- | :---------------- | :---------------- | :----------- |
| total\_records | 634,528,966 | 598,695,608 | -5.65% |
| experience | 293,765,269 | 255,112,090 | -13.16% |
[Mobile Phone Dataset](/docs/mobile-phone-stats)
| Linkage | Coverage in v29.2 | Coverage in v30.0 | Increase (%) |
| :------------- | :---------------- | :---------------- | :----------- |
| total\_records | 486,065,010 | 484,854,828 | -0.25% |
[Company Dataset](/docs/company-stats)
| Linkage | Coverage in v29.2 | Coverage in v30.0 | Increase (%) |
| :------------- | :---------------- | :---------------- | :----------- |
| total\_records | 71,481,597 | 71,480,559 | 0.00% |
| `ticker` | 27,811 | 26,226 | -5.70% |
### Commentary
📌 ***Quarterly Highlights (v29.0 → v30.0)***
* **Major improvements in job title and role fields** within the Resume dataset due to the GA launch of our improved Job Role Taxonomy in February 2025 (v29.1):
* `job_title_sub_role` (+139%)
* `experience.title.sub_role` (+89%)
* `job_title_role` (+71%)
* **`headline`coverage nearly doubled (+94%)** in the Resume dataset due to ongoing backfill efforts
* **Significant enhancements in location data** across datasets due to improved cleaning logic (see [Improvements](#improvements) below):
* `experience.company.location.street_address` (+79%) in Resume
* `location_locality` (+15%) in Resume
* `location.street_address` in Company dataset (+143%)
* **Decline in`skills` coverage (-7%)** in the Resume dataset following improvements to our skill cleaning process (see [Improvements](#improvements) below)
* **`affiliated_profiles`coverage in Company dataset fell 30%** , consistent with ongoing sourcing updates; this is a low fill-rate field currently under review for future improvements.
📌 ***Monthly Highlights (v29.2 → v30.0)***
* **Job title taxonomy fields continued to grow**:
* `job_title_sub_role` (+5.9%)
* `job_title_role` (+5.2%)
* **API dataset saw a small dip in total\_records (-1.4%)**, along with:
* Drop in `skills` (-10.7%) due to ongoing cleanup
* Drop in `emails` (-5.3%) from record quality filtering
* **Location fields continued improving**, with `location_locality` up 9.5%
* **The Company dataset saw a slight dip in`ticker` coverage (-5.7%)** over the past month.
***
## 🛠 Improvements and Bug Fixes
### Improvements
* **Skill Cleaner Improvements**
* We made significant improvements to our skills cleaning that resulted in a **decrease in skills fill rates**, but **higher quality values** in the `skills` array.
* **Location Selection Improvements**
* We made some significant improvements to how we select the primary `location_` object:
* Previously: location objects were selected based on the objects with most detailed location and the most recent timestamp
* Now: location objects are chosen based on the most recent locality / metro with the most recent and granular associated locality
* **Location Cleaning Improvements**
* [Last month](/changelog/march-2025-release-notes-v292#improvements), we released some major improvements to our location cleaner to improve the consistency and quality of our locality and region data
* This update led to significant coverage improvements across our Person, Company and School datasets as seen in the [Coverage](#commentary) section above
* **Metro Values Added to Autocomplete API**
* For US locations in the Autocomplete API, we now include the metro value in the autocomplete response object
* **Improved School Tagging**
* We expanded our logic for classifying academic institutions (i.e. companies with the the type [type](/docs/company-types) `educational`) to now include any companies with a `.edu` primary website.
* **Unique Company Websites**
* We now enforce that the `website` field for each company record is unique across our Company dataset, allowing customers to use this field as a primary identifier when ingesting or using our Company records.
* **Company Website Cleaner Improvements**
* We improved our company domain cleaner to exclude certain invalid websites (such as those containing email-like “@” characters) based on customer feedback
* **Title Tagging Improvements**
* We are continuing to make improvements to our Job Title Taxonomy tagging which led to significant increases in titles tagged across our Person Dataset
### Bug Fixes
* We updated our name cleaner to exclude additional certifications from a person’s name fields
* We fixed a bug that allowed the `tags` array in Company records to contain empty (“ “) entries
* We updated our logic for enforcing known parent/subsidiary company relationships to ensure the correct parent/subsidiary relationship was maintained throughout the Company Data build process.
* We fixed an issue causing null values for the Job Title Class field for executives in certain fields in our Company records.
## Related topics
- [Skill Enrichment API](/docs/skill-enrichment-api.md)
- [Quickstart - Skill Enrichment API](/docs/quickstart-skill-enrichment-api.md)
- [Input Parameters - Skill Enrichment API](/docs/input-parameters-skill-enrichment-api.md)
- [Output Response - Skill Enrichment API](/docs/output-response-skill-enrichment-api.md)
- [Reference - Skill Enrichment API](/docs/reference-skill-enrichment-api.md)