October 2025 Release Notes

Welcome to our October 2025 release notes We’re launching some major updates this month that you don’t want to miss! Here’s what’s new:

• 📊 Freshness Updates: This past quarter, we verified 313M+ jobs and detected 19M+ job changes across our global dataset
• Job Posting Salary and Skill Fields: Standardized fields for compensation ranges and associated skills from job posts
• Daily Job Posting Data: Fresh job posts. Every day.
• Email Deliverability Improvements: Starting this month - lower bounce rates and higher match rates for our top-level emails.

​

Schema Changes

​

Salary and Skill Fields (Job Posting)

What’s New? This month, we’re adding a set of highly requested salary and skills fields to the Job Posting Data Schema. These additions make it easier to analyze compensation trends and identify key skills mentioned in job descriptions – all in a structured, standardized way. Salary Fields Skills Fields Why It Matters These new fields make it easier to filter, compare, and analyze job posts at scale:

• Inferred skills extract the required abilities, tools, and technologies mentioned in job descriptions – useful for skill-based matching, trend analysis, or even technographic enrichment.
• Salary data helps you evaluate pay ranges for roles, support compensation benchmarking, or power salary display features.

By structuring these data points directly in the schema, you can spend less time on parsing and more time on analysis. Availability These fields are immediately available to all Job Posting Dataset 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!

​

Upcoming Breaking Changes

​

Deprecation Notice: Query Builder & API Explorer Tools

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

• Query Builder Tool
• API Explorer Tool

In November 2025, we will be 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 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
• Start 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)

What’s New Starting this month, we’re launching an ongoing initiative to improve how we validate and refresh email data in the Person Dataset. These updates will increase the accuracy and deliverability of our two top-level email fields:

• work_email
• recommended_personal_email

How It Works This month we’ve started validating the deliverability status of our top-level email fields (recommended_personal_email and work_email). Non-deliverable emails will be 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. This work is planned to continue over the next few months and quarters. Validation will roll out in phases with the intent of ensuring a smooth transition. Short-Term Coverage Fluctuations As validation progresses, you may notice short-term changes in top-level work_email and recommended_personal_email fill rates release-to-release. Our long-term goal is to increase coverage and improve overall deliverability and quality, but our focus is on improving quality first. Why This Matters Deliverable, high-quality emails are essential for reliable outreach and enrichment. These improvements will reduce bounce rates, strengthen match accuracy, and ensure more dependable Person data. How To Prepare Most customers won’t need to take action, but if you rely heavily on top-level emails for:

• Data License Customers: Consider matching against the emails array instead of only top-level fields. Our Solutions Engineering team can advise on best practices.
• Matching / Enrichment: Monitor match rates over the coming months for unexpected changes.
• Outreach: We recommend continuing to validate emails before including them in campaigns, as deliverability can change day-to-day.

For more detailed guidance, we wrote a guide on these Email Deliverability Improvements as well. 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! We’d love your input, especially on proposed additions like email validation status metadata to the Person Schema.

​

Daily Deliveries for Job Posting Data (Beta)

What’s New We’re excited to introduce a new daily delivery option for our Job Posting Dataset, now available in Beta starting this month! Why This Matters Many job posting use cases depend on having data that reflects the most current market activity. With daily deliveries, you’ll have access to fresh job posting data every day, helping you stay on top of changes and trends in real time. Some examples of use cases that benefit from daily updates include:

• Keeping internal databases and dashboards current
• Powering job search or labor analytics tools
• Monitoring hiring trends or job market shifts

How It Works Daily deliveries are available as downloadable files hosted in a PDL-managed Amazon S3 bucket. Each day’s delivery includes a dedicated folder with subdirectories organized by record status:

• Deleted – Records from the prior release that no longer appear in the current release
• Deactivated – Records newly marked as inactive (with a deactivated_date after the previous release)
• Updated – Modified records (with a record_update date after the previous release)
• Added – New records (with a first_seen date after the previous release)

You can pull data from any day’s delivery to keep your dataset in sync and always up to date. Push vs Pull Deliveries Unlike our existing data license delivery methods – where we push data directly to each customer’s cloud storage (e.g. your own S3 bucket) – daily deliveries use a pull model. In this setup, you’ll retrieve the latest data directly from PDL’s hosted S3 bucket using your own provisioned S3 access keys. This approach allows us to provide faster, more flexible updates and lays the groundwork for improved delivery performance across our entire product suite. S3 Only (for now) For this initial beta release, daily job posting feeds are available only via AWS S3. Support for additional cloud providers may be added in future releases based on customer demand. Interested in having daily feeds hosted on a different cloud platform? You can vote or share feedback in Canny to help us prioritize future delivery options. Access Daily Deliveries are available as a premium add-on for all Job Posting customers. During the beta period, we’re offering special early adopter pricing, so it’s a great time to explore this new option. How to Get Started

• New to PDL? Get in touch and we’ll help you get set up with access to Job Posting data and the new daily delivery option.
• Existing customers: Reach out to your account team to learn more and see if daily deliveries are a good fit for your use case.

​

Data Updates

​

Freshness

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

​

Coverage

Quarterly (v31.0 → v32.0) Resume Dataset API Dataset Email Dataset Mobile Phone Dataset Company Dataset Job Posting Dataset Monthly (v31.2 → v32.0) Resume Dataset API Dataset Email Dataset Mobile Phone Dataset Company Dataset Job Posting Dataset

​

Commentary

• Person
  • We saw a 35% increase in headline coverage over this past quarter (5% this past month) from adding a new data source.
  • We saw a decrease in fill rate for our work_emails as a result of ongoing work to improve the deliverability of our top-level emails (5% decrease from last quarter, 4% decrease from last month).
• Company
  • We saw a 4.8% increase in the number of companies this month (and quarter) as a result of a series of improvements we made to our pipeline for building our company dataset
• Job Posting Data
  • We saw a 30% increase this quarter (4% this past month) in the number of unique employers in our Job Posting Dataset along with a 17% increase in the number of active job postings this past quarter.

​

Improvements and Bug Fixes

​

Improvements

• Person Enrichment API Matching Improvements
  • We made updates to our Person Enrichment API logic so that we analyze more records before providing a match – this improves the quality of matches, without impacting latency
• Location Selection Logic for Person Primary Location
  • We updated our location selection logic to prioritize the most recent country for a profile’s primary location in our Person records. Previously, our logic prioritized the most complete location rather than the most recent, which led to representing out-of-date locations in our Person records.
• Email Deliverability Improvements
  • This month we are beginning to rollout improvements to the deliverability of our top-level email fields (work_email and recommended_personal_email). See the announcement above for more details.

​

Bug Fixes

• Phone Cleaning in the Person Enrichment API
  • We fixed a bug where some international phone numbers were incorrectly nullified during input processing in the Person Enrichment API. This was causing them to be dropped from requests, reducing match rates.
• Person Enrichment API Deterministic Behavior
  • In cases when two records had the same matching likelihood for a request, PDL would unreliably tiebreak between the records. We have now implemented a deterministic tiebreak in cases where our scoring for 2 records is tied.
• Removal of Inaccurate Birth Years
  • We fixed an issue where incorrect birth dates (100+ years ago) existed for profiles with active jobs.
• Better Country Canonicalization for US States
  • We fixed an issue leading to incorrect location canonicalization where US State codes were mapping to country codes. For example, CA was being canonicalized to Canada instead of California leading to incorrect results in our Location Cleaner.