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: Track internal executive role changes, with improved accuracy for executive hires and departures.
- 💰 Inferred Revenue Improvements: Fresher, more reliable company revenue estimates, plus a new numeric revenue field for more granular analysis.
- 🔧 Data Quality & Coverage Improvements: Improved company address accuracy and employee location data, plus expanded Technology Data coverage for nearly 6.9 million companies.
- 📊 Freshness Updates: This past month, we refreshed 53M+ resume experiences and detected 6.1M+ job changes across our global dataset.
📣 Announcements
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
✨ 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 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:- 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.
- More accurate executive hires and departures: Improved logic distinguishes internal role changes from external hires and more accurately identifies previous and next work experiences.
- 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.
Changes to Existing Executive Hire DataInternal role changes are no longer included in
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.- 13 fields representing internal executive role changes:
recent_exec_internal_changesand 12 of its subfields. - 2 fields providing names of the previous or next companies.
- 6 fields providing executive names and LinkedIn URLs.
New Recent Executive Fields (21)
New Recent Executive Fields (21)
New Executive Hires Fields (3)
New Executive Departures Fields (3)
New Executive Internal Changes Fields (15)
- 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.
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 and introduced a new numeric revenue field for more granular estimates of annual company revenue. This release includes three improvements:- Fresher public company revenue data: We’re now incorporating regularly updated financial reporting data to better reflect the latest reported revenue for public companies.
- Improved revenue estimation logic: We’ve refined our calculations to reduce outliers and improve the consistency of revenue estimates relative to company size.
- New numeric revenue estimates: The new
inferred_revenue_integerfield provides an estimated annual revenue amount in USD, giving you more flexibility than our predefined revenue ranges.
inferred_revenue field, which continues to use the same 10 canonical revenue ranges.
New Inferred Revenue Field
Example
- 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.
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 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
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.
- Review your integrations and queries to identify where these fields are used.
- Update your field mappings to use the corresponding replacement fields, where supported.
- Test your integrations before February 16, 2027, to ensure they continue working as expected.
🚀 Data Updates
Freshness
The number of resume experiences and locations verified in our datasets (based on thejob_last_verified and location_last_updated fields).
Monthly (v35.2 → v36.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 thejob_last_changed field).
Monthly (v35.2 → v36.0)
Job changes detected over the past month.
🌐 Coverage
Monthly Highlights (v35.2 → v36.0)
Resume Dataset
Company Dataset
Job Posting Dataset
Technology Data
Commentary
- Company Data
- The number of companies with Technology Data increased by 1.5%
- The number of companies with Job Posting Data increased by 4.8%
- Job Posting Data
- Job Posting Dataset 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_countrywhen a company has no employees working in those countries.
- We updated our logic to remove countries from
