Welcome to our February 2026 release notes

February may be the shortest month of the year, but this release is packed with plenty of exciting updates for you to check out!

Here’s what’s new:

• 🆕 Person Data x Industry V2: Modern industry classifications now in the Person Dataset
• ✉️ Email Quality, Leveled Up: We are continuing to improve our email quality to support better deliverability and more reliable outreach.
• 📁 Job Posting Daily Deliveries: Clearer directory structure organization for Job Posting Daily Delivery customers
• 💪 Big Data Gains: Big improvements in our fill rates for headline and role tagging
• 📊 Freshness Updates: This past month, we verified 49M+ jobs and detected 7M+ job changes across our global dataset

Dive into the full details below, or jump to what interests you using the table of contents below.

---

Table of Contents

📣 Announcements

📐 Schema Changes

• Person Industry V2 Fields

🚀 Data Updates

• Freshness
• Job Changes
• Coverage
• Commentary

🛠 Improvements and Bug Fixes

• Improvements
• Bug Fixes

---

📣 Announcements

📘

Reminder: Ongoing Email Deliverability Improvements

We’re continuing to improve the quality and deliverability of our work_email and recommended_personal_emails fields to ensure more reliable email performance over time.

See the full announcement here: Email Deliverability Improvements

Additional Resources:

• Email Data for Outreach
• Email Deliverability Improvements Guide

📘

Reminder for Daily Job Posting Customers (Beta)

As of February 10, 2026, customers receiving Daily Job Posting Deliveries (Beta) now receive both monthly and daily files in an updated directory structure:

Monthly (Full) Delivery: YYYYMMDD_{current_release_version}/full/

Daily (delta) delivery: YYYYMMDD_{current_release_version}/daily/

For more details, please see the full announcement: Job Posting Daily Deliveries: Directory Structure Update (Feb 2026)

---

📐 Schema Changes

Person Industry V2 Fields (Person)

What’s New?

This month we’re adding two new industry-related fields to the Person Dataset:

We originally released the industry_v2 for our Company Dataset in September 2025 (v31.2), and based on the strong customer demand, we’ve now added it to our Person Dataset as well!

These fields capture the most recently observed industry classification reported by the associated company, and include expanded support for external industry taxonomies. It ensures our dataset reflects modernized industry categories that may differ from the legacy classifications still in use by the legacy industry fields.

📘

Comparison to the legacy industry fields

The legacy industry fields in the person dataset will continue to be available with their functionality preserved:

• job_company_industry
• experience.company.industry

These legacy fields will provide PDL’s original canonical industry taxonomy, while the industry_v2 field will provide classifications from an expanded industry taxonomy.

For most users, we recommend using the new industry_v2 fields. However, if you have existing workflows reliant on the original PDL industry classifications, then you should continue to leverage the legacy industry field.

Why It Matters

These new fields bring a refreshed set of modern industry classification to our Person dataset, making it easier to filter, search, and categorize person records using an up-to-date taxonomy of industry classifications.

Some of the key benefits include:

• No manual mapping required → reduces the need to build and maintain your own taxonomy or conversion logic
• Improved workflow compatibility → better results in targeting, search, and discovery use cases that depend on modern industry categories

For customers using both our Person and Company Datasets, this update now ensures that you can use the same industry values across both datasets.

Availability
These fields are immediately available to all Person Data Customers and will be automatically included in all new data deliveries moving forward.

We’d Love Your Feedback!
Your input helps shape what we build next. Share your thoughts on these fields or suggest new ones via our Roadmap Feature Request Board!

---

🚀 Data Updates

Freshness

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

Monthly (v33.0 → v33.1)
Freshness updates over the past month.

Job Changes

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

Monthly (v33.0 → v33.1)
Freshness updates over the past month.

Coverage (Full Stats: Person, Company, Job Posting, IP)

Monthly (v33.0 → v33.1)

Resume Dataset

API Dataset

Email Dataset

Mobile Phone Dataset

Company Dataset

Job Posting Dataset

Commentary

• Person
  • We saw a 57% increase in our coverage of headlines due to a bug fix we pushed this month (see Bug Fixes)
  • We saw a 5-7% increase in fill rate for our role-related fields in the resume dataset this month as a result of some improvements we made to our role tagging processes (see Improvements)
  • We saw a 14% decrease in our fill rate for work_email as a result of our ongoing Email Validation efforts (see Improvements)
• Job Posting Data
  • This month, we added another 3k unique companies to our Job Posting dataset.

---

🛠 Improvements and Bug Fixes

Improvements

• Role Tagging Improvements
  • We expanded our Class/Role/SubRole taxonomy to include additional job titles (e.g. “Member of Technical Staff”, “Marketing Manager”), improving role tagging coverage.
  • We added enhanced logic to better handle roles associated with multiple industries.
• Updated Canonical Degrees
  • Removed canonical degree values with no representation in the dataset (e.g. master of community planning) to keep classifications clean and relevant.

Bug Fixes

• More Accurate Experience Locations
  • We fixed an issue that caused some experience records to incorrectly display a company’s headquarters in the experience.location_names field.
• headline Character Validation
  • Updated the character length and character-type constraints on the headline field that were incorrectly rejecting valid values and setting them to null.