February 2025 Release Notes

Welcome to our February 2025 release notes! This month, we’re bringing you some exciting updates that make our data fresher, cleaner, and more actionable than ever. Here’s what’s new:

• 👋 Goodbye, Legacy Taxonomy! The final removal of the Legacy “Role” / “Sub Role” Taxonomy is now here.
• 🧑‍💼 Improved Person Records. Headline coverage increased 61% alongside improvements to our summary field quality.
• :earth_americas: Global Data Refresh. We verified 47M+ jobs and detected 3.6M job changes across our global dataset this month.

Dive into the details below, or jump to a specific section using the table of contents.

​

📣 Key Announcements

​

Schema Changes

​

New field job_title_class (Person Schema)

This month, the job_title_class and experience.title.class fields are now officially included in all person records as a result of the sunsetting of our legacy taxonomy for role and sub roles. These fields were first made available in v27.1 via an opt-in parameter.

---

​

❗Breaking Changes (Going Live This Month)

​

❗ Final Sunset of Legacy Role and Sub Role Job Title Taxonomy

Change expected in: v29.1 / February 2025 Previous Announcements: v26 / Apr. 2024, v27.0 / Jul. 2024, v27.1 / Aug. 2024, v27.2 / Sep. 2024, v28.0 / Oct. 2024, v28.1 / Nov. 2024, v28.2 / Dec. 2024, v29.0 / Jan. 2025 Products Impacted: Person / Company / IP Schema

PersonFields Impacted	CompanyFields Impacted	IPFields Impacted
job_title_role job_title_sub_role experience.title.role experience.title.sub_role	average_tenure_by_role employee_count_by_month_by_role employee_count_by_role recent_exec_departures recent_exec_hires top_next_employers_by_role top_previous_employers_by_role	person.job_title_role person.job_title_sub_role

As of this month’s release, we have fully ended support for our legacy Role and Sub Role Taxonomy. All PDL datasets for all customers have now been transitioned to the new taxonomy. What This Means for You With the final transition to the new taxonomy now in effect, customers will no longer receive datasets using the legacy role and sub role taxonomy. All data will now be delivered using the updated class, roles and subroles values. For Customers Who Have Already Transitioned If you’re a Data License using the new taxonomy, no further action is needed. You will continue to receive your data as normal. If you’re an API customer, the updated_title_roles parameter is no longer needed in your API requests. For Customers Who Have Not Yet Transitioned If you haven’t yet transitioned, this release marks the end of the legacy taxonomy. Data from this month’s build onwards will now contain fields using the new taxonomy, so you will need to migrate your systems to support the new taxonomy.

Resources

If needed, please use the following resources to migrate to the new taxonomy. As always, reach out to your Customer Success and Technical Services teams for questions and support. Documentation for the current Class, Role and Sub Role values can be found here:

• Job Title Class
• Job Title Roles
• Job Title Subroles
• Mapping Job Title Class to Roles to Subroles

​

⚠️ Upcoming Breaking Changes

​

⚠️ Snowflake Listing Migration

Change expected in: v30.0 / April 2025 Previous Announcements: v29.0 / Jan. 2025 Products Impacted: Snowflake Listings In April 2025, we will be migrating all Snowflake customers with multiple listings to a single listing per customer. Why this change?
Historically, Snowflake customers receiving multiple data entities (i.e. both Person and Company datasets) were assigned separate listings in Snowflake for each entity. As of August 2024, we transitioned all new customers to a single-listing approach that improved our ability to support and deliver customer data. By April 2025, we will be migrating our remaining Snowflake customers to a single listing. Options for Migration
For customers with multiple listings, there are 2 options for migrating to a single listing:

1. New Listing (recommended, default): PDL creates a new listing for the customer, and moves all data from the pre-existing listings into the new listing. All pre-existing listings will be removed. Note that this is the recommended approach as it allows more time for customers to transition and ensures acceptance of the new format and listing. This is also the default option that will be applied unless customers request otherwise.
2. Merge and Deprecate: Customers can choose to keep one of their existing listings (e.g. Person) and the data from the other listing (e.g. Company) will be moved over to the first listing. Once the data has been moved over, PDL will remove the second listing.

As mentioned above, we strongly recommend the New Listing approach (option 1) for customers as it ensures proper configuration and consistency across the transition. If no action is taken, customers will automatically be migrated using the New Listing approach. To begin your migration process or specify your desired migration approach, please connect with your Technical Services and Customer Account team.

​

⚠️ (New) Deprecation of Skill Enrichment API

Change expected in: v30.0 / April 2025 Previous Announcements: v29.0 / Jan. 2025 Products Impacted: Skill Enrichment API In April 2025, we will be deprecating the and removing the Skill Enrichment API. Why this change?
The Job Title and Skill Enrichment APIs were designed to help improve the user experience when working with our Person Search API. However, based on historical usage patterns we’ve decided to reprioritize our efforts on these APIs. Specifically, we will be sunsetting the Skill Enrichment API, which has had limited usage, in favor of improving our Job Title Enrichment API (details of this will be announced in a future release). For any questions, please contact your Customer Account Team. If you have feedback or product suggestions, please share them in our Roadmap Feature Request Board!

---

​

🚀 Data Updates

​

Freshness

The number of jobs and locations verified in our datasets over the pastmonth (based on the job_last_verified and location_last_updated fields).

​

Job Changes

The number of person records where the primary job experience changed in our Person Dataset over the pastmonth (based on the job_last_changed field).

​

Coverage (Full Stats: Person, Company)

Resume Dataset API Dataset Email Dataset Mobile Phone Dataset Company Dataset

​

Commentary

• We saw significant improvements in our fill rates for roles (~42%) and sub roles (~79%) in our resume dataset as a result of the release of the new Role and Sub Role taxonomy.
• We saw a 61% increase in our coverage of headline as we continue to backfill headlines for person profiles.
• We saw a roughly 20% increase in fill rates for summaries in our resume dataset as a result of some improvements to our cleaning logic (see below)

---

​

🛠 Improvements and Bug Fixes

​

Improvements

• Person
  • Our new Role / Sub Role Taxonomy has now been released, providing increased fill rates and greater granularity of job title roles across our Person, Company and IP datasets.
  • We improved our summary cleaning logic to be more tolerant of non-English characters (such as diacritics) in summaries. We saw an increase in our summary fill rates this month, which will continue to increase in future builds as we re-crawl and re-ingest data.
  • We made improvements to our entity resolution logic to better handle profiles where individuals had changed their maiden / former last name into their middle name, resulting in us being able to merge an additional 1M records during this month’s build.
• Company
  • We have removed the unemployed role tag from our Company Insights headcount calculations as part of the release of our Role / Sub Role Taxonomy
  • We updated our model for estimating inferred_revenue values for our Company records to leverage the role tagging improvements from the new Role / Sub Role Taxonomy.

​

Bug Fixes

• We fixed a bug in our Person build that was causing us to incorrectly drop work experiences from the experience array.
• We fixed a bug in our new Role / Sub Role taxonomy that was non-deterministically selecting a role / sub_role classification when multiple classifications were applicable. We are now taking a conservative approach by not providing a tag when multiple tags can apply.
• We fixed a bug in our name parser that was incorrectly including the Certified Global Sanctions Specialist certification in the name fields for a subset of person records.