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

# October 2026 Release Notes

| Release Name | Dataset Version | Publish Date |
| :- | :- | :- |
| October 2026 | v36.0 | 10/20/2026 |

**Welcome to our October 2026 release notes! 🎃**

No tricks, just treats! We've got a batch of scary good updates this month, including improved executive movement tracking, fresher and more accurate revenue estimates, and a range of data quality and coverage improvements across our datasets.

Check it out:

* 👥 **[Executive Movement Data](#executive-movement-data-improvements)**: Track internal executive role changes, with improved accuracy for executive hires and departures.
* 💰 **[Inferred Revenue Improvements](#inferred-revenue-improvements)**: Fresher, more reliable company revenue estimates, plus a new numeric revenue field for more granular analysis.
* 🔧 [**Data Quality & Coverage Improvements**](#improvements-and-bug-fixes): Improved company address accuracy and employee location data, plus expanded Technology Data coverage for nearly 6.9 million companies.
* **📊 [Freshness Updates](#freshness)**: This past month, we refreshed [53M+ resume experiences](#freshness) and [detected 6.1M+ job changes](#job-changes) across our global dataset.

***

## 📣 Announcements

> [!WARNING]
>
> **Upcoming Field Deprecations (Feb 2027)**
>
> We're deprecating two legacy **Company Data** fields in favor of newer fields that provide more detailed company relationship information.
>
> These fields will be removed on **February 16, 2027 (v37.1).**
>
> [Deprecation Notice: Company Fields (Sunset: Feb 2027)](#deprecation-notice-company-fields-sunset-feb-2027)

**Using PDL Data in Clay**

**Did you know you can use PDL data directly in Clay?**

Use Clay's built-in PDL connection to get started right away, or connect your own PDL API key to bring your PDL credits and custom field bundles into your Clay workflows.

We were also excited to receive the OG Data Partner Award at Clay's Sculpt Conference this month! 🎉

[Explore the PDL + Clay integration guide](/docs/clay-integration)

***

## ✨ Release Updates

### Executive Movement Data Improvements

Company Data

GA

✨ Product Update

📐 Schema Change

**What's New?**

We've expanded and improved our data on [Recent Executive Changes](/docs/company-schema#recent-executive-changes) to provide a more accurate and complete view of leadership movements across companies, including internal role changes, new hires, and departures.

This release includes three major improvements:

1. **New *Internal* Executive Changes data:** Track executives who have moved into new roles within the same company over the past three months, including their previous and new job titles.
2. **More accurate executive hires and departures:** Improved logic distinguishes internal role changes from external hires and more accurately identifies previous and next work experiences.
3. **Additional executive and company information:** New fields for executive names, LinkedIn profiles, and previous or next company names make it easier to identify executives and track their career movements.

> [!NOTE]
>
> **Changes to Existing Executive Hire Data**
>
> Internal role changes are no longer included in [`recent_exec_hires`](/docs/company-schema#recent_exec_hires) and are now tracked separately in `recent_exec_internal_changes`. As a result, existing customers may notice changes to executive hire counts or records following this release.
>
> Executives who leave a company and later rejoin will continue to be counted as recent hires.

**New Recent Executive Fields**

We've added 21 new fields to the [Company Schema](/docs/company-schema), available as part of the [Company Comprehensive](/docs/company-data-field-bundles#comprehensive) bundle:

* 13 fields representing internal executive role changes: `recent_exec_internal_changes` and 12 of its subfields.
* 2 fields providing names of the previous or next companies.
* 6 fields providing executive names and LinkedIn URLs.

Expand the table below to explore the new fields.

> **New Recent Executive Fields (21)**
>
> ***
>
> **New Executive Hires Fields (3)**
>
> | FIELD NAME | FIELD TYPE | FIELD BUNDLE | FIELD DESCRIPTION |
> | :- | :- | :- | :- |
> | [`recent_exec_hires.name`](/docs/company-schema#recent_exec_hires) | `String` | Company Comprehensive | Full name of the executive hired. |
> | [`recent_exec_hires.linkedin_url`](/docs/company-schema#recent_exec_hires) | `String` | Company Comprehensive | LinkedIn profile URL of the executive hired. |
> | [`recent_exec_hires.previous_company_display_name`](/docs/company-schema#recent_exec_hires) | `String` | Company Comprehensive | Display name of the company the executive previously worked for. |
>
> ***
>
> **New Executive Departures Fields (3)**
>
> | FIELD NAME | FIELD TYPE | FIELD BUNDLE | FIELD DESCRIPTION |
> | :- | :- | :- | :- |
> | [`recent_exec_departures.name`](/docs/company-schema#recent_exec_departures) | `String` | Company Comprehensive | Full name of the departing executive. |
> | [`recent_exec_departures.linkedin_url`](/docs/company-schema#recent_exec_departures) | `String` | Company Comprehensive | LinkedIn profile URL of the departing executive. |
> | [`recent_exec_departures.new_company_display_name`](/docs/company-schema#recent_exec_departures) | `String` | Company Comprehensive | Display name of the company the departing executive joined. |
>
> ***
>
> **New Executive Internal Changes Fields (15)**
>
> | FIELD NAME | FIELD TYPE | FIELD BUNDLE | FIELD DESCRIPTION |
> | :- | :- | :- | :- |
> | [`recent_exec_internal_changes`](/docs/company-schema#recent_exec_internal_changes) | `Array (Object)` | Company Comprehensive | Executives who started a new role within the same company in the past three months. |
> | [`recent_exec_internal_changes.new_role_date`](/docs/company-schema#recent_exec_internal_changes) | `String` | Company Comprehensive | Month the executive started their new role at the company. |
> | [`recent_exec_internal_changes.pdl_id`](/docs/company-schema#recent_exec_internal_changes) | `String` | Company Comprehensive | PDL Person ID of the executive. |
> | [`recent_exec_internal_changes.name`](/docs/company-schema#recent_exec_internal_changes) | `String` | Company Comprehensive | Full name of the executive. |
> | [`recent_exec_internal_changes.linkedin_url`](/docs/company-schema#recent_exec_internal_changes) | `String` | Company Comprehensive | LinkedIn profile URL of the executive. |
> | [`recent_exec_internal_changes.job_title`](/docs/company-schema#recent_exec_internal_changes) | `String` | Company Comprehensive | Executive's new job title at the company. |
> | [`recent_exec_internal_changes.job_title_role`](/docs/company-schema#recent_exec_internal_changes) | `String` | Company Comprehensive | Canonical job role of the executive's new position. |
> | [`recent_exec_internal_changes.job_title_sub_role`](/docs/company-schema#recent_exec_internal_changes) | `String` | Company Comprehensive | Canonical job subrole of the executive's new position. |
> | [`recent_exec_internal_changes.job_title_class`](/docs/company-schema#recent_exec_internal_changes) | `String` | Company Comprehensive | Canonical job class of the executive's new position. |
> | [`recent_exec_internal_changes.job_title_levels`](/docs/company-schema#recent_exec_internal_changes) | `Array (String)` | Company Comprehensive | Canonical seniority levels of the executive's new position. |
> | [`recent_exec_internal_changes.previous_job_title`](/docs/company-schema#recent_exec_internal_changes) | `String` | Company Comprehensive | Executive's previous job title at the company. |
> | [`recent_exec_internal_changes.previous_job_title_role`](/docs/company-schema#recent_exec_internal_changes) | `String` | Company Comprehensive | Canonical job role of the executive's previous position. |
> | [`recent_exec_internal_changes.previous_job_title_sub_role`](/docs/company-schema#recent_exec_internal_changes) | `String` | Company Comprehensive | Canonical job subrole of the executive's previous position. |
> | [`recent_exec_internal_changes.previous_job_title_class`](/docs/company-schema#recent_exec_internal_changes) | `String` | Company Comprehensive | Canonical job class of the executive's previous position. |
> | [`recent_exec_internal_changes.previous_job_title_levels`](/docs/company-schema#recent_exec_internal_changes) | `Array (String)` | Company Comprehensive | Canonical seniority levels of the executive's previous position. |

**Example**

```json theme={null}
{
  "recent_exec_internal_changes": [
    {
      "new_role_date": "2026-08",
      "pdl_id": "pWTQUtRFqdpPZgwSFYwTZI_0000",
      "name": "gail cohen",
      "linkedin_url": "linkedin.com/in/gc87",
      "job_title": "senior vice president gtm strategy, growth and operations",
      "job_title_role": "marketing",
      "job_title_sub_role": "growth",
      "job_title_class": "sales_and_marketing",
      "job_title_levels": [
        "senior",
        "vp"
      ],
      "previous_job_title": "vice president, brand marketing",
      "previous_job_title_role": "marketing",
      "previous_job_title_sub_role": "brand",
      "previous_job_title_class": "sales_and_marketing",
      "previous_job_title_levels": [
        "vp"
      ]
    }
  ],
  "recent_exec_hires": [
    {
      "name": "becky lane",
      "linkedin_url": "linkedin.com/in/bl73",
      "previous_company_display_name": "Berry and Sons"
    }
  ],
  "recent_exec_departures": [
    {
      "name": "cindy dean",
      "linkedin_url": "linkedin.com/in/cd79",
      "new_company_display_name": "Scott, Howard and Vaughn"
    }
  ]
}
```

**Why It Matters**

These improvements provide a more complete picture of executive movements, helping you identify leadership changes and better understand what they signal about a company's direction.

With these updates, you can:

* **Identify executive hiring signals more accurately** by distinguishing external hires from internal role changes.
* **Track internal leadership movements** to uncover organizational restructuring, shifting responsibilities, and potential changes in company priorities.
* **Build executive intelligence workflows more easily** with improved employment histories and direct access to executive names, LinkedIn profiles, and company information.

**Availability**

The new fields are available through the **[Company Comprehensive](/docs/company-data-field-bundles#comprehensive) field bundle** and will be automatically included for all users with access to this bundle.

**Additional Resources**

* [Field Bundle](/docs/company-data-field-bundles#comprehensive)
* [Schema Definition](/docs/company-schema)
* [Fill Rate Stats](/docs/company-stats)

***

### Inferred Revenue Improvements

Company Data

Beta

✨ Product Update

📐 Schema Change

**What's New?**

We've improved the accuracy and freshness of our [Inferred Revenue Data](/docs/inferred-revenue-ranges) and introduced a new numeric revenue field for more granular estimates of annual company revenue.

This release includes three improvements:

1. **Fresher public company revenue data:** We're now incorporating regularly updated financial reporting data to better reflect the latest reported revenue for public companies.
2. **Improved revenue estimation logic:** We've refined our calculations to reduce outliers and improve the consistency of revenue estimates relative to company size.
3. **New numeric revenue estimates:** The new `inferred_revenue_integer` field provides an estimated annual revenue amount in USD, giving you more flexibility than our predefined revenue ranges.

These improvements also apply to our existing [`inferred_revenue`](/docs/company-schema#inferred_revenue) field, which continues to use the same [10 canonical revenue ranges](/docs/inferred-revenue-ranges).

**New Inferred Revenue Field**

| FIELD NAME | FIELD TYPE | FIELD BUNDLE | FIELD DESCRIPTION |
| :- | :- | :- | :- |
| [`inferred_revenue_integer`](/docs/company-schema#inferred_revenue_integer) | `Integer` | [Inferred Revenue Integer](/docs/company-data-field-bundles#inferred-revenue-integer) | A numeric estimate of a company's annual revenue in USD. Available upon request. |

**Example**

```json theme={null}
{
  "inferred_revenue": "$50M-$100M",
  "inferred_revenue_integer": 52000000
}
```

**Why It Matters**

These improvements make our Inferred Revenue Data more reliable and flexible for company segmentation, prospecting, and market analysis.

With these updates, you can:

* **Segment companies more confidently** with fresher revenue data and fewer extreme outliers.
* **Create custom revenue segments** using numeric estimates instead of relying on predefined revenue ranges.
* **Analyze large companies with greater granularity**, including companies with estimated annual revenue above \$10 billion.

**Availability**

The improvements to our existing `inferred_revenue` field are automatically included for customers who already receive this data. No action is required.

The new `inferred_revenue_integer` field is in beta and available as a **premium add-on upon request**. Contact your account team to discuss availability and pricing.

***

### Deprecation Notice: Company Fields (Sunset: Feb 2027)

Company Data

⚠️ Breaking Change

📐 Schema Change

**Removal Date:** February 16, 2027 (v37.1)\

**Impacted Product:** [Company Schema](/docs/company-schema)

**Overview**

We're deprecating two legacy Company Data fields in favor of newer fields that provide more detailed company information.

These fields will be **removed on February 16, 2027 (v37.1)**. If you currently use any of the affected fields, you'll need to update your integrations before this date to avoid disruptions.

**Fields Being Deprecated**

| DEPRECATED FIELD | REPLACEMENT FIELD |
| :- | :- |
| [`funding_details.investing_companies`](/docs/company-schema#funding_details) | [`funding_details.investing_companies_details`](/docs/company-schema#funding_details) |
| [`affiliated_profiles`](/docs/company-schema#affiliated_profiles) | [`affiliated_entities[].affiliated_id`](/docs/company-schema#affiliated_entities) |

> [!WARNING]
>
> **Company Search API Limitations**
>
> The replacement [`affiliated_entities`](/docs/company-schema#affiliated_entities) fields are nested and do not support equivalent filtering in the Company Search API. If you currently use the deprecated `affiliated_profiles` field in Company Search API queries, a direct 1:1 replacement may not be available.
>
> Please contact your account team to discuss your use case and available alternatives.

**Why We're Making This Change**

The replacement fields offer the same core company identifiers while providing richer information about company relationships and funding (such as including company identifiers, display names, and relationship types).

Consolidating these fields helps simplify our Company Schema and make company data easier to work with consistently.

**Timeline**

* **👉 Now – February 15, 2027:** Both the deprecated and replacement fields remain available. Customers can migrate their integrations.
* **February 16, 2027 (v37.1):** The two deprecated fields will be removed from the Company Schema.

**Action You Need to Take**

If you currently use any of the affected fields:

1. **Review your integrations and queries** to identify where these fields are used.
2. **Update your field mappings** to use the corresponding replacement fields, where supported.
3. **Test your integrations** before February 16, 2027, to ensure they continue working as expected.

**Need Help?**

If you have any questions or need help migrating to the new fields, please reach out to your Customer Account Team. We're happy to help you prepare for this change.

***

## 🚀 Data Updates

### Freshness

*The number of resume experiences and locations verified in our datasets (based on the [`job_last_verified`](/docs/fields#job_last_verified) and [`location_last_updated`](/docs/fields#location_last_updated) fields).*

**Monthly (v35.2 → v36.0)**
*Freshness updates over the past month.*

| Dataset | Geography | Field | Records Updated |
| :- | :- | :- | :- |
| Resume | Global | `experience` | 53,680,622 |
| Resume | Global | `location` | 53,639,314 |
| Resume | United States | `experience` | 20,388,452 |
| Resume | United States | `location` | 19,697,083 |

### Job Changes

*The number of person records where the primary job experience changed in our Person Dataset (based on the [`job_last_changed`](/docs/fields#job_last_changed) field).*

**Monthly (v35.2 → v36.0)**
*Job changes detected over the past month.*

| Dataset | Geography | Records Updated |
| :- | :- | :- |
| Resume | Global | 6,126,821 |
| Resume | United States | 1,464,118 |

***

## 🌐 Coverage

### Monthly Highlights (v35.2 → v36.0)

> **[Resume Dataset](/docs/resume-stats)**
>
> | Linkage | Coverage in v35.2 | Coverage in v36.0 | Increase (%) |
> | :- | - | - | - |
> | Total Records | 815,476,877 | 817,762,943 | 0.28% |

> **[Company Dataset](/docs/company-stats)**
>
> | Linkage | Coverage in v35.2 | Coverage in v36.0 | Increase (%) |
> | :- | - | - | - |
> | Total Records | 76,606,079 | 76,878,378 | 0.36% |
> | [`technologies_used`](/docs/company-schema#technologies_used) | 6,758,244 | 6,856,414 | 1.45% |
> | [`active_job_postings`](/docs/company-schema#active_job_postings) | 115,918 | 121,486 | 4.80% |
> | [`deactivated_job_postings`](/docs/company-schema#deactivated_job_postings) | 115,918 | 121,486 | 4.80% |

> **[Job Posting Dataset](/docs/jp-stats)**
>
> | Metric | Coverage in v35.2 | Coverage in v36.0 | Increase (%) |
> | :- | - | - | - |
> | Total Records | 46,188,396 | 51,096,491 | 10.63% |
> | Total Unique Companies | 116,514 | 125,340 | 7.58% |
> | Total Active Postings | 7,024,184 | 7,624,975 | 8.55% |

> **Technology Data**
>
> | Metric | Coverage in v35.2 | Coverage in v36.0 | Increase (%) |
> | :- | - | - | - |
> | Technologies Tracked (The total number of standardized technologies included in our technology taxonomy and available for identification.) | 25,566 | 25,566 | 0.00% |
> | Technologies Observed (The number of distinct technologies observed across all companies in the dataset.) | 22,571 | 22,631 | 0.27% |
> | Companies with Technology Data (The number of companies for which at least one technology has been observed.) | 6,758,244 | 6,856,414 | 1.45% |
> | Observed Company\<>Technology Pairs (The total number of unique company-to-technology relationships observed in the dataset.) | 55,632,265 | 56,840,142 | 2.17% |
> | Total Technology Mentions (The total number of times technologies are referenced across the underlying data sources used to identify technology usage.) | 197,780,611 | 204,782,659 | 3.54% |

### Commentary

* **Company Data**
  * The number of companies with [Technology Data](/docs/company-schema#technologies_used) increased by **1.5%**
  * The number of companies with [Job Posting Data](/docs/jp-stats) increased by **4.8%**
* **Job Posting Data**
  * [Job Posting Dataset](/docs/jp-stats) coverage continued to expand with **7.6%** more unique companies and **8.6%** more active postings this month
* **Technology Data**
  * Total technology mentions increased by **3.5%**, while the number of unique Company \<> Technology linkages grew by **2.2%**
  * We also observed Technology Data across **1.5%** more companies this month

***

## 🛠 Improvements and Bug Fixes

### Bug Fixes

* **Inaccurate Spain Company HQ Addresses**
  * We fixed an issue with a data source that was incorrectly attributing the HQ addresses for some companies to Spain.
* **Incorrect Employee Counts by Country**
  * We updated our logic to remove countries from [`employee_count_by_country`](/docs/company-schema#employee_count_by_country) when a company has no employees working in those countries.


## Related topics

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