September 2025 Release Notes (v31.2)

Release NameDataset VersionPublish Date
September 2025v31.209/16/2025

Welcome to our September 2025 release notes!

This month, we’re rolling out some fresh updates and exciting features across our products.

Here’s what’s new:

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


Table of Contents

📣 Schema Changes

⚠️ Upcoming Breaking Changes

✨ New Products and Features

🚀 Data Updates

🛠 Improvements and Bug Fixes


📣 Schema Changes

New Company Industry Field (Company)

What’s new?
This month, we’ve expanded our Company dataset with a brand new field: industry_v2.

FIELD NAMEFIELD TYPEFIELD BUNDLEFIELD DESCRIPTION
industry_v2Enum (String)Company Base
Company Premium
Company Comprehensive
Industry v2 is the self-reported industry from an expanded list of Canonical v2 Industries. If no industry is found, the field will be null

This field captures the most recently observed industry classification reported by the company, and includes expanded support for the more external industry taxonomies. It ensures our dataset reflects modernized industry categories that may differ from the legacy classifications still in use by the industry field.

Why it matters

This change addresses customer feedback that company industry classifications sometimes appear outdated or inconsistent with what companies currently use to describe themselves. With industry_v2, you get:

  • Up-to-date company classifications → no more mismatched values
  • No manual mapping required → reduces the need to build and maintain your own taxonomy conversions
  • Improved workflow compatibility → better results in targeting, search, and discovery use cases that depend on modern industry categories

This change brings refreshed industry classifications to the 70M+ companies in our Company Dataset.

Availability
The new industry_v2 field is immediately available to all customers across all delivery methods for Company data. This new field is automatically included in the Company Base, Premium, and Comprehensive bundles and is provided at no extra cost.

Comparison to the legacy industry field
The legacy industry field will still be available with its functionality preserved. The industry field will continue to 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 field, however if you have existing workflows reliant on the original PDL industry classifications, then you should continue to leverage the industry field.

📘

Person Records will only contain the existing (legacy) industry field

The Person dataset will continue to contain the legacy industry values in the industry, job_company_industry, and experience.company.industry fields.

The new industry_v2 field is a schema change specific to the Company Dataset.


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!

⚠️ Upcoming Breaking Changes

🚧

Upcoming Breaking Changes

Upcoming breaking changes may impact your current processes. We are announcing them here to provide ample time for you to adjust your processes accordingly.

⚠️ Deprecation Notice: Query Builder & API Explorer Tools

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

In November 2025, we will be deprecating 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

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

Timeline

  • July 2025: API Playground available in your API Dashboard
  • 👉 July–November 2025: Legacy tools and API Playground both available
  • November 2025: Legacy tools fully removed.

Action You Need to Take

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

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

🚀 Pro Plan Trial (Dashboard)

This month we’re excited to introduce the Pro Plan Trial, designed to help new and existing, non-enterprise users explore PDL’s APIs for free before committing to a paid plan.

What's New

During the trial, you’ll receive 500 API credits to use over a single 30-day period via the API Dashboard. You’ll also receive access to premium features like increased rate limits and field bundles across our APIs including:

  • Person Enrichment
  • Person Search
  • Person Identify
  • Company Enrichment
  • Company Search
  • IP Enrichment

Access
The Pro Plan Trial is available to all, non-enterprise users globally. New users can access the trial immediately after completing the onboarding steps and existing users can start a trial from the Home page.

How to Get Started

  1. Sign up for a new PDL account (or log in to an existing non-enterprise account).
  2. Click the Start Trial button on any product you’d like to trial from the Home page.
  3. Provide a credit card for a $1 authorization hold.
  4. Start using500 API credits over 30 days.

💡

Pro Tip: API Playground

Once you start your trial, check out the API Playground to explore your new fields without writing a single line of code.


🚀 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 (v31.1 → v31.2)
Freshness updates over the past month.

DatasetGeographyFieldRecords Updated
ResumeGlobalexperience111,649,232
ResumeGloballocation166,713,893
ResumeUnited Statesexperience31,640,391
ResumeUnited Stateslocation43,908,581

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.1 → v31.2)
Freshness updates over the past month.

DatasetGeographyRecords Updated
ResumeGlobal1,758,083
ResumeUnited States974,038

Coverage (Full Stats:

Person, Company, IP, Job Posting)

📌 Monthly (v31.1 → v31.2)

Resume Dataset

LinkageCoverage in v31.1Coverage in v31.2Increase (%)
Total Records781,715,532782,476,6610.10%
headline92,478,345100,778,5928.98%

API Dataset

LinkageCoverage in v31.1Coverage in v31.2Increase (%)
Total Records2,442,298,0592,442,828,9240.02%

Email Dataset

LinkageCoverage in v31.1Coverage in v31.2Increase (%)
Total Records591,113,964590,959,775-0.03%

Mobile Phone Dataset

LinkageCoverage in v31.1Coverage in v31.2Increase (%)
Total Records481,934,392481,857,739-0.02%

Company Dataset

LinkageCoverage in v31.1Coverage in v31.2Increase (%)
Total Records71,648,10371,658,7190.015%

Job Posting Dataset

LinkageCoverage in v31.1Coverage in v31.2Increase (%)
Total Records14,333,30516,340,50614.00%
Total Unique Companies34,70440,37816.35%
Total Active Postings2,313,7442,565,14210.87%

Commentary

📌 Monthly Highlights (v31.1 → v31.2)

  • Person
    • We saw another 8% increase in coverage for the headline field as result of a new data source we integrated last month.
  • Job Posting Data
    • We saw ~16% growth in the total number of companies in our Job Posting Dataset alongside a 10% increase in the Active Postings in the dataset (and 14% increase in overall volume).

🛠 Improvements and Bug Fixes

Improvements

  • Company “All Office Locations” improvements
    • We introduced a series of refinements to reduce the rate of duplicate company addresses, improve the freshness of primary HQ office designations, and increase the accuracy of the “active” status labels
  • Better Experience Deduplication
    • We improved our logic for experience and education to better detect primary roles, reduce duplicates, and maintain cleaner experience histories.

Bug Fixes

  • No bugs were squashed this time...but we’re ready for the next round. 🐛🥊