July 2026 Release Notes

• 🍟 PDLScores™ GA Launch: Our secret sauce fields are now publicly available, go ahead - have a taste.
• 🔮 Technology Data Fields: Signals into which tech stacks, platforms, service, tools and technologies a company may be using.
• 📈 Job Posting Improvements: Expanded coverage, improved data quality, and new industry fields!
• 🔧 Data Quality & Coverage Improvements: Smarter primary job selection, more GitHub data, and a variety of education data improvements.
• 📊 Freshness Updates: This past month, we refreshed 37M+ resume experiences, 40M+ locations, and detected 3M+ job changes across our global dataset

​

📣 Announcements

​

✨ Release Updates

​

PDLScores™ GA Launch

• profile_score: Indicates whether a profile appears to represent a real person
• activity_score: Indicates whether a profile appears to be actively maintained

• profile_score_factors
  • attribute_fill_rate
  • profile_age_months
  • has_valid_url
  • meets_connection_threshold
• activity_score_factors
  • connection_change
  • profile_change
  • months_since_last_end_resume

​

Technology Data Fields

{
  "technologies_used": [
    {
      "product_id": "aV8mYR0sZFCrWvdkco07nwi7tGTt",
      "name": "Databricks",
      "num_job_posting_mentions": 11,
      "num_resume_mentions": 4
    },
    {
      "product_id": "ZNJNyjIICYIBrhIOyxG5iQfQvzLt",
      "name": "Apache Spark",
      "num_job_posting_mentions": 6,
      "num_resume_mentions": 5
    }
  ]
}

• Technologies used helps you understand a company’s tech stack for lead qualification, recruiting, investment sourcing, or product adoption analysis.
• Technology mention counts provide additional context from our proprietary job posting and resume data.

​

Job Posting Data Improvements

• Expanded Coverage
  We now track over 400,000 unique company career pages (up from 86,000), resulting in over 100,000 unique companies with active job posts (up from 60,000).
• Higher Description Fill Rates
  We dramatically reduced the number of job posts with null description fields - we now have >99% fill rate for active job posts.
• Reduced Duplicate Postings
  We made significant upgrades across our sourcing process to reduce the number of duplicate and low-quality records.
• More Accurate Deactivation Dates
  We improved the accuracy of our deactivated_date field to reduce the number of stale and outdated job posts in our dataset.
• Added Company Industry Fields
  We added new company industry (see release update below) fields to our job posting records, making it easier to search and filter job posts by company industry.

• Daily and Monthly Job Posting Data Licenses
• Job Posting Search API
• Job Posting Insights, available through the Company Data Field Bundles

​

Job Posting Industry Fields

{
  "id": "ARasmflDTd4",
  "company_industry": "computer software",
  "company_industry_v2": "software development"
}

​

🚀 Data Updates

​

Freshness

​

Job Changes

​

🌐 Coverage

​

Monthly Highlights (v34.2 → v35.0)

​

Commentary

• Person Data
  • This month we saw a 59% increase in github-related fields in our resume slice.
  • This month we saw a 6% decrease in our fill rate for work_email in our resume slice as result of our continued work to improve the deliverability of our email fields
• Company Data
  • We now have coverage of technology data for over 6.3M companies with the launch of our new Technology Data fields this month
  • We saw a 65% increase in our coverage of job posting related fields for our company data this month as a result of our broader Job Posting improvements described above..
• Job Posting Data
  • This month we saw a 65% increase in the number of unique companies as a result of our broader Job Posting improvements described above.

​

🛠 Improvements and Bug Fixes

​

Improvements

• Improved Primary Experience Selection
  • We improved our selection logic for a profile’s primary (current) work experience by prioritizing full time employed roles over board member and advisory roles.
• Industry Fields added to Job Posting Search API
  • The company_industry and company_industry_v2 fields have been added as parameterized field filters to the Job Posting Search API. This update allows you to query the Job Posting API based on industry with cleaned and standardized inputs.
• Better Name Cleaning
  • We updated our name-cleaning rules to allow valid profile names containing common English words (such as “cable”, “power”, “book”, etc).
• Improved Education Date Validation
  • We removed education start and end dates where the recorded time span was greater than 15 years.
• Refined CXO Title Tagging
  • We updated our executive-level tagging to prevent job titles containing phrases like “Office of the CEO” from being classified as cxo-level positions.
• Updated School ID Format
  • We standardized school IDs to end in _0000 instead of _0 for greater consistency across the person dataset. Characters preceding the suffix remain unchanged.
  • Example:
    • Previous: 5Ic6qaBcxe2DlWHRIVFnZg_0
    • New : 5Ic6qaBcxe2DlWHRIVFnZg_0000

​

Bug Fixes

• Duplicate Experience Summaries
  • We cleaned up millions of duplicated summaries caused by experience start and end dates being incorrectly parsed.
• Incorrect Experience Merging
  • We fixed an issue where separate experience records with similar job titles could be incorrectly merged into a single record
• Lingering End Dates for Current Roles
  • We fixed a bug where the end date for a current role was not being correctly updated if it was added then removed at a later time
• Duplicate Education Records
  • We fixed an issue where matching education objects were not being properly merged resulting in duplicate education records
• Phantom School Names
  • We corrected an issue where some profiles were being associated with incorrect schools. This was due to some education records referencing old LinkedIn URLs that were previously associated with different schools.
• Inaccurate Locations
  • We corrected the location data for profiles that were not being assigned to San José, Costa Rica (and were instead being assigned to locations like “United States Air Force Academy, Colorado” or “San Jose, California”)