December 2025 Release Notes (v32.2)

Welcome to our December 2025 release notes!

Check out the updates below to stay up to date!

Here’s what’s new:

Parent/Subsidiary Data Expansion: We are introducing new fields in our company dataset that provide rich, contextual information on the relationships between related records. This includes new “Details” information, available now to users that opt-in to provide Alpha release feedback. 📊 Freshness Updates: This past quarter, we verified 278M+ jobs and tracked 723K+ job changes across our global dataset

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

Table of Contents

✨New Products and Features

• 🏬Parent/Subsidiary Data Expansion

🚀 Data Updates

• Freshness
• Job Changes
• Coverage
• Commentary

🛠 Improvements and Bug Fixes

• Improvements
• Bug Fixes

✨New Products and Features

🏬Parent Subsidiary Data Expansion

PDL is introducing the new affiliated_entities field, which creates a place for rich, contextual information on the relationships between related companies.

This new object-based field now holds:

• 3 GA Subfields that present our existing parent/subsidiary data in an easier-to-consume way:

  • Price: No additional cost to any users with access to the existing parent/subsidiary fields
  • Availability: Indefinitely
  • Fields:
    • affiliated_id: The PDL Company ID of the affiliated company profile.
    • display_name: Displayable, case sensitive name of the affiliated company profile.
    • relationship: Indicates the affiliated company’s role in the relationship as it appears in the top-level parent/subsidiary fields (for example, whether it is the parent company or a subsidiary).

• 5 Alpha Subfields that present new parent/subsidiary information:

  • Price: No additional cost to users during the Alpha testing program
  • Availability: In Alpha until June 2026 - contact the PDL team to get access!
  • Fields:
    • relationship_catalyst: Enumerated label indicating the corporate action that created the relationship.
    • relationship_status: Indicates whether the relationship is active, inactive, or pending.
    • start_date: The "as of" date for the start of the relationship.
    • end_date: When applicable, the date that the affiliation ended (e.g., divestiture).
    • relationship_citations: List of URLs (news articles, press releases, webpages) that validate the business relationship.

Sample API Output - Slack Technologies:

{
  "status": 200,
  "name": "slack",
  "display_name": "Slack",
  "employee_count": 3097,
  "id": "Yxps3xWRb5QVlpLX2TFbJAyvHbIT",
  "ultimate_parent": "es7LgyqRNsFDLcWXC3WAvACHVh9g",
  "ultimate_parent_mic_exchange": "xnys",
  "ultimate_parent_ticker": "crm",
  "immediate_parent": "es7LgyqRNsFDLcWXC3WAvACHVh9g",
  "direct_subsidiaries": [
    "CzBNyjIICYIBrhIOyxG5iQfQvzLt",
    "Ah8BojCOBRO5xluvTL2eCwVVxqW7",
    "QEmw9sBsJCuxhLmIabYj9QBBzH1t",
    "B0MC4mBYnBtNq7pHVOYqEQ4d0LHI",
    "M69agS6BgtcBnmAhKh1AQwZ9vkjv"
  ],
  "all_subsidiaries": [
    "CzBNyjIICYIBrhIOyxG5iQfQvzLt",
    "Ah8BojCOBRO5xluvTL2eCwVVxqW7",
    "QEmw9sBsJCuxhLmIabYj9QBBzH1t",
    "B0MC4mBYnBtNq7pHVOYqEQ4d0LHI",
    "M69agS6BgtcBnmAhKh1AQwZ9vkjv"
  ],
  "affiliated_entities": [ // <-- Releasing as GA in v32.2
    {
      "affiliated_id": "es7LgyqRNsFDLcWXC3WAvACHVh9g", // <-- Releasing as GA in v32.2
      "display_name": "Salesforce", // <-- Releasing as GA in v32.2
      "relationship": "ultimate_parent", // <-- Releasing as GA in v32.2
      "relationship_catalyst": "direct_acquisition",  // <-- Releasing as Alpha
      "relationship_status": "active",  // <-- Releasing as Alpha
      "start_date": "2021-07-21",  // <-- Releasing as Alpha
      "end_date": null,  // <-- Releasing as Alpha
      "relationship_citations": [  // <-- Releasing as Alpha
				"salesforce.com/news/press-releases/2021/07/21/salesforce-slack-deal-close",
        "nytimes.com/2020/12/01/technology/salesforce-slack-deal.html",
        "slack.com/blog/news/salesforce-completes-acquisition-of-slack"
      ]
    },  
    ...
        ] 
    
   } 

Why This Matters

The legacy parent/subsidiary fields are structured as a list of related PDL Company IDs (e.g., direct_subsidiaries), requiring users perform additional joins or API calls to obtain displayable company names.

By expanding into a more flexible object-based structure, we are able to embed additional metadata describing the relationships between records.

The first of this data, available to participants that opt-in to our Parent/Subsidiary Details Alpha program, expands the data available on relationships to include the current status, start/end dates, and citation links of each affiliation.

These common Feature Requests make the parent/subsidiary data more actionable, with information to filter out inactive or low confidence relationships, incorporate relationship timelines into products, or to provide URL citations to users or researchers.

How it Works

Any users with access to PDL’s existing parent/subsidiary fields will receive the affiliated_entities field and 3 GA subfields automatically in their API response or deliveries. Any new users, or users who want access to the 5 Alpha subfields, should message their PDL account team.

📘

Parent/Subsidiary Details Alpha Program

We are eager for your feedback on the new relationship metadata fields!

Reach out to your PDL account representative to participate in the program. Access to the data involves sharing brief feedback on how you intend to test the data, and how you will evaluate the quality of the information. At the midpoint (March 2026) and end (June 2026) of the program, our team will reach out to you with additional questions.

🚀 Data Updates

Freshness

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

Coverage

Monthly (v32.1 → v32.2)

Resume Dataset

API Dataset

Email Dataset

Mobile Phone Dataset

Company Dataset

Job Posting Dataset

Commentary

Person

• Work Emails: We’ve added over 3M valid work emails in our database, resulting in a ~2% increase in work_email coverage.
• We also removed a source of emails that was contributing to high duplication / low quality emails across the dataset.

Company

• Company “Affiliated Profiles”: We updated the logic used to populate the legacy affiliated_profiles field to better match user expectations (note: this is different from the new affiliated_entities field).
• The list of affiliated profiles now includes all known related company IDs of each company, including every ultimate parent, immediate parent, direct subsidiary, or indirect subsidiary.

🛠 Improvements and Bug Fixes

Improvements

• School Canonicalization: We identified several schools with generic names that were canonicalizing to the wrong school record. We implemented a rollback with stop gaps to prevent common school names from standardizing to incorrect school entities.
• Certification Abbreviations in Names: We expanded the list of certifications to drop in our name cleaners so common abbreviations are removed (Joe Smith, CENG).
• Company “Affiliated Profiles”: We updated the logic used to populate the legacy affiliated_profiles field to better match user expectations (note: this is different from the new affiliated_entities field). The list of affiliated profiles now includes all known related company IDs of each company, including every ultimate parent, immediate parent, direct subsidiary, or indirect subsidiary.

Bug Fixes

• Education School Raw: There was a bug that was causing many Linkedin URLs to appear in the edcuation.school.raw field that has been fixed and has restored the field to our per-canonicalized text school values.
• Locations: We identified a bug that was causing some duplication in our locations database. The bug fix resulted in several duplicated locations collapsing in the possible_location fields, which we have now removed.
• Inferred Years Experience: We fixed a bug that was double counting years of experience for overlapping experience objects leading to inflated inferred_years_experience for some records.