Skip to main content
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:

📣 Announcements

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)
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:
  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.
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.
New Recent Executive Fields We’ve added 21 new fields to the Company Schema, available as part of the Company 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 Executive Hires Fields (3)
New Executive Departures Fields (3)
New Executive Internal Changes Fields (15)
Example
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 field bundle and will be automatically included for all users with access to this bundle. Additional Resources

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:
  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 field, which continues to use the same 10 canonical revenue ranges. New Inferred Revenue Field Example
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
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
Company Search API LimitationsThe replacement 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 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 the job_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
  • 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_country when a company has no employees working in those countries.