> ## 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.

# February 2026 Release Notes

| Release Name  | Dataset Version | Publish Date |
| :------------ | :-------------- | :----------- |
| February 2026 | `v33.1`         | 02/17/2026   |

**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:

* **📊 Freshness Updates**: This past month, we [verified 49M+ jobs](#freshness) and [detected 7M+ job changes](#job-changes) across our global dataset
* **<Icon icon="dumbbell" /> [Big Data Gains](#-improvements-and-bug-fixes)**: Big improvements in our fill rates for `headline` and role tagging
* **<Icon icon="folder" /> [Job Posting Daily Deliveries](#announcements)**: Clearer directory structure organization for Job Posting Daily Delivery customers
* **<Icon icon="mail" /> [Email Quality, Leveled Up](#announcements)**: We are continuing to improve our email validation to support better deliverability and more reliable outreach.
* **<Icon icon="plus" /> [Person Data x Industry V2](#person-industry-v2-fields-person)**: Modern industry classifications now in the Person Dataset

## Announcements

<Note>
  **Reminder: Ongoing Email Validation 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](/changelog/november-2025-release-notes-v321#/email-deliverability-improvements-person)

  Additional Resources:

  * [Email Deliverability Improvements Guide](https://www.peopledatalabs.com/pdf/email-deliverability-improvements-guide.pdf)
  * [Email Data for Outreach](/docs/email-data-for-outreach)
</Note>

<Note>
  **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)](#job-posting-daily-deliveries-directory-structure-update-feb-2026)
</Note>

## Schema Changes

### Person Industry V2 Fields ([Person](/docs/person-data-overview))

**What's New?**

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

| FIELD NAME                                                         | FIELD TYPE                             | FIELD BUNDLE | FIELD DESCRIPTION                                                                                                                                                                                                      |
| :----------------------------------------------------------------- | :------------------------------------- | :----------- | :--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| [`job_company_industry_v2`](/docs/fields#job_company_industry_v2)  | [`Enum (String)`](/docs/industries-v2) | Person Base  | The v2 industry for the person's current company. Industry v2 is the self-reported industry from an expanded list of [Canonical v2 Industries](/docs/industries-v2). If no industry is found, the field will be `null` |
| [`experience.company.industry_v2`](/docs/fields#experiencecompany) | [`Enum (String)`](/docs/industries-v2) | Person Base  | The v2 industry for the person's company. Industry v2 is the self-reported industry from an expanded list of [Canonical v2 Industries](/docs/industries-v2). If no industry is found, the field will be `null`         |

We originally released the [`industry_v2`](/docs/company-schema#industry_v2) for our Company Dataset in [September 2025 (v31.2)](/changelog/september-2025-release-notes-v312#new-company-industry-field-company-), 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:

* `experience.company.industry`
* `job_company_industry`

These legacy fields will provide PDL's [original canonical industry taxonomy](/docs/industries), while the `industry_v2` field will provide classifications from an [expanded industry taxonomy](/docs/industries-v2).

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:

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

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](https://feedback.peopledatalabs.com/)!

## 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.*

| Dataset | Geography     | Field        | Records Updated |
| :------ | :------------ | :----------- | :-------------- |
| Resume  | Global        | `experience` | 49,965,247      |
| Resume  | Global        | `location`   | 75,221,768      |
| Resume  | United States | `experience` | 24,657,830      |
| Resume  | United States | `location`   | 30,173,859      |

### 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.*

| Dataset | Geography     | Records Updated |
| :------ | :------------ | :-------------- |
| Resume  | Global        | 7,880,536       |
| Resume  | United States | 2,877,546       |

### Coverage (Full Stats: [Person](/docs/datasets), [Company](/docs/company-stats), Job Posting, [IP](/docs/ip-stats))

**Monthly (v33.0 → v33.1)**

**[Resume Dataset](/docs/resume-stats)**

| Linkage                     | Coverage in v33.0 | Coverage in v33.1 | Increase (%) |
| :-------------------------- | :---------------- | :---------------- | :----------- |
| Total Records               | 784,969,022       | 798,953,930       | 1.78%        |
| `headline`                  | 118,319,457       | 186,300,358       | 57.46%       |
| `work_email`                | 75,144,765        | 64,587,835        | -14.05%      |
| `experience.title.role`     | 371,439,134       | 398,397,592       | 7.26%        |
| `experience.title.class`    | 371,439,134       | 398,397,592       | 7.26%        |
| `job_title_class`           | 276,907,792       | 295,046,030       | 6.55%        |
| `job_title_role`            | 276,907,792       | 295,046,030       | 6.55%        |
| `experience.title.sub_role` | 325,919,031       | 343,396,186       | 5.36%        |

**[API Dataset](/docs/stats)**

| Linkage       | Coverage in v33.0 | Coverage in v33.1 | Increase (%) |
| :------------ | :---------------- | :---------------- | :----------- |
| Total Records | 2,438,436,297     | 2,453,435,765     | 0.62%        |

**[Email Dataset](/docs/email-stats)**

| Linkage       | Coverage in v33.0 | Coverage in v33.1 | Increase (%) |
| :------------ | :---------------- | :---------------- | :----------- |
| Total Records | 586,865,405       | 587,237,067       | 0.06%        |

**[Mobile Phone Dataset](/docs/mobile-phone-stats)**

| Linkage       | Coverage in v33.0 | Coverage in v33.1 | Increase (%) |
| :------------ | :---------------- | :---------------- | :----------- |
| Total Records | 479,691,773       | 479,855,809       | 0.03%        |

**[Company Dataset](/docs/company-stats)**

| Linkage       | Coverage in v33.0 | Coverage in v33.1 | Increase (%) |
| :------------ | :---------------- | :---------------- | :----------- |
| Total Records | 74,672,539        | 74,679,887        | 0.010%       |

**[Job Posting Dataset](/docs/jp-stats)**

| Linkage                | Coverage in v33.0 | Coverage in v33.1 | Increase (%) |
| :--------------------- | :---------------- | :---------------- | :----------- |
| Total Records          | 22,291,965        | 24,056,411        | 7.92%        |
| Total Unique Companies | 45,421            | 48,059            | 5.81%        |
| Total Active Postings  | 2,410,753         | 2,792,394         | 15.83%       |

### Commentary

* **Person**
  * We saw a 14% decrease in our fill rate for `work_email` as a result of our ongoing Email Validation efforts (see [Improvements](#improvements))
  * 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](#improvements))
  * We saw a 57% increase in our coverage of headlines due to a bug fix we pushed this month (see [Bug Fixes](#bug-fixes))
* **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](/docs/title-subroles-to-roles) 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

* **`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`.
* **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.

## Job Posting Daily Deliveries: Directory Structure Update (Feb 2026)

**Effective date: February 10, 2026**

We will be updating the directory structure for Job Posting Daily Deliveries to make it easier to distinguish between daily (delta) deliveries and monthly (full) deliveries.

<Note>
  **Reminder:**

  As a Job Posting Daily customer you will receive Monthly full deliveries after each monthly build, and Daily delta deliveries on the other days.
</Note>

## What changed

Each release directory will now include a subdirectory that explicitly indicates the delivery type:

**Monthly (full) delivery:**

`YYYYMMDD_{current_release_version}/full/`

**Daily (delta) delivery:**

`YYYYMMDD_{current_release_version}/daily/`

Previously, both monthly and daily deliveries were written directly to the release directory without a clear indication of which type of delivery they were.

## Impact

This change affects customers ingesting **Job Posting Daily Deliveries**.

Ingestion logic should be updated to check for the presence of a `full/` or `daily/` subdirectory and process the data accordingly.

There are no changes to file contents or schemas.

## Why we made this change

This update reduces ambiguity between daily and monthly deliveries and makes it easier to programmatically handle each delivery type.

<Note>
  **Note:**

  Job Posting Daily Deliveries is currently in **beta**, and some iteration is expected as we incorporate customer feedback.
</Note>

## Related Pages

For additional information on Daily Deliveries for Job Posting Data, see these pages:

<Columns cols={2}>
  <Card title="Daily Deliveries (Job Posting Data)" icon="arrow-right" horizontal href="/docs/daily-deliveries-job-posting-data" />

  <Card title="Data Delivery Using Direct Download" icon="arrow-right" horizontal href="/docs/data-delivery-using-direct-download" />
</Columns>


## Related topics

- [February 2025 Release Notes](/changelog/february-2025-release-notes-v291.md)
- [January 2026 Release Notes](/changelog/january-2026-release-notes-v330.md)
- [June 2026 Release Notes](/changelog/june-2026-release-notes-v342.md)
- [April 2026 Release Notes](/changelog/april-2026-release-notes-v340.md)
- [May 2026 Release Notes](/changelog/may-2026-release-notes-v341.md)
