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

# November 2025 Release Notes

| Release Name  | Dataset Version | Publish Date |
| :------------ | :-------------- | :----------- |
| November 2025 | `v32.1`         | 11/18/2025   |

**Welcome to our November 2025 release notes!**

Check out the updates below to stay up to date!

Here's what's new:

* **📊 Freshness Updates**: This past quarter, we verified [278M+ jobs](#freshness) and tracked [723K+ job changes](#job-changes) across our global dataset
* **Improved Company Facebook / Meta Profile Resolution**: We split Facebook & Meta into two distinct company profiles
* **<Icon icon="mail" /> Email Deliverability Improvements**: Continued work to lower bounce rates and improve match rates for our top-level emails

## Breaking Changes (Going Live This Month)

### Final Sunset: Query Builder & API Explorer Tools

**Deprecation Date:** November 2025 (v32.1)
**Impacted Product:** API Dashboard

**Tools Being Removed**

* Query Builder Tool
* API Explorer Tool

At the end of this month, we are removing several legacy tools in our API Dashboard and public documentation in favor of our new API Playground which went live last month in August.

**Why we're making this change**

The legacy tools created a fragmented experience and required manual query building, especially for non-technical users. Further, the Query Builder had limitations and a lack of parity with our APIs that created confusion.

The new API Playground:

* Lets you build requests and view live data directly in your dashboard
* Replaces the functionality of the API Explorer Tool without having to leave the API Dashboard

**Timeline**

* November 30, 2025 - Legacy tools fully removed
* July–November 2025 - Legacy tools and API Playground both available
* July 2025 - API Playground available in your API Dashboard

**Action You Need to Take**

* Recreate any workflows you currently run in the Query Builder by writing SQL or Elasticsearch queries in the new API Playground
* Continue using the API Playground now to prepare for the upcoming deprecations

Need Help? 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

### Email Deliverability Improvements ([Person](/docs/person-data-overview))

<Note>
  **Email Deliverability Guide**

  For an in-depth guide on these changes and how to take advantage of these improvements, please see this customer guide prepared by our Solutions Engineering Team:

  [Email Deliverability Improvements](https://www.peopledatalabs.com/pdf/email-deliverability-improvements-guide.pdf)
</Note>

**What's New**

This month we've continued to validate the deliverability status of our top-level email fields (`recommended_personal_email` and `work_email`).

Non-deliverable emails have been removed from these two top-level fields. Removed emails will still remain in the `emails` array, and we will begin backfilling our top-level fields with new validated emails.

**What's Next**

These improvements will continue over the coming months with the goal of significantly enhancing deliverability and maintaining ongoing validation.

Have feedback or ideas? Share them on our [roadmap board](https://feedback.peopledatalabs.com/feature-requests?selectedCategory=person-data)! We'd love your input, especially on proposed additions like [email validation status metadata](https://peopledatalabs.canny.io/feature-requests/p/email-validation-status-and-last-validated-date-fields) to the Person Schema.

### Improved Facebook / Meta Profile Resolution ([Company](/docs/company-data-overview))

**What's New**

This release splits Facebook and Meta into separate company profiles and work experience. Previously, we had logic to combine these together as a single entity, and this change standardizes the logic to be consistent with that used for other corporate entity relationships (e.g., Google and Alphabet).

**Meta Example Record**

```json JSON theme={null}
{
  "id": "RjhjJnYUCiAfXFyxCHLDQQ5opPrK",
  "display_name": "Meta",
  "employee_count": 90447,
  "website": "meta.com",
  "ticker": "META",
  "mic_exchange": "xnas",
  "affiliated_profiles": [
    "pNX89m6UGXrHYyTaolvXwg5t5Dtg"
  ],
  "ultimate_parent": null,
  "immediate_parent": null,
  "direct_subsidiaries": [
    "pNX89m6UGXrHYyTaolvXwg5t5Dtg"
  ],
  "all_subsidiaries": [
    "pNX89m6UGXrHYyTaolvXwg5t5Dtg"
  ]
}
```

**Facebook Example Record**

```json JSON theme={null}
{
  "id": "pNX89m6UGXrHYyTaolvXwg5t5Dtg",
  "display_name": "Facebook",
  "employee_count": 12485,
  "website": "facebook.com",
  "alternative_domains": [
    "facebook.com/careers",
    "meta.com"
  ],
  "affiliated_profiles": [
    "RjhjJnYUCiAfXFyxCHLDQQ5opPrK"
  ],
  "ultimate_parent": "RjhjJnYUCiAfXFyxCHLDQQ5opPrK",
  "immediate_parent": "RjhjJnYUCiAfXFyxCHLDQQ5opPrK",
  "direct_subsidiaries": [
    "nqLYBErZDf7t2Kydtrww3wBz3hgZ"
  ],
  "all_subsidiaries": [
    "nqLYBErZDf7t2Kydtrww3wBz3hgZ"
  ]
}
```

## Data Updates

### Freshness

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

| Dataset | Geography     | Field        | Records Updated |
| :------ | :------------ | :----------- | :-------------- |
| Resume  | Global        | `experience` | 278,603,459     |
| Resume  | Global        | `location`   | 448,369,587     |
| Resume  | United States | `experience` | 78,771,136      |
| Resume  | United States | `location`   | 106,930,435     |

### 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 (v31.2 → v32.0)**
*Freshness updates over the past month.*

| Dataset | Geography     | Records Updated |
| :------ | :------------ | :-------------- |
| Resume  | Global        | 723,990         |
| Resume  | United States | 346,723         |

### Coverage

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

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

| Linkage       | Coverage in v32.0 | Coverage in v32.1 | Increase (%) |
| :------------ | :---------------- | :---------------- | :----------- |
| Total Records | 785,943,288       | 785,905,373       | \~0%         |
| `linkedin_id` | 484,219,348       | 519,260,749       | 7.24%        |
| `profiles.id` | 512,224,711       | 546,960,396       | 6.78%        |
| `work_email`  | 78,419,180        | 74,415,166        | -5.11%       |

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

| Linkage                               | Coverage in v32.0 | Coverage in v32.1 | Increase (%) |
| :------------------------------------ | :---------------- | :---------------- | :----------- |
| Total Records                         | 2,445,987,840     | 2,444,867,417     | \~0%         |
| `job_company_location_street_address` | 224,118,901       | 236,159,038       | 5.37%        |

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

| Linkage       | Coverage in v32.0 | Coverage in v32.1 | Increase (%) |
| :------------ | :---------------- | :---------------- | :----------- |
| Total Records | 590,809,897       | 590,217,603       | -0.1%        |

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

| Linkage       | Coverage in v32.0 | Coverage in v32.1 | Increase (%) |
| :------------ | :---------------- | :---------------- | :----------- |
| Total Records | 481,857,739       | 481,373,997       | -0.1%        |

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

| Linkage       | Coverage in v32.0 | Coverage in v32.1 | Increase (%) |
| :------------ | :---------------- | :---------------- | :----------- |
| Total Records | 75,127,347        | 75,127,700        | \~0%         |

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

| Linkage                | Coverage in v32.0 | Coverage in v32.1 | Increase (%) |
| :--------------------- | :---------------- | :---------------- | :----------- |
| Total Records          | 17,977,165        | 19,541,264        | 8.7%         |
| Total Unique Companies | 42,312            | 43,686            | 3.2%         |
| Total Active Postings  | 2,566,979         | 2,587,181         | 0.8%         |

### Commentary

* **Person**
  * We began receiving Linkedin ID from one of our sources, contributing to the increase in fill rates for `profiles.id` and `linkedin_id`.

## Improvements and Bug Fixes

### Improvements

* **Reduce Count of "Escape Characters" in Company Names**
  * We've identified and removed \~16k (>90%) escape characters from company names. Due to some nuances in how we build our company data, there are still some that remain, but we suspect that active projects this quarter may be able to remove these entirely.

### Bug Fixes

* **Fix Location Selection Logic**
  * We fixed an issue in our location selection logic that was causing a previous location to be selected for some records.
* **LIMIT in SQL queries**
  * If a LIMIT clause was used in a Person or Company Search SQL query it was unintentionally overriding the `size` parameter in some circumstances. It now throws a 400 error as expected.


## Related topics

- [November 2024 Release Notes](/changelog/november-2024-release-notes-v281.md)
- [September 2025 Release Notes](/changelog/september-2025-release-notes-v312.md)
- [August 2025 Release Notes](/changelog/august-2025-release-notes-v311.md)
- [October 2025 Release Notes](/changelog/october-2025-release-notes-v320.md)
- [January 2025 Release Notes](/changelog/january-2025-release-notes-v290.md)