Welcome to our November 2025 release notes!

Check out the updates below to stay up to date!

Here’s what’s new:

• 📧 Email Deliverability Improvements: Continued work to lower bounce rates and improve match rates for our top-level emails
• Improved Company Facebook / Meta Profile Resolution: We split Facebook & Meta into two distinct company profiles
• 📊 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

❗Breaking Changes (Going Live This Month)

• ❗ Final Sunset: Query Builder & API Explorer Tools

✨ New Products and Features

• Email Deliverability Improvements (Person)
• Improved Facebook / Meta Profile Resolution (Company)

🚀 Data Updates

• Freshness
• Job Changes
• Coverage
• Commentary

🛠 Improvements and Bug Fixes

• Improvements
• Bug Fixes

❗Breaking Changes (Going Live This Month)

❗ Final Sunset: Query Builder & API Explorer Tools

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

At the end of this month, we are 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:

• 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 30, 2025 - Legacy tools fully removed

Action You Need to Take

• Continue 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

Email Deliverability Improvements (Person)

📘

Email Deliverability Guide

For an in-depth guide on these changes and how to take advantage of these improvements, please see this customer guide prepared by our Solutions Engineering Team:

Email Deliverability Improvements

What’s New

This month we’ve continued to validate the deliverability status of our top-level email fields (recommended_personal_email and work_email).

Non-deliverable emails have been 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.

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.

🏬 Improved Facebook / Meta Profile Resolution (Company)

What’s New
This release splits Facebook and Meta into separate company profiles and work experience. Previously, we had logic to combine these together as a single entity, and this change standardizes the logic to be consistent with that used for other corporate entity relationships (e.g., Google and Alphabet).

Meta Example Record

{
  "id": "RjhjJnYUCiAfXFyxCHLDQQ5opPrK",
  "display_name": "Meta",
  "employee_count": 90447,
  "website": "meta.com",
  "ticker": "META",
  "mic_exchange": "xnas",
  "affiliated_profiles": [
    "pNX89m6UGXrHYyTaolvXwg5t5Dtg",
      ...
  ],
  "ultimate_parent": null,
  "immediate_parent": null,
  "direct_subsidiaries": [
    "pNX89m6UGXrHYyTaolvXwg5t5Dtg",
      ...
  ],
  "all_subsidiaries": [
    "pNX89m6UGXrHYyTaolvXwg5t5Dtg",
      ...
  ]
}

Facebook Example Record

{
  "id": "pNX89m6UGXrHYyTaolvXwg5t5Dtg",
  "display_name": "Facebook",
  "employee_count": 12485,
  "website": "facebook.com",
  "alternative_domains": [
    "facebook.com/careers",
    "meta.com"
  ],
  "affiliated_profiles": [
    "RjhjJnYUCiAfXFyxCHLDQQ5opPrK"
  ],
  "ultimate_parent": "RjhjJnYUCiAfXFyxCHLDQQ5opPrK",
  "immediate_parent": "RjhjJnYUCiAfXFyxCHLDQQ5opPrK",
  "direct_subsidiaries": [
    "nqLYBErZDf7t2Kydtrww3wBz3hgZ",
      ...
  ],
  "all_subsidiaries": [
    "nqLYBErZDf7t2Kydtrww3wBz3hgZ",
      ...
  ]
}

🚀 Data Updates

Freshness

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

Coverage

Monthly (v31.2 → v32.0)

Resume Dataset

API Dataset

Email Dataset

Mobile Phone Dataset

Company Dataset

Job Posting Dataset

Commentary

• Person
  • We began receiving Linkedin ID from one of our sources, contributing to the increase in fill rates for profiles.id and linkedin_id.

🛠 Improvements and Bug Fixes

Improvements

• Reduce Count of “Escape Characters” in Company Names
  • We've identified and removed ~16k (>90%) escape characters from company names. Due to some nuances in how we build our company data, there are still some that remain, but we suspect that active projects this quarter may be able to remove these entirely.

Bug Fixes

• LIMIT in SQL queries
  • If a LIMIT clause was used in a Person or Company Search SQL query it was unintentionally overriding the size parameter in some circumstances. It now throws a 400 error as expected.
• Fix Location Selection Logic
  • We fixed an issue in our location selection logic that was causing a previous location to be selected for some records.