# April 2021 Release Notes Source: https://docs.peopledatalabs.com/changelog/april-2021-release-notes | Release Name | Dataset Version | Publish Date | | :----------- | :-------------- | :----------- | | April 2021 | `v14.0` | 04/01/2021 | *Released on 4/1/2021* **DEPRECATION NOTICE -- v4 API ENDPOINT** We released the v5 person/enrich API endpoint in [July of 2020](/changelog/q2-2020-release-notes). We will **end of life** the v4 person/enrich and person/bulk endpoints during our **October 2021** release. We will end support and maintenance for the v4 endpoint in July 2021. We’ll continue to push new data updates to the v4 endpoint until the End of Life date.\ Please reach out to your Customer Success team at PDL if you have any questions or need assistance with the migration. **DEPRECATION NOTICE -- Canonical Company Data** We are continuing to put the "canonical" location, school, and company files in s3://pdl-prod-schema. We expect to deprecate school.jsonl, location.jsonl, and company.jsonl files at the end of this year, while providing this relational data via complimentary access to our [Cleaner Endpoints](/docs/cleaner-apis) for all customers. ### Data Field Changes #### [Person Schema](/docs/fields) | Field Name | Field Type | Field Description | Change in v14 | | :--------------- | :------------ | :------------------------------------------------------- | :-------------- | | personal\_emails | List (String) | An array of all personal emails associated with a person | New field added | ### Freshness This quarter, we made great strides in updating our datasets and have updated job titles for over **315mm** of our global profiles and locations for over **344mm**. We also updated jobs for **88mm** of our United States profiles and locations for **95mm**. Most of the profiles with updated jobs have had their full resume refreshed, not just their current job. ### Coverage We are continuing to make strides to link more PII to our core datasets. See some highlights below and click the links on each slice to see the full set of stats for each. #### [API Dataset](/docs/stats) | Linkage | Previous Release | Current Release | Increase (%) | | :------------ | :--------------- | :-------------- | :----------- | | mobile\_phone | 289,313,140 | 477,276,806 | 65.0% | | linkedin\_url | 593,796,114 | 664,266,786 | 12% | #### [Resume Dataset](/docs/resume-stats) | Linkage | Previous Release | Current Release | Increase (%) | | :--------------- | :--------------- | :-------------- | :----------- | | work\_email | 36,924,447 | 40,741,225 | 10.34% | | street\_address | 22,330,002 | 24,053,487 | 7.7% | | twitter\_url | 5,361,344 | 9,282,341 | 73.1% | | job\_start\_date | 137,762,454 | 201,804,179 | 46.49% | | mobile\_phone | 7,468,704 | 12,844,818 | 71.98% | #### [Email Dataset](/docs/email-stats) | Linkage | Previous Release | Current Release | Increase (%) | | :------------ | :--------------- | :-------------- | :----------- | | facebook\_url | 27,637,269 | 42,862,078 | 55.09% | #### [Mobile Phone Dataset](/docs/mobile-phone-stats) | Linkage | Previous Release | Current Release | Increase (%) | | :------------ | :--------------- | :-------------- | :----------- | | facebook\_url | 240,935,010 | 425,202,496 | 76.48% | ### Commentary * We’ve dramatically increased our mobile phone coverage by 72%. All of these new mobile phones are tied to a facebook URL and primarily bolster our global phone coverage. * We’ve also increased the linkage of mobile phone to resume data by 72%, from \~7.4mm to \~12.8mm * We’ve expanded the number of resumes in our person dataset, increasing the total size of our resume slice by \~10%, and increasing the fullness of our resume profiles. One metric for understanding the fill rates of our resumes is the **job\_start\_date** field, whose coverage increased \~45% ### Improvements * We’ve added the ability to [enrich profiles using MD-5 hashed emails](/docs/enrichment-api#email-hash) in our Enrichment API. These can be inputted in the **email\_hash** parameter. * Our canonical company coverage of our person dataset has improved from 65% to 69% * We added deduplication processes that increased the work email coverage and mobile phone coverage in our resume slice * Our internal data build/release were revamped to help us output more in each future release * We are launching an internal API usage analysis tool so our customer success team can help optimize API usage to reduce errors and help customers increase the likelihood scores they get back. * We will be releasing a new customer facing API dashboard at [peopledatalabs.com/main](https://peopledatalabs.com/main) ### Bug Fixes * We removed a data source with some inferred emails. * We added additional filtering to remove a small set of records with an abnormally large number of phones or addresses. * We fixed issues with foreign job title encoding ## April 1, 2021 Self-Serve API Changes We hope you’ve been getting tremendous value from your People Data Labs experience to date. Firstly, we wanted to thank you for being a PDL customer and for utilizing our Pay as you Go API services via our Self Service. Originally, our Pay as you Go model was intended to support low volume usage and encourage people to try out our product without committing to an annual subscription. While we believe that this has been successful, we also believe that it is no longer serving the needs of our customers in the best way possible. As a result of that,we will be deprecating this option and replacing it with a monthly committed package model starting on April 1, 2021. In conjunction with that change, we’ll also be releasing a new API dashboard that includes public access to our Person Search and Company Enrichment endpoints. What does this mean for you? If you would like to continue using PDL data past March 31st, 2021, you will need to select one of our monthly-committed API packages based on what your needs are. Of course, we don’t want to break your existing application, so on April 1st you’ll lose unlimited access, but we’ll grant you a one-time additional 5,000 matches towards our person enrichment API for free. Think of this as a bridge that will get you started on our new monthly, pre-paid, package. We encourage you to visit your API dashboard and choose your committed package if you’d like to continue using PDL -- this is very important. The minimum committed package will continue to be \$.25 a match and will require a 1,000 match / month minimum commitment. However, a committed model will allow us to provide higher discounted tiers at 2,500 and 5,000 committed matches monthly, which many of our Pay as you Go customers have already been hitting consistently over time. If you have any questions, feel free to reach out to us. We’re committed to making this as smooth of a transition as possible. # April 2022 Release Notes Source: https://docs.peopledatalabs.com/changelog/april-2022-release-notes-v18 | Release Name | Dataset Version | Publish Date | | :----------- | :-------------- | :----------- | | April 2022 | `v18.0` | 03/29/2022 | *Person v18.0 was released on 3/29/2022 and Data License deliveries will begin on 4/4/2022.* Welcome to our April 2022 release notes! One quarter into the new year and we have a ton of exciting updates to share! Here are some of the key highlights: * The long-awaited [field updates](#field-updates): **O\*NET Title Tags** and **NAICS/SIC Industry codes** are finally here! * [Person Retrieve API](#person-retrieve-api-credit-usage-updates) now supports new workflows for maintaining fresh data! * New [Javascript SDK](#javascript-sdk) for all our awesome JS devs out there! * [Two exciting new integrations](#integrations): Snowflake and Make (formerly Integromat) * [An early preview of some upcoming improvements to our self-serve subscription plans](#upcoming-subscription-plan-updates) * [Over 228 million jobs and 209 million locations](#freshness) have been updated this past quarter and [tons of new linkages between emails and contact information](#commentary)! Excited yet? Read on to learn more, or jump to a specific section using the table of contents below. *** ## 📣 Key Announcements ### Deprecations #### ❗️DEPRECATION NOTICE – Rate Limiting and Credit Usage Headers In the next quarterly release (v19 - July 2022), PDL will be deprecating the current functionality of the [header response fields](/docs/rate-limiting) . Instead, the headers will be updated (as shown below) in order to improve the alignment between the values returned by header fields and the values reflected in the API dashboard. The updated schema will be as follows: ``` { "x-ratelimit-reset": 2022-02-23T20:19:55Z, \# Flask "x-ratelimit-remaining": { 'minute': 1200, 'day': 12000, 'month': 120000 } \# Flask "x-ratelimit-limit": { 'minute': 1201, 'day': 12001, 'month': 120001 } "x-lifetime-used": 984152, "x-totallimit-remaining": 1342, “x-totallimit-spent”: 1, "x-totallimit-purchased-remaining": 342, "x-totallimit-overages-remaining": 1000, } ```
| Header Field | Description | Example | | :--------------------------------- | :---------------------------------------------------------------------------------------------------------------------- | :---------------------- | | `x-ratelimit-reset` | The UTC timestamp at which the rate limit will reset | `2022-02-23T20:19:55Z,` | | `x-ratelimit-remaining` | A collection of fields describing the number of credits remaining over a subsequent time period based on the rate limit | | | `x-ratelimit-remaining.minute` | The number of credits available to be used in the next minute | 1200 | | `x-ratelimit-remaining.day` | The number of credits available to be used in the next day | 12000 | | `x-ratelimit-remaining.month` | The number of credits available to be used in the next month | 120000 | | `x-ratelimit-limit` | A collection of fields describing the maximum number of credits that can be used in a given time period | | | `x-ratelimit-limit.minute` | The maximum number of credits that can be used in a minute | 1201 | | `x-ratelimit-limit.day` | The maximum number of credits that can be used in a day | 12001 | | `x-ratelimit-limit.month` | The maximum number of credits that can be used in a month | 120001 | | `x-lifetime-used` | The total number of credits that have been used over an account’s lifetime | `984152` | | `x-totallimit-remaining` | The total number of credits available to consume (purchased + overages) | `1342` | | `x-totallimit-spent` | Number of credits billed for this call. | `1` | | `x-totallimit-purchased-remaining` | The number of purchased credits remaining | `342` | | `x-totallimit-overages-remaining` | The number of overage credits remaining | `1000` | Please reach out to your Customer Success Team if you have any questions or concerns about migrating to the new headers.
### Schema Changes In this release, PDL is officially introducing support for 2 industry-standard codes: 1. O\*NET Occupational Codes 2. NAICS / SIC Industry Classification Codes Support for these standards has been heavily requested, and we are very excited to begin the rollout of these fields! The schema additions are below, and check out the [Field Updates](#heading=h.6h1qhstzfkrf) section below for more details as well as information on how to access these new data fields. #### O\*NET Occupation Codes ([Person Schema](/docs/fields#premium-resume-fields)) | Field Name | Field Type | Field Description | Example | | :----------------------------- | :--------- | :------------------------------------------------------------------------------------------------------------------------------------------------------------------- | :------------------------- | | `job_onet_code` | `String` | The 6-digit O\*NET code for a person’s current job title, [following the 2018 SOC guidelines](https://www.bls.gov/soc/2018/soc_2018_class_and_coding_structure.pdf). | ”11-1011.00” | | `job_onet_major_group` | `String` | The O\*NET Major Group associated with a person’s current job title. | ”Management Occupations” | | `job_onet_minor_group` | `String` | The O\*NET Minor Group associated with a person’s current job title. | “Top Executives” | | `job_onet_broad_occupation` | `String` | The O\*NET Broad Occupation category associated with a person’s current job title. | “Chief Executives” | | `job_onet_specific_occupation` | `String` | The O\*NET Detailed Occupation category associated with a person’s current job title. | “Chief Executives” | | `job_onet_title` | `String` | An O\*NET Alternative Title associated with a person’s current job title. | “Chief Technology Officer” |
#### NAICS / SIC Industry Classification Codes ([Company Schema](/docs/company-fields#base-company-fields)) | Field Name | Field Type | Field Description | Example | | :------------------------ | :--------- | :----------------------------------------------------------------------------------------------------------------------------------------------------------- | :------------------------------------------- | | `naics` | `Object` | An object containing the [NAICS](https://en.wikipedia.org/wiki/North_American_Industry_Classification_System) industry information associated with a company | | | `naics.naics_code` | `String` | The NAICS code associated with a company’s industry classification | “111110” | | `naics.sector` | `String` | The NAICS sector associated with a company’s industry classification | “agriculture, forestry, fishing and hunting” | | `naics.sub_sector` | `String` | The NAICS subsector associated with a company’s industry classification | “crop production” | | `naics.industry_group` | `String` | The NAICS industry group associated with a company’s industry classification | “oilseed and grain farming” | | `naics.naics_industry` | `String` | The NAICS industry associated with a company’s industry classification | “soybean farming” | | `naics.national_industry` | `String` | The NAICS national industry associated with a company’s industry classification | “soybean farming” | | `sic` | `Object` | An object containing the [SIC](https://en.wikipedia.org/wiki/Standard_Industrial_Classification) industry information associated with a company | | | `sic.sic_code` | `String` | The SIC industry code associated with a company’s industry classification | “5731” | | `sic.major_group` | `String` | The SIC major group associated with a company’s industry classification | “agricultural production - crops” | | `sic.industry_group` | `String` | The SIC industry group associated with a company’s industry classification | “cash grains” | | `sic.industry_sector` | `String` | The SIC industry sector associated with a company’s industry classification | “soybeans” | *** ## ✨ New Products and Features ### Field Updates The v18 (April 2022) quarterly release, we are officially introducing support for 2 heavily requested industry-standard codes to our data: 1. **O\*NET Occupation Codes** (supporting the [O\*NET v26.0](https://www.onetcenter.org/listings/26.0/updated.html) standard) have been added to our [Person Schema](/docs/fields#premium-resume-fields) as a new premium field bundle. 2. **NAICS/SIC Industry Classification Codes** have been added to our [Company Schema](/docs/company-fields#base-company-fields) as Base Company Fields.
#### O\*NET Job Title Codes Six new O*NET-related fields have been added to our Person Schema to support the industry standard for job role tagging. In this initial rollout, we have tagged a subset of the primary job objects across our resume records (meaning no O*NET coverage for historical job titles just yet). In the coming data releases, we will be launching improvements to this field to build increasing coverage across every O\*NET code. The O\*NET additions broaden the set of title classifications we have for our employment data (expanding on our current `job_role` and `job_sub_role` fields) and to better support customers building on top of census data. The O\*NET fields are available as a **premium field bundle** that can be added to any person data package to provide additional information on the existing primary job title. [See the updated schema here](/docs/fields#premium-resume-fields). To learn more about our new O\*NET fields or to request access please reach out to your Customer Success team.
#### NAICS/SICS To support more granular industry classification for companies in our Company Data, we have introduced [NAICS](https://en.wikipedia.org/wiki/North_American_Industry_Classification_System) and [SIC](https://en.wikipedia.org/wiki/Standard_Industrial_Classification) code. These fields will provide additional segmentation power and value to the PDL company data. Additionally, fields have been added to our [Base Company Fields](/docs/company-fields#base-company-fields), meaning that they are freely available by default to any customer. The Company Search API can also be leveraged to access NAICS and SIC codes, so users can filter and target companies in their search queries. [You can view the schema for these fields here](/docs/company-fields#base-company-fields). We encourage all our users to assess these new fields and share any feedback regarding quality and usefulness, you may have with your client team. This is just the beginning and we will continue to iterate and improve on these fields moving forward.
### Person Retrieve API Credit Usage Updates The [Person Retrieve API](/docs/person-retrieve-api) has been updated such that credits will now only be consumed when the API returns a record that has an update since the last time you called it. As a refresher, the Person Retrieve API is billed against your existing pool of person enrichment credits and allows you to pull down a record using a PDL ID as input.\ With this update, the Person Retrieve API can now be leveraged to refresh a record using the persistent PDL ID since the last time a user retrieved it via any API endpoint. PDL is currently updating \~100 million records with each monthly API rebuild, so this is a great way for customers to keep specific batches of profiles as fresh as possible.
### JavaScript SDK This past quarter, we released our first developer SDK! The [peopledatalabs-js](/docs/javascript-sdk) package is a streamlined PDL client to support our API users working with JavaScript. This library supports all of our current API endpoints and allows you to make API requests with just a single function call. We also wrote it using plain vanilla JS, meaning you can use this client for both code that runs in the browser as well as backend server code. This package can be downloaded and installed from the [npm package repository](https://www.npmjs.com/package/peopledatalabs) or directly cloned from its [public github repository](https://github.com/peopledatalabs/peopledatalabs-js). We made this library open source and we encourage anyone to submit issues, feature requests and pull requests. In the future, more SDKs will be released so please share any feedback you have with us!
### Integrations This past quarter, we officially launched 2 new integrations as well: 1. Snowflake 2. Make (formerly Integromat)
#### Snowflake Integration PDL is now live in the [Snowflake Data Marketplace](https://www.snowflake.com/data-marketplace/)! Customers can request to subscribe to our Person Dataset and openly access our free company dataset via Snowflake. This integration allows us to deliver data directly to Data License customers, and requires minimal additional setup for customers already using Snowflake for other purposes. If you are interested in our snowflake integration, you can request access by [searching for PDL in the Snowflake Data Marketplace](/docs/data-delivery-using-snowflake) or by speaking to your Customer Success team. We hope to build more integrations like these in the future, so please share any feedback you have with us as you test it out!
#### Make Integration A [new integration with Make (formerly Integromat)](https://www.make.com/en/integrations/people-data-labs) is now live! Make is a workflow automation tool that allows you to connect various apps together and seamlessly pass data between them. It is a no-code solution that allows you to build complex logic and pipelines for coordinating your apps and services together. Person and Company data can now be added directly into your automated workflows. [Sign up for access to our integration here](https://www.make.com/en/hq/app-invitation/851324c93c88059147b7111e3a513018), and as always, please share any feedback you have with us!
### Upcoming Subscription Plan Updates In the next few weeks, we will be rolling out several updates to our subscription plans for self-serve customers. As a preview, these changes will include: * Standardized pricing tiers across our products * An updated freemium tier with a renewing monthly allotment of free credits * The option to purchase annual subscriptions * Streamlined processes for upgrading and downgrading subscriptions We are excited about these improvements for our self-serve customers, so stay tuned for an official announcement via email soon! *** ## 🚀 Data Updates ### Freshness This quarter, we updated millions of jobs and locations in our [Global Resume Dataset](/docs/resume-stats). See below for details: | Dataset | Geography | Field | Records Updated | | :------ | :------------ | :----------- | --------------- | | Resume | Global | `experience` | 228,256,002 | | Resume | Global | `location` | 209,846,161 | | Resume | United States | `experience` | 76,269,414 | | Resume | United States | `location` | 84,521,983 |
### Coverage [Resume Dataset](/docs/resume-stats) | Linkage | Coverage in v17 | Coverage in v18 | Increase (%) | | :-------------------- | --------------- | --------------- | ------------ | | `total_records` | 684,434,661 | 700,613,882 | 2.36% | | `birth_year` | 8,478,127 | 10,254,962 | 20.96% | | `job_company_ticker` | 18,109,504 | 20,325,049 | 12.23% | | `street_addresses` | 25,582,324 | 28,318,775 | 10.70% | | `job_company_website` | 202,077,270 | 221,853,296 | 9.79% | [API Dataset](/docs/stats) | Linkage | Coverage in v17 | Coverage in v18 | Increase (%) | | :------------------- | --------------- | --------------- | ------------ | | `total_records` | 3,026,851,628 | 3,110,029,187 | 2.75% | | `personal_emails` | 586,232,294 | 661,722,011 | 12.88% | | `street_addresses` | 679,766,613 | 763,341,777 | 12.29% | | `job_company_ticker` | 20,278,340 | 22,696,445 | 11.92% | [Email Dataset](/docs/email-stats) | Linkage | Coverage in v17 | Coverage in v18 | Increase (%) | | :----------------- | --------------- | --------------- | ------------ | | `total_records` | 687,784,131 | 774,399,256 | 12.59% | | `street_addresses` | 248,611,221 | 348,804,217 | 40.30% | | `personal_emails` | 479,704,633 | 565,117,411 | 17.81% | | `mobile_phone` | 28,569,823 | 33,367,435 | 16.79% | | `birth_date` | 66,094,400 | 76,527,251 | 15.78% | | `gender` | 534,231,011 | 606,542,899 | 13.54% | | `full_name` | 687,784,131 | 774,399,256 | 12.59% |
### Commentary * Strong improvements to linkages in our Email slice, in particular: * Email \<> `street_addresses` linkages increased by 40.3% * Email \<> `mobile_phone` linkages increased by 16.8% * Email \<> `full_name` linkages increased by 12.6% * 11.9% increase in `job_company_tickers` across our entire dataset * Significant bump in `street_address` coverage across the board including a 17.1% increase in `street_address` \<> `job_title` linkages and 9.1% increase in `street_address` \<> `linkedin_url` linkages * The Person Dataset saw a 7.1% increase in coverage for `birth_year` *** ## 🛠 Improvements and Bug Fixes
### Improvements * Support for POST requests was added to our [Person](/docs/search-api#using-post-requests) and [Company](/docs/company-search-api#using-post-requests) Search APIs, allowing users to send large queries within their API requests. See examples requests here: [person search example](/docs/search-api#using-post-requests), [company search example](/docs/company-search-api#using-post-requests) * The limit for the number of ‘terms’ in input queries increased from 100 elements to 1,000 for all Person and Company Search APIs. * `job_title` matching was added to the Identify API, and is now supported as an input parameter. * The criteria for cleaning emails was relaxed in our dataset for increased coverage of temporary email domains to support fraud use cases. * The error response codes for the Bulk Enrichment API were improved for individual errors within a bulk enrichment request. The API will now always return a status code 200, with 400 errors nested appropriately within the response object
### Bug Fixes * Within the Company Search API, a bug that was preventing insights fields from being searchable * The Bulk Enrichment API no longer drops invalid input parameters and instead returns 400 status codes nested within the response object. * The Identify API will return an error code 400 when there are no inputs provided. * Error 400 codes are returned in the School and Company cleaners when invalid input parameters are sent. # April 2023 Release Notes Source: https://docs.peopledatalabs.com/changelog/april-2023-release-notes-v22 | Release Name | Dataset Version | Publish Date | | :----------- | :-------------- | :----------- | | April 2023 | `v22.0` | 04/04/2023 | *v22.0 was released on 4/4/2023.* Welcome to our April 2023 release notes! We’re rolling out some exciting updates with this release. Here are some of the key highlights: * Keep your data up to 3x fresher with PDL’s new monthly data license delivery service! * Automatically keep records up-to-date with our Person Retrieve Webhook, now available for API and Data License customers! * We’re making it easier than ever to contact leads with our `recommended_personal_email` field, now available in our Base Person Bundle! * Huge increases in parent & subsidiary company information! Excited yet? Read on to learn more, or jump to a specific section using the table of contents below. *** ## 📣 Key Announcements ### Recommended Personal Email in Base Person Bundle We launched the [recommended\_personal\_email](/docs/fields#recommended_personal_email) field to our Person Dataset in [v20](/changelog/october-2022-release-notes-v20#recommended-personal-email). This field is the statistically most likely deliverable personal email for a profile. When we ran deliverability tests on this field, it showed a **37% improvement in deliverability**. Previously, this field was in its own premium bundle. We are pleased to announce that the `recommended_personal_email` field will be moved from the Premium Bundle to the Base Person Bundle! There will be no changes made to the pricing of the Base Person Bundle, and we will continue to list additional emails in the [`emails`](/docs/fields#emails) field. The recommended email is chosen using a proprietary process that probabilistically correlates to higher deliverability, but is not guaranteed to be deliverable. We are continuing to improve our overall deliverability of this field and our other email fields by investing in our data sourcing efforts. ### Parent & Subsidiary Company Tagging Improvements In this release, we’ve updated our [company parent & subsidiary](/docs/company-schema#parents-and-subsidiaries) logic to increase the connections between companies that already exist as profiles in our company data. This change will increase the accuracy and coverage of the parent/subsidiary fields within our company records, which makes it more reliable for users to understand key relationships between matched profiles and easier for users to roll up the headcount or employee movement summaries of companies operating within larger corporate conglomerates. This change affects the fill rates in the [all\_subsidiaries](/docs/company-schema#all_subsidiaries), [direct\_subsidiaries](/docs/company-schema#direct_subsidiaries), [immediate\_parent](/docs/company-schema#immediate_parent), and [ultimate\_parent](/docs/company-schema#ultimate_parent) fields. Here’s a quick overview of our increased linkages: | | Old # | New # | % Increase | | :----------------------- | :----- | :----- | :--------- | | Companies with 1+ Parent | 32,193 | 81,353 | 152.7% | | Companies with 1+ Child | 9,121 | 29,362 | 221.9% | ### Person ID Length Upcoming Changes We will be adjusting the maximum character length of [PDL Persistent Person IDs](/docs/fields#id). We will be launching this change in **October** to allow for ample time to adjust any of your processes impacted by this change. Currently, IDs are 22 characters long. We recommend allowing for a **64 character maximum** for our IDs and will not have any IDs beyond this length, but in practice we expect the changes to result in IDs closer to 32 characters in length. Existing IDs will not change or change length. Only newly created IDs will have the new length. *** ## ✨ New Products and Features ### Monthly Data License Delivery Options Currently, PDL delivers Data Licenses on a quarterly cadence. We've had a number of customers request a more frequent Data License delivery cadence and we hear you! With this release, we are implementing **monthly delivery options** for Data License customers. Monthly deliveries will be directly tied to our monthly data build timelines, meaning we will be providing the freshest data we can to our customers. Monthly delivery options will be available at an additional cost for all of our global datasets, including Person and Company data! If you’d like to upgrade your Data License delivery, please [reach out to us](https://www.peopledatalabs.com/talk-to-sales). ### Retrieve Webhook for Data License Customers Last quarter ([V21](/changelog/january-2023-release-notes-v21)), we released the [webhook functionality](/docs/webhook-for-person-retrieve-api) for the [Person Retrieve API](/docs/person-retrieve-api). As a quick refresher, the webhook functionality enables customers to receive updated profiles automatically instead of periodically having to make hundreds of thousands of Retrieve API calls to keep their records up-to-date. With this release, we are expanding the webhook functionality to **Data License customers** who want a delta of IDs that have changed on a monthly basis. Functionally, the only difference in the webhook between API and Data License customers is which IDs will be pulled. For API customers, the webhook checks for updates to all person profiles accessed by calling the Person Enrichment, Person Search, and Person Identify APIs. For Data License customers, the webhook will check for updates to all person profiles included in the customer’s data pull query. If you’d like access, please [reach out to us](https://www.peopledatalabs.com/talk-to-sales). ### Person Enrichment & Preview API Support for PDL ID Input The [Person Enrichment API](/docs/person-enrichment-api) will now support PDL Persistent Person ID as an input parameter. Additionally, customers who use our Search or Enrichment Preview APIs can now choose to enrich their new records on ID as opposed to currently supported PII parameters. If you enrich on ID and anything else, only ID is used and the other inputs for matching are ignored. `pdl_id` | Type | Description | Example | | :----- | :-------------------------------------------------------------------------------- | :--------------------------- | | String | The [PDL Persistent ID](/docs/persistent-ids) for a record in our Person Dataset. | qEnOZ5Oh0poWnQ1luFBfVw\_0000 | *** ## 🚀 Data Updates ### Freshness This quarter, we updated millions of jobs and locations in our [Global Resume Dataset](/docs/resume-stats). See below for details: | Dataset | Geography | Field | Records Updated | | :------ | :------------ | :----------- | :-------------- | | Resume | Global | `experience` | 149,059,103 | | Resume | Global | `location` | 96,426,401 | | Resume | United States | `experience` | 49,852,494 | | Resume | United States | `location` | 40,190,936 | ### Coverage (Full Stats: [Person](/docs/datasets), [Company](/docs/company-stats)) [API Dataset](/docs/stats) | Linkage | Coverage in v21 | Coverage in v22 | Increase (%) | | :---------------- | --------------- | --------------- | ------------ | | Total | 3,137,752,354 | 3,161,998,162 | 0.77% | | personal\_emails | 683,676,725 | 708,085,315 | 3.57% | | street\_addresses | 784,304,951 | 803,791,775 | 2.48% | | phones | 1,140,318,222 | 1,150,823,707 | 0.92% | [Resume Dataset](/docs/resume-stats) | Linkage | Coverage in v21 | Coverage in v22 | Increase (%) | | :------- | :-------------- | :-------------- | :----------- | | `Total` | 732,702,622 | 741,406,022 | 1.19% | | `phones` | 44,881,015 | 54,048,415 | 20.43% | [Email Dataset](/docs/email-stats) | Linkage | Coverage in v21 | Coverage in v22 | Increase (%) | | :------- | :-------------- | :-------------- | :----------- | | `phones` | 292,736,432 | 310,472,440 | 6.06% | [Phone Dataset](/docs/phone-stats) | Linkage | Coverage in v21 | Coverage in v22 | Increase (%) | | :--------------- | :-------------- | :-------------- | :----------- | | work\_email | 21,710,227 | 28,850,007 | 32.89% | | personal\_emails | 222,133,824 | 234,147,898 | 5.41% | [Street Address Dataset](/docs/street-address-stats) | Linkage | Coverage in v21 | Coverage in v22 | Increase (%) | | :---------- | :-------------- | :-------------- | :----------- | | work\_email | 3,341,191 | 3,810,241 | 14.04% | [Developer Dataset](/docs/developer-stats) | Linkage | Coverage in v21 | Coverage in v22 | Increase (%) | | :--------------- | :-------------- | :-------------- | :----------- | | work\_email | 241,862 | 288,563 | 19.31% | | personal\_emails | 338,597 | 374,996 | 10.75% | [Company Dataset](/docs/company-stats) | Linkage | Coverage in v21 | Coverage in v22 | Increase (%) | | :------------------- | --------------- | --------------- | ------------ | | Total | 22,876,457 | 28,212,381 | 23.33% | | all\_subsidiaries | 9,121 | 29,362 | 221.92% | | direct\_subsidiaries | 9,121 | 29,362 | 221.92% | | immediate\_parent | 32,193 | 81,353 | 152.70% | | ultimate\_parent | 32,193 | 81,353 | 152.70% | ### Commentary * Significant increases in contact information linkages across all person datasets * `work_email` and `personal_emails` linkages increased in all, most notably work\_email increased by 33% in in the phone dataset * `phones` linkages in the resume dataset increased by 20% * Added 9.7 million profiles to the resume dataset * Added 4.8 million profiles to the company dataset (23% increase) *** ## 🛠 Improvements and Bug Fixes ### Improvements * Added [Company HQ by country stats](/docs/company-countries) to our build process & docs. * Previously, if a company did not have a value in an insights field, that field would be missing from the response. Now, all fields will populate with any blank values shown as `None`. * Removed inappropriate words or phrases from our titles and skills. ### Bug Fixes * Resolved instances where end date is before start date in the experience object. * Continued reduction of LinkedIn URL duplication across profiles by improving our resolving logic for nicknames (Richard → Rick). * Fixed non-canonical values appearing in the `size` field for certain companies in our company dataset. * Resolved instances where certain signifiers would incorrectly be parsed as first or last names. For example, fixed ‘CSPO’ appearing as a last name. # April 2024 Release Notes Source: https://docs.peopledatalabs.com/changelog/april-2024-release-announcement-v260 | Release Name | Dataset Version | Publish Date | | :----------- | :-------------- | :----------- | | April 2024 | `v26.0` | 04/02/2024 | *v26.0 was released on **April 2, 2024**.* Welcome to our April 2024 release notes! We’re rolling out some exciting updates with this release. Here are some of the key highlights: * Significant improvements in our coverage mobile phone numbers * Better insight into job freshness with our new [Resume Timestamp fields](#new-resume-timestamps-person-schema) * New [employee count by role aggregations](#employee-count-by-role-fields-company-schema) in our Company dataset * An important breaking change to our [person.gender field](#rename-persongender-to-personsex-person-schema) * Significant updates to our [IP data and matching logic](#-improvements-and-bug-fixes) to help with reliability and accuracy * An open solicitation for customer feedback to improve our [Role and Sub\_Role tagging](#role-and-sub_role-updates) * [Over 128 million jobs and 230 million locations have been updated](#freshness) this past quarter! Excited yet? Read on to learn more, or jump to a specific section using the table of contents below. *** ## 📣 Key Announcements ### Schema Updates #### Rename `person.gender` to `person.sex` ([Person Schema](/docs/fields)) Note this is a breaking change - please see the [breaking changes](#breaking-changes) section for previous announcements As a reminder, with the v26.0 release, we are renaming the `person.gender` field to `person.sex` in the Person Schema. **The output of the field will remain the same**, as shown in the example record below: **Example PDL Record - v26.0** ``` "id": "qEnOZ5Oh0poWnQ1luFBfVw_0000", "full_name": "sean thorne", "first_name": "sean", "middle_initial": "f", "middle_name": "fong", "last_initial": "t", "last_name": "thorne", "sex": "male", -> renamed from gender ... ``` This change is required to demonstrate adherence with legislative changes defining aspects of gender as sensitive personal data (which PDL does not process or output). For help moving over to the new field, please reach out to your Customer Success team for support and enablement resources. Please also see this easy-to-follow guide prepared by our Technical Services team for instructions on how to transition to this new schema: [Breaking Change Guide: Field Rename from Gender to Sex.pdf](https://drive.google.com/file/d/1lPgywDeI829oaFM5sh_6rYPlotTaD_cb/view?usp=sharing)
#### New Resume Timestamps ([Person Schema](/docs/fields)) This change is associated with a deprecation of our current `job_last_updated` field in the Person Schema as part of the July 2024 (v27.0) release. See the [Deprecation announcement](#heading=h.e2coxhmk18co) for additional details. This quarter, we are excited to announce the launch of two new fields in our Person Schema: `job_last_changed` and `job_last_verified`. | Field Name | Data Type | Field Description | Example | | :------------------ | :-------------------------------------- | :-------------------------------------------------------------------------------------------------- | :--------------------------------- | | `job_last_changed` | [String (Date)](/docs/data-types#dates) | The timestamp that reflects when the top-level job information changed. | `"job_last_changed": "2023-10-04"` | | `job_last_verified` | [String (Date)](/docs/data-types#dates) | The timestamp that reflects when the top level job information was last validated by a data source. | `"job_last_updated": "2024-01-05"` | These new fields contain timestamps associated with the top-level job on a profile (i.e. the most current experience) and provide additional clarity and granularity on the freshness of a person’s current work experience. These new fields are now included in all Person data records, and are immediately available to all PDL users who have access to our job information. These two timestamps are intended to replace the existing timestamp field, `job_last_updated`, which will be deprecated in v27.0. **Any customers currently using the `job_last_updated` field should transition to the new `job_last_changed` and `job_last_verified` fields over this next quarter.** **Sample Response:** ```javascript JavaScript theme={null} { "status": 200, "likelihood": 10, "data": { "id": "qEnOZ5Oh0poWnQ1luFBfVw_0000", "full_name": "sean thorne", "first_name": "sean", "middle_initial": "f", "middle_name": "fong", "last_initial": "t", "last_name": "thorne", "gender": "male", ... "job_company_name": "peopledatalabs", ... "job_last_updated": "2022-09-07", -> current field, deprecated in v27.0 "job_last_verified": "2022-09-07", -> new field "job_last_changed": "2022-06-01" -> new field } ``` **Limitations of Observed Data** The job\_last\_changed timestamp reflects the date when the information was observed in our data sources, which can contain a lag time compared to real-life events. For more information see: [`last_updated` Field](/docs/last_updated-field) **Limitations of Observed Data**\ While these new fields are intended to provide more reliable information on the freshness of our person profiles, they still only reflect observed data. This means that these timestamps will reflect the date when updates were propagated into our data build from our data sources, and may contain some lag time compared to real-life events. For example, if User A changed their job on October 1, 2023, but did not update that publicly until December 1, 2023, our timestamp for `job_last_changed` will be December. For support transitioning off of the job\_last\_updated field and onto our newly released resume timestamp fields, please see this guide prepared by our Technical Services team: [Breaking Changes Guide *Deprecation of job*last\_updated.pdf](https://drive.google.com/file/d/1tP-u9D1QKpPRg79GaMN4zc1Zlfmk5QJi/view?usp=drive_link)
#### Employee Count By Role Fields ([Company Schema](/docs/company-schema#funding-data)) We are excited to share that 2 new fields have been added to our company schema as of our v25.2 release: These fields are now also live in the [PDL Salesforce Integration](/docs/salesforce-integration) | Field Name | Data Type | Field Description | | :-------------------------------------- | :--------------------------------- | :--------------------------------------------------------------------------------------------- | | `employee_count_by_role` | `Object` | The number of employees (INT) by Job Role on the final day of the most recent month. | | `employee_growth_rate_12_month_by_role` | [`Object`](/docs/data-types#dates) | The twelve month rate of change (FLOAT) by Job Role on the final day of the most recent month. | Examples (click to expand): | FIELD NAME | EXAMPLE | | :-------------------------------------- | :------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `employee_count_by_role` | `"employee_count_by_role": { "real_estate": 0, "design": 2, "trades": 0, "marketing": 4, "education": 4, "legal": 0, "customer_service": 10, "finance": 6, "public_relations": 1, "engineering": 24, "human_resources": 3, "media": 1, "sales": 12, "operations": 10, "health": 0 }` | | `employee_growth_rate_12_month_by_role` | `"employee_count_by_role": { "real_estate": 0, "design": 2, "trades": 0, "marketing": 4, "education": 4, "legal": 0, "customer_service": 10, "finance": 6, "public_relations": 1, "engineering": 24, "human_resources": 3, "media": 1, "sales": 12, "operations": 10, "health": 0 }` | These fields provide quick access for our customers to the most recent department/role headcounts for companies without the need to un-nest this information from our insights data. Customers using our [Salesforce Integration](/docs/salesforce-integration) in particular may find these new fields especially valuable, making it possible to now assign role tags and department growth rates to customer accounts directly within the integration. Both of these new fields have been added to the existing Premium and Comprehensive Company Data Bundles and are immediately available to customers with these bundles. #### Role and Sub\_Role Updates In our October release (v28.0) we will be making significant changes to our job\_title\_role and job\_title\_sub\_role enum values in order to improve our tag fill rates and improve the categories we use to represent titles. We’ll be posting a formal breaking change notice and updated canonical values alongside the v27.0 release. **If you’d like to get a preview and/or give feedback on the taxonomy please reach out to your Customer Success Manager. We are currently soliciting feedback on our existing taxonomy and a draft of the new taxonomy.** *** ## ❗Breaking Changes (Going Live This Month) ### Rename `person.gender` to `person.sex` **Previous Announcements: [v24 / October 2023](/changelog/october-2023-release-notes-v24#rename-gender), [v25 / January 2024](/changelog/january-2024-release-notes-v25#rename-gender)** We have renamed the [gender field](/docs/fields#gender) to sex in the Person Schema. The [output](/docs/genders) will remain the same. We output the biological sex of a profile, but not their gender as defined in applicable legislation. This change is required to demonstrate adherence with legislative changes defining aspects of gender as sensitive personal data (which People Data Labs does not process or output). **Example PDL Record - v26.0** ``` "id": "qEnOZ5Oh0poWnQ1luFBfVw_0000", "full_name": "sean thorne", "first_name": "sean", "middle_initial": "f", "middle_name": "fong", "last_initial": "t", "last_name": "thorne", "sex": "male", -> renamed from gender ... ``` For help moving over to the new field, please reach out to your Customer Success team for support and enablement resources. Please also see this easy-to-follow guide prepared by our Technical Services team for instructions on how to transition to this new schema: [Breaking Change Guide: Field Rename from Gender to Sex.pdf](https://drive.google.com/file/d/1lPgywDeI829oaFM5sh_6rYPlotTaD_cb/view?usp=sharing) ### Company ID Format Changes **Previous Announcements: [v25 / January 2024](/changelog/january-2024-release-notes-v25#company-id)** **Change to Format**\ While the field name (“id”) and data format (string) remain the same as before, **PDL’s Company IDs will now have an alphanumeric hash format similar to our Person IDs**. **The Company ID for the People Data Labs record** | v25.2 | v26.0 | | :------------------------- | :--------------------------------------- | | `"id":` `"peopledatalabs"` | `"id":` `"tnHcNHbCv8MKeLh92946LAkX6PKg"` | **Old ID Shortcomings**\ For v25.2 and prior releases, the Company ID for each company record was generated from the profile’s most recent LinkedIn URL. This created barriers to serving as a reliable ID for updating and managing profiles over time, as LinkedIn URLs can change when a company changes their name, companies can edit their LinkedIn URL at any point, and old LinkedIn URLs may be reused by new companies in the future. **Benefits of the New IDs**\ While **the new format Company IDs are not persistent IDs**, they were designed in a manner intended to undergo fewer changes than the previous LinkedIn URL slug-defined format. In addition, since the new Company IDs are generated independent of LinkedIn URLs, we can now add companies to our dataset that do not have an associated LinkedIn profile. **Handling the Changes**\ There are a few things we’ve planned to to help make the transition as smooth as possible: **The ID field name and datatype are the same as before** * Neither the field name (“id”) nor the datatype (string) of the ID field are changing, so any queries, joins, or other code references to that field should continue to function as they did previously. **The old ID exists in a new field called `linkedin_slug`, which is still used in enrichment matching** * If you’ve stored past company IDs and would like to use those as Company Enrichment inputs, the old ID field still exists under the new field name `linkedin_slug`, generated using the exact same logic as our old IDs. * In addition, as of the v26.0 release, Company Enrichment queries using the [`pdl_id`](/docs/input-parameters-company-enrichment-api#pdl_id) field will match against both the `id` or `linkedin_slug` fields to help maintain backwards compatibility. **Mapping of v26.0 Company ID to LinkedIn Slug (prior ID format)** **Only for v26.0** This is a one-time file that we have created specifically for the v26.0 release. We will not be maintaining this file in future releases. Please reach out to your Customer Success team for access to this resource and additional support material. * We have created a map of v26.0 Company `id` mapped to `linkedin_slug` that we can provide to users to support their transition to the new Company IDs. * The format for this file is: | display\_name | linkedin\_slug | id | | :--------------- | :------------- | :--------------------------- | | People Data Labs | peopledatalabs | tnHcNHbCv8MKeLh92946LAkX6PKg | | Google | google | aKCIYBNF9ey6o5CjHCCO4goHYKlf | | … | | | **PDL Record - v25.2** ``` "name": "people data labs", "id": "peopledatalabs", -> linkedin_slug format in v25.2 "linkedin_url": "linkedin.com/company/peopledatalabs" "linkedin_slug": "peopledatalabs" ``` **PDL Record - v26.0** ``` "name": "people data labs", "id": "tnHcNHbCv8MKeLh92946LAkX6PKg", -> alphanumeric format in v26.0 "linkedin_url": "linkedin.com/company/peopledatalabs" "linkedin_slug": "peopledatalabs" ``` ### ⚠️ Upcoming Breaking Changes **Upcoming Breaking Changes** **Upcoming breaking changes** in future versions may impact your current processes. We are announcing them here to provide ample time for you to adjust your processes accordingly. #### ⚠️ Snowflake Schema Standardization Change expected in: **v26.1 / May 2024**\ Previous Announcements: [v24 / October 2023](/changelog/october-2023-release-notes-v24#snowflake), [v25 / January 2024](/changelog/january-2024-release-notes-v25#snowflake), [v25.1 / February 2024](/changelog/february-2024-release-announcement-v25-1) As announced in our previous release notes (linked above) we will be standardizing our Snowflake Person and Company Schemas in May 2024 (v26.1). This is a reminder that this change will be a breaking change to our existing Snowflake schema. To prepare for this transition, we strongly encourage our snowflake customers to follow the steps below: 1. Make a copy of your current data after your April 2024 delivery. This way you not only have a backup, but can also compare new to old after you switch over. 2. Go through the new standard schemas, which are included in the Resources section below as well as here 3. Prepare any script changes to your existing processes before the switch in May 2024. For any questions or help transitioning to these new schema, please reach out to your Customer Success Manager. *The Standard Person and Company Schemas that will be used for Snowflake deliveries are available [here](/docs/data-delivery-using-snowflake#standard-schemas).*
#### ⚠️ Deprecation of `person.job_last_updated` Change expected in: **v27.0 / July 2024** As part of our [new resume timestamps](#heading=h.i1m1gfwp71e6) that were released this quarter, we will be deprecating our existing `job_last_updated` field in the July 2024 (v27.0) release. Our newly released resume timestamps provide more granularity and clarity than our existing `job_last_updated` timestamp, and resolve ambiguity in the freshness of a person’s current work experience. Any customers currently using our `job_last_updated` field will need to migrate to the new `job_last_verified` and `job_last_changed` fields before v27.0. For help moving over to the new field, please reach out to your Customer Success and Technical Services for support and enablement resources. Please also see this easy-to-follow guide prepared by our Technical Services team for instructions on how to transition to this new schema: [Breaking Changes Guide *Deprecation of job*last\_updated.pdf](https://drive.google.com/open?id=1tP-u9D1QKpPRg79GaMN4zc1Zlfmk5QJi) *** ## 🚀 Data Updates ### Freshness *The number of jobs and locations verified in our datasets over the past **month** (based on the `job_last_verified` and `location_last_updated` fields).* | Dataset | Geography | Field | Records Updated | | :------ | :------------ | :----------- | --------------- | | Resume | Global | `experience` | 199,381,717 | | Resume | Global | `location` | 298,777,846 | | Resume | United States | `experience` | 53,538,566 | | Resume | United States | `location` | 82,270,299 |
### Coverage (Full Stats: [Person](/docs/datasets), [Company](/docs/company-stats)) **[Resume Dataset](/docs/resume-stats)** | Linkage | Coverage in v25 | Coverage in v26 | Increase (%) | | :------------------ | --------------- | --------------- | ------------ | | `total_records` | 794,313,831 | 744,191,278 | -6.31% | | `mobile_phone` | 17,666,371 | 53,088,015 | 200.50% | | `phone_numbers` | 69,139,249 | 44,226,279 | 56.33% | | `education.gpa` | 4,563,280 | 8,757,491 | 91.91% | | `education.summary` | 29,679,966 | 49,868,050 | 68.02% | | `education.majors` | 141,539,272 | 179,725,851 | 26.98% | | `education.degrees` | 126,248,489 | 156,797,783 | 24.20% | **[API Dataset](/docs/stats)** | Linkage | Coverage in v25 | Coverage in v26 | Increase (%) | | :------------------ | --------------- | --------------- | ------------ | | `total_records` | 3,225,330,100 | 3,178,815,044 | -1.44% | | `mobile_phone` | 478,067,684 | 513,257,630 | 7.36% | | `phone_numbers` | 1,125,062,185 | 1,157,207,007 | 2.86% | | `education.gpa` | 9,730,993 | 5,548,676 | 75.38% | | `education.summary` | 50,039,000 | 29,954,669 | 67.05% | | `education.majors` | 209,162,040 | 171,610,325 | 21.88% | | `education.degrees` | 169,748,056 | 139,634,548 | 21.57% | **[Company Dataset](/docs/company-stats)** | Linkage | Coverage in v25 | Coverage in v26 | Increase (%) | | :-------------------- | --------------- | --------------- | ------------ | | `total_records` | 61,297,152 | 62,109,427 | 1.33% | | `funding_details` | 221,107 | 226,302 | 2.35% | | `all_subsidiaries` | 40,994 | 42,496 | 3.66% | | `direct_subsidiaries` | 40,908 | 42,393 | 3.63% | | `ultimate_parent` | 112,785 | 116,367 | 3.18% | | `immediate_parent` | 111,943 | 115,394 | 3.08% | | `alternative_domains` | 4,504,007 | 4,504,390 | 0.01% | ### Commentary * We saw significant improvements (over 200% increase) in our coverage of mobile phones tied to linkedin profiles due to new data partnerships. * We rebuilt our school dataset and additionally ingested new sources of education data resulting in significant increases in coverage of our education-related fields including Degrees, Summaries, Majors, and GPAs. * We decreased our total records in the resume data slice by \~6% as a result of improvements to our deduplication logic as well as improved QA of low-quality data sources *** ## 🛠 Improvements and Bug Fixes
### Improvements * We’ve made a significant amount of updates to our IP data and matching to help with reliability and accuracy * We decreased the number of [frankenstein](/docs/datasets#description) records in our person dataset by over 13% and improved our work email quality by removing inferred emails being contributed by some of our data sources * We improved the accuracy of our alternative\_domains field by removing a low-quality data source without impact to our overall fill rate in the company dataset * We reduced the number of duplicate company tags present in our our company records ### Bug Fixes * Fixed a bug in our Autocomplete API where autocompletion using the `region` field was not returning location-based metadata * We fixed a bug in our changelog process that was erroneously creating multiple changelog records in certain cases. These multiple records are now stored in an array in the [`to`](/docs/id-changelog#additional-metadata) field of a changelog record. * We made some changes to our inferred\_years\_experience logic which allows us to under-emphasize education when we have detailed job history with start/end dates increasing the overall accuracy of this value. * We fixed a bug where certain degree abbreviations were being added into the name fields in a person profile * Resolved unexpected company enrichment matching behavior on websites where the input was actually an email domain such as sbcglobal.com and sbcglobal.net. # April 2025 Release Notes Source: https://docs.peopledatalabs.com/changelog/april-2025-release-notes-v300 | Release Name | Dataset Version | Publish Date | | :----------- | :-------------- | :----------- | | April 2025 | `v30.0` | 04/15/2025 | **Welcome to our April 2025 release notes!** This month, we’re rolling out some exciting and important updates across our data products.\ Here’s what’s new: * **🏢 New Company Insights Fields**: We just launched a whole batch of exciting [new Company Insight fields](#new-insights)! * **❄️ Snowflake Single Listing Migration**: We’ve completed the [migration of Snowflake customers](#snowflake-migration) to a unified, single listing for their data. * **🥷 Sunset of Skill Enrichment API**: The Skill Enrichment API is now [officially removed](#skill-enrich-deprecation). * **🆓 Free Job Title Enrichment API Plans**: Free & Pro users now have [access to the Job Title Enrichment API](#ss-job-title-enrichment) * **🎓 Expanded School Tagging**: Academic institutions are now [better labeled](#improvements) in our Company dataset using the `educational` company type. * **📊 Freshness Updates**: This past quarter, we [verified 296M+ jobs](#freshness) and [detected 9M+ job changes](#job-changes) across our global dataset Explore the full details below, or skip ahead to a specific section using the table of contents. ## 📣 Key Announcements ### Schema Changes #### New Company Insights Fields ([Company Schema](/docs/company-schema)) | Field | Type | Short Description | Bundle | | :------------------------------------------------------------------------------------------------------------ | :------- | :------------------------------------------------------------------------------------------------------------------------------------------------------- | :------------------------------------------------------------------------------------------------------------------------- | | [`top_next_employers`](/docs/company-schema#top_next_employers) | `Object` | The top ten companies employees moved to, and how many employees moved there, across all time periods | [Comprehensive](/docs/company-data-field-bundles#comprehensive) | | [`top_previous_employers`](/docs/company-schema#top_previous_employers) | `Object` | The top ten previous companies employees worked for previously, and how many current employees were previously employed by them, across all time periods | [Comprehensive](/docs/company-data-field-bundles#comprehensive) | | [`top_next_employers_12_month`](/docs/company-schema#top_next_employers_12_month) | `Object` | The top ten next employers, counting only employee changes within the last 12 months | [Comprehensive](/docs/company-data-field-bundles#comprehensive) | | [`top_previous_employers_12_month`](/docs/company-schema#top_previous_employers_12_month) | `Object` | The top ten previous employers, counting only employee changes within the last 12 months | [Comprehensive](/docs/company-data-field-bundles#comprehensive) | | [`employee_count_by_sub_role`](/docs/company-schema#employee_count_by_sub_role) | `Object` | The number of current employees broken down by [Job Title Sub Role](/docs/job-title-subroles). | [Comprehensive](/docs/company-data-field-bundles#comprehensive) | | [`employee_growth_rate_12_month_by_sub_role`](/docs/company-schema#employee_growth_rate_12_month_by_sub_role) | `Object` | The twelve month rate of change by [Job Title Sub Role](/docs/job-title-subroles) | [Comprehensive](/docs/company-data-field-bundles#comprehensive) | | [`employee_count_by_class`](/docs/company-schema#employee_count_by_class) | `Object` | The number of current employees broken down by [Job Title Class](/docs/job-title-class) | [Premium](/docs/company-data-field-bundles#premium)
[Comprehensive](/docs/company-data-field-bundles#comprehensive) | | [`employee_growth_rate_12_month_by_class`](/docs/company-schema#employee_growth_rate_12_month_by_class) | `Object` | The twelve month rate of change by [Job Title Class](/docs/job-title-class) | [Premium](/docs/company-data-field-bundles#premium)
[Comprehensive](/docs/company-data-field-bundles#comprehensive) | This month, we’re excited to introduce eight new Company Insight fields as part of the April 2025 (v30.0) release! These enhancements provide deeper visibility into employee movement trends and organizational composition, offering our customers even more actionable insights. These Company Data fields are currently in beta and are automatically available to customers with [Company Comprehensive](/docs/company-data-field-bundles#comprehensive) and [Company Premium](/docs/company-data-field-bundles#premium) field bundles, as indicated in the table above. **Key Highlights** * **Better Classification Support**: Headcount metrics are now broken down using our new Job Title Class and Job Sub Role taxonomies, providing more granularity and flexibility in workforce analysis. * **Time-Bound Talent Flow Summaries**: New 12-month versions of the Top Previous and Top Next Employers fields allow you to isolate and analyze recent employee movements, giving a sharper view of current hiring and attrition trends. * **Improved Data Readability**: All Top Employers summaries now include displayable company names, making analysis clearer and the data more presentation-ready. **Availability**\ These new fields are automatically included for customers with the following Company Data field bundles: * [Company Comprehensive](/docs/company-data-field-bundles#comprehensive) * [Company Premium](/docs/company-data-field-bundles#premium) See the table above for field availability across bundles. If you’re not currently seeing these fields and would like to enable access, please reach out to your Account Team for assistance. **Deprecation Notice**\ Please note that two of these new fields will fully replace two existing Company Insights fields (now considered legacy) in July 2025 as part of the v31.0 release. Please see the full [deprecation notice](#legacy-insights) below for more information. **We’d Love Your Feedback!**\ We’re always looking to improve. If you have thoughts on how these fields are working for you - or ideas for what insights you'd like to see next - please don’t hesitate to share your feedback with us. We would love to hear your input and ideas through our [Roadmap Feature Request Board](https://feedback.peopledatalabs.com/)! *** ## ❗Breaking Changes (Going Live This Month) ### ❗ Snowflake Listing Migration Change expected in: **v30.0 / April 2025**\ Previous Announcements: [v29.0 / Jan. 2025](/changelog/january-2025-release-notes-v290#snowflake-migration), [v29.1 / Feb. 2025](/changelog/february-2025-release-notes-v291#snowflake-migration), [v29.2 / Mar. 2025](/changelog/march-2025-release-notes-v292#snowflake-migration) Products Impacted: **Snowflake Listings** | Products Impacted | | :----------------------------------------------------------------------- | | [Snowflake Data License Deliveries](/docs/data-delivery-using-snowflake) | As of the April 2025 (v30.0) release, the migration of all Snowflake customers to a single listing per customer is now complete. **Why did we make this change?**\ Previously, Snowflake customers receiving multiple data entities (e.g. Person and Company datasets) were assigned separate listings for each entity. Starting in August 2024, new customers began receiving a unified, single listing. With this release, we have completed that same transition for all existing customers. All customers who previously had multiple listings have now been migrated to a single listing. This change simplifies data delivery and improves consistency and support across all Snowflake-based data products. **Migration Options and Final Status**\ Prior to this release, customers with multiple listings were given the opportunity to choose how they’d like to consolidate their data: * **Create a New Listing (default)**: PDL would set up a new, consolidated listing and retire the existing ones. * **Merge and Deprecate**: Customers could choose to retain one of their existing listings and have the other merged into it. With the April 2025 release now complete, all customer migrations have been finalized. In cases where no preference was shared, the default New Listing approach was applied to ensure a smooth transition.
### ❗ Sunset of Skill Enrichment API Change expected in: **v30.0 / April 2025**\ Previous Announcements: [v29.0 / Jan. 2025](/changelog/january-2025-release-notes-v290#skill-enrich-deprecation), [v29.1 / Feb. 2025](/changelog/february-2025-release-notes-v291#skill-enrich-deprecation), [v29.2 / Mar. 2025](/changelog/march-2025-release-notes-v292#skill-enrich-deprecation) Products Impacted: **Skill Enrichment API** | Products Impacted | | :------------------------------------------------- | | [Skill Enrichment API](/docs/skill-enrichment-api) | As of the April 2025 (v30.0) release, the Skill Enrichment API has been officially sunset and is no longer available. **Why this change?**\ The Skill Enrichment API was originally developed to enhance the user experience alongside our Person Search API. However, based on historical usage and customer feedback, we made the decision to shift focus toward our Job Title Enrichment API and sunset the Skill Enrichment API. If you have any questions about this change, we welcome your input and ideas via our [Roadmap Feature Request Board](https://feedback.peopledatalabs.com/)! ### ⚠️ Upcoming Breaking Changes **Upcoming Breaking Changes** **Upcoming breaking changes** may impact your current processes. We are announcing them here to provide ample time for you to adjust your processes accordingly.
#### ⚠️ (*New*) Deprecation of Legacy Employer Insights Fields ([Company](/docs/company-schema)) Change expected in: **v31.0 / July 2025** Products Impacted: **Company**
Company Fields Impacted
[`top_next_employers_by_role`](/docs/company-schema#top_next_employers_by_role) [`top_previous_employers_by_role`](/docs/company-schema#top_previous_employers_by_role)
As of April 2025 (v30.0), we are deprecating two fields in our [Company Schema](/docs/company-schema), which are now considered legacy. These fields will be fully replaced in July 2025 (v31.0) by the improved Company Insights fields that were released this month ([see above](#new-insights)). **Why this change?**\ Over the past few months, we’ve made several improvements based on customer feedback requesting more display-ready and flexible insights fields. One of the key improvements is the inclusion of displayable company names, which makes it much easier to build visualizations like Sankey charts or other talent flow views without needing additional API calls. The result is a simpler implementation experience and reduced API credit usage. To support these updates, we introduced a new set of fields rather than modifying the existing ones in order to provide an overlap period, giving users time to transition smoothly. **Migration Plan** * **April 2025 (v30.0)**: New fields are available. * **April - July 2025 (v30.0 - v31.0)**: Both legacy and new fields are available in the Company Schema to support a smooth transition. * **July 2025 (v31.0)**: Legacy fields will be removed. **Action Required**\ If you currently use the `top_next_employers_by_role` or `top_previous_employers_by_role` fields, you’ll need to update your systems to use the new fields listed below before July 2025 (v31.0): | Deprecated Fields (Removed in v31.0) | Replacement Fields (Released in v30.0) | | :-------------------------------------------------------------------------------------- | :---------------------------------------------------------------------- | | [`top_next_employers_by_role`](/docs/company-schema#top_next_employers_by_role) | [`top_next_employers`](/docs/company-schema#top_next_employers) | | [`top_previous_employers_by_role`](/docs/company-schema#top_previous_employers_by_role) | [`top_previous_employers`](/docs/company-schema#top_previous_employers) | The new fields capture all the value of the legacy versions - with the added benefit of being easier to use in visual tools and product interfaces. 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 ### Free & Pro plan Job Title Enrichment API Access We are excited to announce that we have added free access to the [Job Title Enrichment API](/docs/job-title-enrichment-api) for all Free and Pro plans! You can use the Job Title Enrichment API to enrich a job title and return the **top 5 matching job titles** in our dataset along with the **top 5 relevant skills** related to the job title. This allows you to enhance your Person Search API requests by easily broadening your search criteria without the need for complex fuzzy matching and guessing. **What do I have access to?**\ If you have a **Pro plan for the Person Search API**, you’ll be allocated **1,000 free credits per month** or **12,000 per year** with your annual plan. If you have a **Free plan for the Person Search API**, you have access to **10 free credits per month** to help facilitate testing. **Where can I learn more?** * Check out our API documentation here: [Job Title Enrichment API](/docs/job-title-enrichment-api) * Check out our Help Center article here: [Person Search Support API - Job Title Enrichment API](https://support.peopledatalabs.com/hc/en-us/articles/36025065882907-Person-Search-Support-API-Job-Title-Enrichment-API) * Get in touch with technical support here: [Submit a request](https://support.peopledatalabs.com/hc/en-us/requests/new) *** ## 🚀 Data Updates ### Freshness *The number of jobs and locations verified in our datasets (based on the`job_last_verified` and `location_last_updated` fields).* 📌 **Quarterly (v29.0 → v30.0)**\ *Freshness updates over the past quarter.* | Dataset | Geography | Field | Records Updated | | ------- | ------------- | ------------ | --------------- | | Resume | Global | `experience` | 296,822,089 | | Resume | Global | `location` | 436,083,756 | | Resume | United States | `experience` | 84,572,377 | | Resume | United States | `location` | 108,684,741 |
📌 **Monthly (v29.2 → v30.0)**\ *Freshness updates over the past month.* | Dataset | Geography | Field | Records Updated | | ------- | ------------- | ------------ | --------------- | | Resume | Global | `experience` | 85,384,126 | | Resume | Global | `location` | 109,570,460 | | Resume | United States | `experience` | 31,141,735 | | Resume | United States | `location` | 35,652,759 | #### Job Changes *The number of person records where the primary job experience changed in our Person Dataset (based on the`job_last_changed` field).* 📌 **Quarterly (v29.0 → v30.0)**\ *Freshness updates over the past quarter.* | Dataset | Geography | Records Updated | | ------- | ------------- | --------------- | | Resume | Global | 9,204,577 | | Resume | United States | 1,764,710 | 📌 **Monthly (v29.2 → v30.0)**\ *Freshness updates over the past month.* | Dataset | Geography | Records Updated | | ------- | ------------- | --------------- | | Resume | Global | 160,907 | | Resume | United States | 68,881 | ### Coverage (Full Stats: [Person](/docs/datasets), [Company](/docs/company-stats)) #### 📌 Quarterly (v29.0 → v30.0) **[Resume Dataset](/docs/resume-stats)** | Linkage | Coverage in v29.0 | Coverage in v30.0 | Increase (%) | | -------------------------------------------- | ----------------- | ----------------- | ------------ | | total\_records | 736,325,366 | 756,205,993 | 2.70% | | `job_title_sub_role` | 91,464,350 | 218,966,414 | 139.40% | | `headline` | 38,462,189 | 74,745,897 | 94.34% | | `experience.title.sub_role` | 165,187,811 | 312,906,910 | 89.42% | | `experience.company.location.street_address` | 172,581,307 | 309,548,414 | 79.36% | | `job_title_role` | 156,985,217 | 267,779,170 | 70.58% | | `experience.title.role` | 238,896,469 | 357,062,928 | 49.46% | | `experience.location_names` | 183,408,859 | 227,614,350 | 24.10% | | `summary` | 115,792,801 | 142,664,883 | 23.21% | | `location_locality` | 438,460,583 | 503,593,899 | 14.86% | | `experience.summary` | 136,829,932 | 154,738,826 | 13.09% | | `location_address_line_2` | 3,417,978 | 3,678,767 | 7.63% | | `education.school.linkedin_url` | 242,794,815 | 256,023,067 | 5.45% | | `skills` | 148,404,392 | 137,431,706 | -7.39% | [API Dataset](/docs/stats) | Linkage | Coverage in v29.0 | Coverage in v30.0 | Increase (%) | | ------------------------- | ----------------- | ----------------- | ------------ | | total\_records | 2,458,046,594 | 2,438,028,671 | -0.81% | | `summary` | 135,392,275 | 164,194,016 | 21.27% | | `location_locality` | 1,283,837,335 | 1,464,066,706 | 14.04% | | `location_address_line_2` | 68,105,393 | 74,583,404 | 9.51% | [Email Dataset](/docs/email-stats) | Linkage | Coverage in v29.0 | Coverage in v30.0 | Increase (%) | | -------------- | ----------------- | ----------------- | ------------ | | total\_records | 634,898,506 | 598,695,608 | -5.70% | | `experience` | 293,137,070 | 255,112,090 | -12.97% | [Mobile Phone Dataset](/docs/mobile-phone-stats) | Linkage | Coverage in v29.0 | Coverage in v30.0 | Increase (%) | | :------------- | :---------------- | :---------------- | :----------- | | total\_records | 485,553,309 | 484,854,828 | -0.14% | [Company Dataset](/docs/company-stats) | Linkage | Coverage in v29.0 | Coverage in v30.0 | Increase (%) | | :------------------------ | :---------------- | :---------------- | :----------- | | total\_records | 71,478,660 | 71,480,559 | 0.003% | | `location.street_address` | 18,962,288 | 46,024,415 | 142.72% | | `industry` | 45,769,144 | 53,934,583 | 17.84% | | `location.locality` | 50,338,832 | 57,775,410 | 14.77% | | `founded` | 13,602,870 | 15,108,123 | 11.07% | | `location.region` | 55,680,104 | 59,910,659 | 7.60% | | `ticker` | 27,674 | 26,226 | -5.23% | | `affiliated_profiles` | 281,740 | 195,851 | -30.49% |
#### 📌 Monthly (v29.2 → v30.0) **[Resume Dataset](/docs/resume-stats)** | Linkage | Coverage in v29.2 | Coverage in v30.0 | Increase (%) | | :----------------------------------- | :---------------- | :---------------- | :----------- | | total\_records | 751,349,471 | 756,205,993 | 0.65% | | `education.school.location.locality` | 196,060,230 | 242,981,350 | 23.93% | | `job_title_sub_role` | 206,788,089 | 218,966,414 | 5.89% | | `location_address_line_2` | 3,484,436 | 3,678,767 | 5.58% | | `job_title_role` | 254,637,685 | 267,779,170 | 5.16% | [API Dataset](/docs/stats) | Linkage | Coverage in v29.2 | Coverage in v30.0 | Increase (%) | | :------------------ | :---------------- | :---------------- | :----------- | | total\_records | 2,473,230,064 | 2,438,028,671 | -1.42% | | `skills` | 163,076,220 | 145,686,456 | -10.66% | | `location_locality` | 1,337,713,215 | 1,464,066,706 | 9.45% | | `emails` | 685,747,622 | 649,474,773 | -5.29% | [Email Dataset](/docs/email-stats) | Linkage | Coverage in v29.2 | Coverage in v30.0 | Increase (%) | | :------------- | :---------------- | :---------------- | :----------- | | total\_records | 634,528,966 | 598,695,608 | -5.65% | | experience | 293,765,269 | 255,112,090 | -13.16% | [Mobile Phone Dataset](/docs/mobile-phone-stats) | Linkage | Coverage in v29.2 | Coverage in v30.0 | Increase (%) | | :------------- | :---------------- | :---------------- | :----------- | | total\_records | 486,065,010 | 484,854,828 | -0.25% | [Company Dataset](/docs/company-stats) | Linkage | Coverage in v29.2 | Coverage in v30.0 | Increase (%) | | :------------- | :---------------- | :---------------- | :----------- | | total\_records | 71,481,597 | 71,480,559 | 0.00% | | `ticker` | 27,811 | 26,226 | -5.70% | ### Commentary 📌 ***Quarterly Highlights (v29.0 → v30.0)*** * **Major improvements in job title and role fields** within the Resume dataset due to the GA launch of our improved Job Role Taxonomy in February 2025 (v29.1): * `job_title_sub_role` (+139%) * `experience.title.sub_role` (+89%) * `job_title_role` (+71%) * **`headline`coverage nearly doubled (+94%)** in the Resume dataset due to ongoing backfill efforts * **Significant enhancements in location data** across datasets due to improved cleaning logic (see [Improvements](#improvements) below): * `experience.company.location.street_address` (+79%) in Resume * `location_locality` (+15%) in Resume * `location.street_address` in Company dataset (+143%) * **Decline in`skills` coverage (-7%)** in the Resume dataset following improvements to our skill cleaning process (see [Improvements](#improvements) below) * **`affiliated_profiles`coverage in Company dataset fell 30%** , consistent with ongoing sourcing updates; this is a low fill-rate field currently under review for future improvements. 📌 ***Monthly Highlights (v29.2 → v30.0)*** * **Job title taxonomy fields continued to grow**: * `job_title_sub_role` (+5.9%) * `job_title_role` (+5.2%) * **API dataset saw a small dip in total\_records (-1.4%)**, along with: * Drop in `skills` (-10.7%) due to ongoing cleanup * Drop in `emails` (-5.3%) from record quality filtering * **Location fields continued improving**, with `location_locality` up 9.5% * **The Company dataset saw a slight dip in`ticker` coverage (-5.7%)** over the past month. *** ## 🛠 Improvements and Bug Fixes ### Improvements * **Skill Cleaner Improvements** * We made significant improvements to our skills cleaning that resulted in a **decrease in skills fill rates**, but **higher quality values** in the `skills` array. * **Location Selection Improvements** * We made some significant improvements to how we select the primary `location_` object: * Previously: location objects were selected based on the objects with most detailed location and the most recent timestamp * Now: location objects are chosen based on the most recent locality / metro with the most recent and granular associated locality * **Location Cleaning Improvements** * [Last month](/changelog/march-2025-release-notes-v292#improvements), we released some major improvements to our location cleaner to improve the consistency and quality of our locality and region data * This update led to significant coverage improvements across our Person, Company and School datasets as seen in the [Coverage](#commentary) section above * **Metro Values Added to Autocomplete API** * For US locations in the Autocomplete API, we now include the metro value in the autocomplete response object * **Improved School Tagging** * We expanded our logic for classifying academic institutions (i.e. companies with the the type [type](/docs/company-types) `educational`) to now include any companies with a `.edu` primary website. * **Unique Company Websites** * We now enforce that the `website` field for each company record is unique across our Company dataset, allowing customers to use this field as a primary identifier when ingesting or using our Company records. * **Company Website Cleaner Improvements** * We improved our company domain cleaner to exclude certain invalid websites (such as those containing email-like “@” characters) based on customer feedback * **Title Tagging Improvements** * We are continuing to make improvements to our Job Title Taxonomy tagging which led to significant increases in titles tagged across our Person Dataset ### Bug Fixes * We updated our name cleaner to exclude additional certifications from a person’s name fields * We fixed a bug that allowed the `tags` array in Company records to contain empty (“ “) entries * We updated our logic for enforcing known parent/subsidiary company relationships to ensure the correct parent/subsidiary relationship was maintained throughout the Company Data build process. * We fixed an issue causing null values for the Job Title Class field for executives in certain fields in our Company records. # April 2026 Release Notes Source: https://docs.peopledatalabs.com/changelog/april-2026-release-notes-v340 | Release Name | Dataset Version | Publish Date | | :----------- | :-------------- | :----------- | | April 2026 | `v34.0` | 04/21/2026 | **Welcome to our April 2026 release notes!** This month, we’ve got an exciting new product launch alongside some impactful data quality improvements to share. Check it out: * ** [Job Posting API](#new-beta-launch-job-posting-api-docs)** It's here - our brand new API for real-time access to global hiring data * 🔧 [**Data Quality & Coverage Improvements**](#commentary): Big jumps in work email deliverability along with improved matching for location and school data across datasets. * ** [Important Bug Fixes](#bug-fixes)** Squashed key issues to improve deduplication and consistency in our Person dataset * **📊 [Freshness Updates](#freshness)**: This past month, we [verified 68M+ jobs](#freshness) and [detected 6M+ job changes](#job-changes) across our global dataset Dive into the full details below, or jump to what interests you using the table of contents below. *** ## Announcements **Using Email Data? Check out Our New Post on Email Deliverability** Improving our Email Deliverability has been a key focus on our Data Roadmap since [last October](/changelog/october-2025-release-notes-v320#email-deliverability-improvements-person). This month, we wrote a new blog post that provides a comprehensive overview of this project and where we’re going. If email outreach and deliverability is a key focus of yours, this post is definitely worth a read! [Building for Email Deliverability](https://www.peopledatalabs.com/blog/post/building-for-email-deliverability) *** ## New Products and Features ## New Beta Launch: Job Posting API ([Docs](/docs/job-posting-search-api))
**What’s New** This month, we’re excited to announce the launch of our new Job Posting API to enable real-time access to complete records from our Job Posting Dataset. The Job Posting API is a **search endpoint** that allows you to query and retrieve structured job posting records without needing to manage a full dataset. With this API, you can: * Search millions of active and historical job postings * Filter by company, title, location, salary, and more * Retrieve full job posting records, including raw descriptions and metadata * Access daily-updated data sourced directly from company career pages
**Why We Built This** Our goal with the Job Posting API was to provide a **more flexible and accessible way** to work with job posting data. While the full [Job Posting Dataset](/docs/job-posting-data-overview) is ideal for large-scale use cases, many users need a lighter-weight, query-based solution. This API makes it easier to: * Access only the data you need, when you need it * Iterate on searches dynamically without managing full data pipelines * Integrate real-time hiring data directly into applications and workflows
**Key Features** * **Flexible Search Options**: Use simple field filters or full Elasticsearch queries for advanced use cases * **Built-in Data Cleaning**: Company names, locations, and titles are normalized automatically for easier querying * **Multi-field Filtering**: Combine filters across multiple attributes using AND logic * **Bulk Retrieval**: Paginate and pull down all records matching your query * **Near Real-Time Data**: Job postings are updated within \~24 hours of detection **Check out the Docs!**\ To learn more and see various use cases in action, take a look at these resources: * [Job Posting API Overview](/docs/job-posting-search-api) * [Quickstart Guide](/docs/quickstart-job-posting-search-api) * [Use Cases](/docs/use-cases-job-posting-search-api)
**How To Get Started** The Job Posting API is currently in **beta**. To get started: * **PDL Customers**: Reach out to your account team to enable access * **New to PDL?** [Request access here](https://www.peopledatalabs.com/job-posting-beta-sign-up)
**What’s Next** This beta release is the first step in expanding how users interact with our Job Posting Data. Over the coming months, we plan to: * Expand data coverage and volume * Refine the API experience and schema * Incorporate feedback from early users to guide improvements Have questions or suggestions? [Let us know](https://feedback.peopledatalabs.com/feature-requests?selectedCategory=job-posting-data)! We’re actively building this product alongside our users. *** ## 🚀 Data Updates ### Freshness *The number of jobs and locations verified in our datasets (based on the `job_last_verified` and `location_last_updated` fields).* **Monthly (v33.2 → v34.0)**\ *Freshness updates over the past month.* | Dataset | Geography | Field | Records Updated | | :------ | :------------ | :----------- | --------------- | | Resume | Global | `experience` | 68,637,489 | | Resume | Global | `location` | 96,306,800 | | Resume | United States | `experience` | 26,312,224 | | Resume | United States | `location` | 34,430,551 | ### 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 (v33.2 → v34.0)**\ *Freshness updates over the past month.* | Dataset | Geography | Records Updated | | :------ | :------------ | --------------- | | Resume | Global | 6,375,225 | | Resume | United States | 1,648,264 |
## Coverage (Full Stats: [Person](/docs/datasets), [Company](/docs/company-stats), [Job Posting](/docs/jp-stats), [IP](/docs/ip-stats)) ### Monthly (v33.2 → v34.0) [**Resume Dataset**](/docs/resume-stats) | Linkage | Coverage in v33.2 | Coverage in v34.0 | Increase (%) | | :------------ | ----------------- | ----------------- | ------------ | | Total Records | 809,343,157 | 807,504,074 | -0.23% | | work\_email | 68,063,562 | 89,503,938 | 31.5% | | emails | 199,458,707 | 225,452,984 | 13.03% | | headline | 181,448,484 | 202,801,405 | 11.77% | | mobile\_phone | 55,480,692 | 52,054,473 | -6.18% | [**API Dataset**](/docs/stats) | Linkage | Coverage in v33.2 | Coverage in v34.0 | Increase (%) | | :------------ | ----------------- | ----------------- | ------------ | | Total Records | 2,462,179,997 | 2,459,165,018 | -0.12% | [**Email Dataset**](/docs/email-stats) | Linkage | Coverage in v33.2 | Coverage in v34.0 | Increase (%) | | :------------ | ----------------- | ----------------- | ------------ | | Total Records | 586,900,394 | 613,121,153 | 4.47% | [**Mobile Phone Dataset**](/docs/mobile-phone-stats) | Linkage | Coverage in v33.2 | Coverage in v34.0 | Increase (%) | | :------------ | ----------------- | ----------------- | ------------ | | Total Records | 479,651,097 | 479,255,846 | -0.08% | [**Company Dataset**](/docs/company-stats) | Linkage | Coverage in v33.2 | Coverage in v34.0 | Increase (%) | | :------------------- | ----------------- | ----------------- | ------------ | | Total Records | 74,685,793 | 74,690,041 | 0.006% | | affiliated\_profiles | 173,214 | 167,897 | -3.07% | [**Job Posting Dataset**](/docs/jp-stats) | Linkage | Coverage in v33.2 | Coverage in v34.0 | Increase (%) | | :--------------------- | ----------------- | ----------------- | ------------ | | Total Records | 25,931,674 | 30,644,394 | 18.17% | | Total Unique Companies | 52,236 | 54,997 | 5.29% | | Total Active Postings | 3,178,613 | 3,875,335 | 21.92% |
## Commentary * **Person Data** * This month we saw a 31% increase in coverage of deliverable `work_emails` as a result of our ongoing work to improve our email deliverability. See [improvements](#improvements). * We saw an 11% increase in coverage for the `headline` field. * We saw a 6% drop in coverage for mobile\_phones in our resume dataset this month. * **Company Data** * We saw a decrease in the fill rate for the `affiliated_profiles` as a result of some [improvements](#improvements) to this field this past month. * **Job Posting Data** * We saw a 5% increase in the number of unique companies tracked in our Job Posting Dataset over the past month. *** ## 🛠 Improvements and Bug Fixes ## Improvements * **Email Deliverability Improvements** * We integrated more validated emails into our data build process and improved our internal benchmarking and QA pipeline for monitoring our email deliverability * As a result of these changes, we saw significant increases in both coverage and deliverability this month. * Customers should see improvements, but should still expect some continued month-to-month variability in fill rates as this project continues * **Updated Affiliated Profile Logic** * The `affiliated_profiles` field now represents a deduplicated list of all related company IDs (parent and subsidiary affiliated companies). Previously, this was capped at a max of 25 associated record IDs. * **Location Canononicalization Improvements** * We improved location parsing and canonicalization for some specific locations, such as São Paulo, Bangalore/Bengaluru, Mexico City, and accented Brazilian city names. * This improves accuracy for international localities, district-style city names, and edge cases involving formatting or diacritics ## Bug Fixes * **More Reliable Profile Merging** * We fixed an issue that prevented some profiles with the same `linkedin_id` from merging correctly. * **School Canonicalization Reliability** * We resolved cases where the same school raw value could map to different canonical schools. * **Names with Parenthetical Certifications** * We fixed an issue where names containing parenthetical credentials or certifications could be parsed incorrectly, producing malformed name outputs. # August 2024 Release Notes Source: https://docs.peopledatalabs.com/changelog/august-2024-release-announcement-v271 | Release Name | Dataset Version | Publish Date | | :----------- | :-------------- | :----------- | | August 2024 | `v27.1` | 08/06/2024 | *v27.1 was released on **August 6, 2024**.* Welcome to our August 2024 release notes! We have exciting updates to share to kick off the second half of the year! Here are some of the key highlights: * A new tabular file format for Data License customers * New updates to our API dashboard * Beta Release of our new Role / Subrole Taxonomy * Significant QA improvements to profiles in our resume slice Excited yet? Read on to learn more, or jump to a specific section using the table of contents below. ## ❗Breaking Changes (Going Live This Month) ### ⚠️ Upcoming Breaking Changes **Upcoming Breaking Changes** **Upcoming breaking changes** in future versions may impact your current processes. We are announcing them here to provide ample time for you to adjust your processes accordingly. #### ⚠️ New Role and Sub Role Job Title Taxonomy (Person / Company / IP) Change expected in: **v29.1 / February 2025** Previous Announcements: [v26 / April 2024](/changelog/april-2024-release-announcement-v260#title-tagging-updates)**,** [v27.0 / July 2024](/changelog/july-2024-release-announcement-v270#title-taxonomy) Products Impacted: **Person** / **Company** / **IP Schema** | Person Fields Impacted | Company Fields Impacted | IP Fields Impacted | | :-------------------------------------------------------------------------------------- | :------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | :--------------------------------------------------- | | job\_title\_role job\_title\_sub\_role experience.title.role experience.title.sub\_role | average\_tenure\_by\_role employee\_count\_by\_month\_by\_role employee\_count\_by\_role recent\_exec\_departures recent\_exec\_hires top\_next\_employers\_by\_role top\_previous\_employers\_by\_role | person.job\_title\_role person.job\_title\_sub\_role | As announced in our [July 2024 release notes](/changelog/july-2024-release-announcement-v270#title-taxonomy), we are in the process of revising our `job_title_role` and `job_title_sub_role` enums by implementing a new job role taxonomy. This breaking change will impact customers using any of the fields in the table listed above. This month, we are opening up [beta access](#role-subrole-updated-taxonomy-beta-rollout) to our updated taxonomy along with a migration guide to support customers through the transition to the new taxonomy. As a reminder, **all customers must be fully transitioned to the new taxonomy by February 2025 (v29.1)**. **Timeline** Given the scope of the changes, our goal is to provide clear visibility on the process and ample opportunity to work through this transition together. The expected timeline for this release is as follows: **\[✅] V27.0 (July 2024) - Breaking Change Announcement and Resource Launch:** * Public notice of our planned role / subrole transition and initial resources provided **\[✅] V27.1 (August 2024) - Beta:** * [Beta access](#role-subrole-updated-taxonomy-beta-rollout) is now available for the new role / subrole taxonomy which includes a new data field `title.class` * Customers are now able to test sample data through our Technical Services team to explore the new taxonomy and the potential data impacts * We have released a guide documenting our recommended best practices for transitioning to the new taxonomy with the beta release as well **V28.0 (October 2024) - General Availability:** * We will make the new role / subrole taxonomy generally available for all customers and begin the deprecation process for the previous taxonomy * Customers can opt in to accessing the new taxonomy via API and flat file deliveries (but will have the option to delay transitioning until their systems are updated) **\[Upcoming] V29.1 (February 2025) - Final Deprecation:** * We will fully deprecate and officially end support for the previous taxonomy * All new and existing customers will be moved onto the new role / subrole taxonomy. **Resources** Please use the following resources to better understand the upcoming changes and to start preparing for the transition. As always, reach out to your Customer Success and Technical Services teams for questions and support. \[✨NEW] Migration Guide: A document that walks customers through transitioning their codebase and datasets to the new taxonomy is here: * [Breaking Changes Guide: v27.1 Role / Subrole Taxonomy Migration](/docs/product-integration-guides#v271---migration-guide-for-updated-role-and-sub_role-taxonomy) Migration Table: A spreadsheet that explicitly maps each role and sub\_role from the previous taxonomy to the new taxonomy is here: * [Migration Table for New Role / Sub\_Role Taxonomy \[Post-v27.1\]](https://docs.google.com/spreadsheets/d/1XCYraEJnMIG5AgmVCzZOpdWZZMlIG7_xq5LXbSY-9b8/edit?usp=sharing) The new set of canonical classes, roles, and subroles is here: * [Job Title Class \[post-v27.1\]](/docs/job-title-class-post-v271) * [Job Title Roles \[post-v27.1\]](/docs/job-title-roles-post-v271) * [Job Title Subroles \[post-v27.1\]](/docs/job-title-subroles-post-v271) * [Mapping of Job Title Class to Roles to Subroles \[post-v27.1\]](/docs/mapping-job-title-class-to-roles-to-subroles-post-v271) Sample records using the updated role / subrole taxonomy are here: * [Example Person Record \[New Role / Subrole Taxonomy\]](/docs/example-person-record-new-role-subrole-taxonomy) * [Example Company Record \[New Role / Subrole Taxonomy\]](/docs/example-company-record-new-role-subrole-taxonomy) * [Example IP Record \[New Role / Subrole Taxonomy\]](/docs/example-ip-record-new-role-subrole-taxonomy) #### ⚠️ Location Country Enum Updates Change expected in: **v28.0 / October 2024** Previous Announcements: [v27.0 / July 2024](/changelog/july-2024-release-announcement-v270#location-updates) Products Impacted: **Person** / **Company** / **IP Schema** | Person Fields Impacted | Company Fields Impacted | IP Fields Impacted | | :------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | :-------------------------------------------- | :---------------------------------------------- | | location\_country countries street\_addresses.country possible\_street\_addresses.country job\_company\_location\_country experience.company.location.country education.school.country | location.country employee\_count\_by\_country | ip.location.country Ip.company.location.country | In October 2024, we will be updating the set of [canonical countries](/docs/location-countries) values to better accommodate geographical renamings as well as correct redundancies in our set of country values. This change is part of an ongoing effort to improve our overall location standardization process within our data. As such it will impact the location country values in our Person, Company and IP datasets. The updated set of country values that will be released in v28.0 is here: * [Location Countries \[post-v28.0\]](/docs/location-countries-post-v280) In addition a mapping from the current country values to the upcoming country values can be found here: | Country (pre-v28.0) | Change Type | Country (post-v28.0) | Comments | | :------------------ | :---------- | :------------------- | :----------------------------- | | `swaziland` | Renamed | `eswatini` | | | `antarctica` | Deleted | – | | | `macedonia` | Renamed | `north macedonia` | | | `pitcairn` | Renamed | `pitcairn islands` | | | `gambia` | Renamed | `the gambia` | | | `ivory coast` | Deleted | – | Redundant with `côte d'ivoire` | #### ⚠️ Company Type Enum Change Products Impacted: **Person** / **Company** **Schema** Previous Announcements: [v27.0 / July 2024](/changelog/july-2024-release-announcement-v270#company-type-updates) Change expected in: **v28.0 / October 2024** | Person Fields Impacted | Company Fields Impacted | | :----------------------------------------- | :---------------------- | | job\_company\_type experience.company.type | type | Next quarter, we will be updating the set of [canonical company type](/docs/company-types) values to include a new `public_subsidiary` value in the set of canonical values: | Canonical Company Types (pre-v28.0) | Canonical Company Types (post-v28.0) | | :---------------------------------------------- | :--------------------------------------------------------------------- | | educational government nonprofit private public | educational government nonprofit private public **public\_subsidiary** | This change is part of an ongoing effort to improve our coverage of stock ticker fields and how we enable customers to roll up Company Insights information to public companies. The addition of the `public_subsidiary` company type specifically is intended to help provide customers a mechanism to easily filter and pull all public companies and their subsidiaries. *** ## ✨ New Products and Features ### Table (Flattened) Data License Format We are releasing a new [tabular file format](/docs/table-flattened-data-license-format) for our Person & Company Data Licenses. This new delivery format transforms and schematizes our datasets into flattened tables making it easier to load into databases like PostgreSQL and MySQL. For customers housing their data in relational databases, this tabular data license format helps simplify the ingestion process and accelerate delivery of new information and insights to your end users. The Tabular Data License Format is now available as an option to all data license customers at no added cost. To request access, please reach out to your Customer Success and Technical Services team. Note: This is a new file delivery format, and so moving to this format means you will no longer receive your previous format (unless specifically requested). ### Role Subrole Updated Taxonomy (Beta Rollout) This month, we are officially opening up **beta access** to the new Role / Subrole taxonomy by providing custom data samples. We **strongly encourage** any customers impacted by the [breaking change notice](#️-new-role-and-sub-role-job-title-taxonomy-person--company--ip) above to participate in this beta rollout and explore this sample data. Our intention is for customers to understand the new taxonomy changes in real data and to begin scoping out any modifications to their data ingestion process. How it works: * To request a data sample, get in contact with your Customer Success and Technical Services team * We will work with you to design a query for our Person and / or Company dataset that we will use to create your custom data sample * Your custom data sample will contain up to 100k records and will be delivered as a JSON file Additionally, we have also released a migration guide as part of this beta rollout, that outlines our recommended strategy for transitioning your codebase and datasets to the new taxonomy. [Breaking Changes Guide: v27.1 Role / Subrole Taxonomy Migration](/docs/product-integration-guides#v271---migration-guide-for-updated-role-and-sub_role-taxonomy) As a reminder, **all customers must be fully transitioned to the new taxonomy by February 2025 (v29.1)**, and so we highly recommend participating in this beta release. The full rollout timeline is available in the [breaking change notice](#️-new-role-and-sub-role-job-title-taxonomy-person--company--ip) above. To get started, reach out to your Customer Success and Technical Services team. ### API Dashboard Usage Alerts We are excited to announce updates to credit usage reporting within our API Dashboard. **Usage Alerts** Customers can now set up real-time usage alerts to better track credit usage. Email alerts can be set up with customizable notification thresholds that will be sent immediately once the configured threshold is reached. This new feature allows users to stay informed about usage and top up before running out of credits. To configure alerts, navigate to the [Usage Alerts](https://dashboard.peopledatalabs.com/settings/usage-alerts) tab in the Settings page. **Usage Summary Reports** Customers can now choose to receive daily, weekly, and/or monthly Usage Summary Report emails. These reports offer insights into credit consumption across all PDL APIs and highlight changes since the previous period. They help identify usage irregularities and plan for fluctuations. To configure these reports, visit the [Usage Alerts](https://dashboard.peopledatalabs.com/settings/usage-alerts) tab on the Settings page. **API Dashboard Usage Page Updates** Previously, customers could only view monthly aggregated usage, making it hard to track short-term trends. Our newly updated [Usage page](https://dashboard.peopledatalabs.com/usage) allows for more granular credit usage stats across any specified date range. Customers can view usage by hour, day, week, month, or year, and access data in a tabular format or as a downloadable CSV for sharing. *** ## 🚀 Data Updates **August 2024 (v27.1) is a Minor Release** As a reminder, August 2024 is a minor release. This means that the information reported below is based off of the last one month of updates (rather than the 3 months of updates we typically report for the major releases). ### Freshness *The number of jobs and locations verified in our datasets over the past **month** (based on the `job_last_verified` and `location_last_updated` fields).* | Dataset | Geography | Field | Records Updated | | :------ | :------------ | :----------- | --------------- | | Resume | Global | `experience` | 196,285,619 | | Resume | Global | `location` | 227,746,574 | | Resume | United States | `experience` | 33,224,447 | | Resume | United States | `location` | 40,366,861 | #### Job Changes *The number of person records where the primary job experience changed in our Person Dataset over the past **month** (based on the `job_last_changed` field).* | Dataset | Geography | Records Updated | | :------ | :------------ | --------------- | | Resume | Global | 1,641,212 | | Resume | United States | 683,476 | ### Coverage (Full Stats: [Person](/docs/datasets), [Company](/docs/company-stats)) **[Resume Dataset](/docs/resume-stats)** | Linkage | Coverage in v27.0 | Coverage in v27.1 | Increase (%) | | :--------------------- | ----------------- | ----------------- | ------------ | | `total_records` | 721,091,212 | 725,973,888 | 0.68% | | `mobile_phone` | 62,390,071 | 53,145,648 | 17.39% | | `linkedin_connections` | 472,583,136 | 504,020,877 | -6.24% | | `linkedin_urls` | 721,091,212 | 688,878,324 | -4.47% | ### Commentary * Mobile phone linkages increased by 17% as we continue to onboard new sources to improve coverage. * We made a change to how we define the top-level `linkedin_url` field. We are now internally validating linkedin\_urls and are removing top-level linkedin\_urls that result in a 404. * We saw a decrease of \~32mm linkedin\_urls in our resume data slice based on this change. These records will still appear in the resume slice, but the linkedin urls associated with the profile will only appear in the `profiles` array and are considered historic. *** ## 🛠 Improvements and Bug Fixes ### Improvements * We improved our matching and canonicalization logic for schools resulting in more accurate school data in our person records and School Cleaner API * As mentioned above, we are making improvements to ensure that top-level `linkedin_url` values do not produce 404 errors. * We now strip null terminators from all fields in our data * We now provide gzip and json file formats for our Company Changelog ### Bug Fixes * We fixed a bug in our company data that was occasionally allowing older data to persist in some records * We updated our list of invalid tokens in our name cleaner to allow some missing profiles back into our dataset # August 2025 Release Notes Source: https://docs.peopledatalabs.com/changelog/august-2025-release-notes-v311 | Release Name | Dataset Version | Publish Date | | :----------- | :-------------- | :----------- | | August 2025 | `v31.1` | 08/19/2025 | **Welcome to our August 2025 release notes!** This month, we're rolling out some fresh updates and exciting features across our products. Here's what's new: * **📊 Freshness Updates**: This past quarter, we [verified 65M+ jobs](#freshness) and detected [984K+ job changes](#job-changes) across our global dataset * ** Job Posting Growth**: Another month of [continued \~20% growth](#coverage) in our Job Posting Dataset. * ** API Playground**: A [streamlined tool](#api-playground) to build API requests and view live data directly from your dashboard. * ** More Office Insights (Beta)**: [Four new fields](#additional-office-insights-fields-beta) in our company records to give you richer company location context. ## Key Announcements ### Additional Office Insights Fields (Beta) **What's new?** This month, we are adding four new fields to the [Location Details](/docs/company-data-field-bundles#location-details) field bundle that we released last month for our Company Dataset: | FIELD NAME | FIELD TYPE | FIELD BUNDLE | FIELD DESCRIPTION | | :------------------------------------------------------------------ | :------------ | :-------------------------------------------------------------------- | :-------------------------------------------------------------------------------------------------- | | [`locations.first_seen`](/docs/company-schema#locations) | `Object` | [Location Details](/docs/company-data-field-bundles#location-details) | The date that this location was first observed in association with the company record. | | [`locations.last_seen`](/docs/company-schema#locations) | `String` | [Location Details](/docs/company-data-field-bundles#location-details) | The date that this location was last observed in association with the company record. | | [`locations.is_active`](/docs/company-schema#locations) | `Boolean` | [Location Details](/docs/company-data-field-bundles#location-details) | Denotes whether this location was active ("true") or inactive ("false") as of the last observation. | | [`num_active_locations`](/docs/company-schema#num_active_locations) | `Integer > 0` | [Location Details](/docs/company-data-field-bundles#location-details) | Count of all active locations associated with the company record. | **Why it matters** These new fields offer richer context on company locations: * **Get a clear count** - `num_active_locations` complements `num_total_locations` (from v31.0) to show active vs. total historical locations. * **Spot activity changes** - Quickly determine if a location is still operational. * **Track history** - See when a location was first and last active. Together, these insights make it easier to understand a company's physical footprint and operational changes over time. **Availability** The Location Details bundle remains in Beta until v32.0 (October), when it will move to General Availability. **Pricing & Packaging** * New customers can purchase the bundle now at incentivized Beta pricing. * Existing customers with the Location Details bundle automatically get these new fields. **We'd Love Your Feedback!** Your input helps shape what we build next. Share your thoughts on these fields or suggest new ones via our [Roadmap Feature Request Board](https://feedback.peopledatalabs.com/)! ## Upcoming Breaking Changes Upcoming breaking changes may impact your current processes. We are announcing them here to provide ample time for you to adjust your processes accordingly. ### Deprecation Notice: Query Builder & API Explorer Tools **Deprecation Date:** November 2025 (v32.1) **Impacted Product:** API Dashboard **Tools Being Removed** * Query Builder Tool * API Explorer Tool In November 2025, we will be deprecating several legacy tools in our API Dashboard and public documentation in favor of our new API Playground going live this month. **Timeline** * November 2025: Legacy tools fully removed. * July–November 2025: Legacy tools and API Playground both available * July 2025: API Playground available in your API Dashboard **Action You Need to Take** * Recreate any queries or workflows you currently run in the Query Builder by writing SQL in the new API Playground * Start using the API Playground now to prepare for the upcoming deprecations * Pro tip: Check out the Reference panel by clicking the Reference button for SQL and Elasticsearch examples 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 ### API Playground This month, we're excited to introduce the API Playground - a new, all-in-one tool inside your API Dashboard that makes it easier than ever to explore, test, and learn our APIs without writing a single line of code. **What's New** The API Playground combines and replaces our legacy Query Builder and API Explorer tools (retiring in November 2025): * **Instant Request Building:** Select an endpoint, add parameters, and send requests directly from your dashboard. * **Dual Views:** View results as clean, searchable tables or raw JSON. * **One-Click Code Snippets:** Instantly generate code in 20+ languages and SDKs. * **Credit Visibility:** See your current balance and how many credits a request will use before you send it. **Access** The API Playground is available to all users on Free, Pro, and Enterprise plans. You can find it directly in your API Dashboard under the Tools section - no installation or setup required. **How to Get Started** 1. Open the Playground in your dashboard. (Sign up for a free account if you don't have access yet) 2. Choose an endpoint from the dropdown menu. 3. Add parameters manually or start with a pre-filled example request. 4. Send the request to instantly view results in either a table or JSON format. 5. Copy a code snippet in your preferred language or SDK to start building. If you're on the Free plan, upgrade to Pro or Enterprise to unlock location and contact data values For additional guidance, check out the [API Playground documentation](https://support.peopledatalabs.com/hc/en-us/articles/39343616025755-API-Playground) in the Help Center or contact your Customer Account Team. ## Data Updates ### Freshness *The number of jobs and locations verified in our datasets (based on the `job_last_verified` and `location_last_updated` fields).* **Monthly (v31.0 → v31.1)** *Freshness updates over the past month.* | Dataset | Geography | Field | Records Updated | | :------ | :------------ | :----------- | :-------------- | | Resume | Global | `experience` | 65,066,673 | | Resume | Global | `location` | 94,049,991 | | Resume | United States | `experience` | 20,158,570 | | Resume | United States | `location` | 25,546,109 | ### 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.0 → v31.1)** *Freshness updates over the past month.* | Dataset | Geography | Records Updated | | :------ | :------------ | :-------------- | | Resume | Global | 984,443 | | Resume | United States | 566,286 | ### Coverage (Full Stats: [Person](/docs/datasets), [Company](/docs/company-stats), [IP](/docs/ip-stats), [Job Posting](/docs/jp-stats)) **Monthly (v31.0 → v31.1)** **[Resume Dataset](/docs/resume-stats)** | Linkage | Coverage in v31.0 | Coverage in v31.1 | Increase (%) | | :------------ | :---------------- | :---------------- | :----------- | | Total Records | 769,145,862 | 781,715,532 | 1.63% | **[API Dataset](/docs/stats)** | Linkage | Coverage in v31.0 | Coverage in v31.1 | Increase (%) | | :------------ | :---------------- | :---------------- | :----------- | | Total Records | 2,430,515,644 | 2,442,298,059 | 0.48% | | `headline` | 78,601,662 | 92,526,656 | 17.72% | **[Email Dataset](/docs/email-stats)** | Linkage | Coverage in v31.0 | Coverage in v31.1 | Increase (%) | | :------------ | :---------------- | :---------------- | :----------- | | Total Records | 591,663,319 | 591,113,964 | -0.09% | **[Mobile Phone Dataset](/docs/mobile-phone-stats)** | Linkage | Coverage in v31.0 | Coverage in v31.1 | Increase (%) | | :------------ | :---------------- | :---------------- | :----------- | | Total Records | 482,117,257 | 481,934,392 | -0.04% | **[Company Dataset](/docs/company-stats)** | Linkage | Coverage in v31.0 | Coverage in v31.1 | Increase (%) | | :------------ | :---------------- | :---------------- | :----------- | | Total Records | 71,647,425 | 71,648,103 | 0.001% | **[Job Posting Dataset](/docs/jp-stats)** | Linkage | Coverage in v31.0 | Coverage in v31.1 | Increase (%) | | :--------------------- | :---------------- | :---------------- | :----------- | | Total Records | 12,035,048 | 14,333,305 | 19.10% | | Total Unique Companies | 32,534 | 34,704 | 6.67% | | Total Active Postings | 2,183,409 | 2,313,744 | 5.97% | ### Commentary * **Person** * We saw a 17% increase in coverage for the `headline` field as result of a new data source we integrated * **Job Posting Data** * We saw continued growth in our recently released Job Posting dataset with a \~19% increase in total number of posts and \~5-6% increase number of unique companies and active job posts ## Improvements and Bug Fixes ### Improvements * **Improved Title Cleaning** * We refined our title cleaning process to preserve text within parentheses. This fix helps prevent unintended merges in cases where experience records are distinguished by the text within parentheses. For example, "Manager (NYC Area)" and "Manager (Northeast Region)" will now remain separate experiences. * **Name Alias Updates** * We enhanced our name alias matching to recognize similar names, improving record merges and API matching. * **Name Cleaning Improvements** * We improved our name cleaning process to remove extraneous text, such as website URLs, business names, or email characters, that were incorrectly appearing in name fields (e.g. `full_name = "JAMES HTTPS"`) ### Bug Fixes * **API Dashboard Batch Enrich Tool error** * Users will no longer experience a perpetual load state when starting a new job on the last step of the Batch Enrich tool * **Peru Location Cleaning Fix** * We fixed an issue where locations spelled "Perú" with the accent were incorrectly mapped to Peru, Nebraska. * **School Over-Canonicalization** * We resolved an issue from last month's build where schools were being over-canonicalized to generic names like "Campus" or "Senior High School." We also fixed cases where some school abbreviations were incorrectly canonicalized to similar but unrelated school names. * **CCO Title Standardization** * We fixed our job title cleaner so that the title "CCO" is no longer automatically standardized to Chief Creative Officer, since it can also represent Chief Compliance Officer or Chief Customer Officer. # August 2026 Release Notes Source: https://docs.peopledatalabs.com/changelog/august-2026-release-notes-v351 | Release Name | Dataset Version | Publish Date | | :----------: | :-------------: | :----------: | | August 2026 | v35.1 | 08/18/2026 | **Welcome to our August 2026 release notes!** The end of summer is just around the corner, but that doesn’t mean the fun has to stop! This month, we’ve got some significant updates to our new Technology Data, some updates for our Company Funding Details bundle, and a host of other data quality and freshness improvements for you to enjoy. Check it out: * 🔮 **[Technology Data Improvements](#technology-data-improvements)**: 3x more technologies and 6 new fields to give you a more complete picture of a company’s technology usage and adoption * 💰 **[More Funding Details Fields](#new-funding-details-fields)**: 3 new fields to help display investor information more easily * 🔧 [**Data Quality & Coverage Improvements**](#improvements-and-bug-fixes): More GitHub data and better title tagging! * **📊 [Freshness Updates](#freshness)**: This past month, we refreshed [30M+ resume experiences](#freshness) and [detected 2.7M+ job changes](#job-changes) across our global dataset *** ## ✨ Release Updates ### Technology Data Improvements Company Data Beta ✨ Product Update 📐 Schema Change **What’s New?** This month, we’re excited to share several significant improvements to the Technology Data fields we recently introduced within our [Company Data Schema](/docs/company-schema). Our new Technology Data fields offer a fresh take on traditional technographics by using workforce-based signals to identify the technologies companies likely use. This month’s updates include: 1. A 3x expansion of the number of technologies tracked in our dataset 2. A new set of fields displaying dates of signals and adoption | July 2026 (v35.0) | August 2026 (v35.1) | | :---------------: | :-----------------: | | 8,597 | 25,566 | Our [`technologies_used`](/docs/company-schema#technologies_used) fields track a fixed number of canonical technologies by identifying specific mentions across job postings and resume work experiences. At launch last month, we were monitoring roughly 8,000 canonical technologies. **This month, we’ve more than tripled that number and are now tracking over 25,000 unique technologies.** This expansion unlocks a significantly broader view of the technology landscape, and enables Technology Data users to discover, analyze, and act on more signals across more companies. For additional stats, see the [Technology Data coverage](#coverage) section below. **New Technology Data Fields** We’ve also added additional Technology Data fields as a fast follow to our release last month. Technographics are often a black box when it comes to the timeliness of the represented signals. As part of our commitment to transparency, we’ve added timestamps of the first and last observation for each source of signals in our Technology Data. We’ve also created a statistically inferred range, built off the observations (but excluding outliers) to create PDL’s “best estimate” of when a technology was used by the company. | FIELD NAME | FIELD TYPE | FIELD BUNDLE | FIELD DESCRIPTION | | :--------------------------------------------------------------------- | :-------------- | :-------------- | :--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | [`job_posting_first_observed`](/docs/company-schema#technologies_used) | `String (Date)` | Technology Data | The earliest date in which a technology is mentioned in a job posting associated with the company. | | [`job_posting_last_observed`](/docs/company-schema#technologies_used) | `String (Date)` | Technology Data | The latest of the final observed date (inactive job postings) or most recent data build (active job postings) in which a technology is mentioned in a job posting associated with the company. | | [`resume_first_observed`](/docs/company-schema#technologies_used) | `String (Date)` | Technology Data | The earliest date in which a technology is mentioned in work experience associated with the company. | | [`resume_last_observed`](/docs/company-schema#technologies_used) | `String (Date)` | Technology Data | The end date (inactive work experience) or most recent data build (active work experience) in which a technology is mentioned in resume work experience associated with the company. | | [`inferred_first_used`](/docs/company-schema#technologies_used) | `String (Date)` | Technology Data | A proprietary PDL calculation representing the first point in which the company was most likely to be using a technology. | | [`inferred_last_used`](/docs/company-schema#technologies_used) | `String (Date)` | Technology Data | A proprietary PDL calculation representing the most recent point in which the company was most likely to be using a technology. | **Example** ```json theme={null} { "technologies_used": [ { "product_id": "aV8mYR0sZFCrWvdkco07nwi7tGTt", "name": "Databricks", "num_job_posting_mentions": 14, "job_posting_first_observed": "2024-12-08", "job_posting_last_observed": "2026-07-01", "num_resume_mentions": 6, "resume_first_observed": "2020-06-01", "resume_last_observed": "2026-07-01", "inferred_first_used": "2024-12-08", "inferred_last_used": "2026-07-01" }, { "product_id": "ZNJNyjIICYIBrhIOyxG5iQfQvzLt", "name": "Apache Spark", "num_job_posting_mentions": 14, "job_posting_first_observed": "2024-12-08", "job_posting_last_observed": "2026-07-01", "num_resume_mentions": 5, "resume_first_observed": "2021-05-01", "resume_last_observed": "2026-07-01", "inferred_first_used": "2024-03-01", "inferred_last_used": "2026-07-01" } ] } ``` **Why It Matters** These new fields provide observation counts from company job postings and employee work experiences, along with freshness indicators for each technology signal. Together, they give you more context into both the strength and recency of a company’s technology usage. Combined with our increased coverage, these updates provide a more complete picture of technology usage at individual companies, as well as broader market adoption and penetration across technologies. **Availability** These fields are now available through the [Technology Data](/docs/company-data-field-bundles#technology-data) beta bundle for select Company Data customers. To ask about joining the beta, please reach out to your account team. For more details, see the [`technologies_used`](/docs/company-schema#technologies_used) field reference, the [Company Data Field Bundles](/docs/company-data-field-bundles#technology-data) page, and the [Example Company Record](/docs/example-company-record). *** ### New Funding Details Fields Company Data GA ✨ Product Update 📐 Schema Change **What’s New** This month, we’re also releasing a new set of `investing_companies_details` fields for our Funding Details bundle within our [Company Schema](/docs/company-schema). These fields make it easier for users to access and display information about a company’s investor entities. **New Funding Details Fields** | FIELD NAME | FIELD TYPE | FIELD BUNDLE | FIELD DESCRIPTION | | :----------------------------------------------------------- | :--------------- | :-------------- | :------------------------------------------------------------------------------- | | `investing_companies_details` | `Array (Object)` | Funding Details | Object containing all associated companies participating in the funding event. | | `investing_companies_details.investing_company_display_name` | `String` | Funding Details | The displayable names of investing companies participating in the funding event. | | `investing_companies_details.investing_company_id` | `String` | Funding Details | The PDL IDs of investing companies participating in the funding event. | **Example** ```json theme={null} { "investing_companies_details": [ { "investing_company_id": "1xJFYjurbJy1OUqmwhF76ADMReXB", "investing_company_display_name": "Andreessen Horowitz" } ] } ``` **Why This Matters** Previously, customers using the Funding Details bundle had no way of displaying investor information without additional processing. The existing `investing_companies` field contains only PDL Company IDs, which require additional data or API calls to resolve into displayable company names. The new `investing_companies_details` field complements the existing `investing_companies` field by providing displayable company names directly in the company record, removing the need for additional processing steps. This is a lightweight, but meaningful update intended to make our Funding Details data easier to work with. **Availability** These new fields are immediately available to all customers currently receiving the Funding Details field bundle or custom bundles that include the `investing_companies` field. **Additional Resources** For field definitions, examples, and additional documentation, see the [Company Schema](/docs/company-schema) and [Company Data Field Bundles](/docs/company-data-field-bundles) pages. *** ## 🚀 Data Updates ### Freshness *The number of resume experiences and locations verified in our datasets (based on the [`job_last_verified`](/docs/fields#job_last_verified) and [`location_last_updated`](/docs/fields#location_last_updated) fields).* **Monthly (v35.0 → v35.1)**\ *Freshness updates over the past month.* | Dataset | Geography | Field | Records Updated | | :------ | :------------ | :----------- | :-------------- | | Resume | Global | `experience` | 30,769,403 | | Resume | Global | `location` | 29,432,860 | | Resume | United States | `experience` | 15,270,033 | | Resume | United States | `location` | 14,517,173 | ### Job Changes *The number of person records where the primary job experience changed in our Person Dataset (based on the [`job_last_changed`](/docs/fields#job_last_changed) field).* **Monthly (v35.0 → v35.1)**\ *Job changes detected over the past month.* | Dataset | Geography | Records Updated | | :------ | :------------ | :-------------- | | Resume | Global | 2,741,832 | | Resume | United States | 918,203 | *** ## 🌐 Coverage ### Monthly Highlights (v35.0 → v35.1) | Linkage | Coverage in v35.0 | Coverage in v35.1 | Increase (%) | | :------------ | ----------------- | ----------------- | ------------ | | Total Records | 814,778,903 | 814,867,031 | 0.01% | | `github_url` | 1,994,722 | 2,075,559 | 4.05% | | Linkage | Coverage in v35.0 | Coverage in v35.1 | Increase (%) | | :------------- | ----------------- | ----------------- | ------------ | | Total Records | 4,083,001 | 4,166,504 | 2.05% | | `linkedin_url` | 1,743,324 | 1,819,345 | 4.36% | | `id` | 4,085,892 | 4,169,337 | 2.04% | | Linkage | Coverage in v35.0 | Coverage in v35.1 | Increase (%) | | :------------------------- | ----------------- | ----------------- | ------------ | | Total Records | 74,753,971 | 74,785,388 | 0.042% | | `technologies_used` | 6,349,659 | 6,462,182 | 1.77% | | `active_job_postings` | 108,549 | 109,709 | 1.07% | | `deactivated_job_postings` | 108,549 | 109,709 | 1.07% | | Metric | Coverage in v35.0 | Coverage in v35.1 | Increase (%) | | :--------------------- | ----------------- | ----------------- | ------------ | | Total Records | 37,001,534 | 40,614,651 | 9.76% | | Total Unique Companies | 108,626 | 109,824 | 1.10% | | Total Active Postings | 6,188,347 | 6,293,692 | 1.70% |
| Metric | Coverage in v35.0 | Coverage in v35.1 | Increase (%) | | :----------------------------------------------------- | ----------------- | ----------------- | ------------ | | Technologies Tracked | 8,597 | 25,566 | 197.38% | | Technologies Observed | 7,553 | 22,249 | 194.57% | | Companies with Technology Data | 6,349,659 | 6,462,182 | 1.77% | | Observed Company\<>Technology Pairs | 51,098,313 | 53,635,904 | 4.97% | | Total Technology Mentions | 180,400,858 | 186,560,858 | 3.41% |
### Commentary * **Person Data** * We saw a \~4% increase in the number of linkages between `linkedin_url` and `github_url` across both our resume and developer datasets. * **Company Data** * We saw a 1.77% increase in the number of company records with `technologies_used`, building on the broader [Technology Data improvements](#technology-data-improvements) described above. * **Technology Data** * We saw a 3x increase in the number of canonical technologies tracked and observed in our dataset this month. *** ## 🛠 Improvements and Bug Fixes ### Improvements * **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. * **GitHub Data Improvements** * We are continuing to increase coverage of our developer dataset by increasing the number of `github_url`'s that we can track and link to `linkedin_url`'s. * This month we saw another 4% increase building on the previous few months of improvements in this area (see [stats above](#coverage)). # December 2024 Release Notes Source: https://docs.peopledatalabs.com/changelog/december-2024-release-notes-v282 | Release Name | Dataset Version | Publish Date | | :------------ | :-------------- | :----------- | | December 2024 | `v28.2` | 12/03/2024 | *v28.2 was released on December 3 2024.* **December 2024 (v28.2) is a Minor Release** PDL releases data updates every month with a major release every quarter. Minor releases (such as v28.2) typically contain fewer product updates or key changes, but still contain important data improvements. Welcome to our December 2024 release notes! We have some exciting updates to share for the last month of the year: Here are the key highlights: * The beta release of our new [Person Changelog API](#changelog-api) endpoint! * Significant quality improvements to our [mobile phone data](#improvements) * Over [123M jobs verified and 674k job changes detected globally](#freshness) across our person dataset this month Excited yet? Read on to learn more, or jump to a specific section using the table of contents below. ## ❗Breaking Changes ### ⚠️ Upcoming Breaking Changes **Upcoming Breaking Changes** **Upcoming breaking changes** in future versions may impact your current processes. We are announcing them here to provide ample time for you to adjust your processes accordingly. #### ⚠️ New Role and Sub Role Job Title Taxonomy (Person / Company / IP) Change expected in: **February 2025** **Previous Announcements**: [v26 / April 2024](/changelog/april-2024-release-announcement-v260#title-tagging-updates), [v27.0 / July 2024](/changelog/july-2024-release-announcement-v270#title-taxonomy), [v27.1 / August 2024](/changelog/august-2024-release-announcement-v271#title-taxonomy), [v27.2 / September 2024](/changelog/september-2024-release-announcement-v272#title-taxonomy), [v28.0 / October 2024](/changelog/october-2024-release-announcement-v280#title-taxonomy), [v28.1 / November 2024](/changelog/november-2024-release-notes-v281#title-taxonomy) Products Impacted: **Person / Company / IP Schema**
[Person](/docs/fields) Fields Impacted [Company](/docs/company-schema) Fields Impacted [IP](/docs/ip-fields) Fields Impacted
`job_title_role` `job_title_sub_role` `experience.title.role` `experience.title.sub_role` `average_tenure_by_role`\ `employee_count_by_month_by_role`\ `employee_count_by_role`\ `recent_exec_departures`\ `recent_exec_hires`\ `top_next_employers_by_role`\ `top_previous_employers_by_role` `person.job_title_role`\ `person.job_title_sub_role`
Last month (v28.0), we officially released our new Role and Sub Role Job Title Taxonomy for full **General Availability** to all customers. With the GA release of this new taxonomy, the previous (legacy) taxonomy has now entered its deprecation period with support fully ending as of February 2025 (v29.1). **Legacy Taxonomy will be fully deprecated in February 2025** As of the February 2025 (v29.1 release, PDL datasets for **all customers** will be transitioned to the new taxonomy. To access the new taxonomy, customers must explicitly opt-in for `v28.1`, `v28.2`, and `v29.0` (Nov - Jan releases) by reaching out to your Account team to enable these fields in your data deliveries. API customers can access the new taxonomy by using a new updated\_title\_roles parameter in their API requests. Existing customers still using the legacy taxonomy can choose to delay opting-in to receive the new taxonomy until the legacy taxonomy is fully deprecated in the v29.1 release. **Our Recommendations** If you are an existing customer who has not yet evaluated the new taxonomy: * Please reach out to receive a sample as soon as possible. * Opt-in to the new taxonomy and begin transitioning your systems to the new taxonomy. The January 2025 (v29.0) release will be the last supported release that you will be able to receive the legacy taxonomy. In February (v29.1), all customers will be transitioned to the new taxonomy. Connect with your CS and TS team to plan and coordinate your migration process. * If you are an API customer, you can begin accessing the new taxonomy by including a new `updated_title_roles` parameter in your API requests and setting it to `True`. If you an existing customer who has already begun evaluating the data or participated in the beta release: * Continue or begin your migration process. We strongly encourage you to fully transition your systems to using the new taxonomy as early as possible ahead of the February 2025 deprecation to provide time to address any unforeseen transition challenges you run into. If you are a new customer or you do not currently use any of the fields impacted by this change: * In February (v29.1), you will be automatically transitioned to the new taxonomy. * Again, if you are an API customer, you can access the new taxonomy by including a new `updated_title_roles` parameter in your API requests and setting it to `True`. ##### **Timeline** Given the scope of the changes, our goal is to provide clear visibility on the process and ample opportunity to work through this transition together. The projected timeline for this release is as follows: * :white\_check\_mark: **July 2024 - Breaking Change Announcement and Resource Launch:** * Public notice of our planned role / subrole transition and initial resources provided (see below) * :white\_check\_mark: **August 2024 - Beta:** * We will open up beta access to the new role / subrole taxonomy as well as a new data field `title.class` * Customers will be able to test sample data from our Technical Services team to explore the new taxonomy and the potential data impacts * We will release a guide documenting our recommended best practices for transitioning to the new taxonomy with the beta release as well * :white\_check\_mark: **October 2024 - General Availability:** * We will make the new role / subrole taxonomy generally available for all customers and begin the deprecation process for the previous taxonomy * Customers can opt in to accessing the new taxonomy via API (using a new `updated_title_roles` parameter) and flat file deliveries. Customers will have the ability to delay transitioning until their systems are updated * :next\_track\_button: **February 2025 - Final Deprecation:** * We will fully deprecate and officially end support for the previous taxonomy * All new and existing customers will be moved onto the new role / subrole taxonomy. ##### **Resources** Please use the following resources to better understand the upcoming changes and to start preparing for the transition. As always, reach out to your Customer Success and Technical Services teams for questions and support. The new set of canonical classes, roles, and subroles is here: * [Job Title Class \[post-v27.1\]](/docs/job-title-class-post-v271) * [Job Title Roles \[post-v27.1\]](/docs/job-title-roles-post-v271) * [Job Title Subroles \[post-v27.1\]](/docs/job-title-subroles-post-v271) * [Mapping Job Title Class to Roles to Subroles \[post-v27.1\]](/docs/mapping-job-title-class-to-roles-to-subroles-post-v271) The mapping from the current role/subrole taxonomy to the improved taxonomy is here: * [Role / Subrole Taxonomy Restructure \[post-v27.1\]](https://docs.google.com/spreadsheets/d/1XCYraEJnMIG5AgmVCzZOpdWZZMlIG7_xq5LXbSY-9b8/edit?usp=sharing) Sample records using the updated role / subrole taxonomy are here: * [Example Person Record \[New Role / Subrole Taxonomy\]](/docs/example-person-record-new-role-subrole-taxonomy) * [Example Company Record \[New Role / Subrole Taxonomy\]](/docs/example-company-record-new-role-subrole-taxonomy) * [Example IP Record \[New Role / Subrole Taxonomy\]](/docs/example-ip-record-new-role-subrole-taxonomy) #### ⚠️ New Release Schedule (All Products) Change expected in: **v29.0 / January 2025**\ Products Impacted: **All PDL Products** Beginning in January 2025 (v29.0), we will be modifying the schedule for our releases, shifting the release date by 15 days to the middle of the month. Currently, all releases (major and minor) occur on the first Tuesday of every month. Under the new schedule, all releases will occur on the **third Tuesday of the month**, with the first release following this new schedule occurring on January 21, 2024 (v29.0). **Why are we making this change?**\ The primary goal for this change is to increase the freshness of our Company Insights data, which summarizes aggregate employee headcounts to the “last completed month” of data. Shifting our release schedule by half a month allows us to calculate the aggregated headcount totals immediately after the completion of a month. The end result is that we will be able to report our Insights data with an extra month’s worth of information in each data release. **Timeline** Notice that between v28.2 and v29.0 there will be an additional gap of half a month as we shift from one release schedule to the other. | Release Version | Release Date | Comments | | :-------------- | :--------------- | :----------------------------- | | `v28.0` | Oct 1, 2024 | First Tuesday of the Month | | `v28.1` | Nov 5, 2024 | First Tuesday of the Month | | `v28.2` | Dec 3, 2024 | First Tuesday of the Month | | **`v29.0`** | **Jan 21, 2025** | **Third Tuesday of the Month** | | `v29.1` | Feb 18, 2025 | Third Tuesday of the Month | #### ⚠️ Deprecation of `gics_sector` (Company) Change expected in: **v29.0 / January 2025**\ Products Impacted: **Company** | [Company](/docs/company-schema) Fields Impacted | | :------------------------------------------------ | | [`gics_sector`](/docs/company-schema#gics_sector) | In January 2025 (v29.0), we will be removing the `gics_sector` field from our data. This change will only impact a subset of records in our company dataset. Currently, this field is only populated in \~27.8k PDL company records (0.003% of our company dataset) since it is derived from the self-identified industry sector reported in the filings of public companies. This field is redundant with other self-reported industry fields contained in our company records (which have much higher coverage). As a result, we have made the decision to deprecate this field in favor of our other industry field representations. For customers interested in continuing to source public company sector information, we recommend the following resources: * Free web sources: * [Finbox.com](http://finbox.com): Presents the GICS sector label on each company profile ([example](https://finbox.com/NASDAQGS:NVDA/)) * [Yahoo! Finance](http://finance.yahoo.com): Presents the Morningstar sector label on each company profile ([example](https://finance.yahoo.com/quote/NVDA/)) * Paid API and programmatic resources: * [SEC-API.io](http://SEC-API.io): Provides an API endpoint that returns the Morningstar sector label among the company attributes returned ([documentation](https://sec-api.io/docs/mapping-api/map-ticker-to-company-details)) * [Financial Modeling Prep](http://financialmodelingprep.com): Provides an API endpoint that returns the Morningstar sector label among the company attributes returned ([documentation](https://site.financialmodelingprep.com/developer/docs#company-profile-company-information))\
#### ⚠️ Deprecation of `version_status` (Person) Change expected in: **v29.0 / January 2025**\ **Previous Announcements**: [v17.0 / January 2022](/changelog/january-2022-release-notes-v17#deprecations-a-namedeprecationsa) Products Impacted: **Person** | [Person](/docs/fields) Fields Impacted | | :---------------------------------------------- | | [`version_status`](/docs/fields#version_status) | In January 2025 (v29.0), we will be removing the `version_status` field from our person dataset. We officially deprecated this field in January 2022 (v17.0). While this field has continued to exist in our data since then, we have introduced more reliable references to a profile’s history / lineage across releases via the recommended alternatives below. As such, we are fully removing this field from our schema. **Recommended Alternatives**\ For customers that were using the `version_status` field to lookup the current version of the data, please use the `dataset_version` field available in both our [Person](/docs/fields#dataset_version) and [Company](/docs/company-schema#dataset_version) records. For customers using this field to understand the change history of records, please use the ID Changelogs ([Person](/docs/id-changelog) / [Company](/docs/company-changelog)) for the relevant monthly / quarterly time period that you are looking to compare against. #### ⚠️ Free Tier Restructure for Self-Serve Plans Change expected in: **v29.0 / January 2025** Products Impacted: **Person**
[Person](/docs/fields) Fields Impacted
[`work_email`](/docs/fields#work_email) [`recommended_personal_email`](/docs/fields#recommended_personal_email) [`personal_emails`](/docs/fields#personal_emails) [`emails`](/docs/fields#emails) [`phone_numbers`](/docs/fields#phone_numbers) [`mobile_phone`](/docs/fields#mobile_phone) All [`locations`](/docs/fields#location) (except country and continent) [`birth_date`](/docs/fields#birth_date) [`birth_year`](/docs/fields#birth_year)
In January 2025, we will be restructuring all existing free-tier plans to limit access to specific fields in our Person datasets. This change impacts all self-serve customers with free tier plans created before July 29, 2024. Back in July 2024, we made the decision to limit access for new free tier plans to certain person fields that were prone to exploitation for unauthorized and potentially nefarious use cases. Based on the usage patterns we’ve observed since then, we have made the decision to migrate all legacy free tier users to this new free tier plan. This migration will go into effect in January 2025, after which the person fields shown in the table above will be converted from values to `true`/`false` flags. To continue accessing these fields, customers will need to upgrade to a Pro plan with at least \$100 minimum monthly commitment. **Example Free Tier Field** | Legacy Plan (Pre-Migration) | New Plan (Post-Migration) | | :-------------------------------------- | :------------------------ | | `”work_email”: “sr49@chang-fisher.com”` | `”work_email”: true` | *** ## ✨ New Products and Features ### Person Changelog API This month, we are excited to announce the beta release of our new [Person Changelog API](/docs/person-changelog-api). This new endpoint lets you instantly search for record changes across releases, without needing to ingest, host, or process any large files to do so. This solution also provides an easier way to interface with data updates compared to the Webhooks flow **How does it work?**\ The Person Changelog API is built on top of our existing Person Changelog, and provides an interface to directly query for information from the changelog. For example, you could use the Person Changelog API to identify all the records that were `deleted` in the last release, which would return the list of corresponding PDL IDs and metadata from the changelog. **What can you do with it?**\ One of the key benefits to using the Person Changelog API is using it to filter records based on which fields were updated. This means, you can easily perform queries over previous monthly/quarterly releases to: * Find all the records with new contact information from this release * Check if specific records had `updated` work experience from this release * Query for records that were `added`, `deleted`, `merged`, `opted_out`, or `updated` Subsequently, you can take the records IDs that you’ve retrieved and get the up-to-date data via the Person Enrichment API. **How to get started**\ The Person Changelog API is a free endpoint that is available to all PDL customers to use (similar to some of our other supporting endpoints, like our Cleaner APIs). All you need is a PDL API key (you can sign up for one for free), to begin using this API endpoint. We recommend checking out the [documentation pages](/docs/person-changelog-api) for additional details and code examples. If you have any product feedback or suggestions, please get in touch with your customer success team or share your input on the feature request ticket! *** ## 🚀 Data Updates **December 2024 is a Minor Release** As a reminder, December 2024 is a minor release. This means that the information reported below is based off of the **last one month of updates** (rather than the 3 months of updates we typically report for the major releases). ### Freshness *The number of jobs and locations verified in our datasets over the past**month** (based on the `job_last_verified` and `location_last_updated` fields).* | Dataset | Geography | Field | Records Updated | | ------- | ------------- | ---------- | --------------- | | Resume | Global | experience | 123,236,294 | | Resume | Global | location | 177,753,601 | | Resume | United States | experience | 45,307,700 | | Resume | United States | location | 57,613,402 | #### Job Changes *The number of person records where the primary job experience changed in our Person Dataset over the past**month** (based on the `job_last_changed` field).* | Dataset | Geography | Field | Records Updated | | ------- | --------- | ------------ | --------------- | | Resume | Global | `experience` | 674,504 | | Resume | US | `location` | 180,602 | ### Coverage (Full Stats: [Person](/docs/datasets), [Company](/docs/company-stats)) **[Resume Dataset](/docs/resume-stats)** | Linkage | Coverage in v28.1 | Coverage in v28.2 | Increase (%) | | -------------- | ----------------- | ----------------- | ------------ | | total\_records | 724,408,322 | 735,903,932 | 1.59% | | mobile\_phone | 68,535,584 | 57,551,615 | -16.03% | **[API Dataset](/docs/stats)** | Linkage | Coverage in v28.1 | Coverage in v28.2 | Increase (%) | | -------------- | ----------------- | ----------------- | ------------ | | total\_records | 2,462,408,799 | 2,472,221,284 | 0.40% | **[Email Dataset](/docs/email-stats)** | Linkage | Coverage in v28.1 | Coverage in v28.2 | Increase (%) | | -------------- | ----------------- | ----------------- | ------------ | | total\_records | 637,512,395 | 636,228,659 | -0.20% | **[Mobile Phone Dataset](/docs/mobile-phone-stats)** | Linkage | Coverage in v28.1 | Coverage in v28.2 | Increase (%) | | -------------- | ----------------- | ----------------- | ------------ | | total\_records | 587,370,396 | 486,453,297 | -17.18% | **[Company Dataset](/docs/company-stats)** | Linkage | Coverage in v28.1 | Coverage in v28.2 | Increase (%) | | -------------- | ----------------- | ----------------- | ------------ | | total\_records | 71,418,115 | 71,470,878 | 0.07% | ### Commentary * We saw a significant decrease in the number of mobile phones across our datasets as a result of our mobile phone quality improvement (see below). *** ## 🛠 Improvements and Bug Fixes ### Improvements * This month, we released several improvements for our Mobile Phone data: * Better accuracy in mobile phone tagging: We demoted phone numbers from the `mobile_phone` field into the `phones` array that did not correspond to cell numbers or are no longer owned by the associated person * Improved mobile phone promotion: numbers in the `phones` array that were determined to be mobile are now elevated to the mobile\_phone field * Ensured unique ownership: each `mobile_phone` is now uniquely linked to one person, distinguished based on first name. * **Updated list of company websites where we allow subdomains and paths** * For v28.1 we had narrowed the list of company websites for which we allow a subdomain or path. Unfortunately, this resulted in unwanted duplication of the website field for important websites, including “apple.com” and “amazon.com”. * For v28.2 we reverted this change and further expanded the list of company domains for which we allow a subdomain and a path. * For v28.2 users can still expect to find some longtail cases of duplication in the website field. The team is working on a solution to ensure the website field is distinct. ### Bug Fixes * We made improvements to our school name canonicalization * We fixed a bug that was allowing certain certifications to appear in profile name fields (e.g. `MCIPS` or `FRCPC` certifications) * We fixed a bug that resulted in inaccurate `inferred_revenue` values for \~1,600 large, public companies. * We fixed a bug that allowed individuals to have -1 `inferred_years_experience` # December 2025 Release Notes Source: https://docs.peopledatalabs.com/changelog/december-2025-release-notes-v322 | Release Name | Dataset Version | Publish Date | | :------------ | :-------------- | :----------- | | December 2025 | `v32.2` | 12/17/2025 | **Welcome to our December 2025 release notes!** Check out the updates below to stay up to date! Here's what's new: * **📊 Freshness Updates**: This past quarter, we verified 278M+ jobs and tracked 723K+ job changes across our global dataset * **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. ## 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: **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. **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). **Sample API Output - Slack Technologies:** ```json JSON expandable theme={null} { "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": [ { "affiliated_id": "es7LgyqRNsFDLcWXC3WAvACHVh9g", "display_name": "Salesforce", "relationship": "ultimate_parent", "relationship_catalyst": "direct_acquisition", "relationship_status": "active", "start_date": "2021-07-21", "end_date": null, "relationship_citations": [ "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** 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. We are eager for your feedback on the new relationship metadata fields! ## Data Updates ### Freshness **Monthly (v32.1 → v32.2)** *Freshness updates over the past month.* | Dataset | Geography | Field | Records Updated | | :------ | :------------ | :----------- | :-------------- | | Resume | Global | `experience` | 139,582,884 | | Resume | Global | `location` | 230,190,486 | | Resume | United States | `experience` | 38,458,917 | | Resume | United States | `location` | 58,918,578 | ### 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.* | Dataset | Geography | Records Updated | | :------ | :------------ | :-------------- | | Resume | Global | 2,578,976 | | Resume | United States | 847,716 | ### Coverage **Monthly (v32.1 → v32.2)** **[Resume Dataset](/docs/resume-stats)** | Linkage | Coverage in v32.1 | Coverage in v32.2 | Increase (%) | | :-------------------- | :---------------- | :---------------- | :----------- | | Total Records | 785,976,953 | 784,435,329 | -0.20% | | `linkedin_id` | 519,260,749 | 551,022,808 | 6.12% | | `work_email` | 74,415,166 | 75,836,800 | 1.91% | | `education.school.id` | 300,585,468 | 326,032,588 | -7.81% | **[API Dataset](/docs/stats)** | Linkage | Coverage in v32.1 | Coverage in v32.2 | Increase (%) | | :----------------- | :---------------- | :---------------- | :----------- | | Total Records | 2,446,253,614 | 2,439,406,806 | -0.28% | | `education.school` | 728,909,950 | 693,983,165 | 5.03% | **[Email Dataset](/docs/email-stats)** | Linkage | Coverage in v32.1 | Coverage in v32.2 | Increase (%) | | :------------ | :---------------- | :---------------- | :----------- | | Total Records | 590,217,603 | 587,112,581 | -0.53% | **[Mobile Phone Dataset](/docs/mobile-phone-stats)** | Linkage | Coverage in v32.1 | Coverage in v32.2 | Increase (%) | | :------------ | :---------------- | :---------------- | :----------- | | Total Records | 481,467,452 | 479,598,849 | -0.39% | **[Company Dataset](/docs/company-stats)** | Linkage | Coverage in v32.1 | Coverage in v32.2 | Increase (%) | | :------------ | :---------------- | :---------------- | :----------- | | Total Records | 75,127,700 | 74,745,952 | -0.51% | **[Job Posting Dataset](/docs/jp-stats)** | Linkage | Coverage in v32.1 | Coverage in v32.2 | Increase (%) | | :--------------------- | :---------------- | :---------------- | :----------- | | Total Records | 19,541,264 | 20,815,990 | 6.52% | | Total Unique Companies | | 44,631 | 2.16% | | Total Active Postings | 2,587,181 | 2,425,730 | -6.24% | ### 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 * **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. * **Certification Abbreviations in Names** * We expanded the list of certifications to drop in our name cleaners so common abbreviations are removed (Joe Smith, CENG). * **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. ### Bug Fixes * **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. * **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. * **Education School Raw** * There was a bug that was causing many Linkedin URLs to appear in the `education.school.raw` field that has been fixed and has restored the field to our pre-canonicalized text school values. # February 2024 Release Announcement Source: https://docs.peopledatalabs.com/changelog/february-2024-release-announcement-v25-1 **This announcement is for PDL Snowflake Customers** If you are a current PDL customer receiving data through Snowflake, please read this announcement regarding the upcoming changes to the Snowflake Table Schemas scheduled for the May 2024 release. ## ⚠️ Snowflake Schema Standardization **Change Expected In: v26.1 / May 2024**\ Previous Announcements: [v24 / October 2023](/changelog/october-2023-release-notes-v24), [v25 / January 2024](/changelog/january-2024-release-notes-v25#snowflake) As announced in our previous release notes (linked above) we will be standardizing our Snowflake Person and Company Schemas **in May 2024 (v26.1)**. This will be a breaking change to our existing Snowflake schema, and so this announcement aims to provide some additional resources and information to prepare our customers for the transition. ### Summary of Schema Changes We are migrating all Snowflake users to a common delivery schema, which represents changes to the current format that data is being received in. These changes apply to both the **Person and Company Snowflake Schema** and include: * Table and column name changes * Additions/modifications of columns within tables * Data type changes across columns The summary of these changes is as follows: **Person Schema Changes for Snowflake** * (Table Rename) “Plural” table names will now be “Singular” (i.e. `languages` is now `language`, `certifications` is now `certification`, etc) * (Column Rename) `num_sources` will now be `count_sources` * (Column Rename) `num_records` will now be `count_records` * (Column Rename) `linkedin_connections` will now be `count_linkedin_connections` * (Column Rename) `facebook_friends` will now be `count_facebook_friends` * (Column Rename) `gender` will now be `sex` * (Type Change) All `Date` types will now be `String` types **Company Schema Changes for Snowflake** * (Table Rename) “Plural” table names will now be “Singular” (i.e. `subsidiaries` is now `subsidiary`, `profiles` is now `profile`, etc) * (Table Schema Change) Table `top_us_employee_metro` now contains separate columns for `headcount` (`INT`) and `growth_rate_12_month` (`FLOAT`) * (Column Rename) `top_next_employer_by_role.employer` will be renamed to `top_next_employer_by_role.next_company_id` * (Column Rename) `top_previous_employer_by_role.employer` will be renamed to `top_previous_employer_by_role.previous_company_id` * (Column Rename) `recent_exec_departure.pdl_id` will be renamed to `recent_exec_departure.person_id` * (Column Rename) `recent_exec_departure_job_title_level.pdl_id` will be renamed to `recent_exec_departure_job_title_level.person_id` * (Column Rename) `recent_exec_departure_new_company_job_title_level.pdl_id` will be renamed to `recent_exec_departure_new_company_job_title_level.person_id` * (Column Rename) `recent_exec_hire.pdl_id` will be renamed to `recent_exec_hire.person_id` * (Column Rename) `recent_exec_hire_job_title_level.pdl_id` will be renamed to `recent_exec_hire_job_title_level.person_id` * (Column Rename) `recent_exec_hire_previous_company_job_title_level.pdl_id` will be renamed to `recent_exec_hire_previous_company_job_title_level.person_id` * (Column Rename) All columns referencing employee count metrics will be renamed to `count` * (Column Rename) More descriptive columns within tables describing growth rates (e.g. column `tenure` in table `average_tenure_by_level` and column `growth_rate` in table `headcount_12mo_growth_by_role`) * (Column Rename) Closer adherence to SQL naming conventions (e.g. `linkedin_employee_count` will now be `count_linkedin_employee` * (Type Change) All `Date` types will now be `String` types ### How to Prepare for the Transition Before the May 2024 (v26.1), we strongly suggest you: 1. Make a copy of your current data after your April 2024 delivery. This way you not only have a backup, but can also compare new to old after you switch over. 2. Go through the new standard schemas, which are included in the **Resources** section below as well as [here](/docs/data-delivery-using-snowflake#standard-schemas) 3. Prepare any script changes to your existing processes before the switch in May 2024. For any questions or help transitioning to these new schema, please reach out to your Customer Success Manager. ### Resources **Standard Schemas** We now have explicit documentation of the Person and Company Snowflake Schemas that will go into effect with the May 2024 Release (v26.1). We encourage our snowflake customers to ensure their data pipelines can support the specifications linked below. These documents are also linked in the [Data Delivery Using Snowflake](/docs/data-delivery-using-snowflake#standard-schemas) page as well. * [Person Schema for Snowflake (v26.1)](https://drive.google.com/file/d/1AFGb2CLTOUUSdC0XZzND0NDvYCyHtOQG/view?usp=sharing) * [Company Schema for Snowflake (v26.1)](https://drive.google.com/file/d/15FIv6U1O6BzLAhYvv8tmNsDDGvq30xQq/view?usp=sharing) **Snowflake Data Sample** In addition, we will also have some sample data in these new schema formats available for customers to test with to ensure their data pipelines fully support the upcoming changes. * Data Sample on Snowflake Marketplace (coming soon) # February 2025 Release Notes Source: https://docs.peopledatalabs.com/changelog/february-2025-release-notes-v291 | Release Name | Dataset Version | Publish Date | | :------------ | :-------------- | :----------- | | February 2025 | `v29.1` | 02/18/2025 | **Welcome to our February 2025 release notes!** This month, we’re bringing you some exciting updates that make our data fresher, cleaner, and more actionable than ever. Here’s what’s new: * 👋 **Goodbye, Legacy Taxonomy!** The final removal of the [Legacy "Role" / "Sub Role" Taxonomy](#title-taxonomy) is now here. * 🧑‍💼 **Improved Person Records**. [Headline coverage increased 61%](#commentary) alongside [improvements to our `summary` field](#improvements) quality. * :earth\_americas: **Global Data Refresh**. We [verified 47M+ jobs](#freshness) and [detected 3.6M job changes](#job-changes) across our global dataset this month. Dive into the details below, or jump to a specific section using the table of contents. ## 📣 Key Announcements ### Schema Changes #### New field `job_title_class` ([Person Schema](/docs/person-schema#job_title_class)) | Field Name | Field Type | Field Description | | :------------------------------------------------------- | :--------------------------------------- | :----------------------------------------------------------------------------------------------------------------------- | | [`job_title_class`](/docs/fields#job_title_class) | [`Enum (String)`](/docs/job-title-class) | The expense line item category this employee would fall into. One of the [Canonical Job Classes](/docs/job-title-class). | | [`experience.title.class`](/docs/fields#experiencetitle) | [`Enum (String)`](/docs/job-title-class) | The canonicalized [Job Class](/docs/job-title-class) associated with this job experience | This month, the `job_title_class` and `experience.title.class` fields are now officially included in all person records as a result of the [sunsetting](#title-taxonomy) of our legacy taxonomy for role and sub roles. These fields were first made available in v27.1 via an opt-in parameter. *** ## ❗Breaking Changes (Going Live This Month) ### ❗ Final Sunset of Legacy Role and Sub Role Job Title Taxonomy Change expected in: **v29.1 / February 2025** **Previous Announcements**: [v26 / Apr. 2024](/changelog/april-2024-release-announcement-v260#title-tagging-updates), [v27.0 / Jul. 2024](/changelog/july-2024-release-announcement-v270#title-taxonomy), [v27.1 / Aug. 2024](/changelog/august-2024-release-announcement-v271#title-taxonomy), [v27.2 / Sep. 2024](/changelog/september-2024-release-announcement-v272#title-taxonomy), [v28.0 / Oct. 2024](/changelog/october-2024-release-announcement-v280#title-taxonomy), [v28.1 / Nov. 2024](/changelog/november-2024-release-notes-v281#title-taxonomy), [v28.2 / Dec. 2024](/changelog/december-2024-release-notes-v282#title-taxonomy), [v29.0 / Jan. 2025](/changelog/january-2025-release-notes-v290#title-taxonomy) Products Impacted: **Person / Company / IP Schema**
[Person](/docs/fields) Fields Impacted [Company](/docs/company-schema) Fields Impacted [IP](/docs/ip-fields) Fields Impacted
`job_title_role` `job_title_sub_role` `experience.title.role` `experience.title.sub_role` `average_tenure_by_role`\ `employee_count_by_month_by_role`\ `employee_count_by_role`\ `recent_exec_departures`\ `recent_exec_hires`\ `top_next_employers_by_role`\ `top_previous_employers_by_role` `person.job_title_role`\ `person.job_title_sub_role`
As of this month’s release, we have fully ended support for our legacy Role and Sub Role Taxonomy. All PDL datasets for all customers have now been transitioned to the new taxonomy. **As of this month’s release (February 2025, v29.1), all PDL datasets for all customers have been transitioned to the new taxonomy.** **What This Means for You** With the final transition to the new taxonomy now in effect, customers will no longer receive datasets using the legacy role and sub role taxonomy. All data will now be delivered using the updated class, roles and subroles values. **For Customers Who Have Already Transitioned** If you’re a Data License using the new taxonomy, no further action is needed. You will continue to receive your data as normal. If you’re an API customer, the `updated_title_roles` parameter is no longer needed in your API requests. **For Customers Who Have Not Yet Transitioned** If you haven’t yet transitioned, this release marks the end of the legacy taxonomy. Data from this month’s build onwards will now contain fields using the new taxonomy, so you will need to migrate your systems to support the new taxonomy. ##### **Resources** If needed, please use the following resources to migrate to the new taxonomy. As always, reach out to your Customer Success and Technical Services teams for questions and support. Documentation for the current Class, Role and Sub Role values can be found here: * [Job Title Class](/docs/job-title-class) * [Job Title Roles](/docs/job-title-roles) * [Job Title Subroles](/docs/job-title-subroles) * [Mapping Job Title Class to Roles to Subroles](/docs/title-subroles-to-roles) **Legacy Documentation** Documentation for the **legacy** role and sub role canonical fields will be preserved for the time being here: * [Legacy Job Title Roles (pre-v27.1)](/docs/job-title-roles-legacy-v271) * [Legacy Job Title Sub Roles (pre-v27.1)](/docs/job-title-subroles-legacy-v271) * [Legacy Mapping of Roles to Sub Roles (pre-v27.1)](/docs/legacy-mapping-title-subroles-to-roles-prev-v271) The mapping from the legacy taxonomy to the new taxonomy can still be found here: * [Role / Subrole Taxonomy Restructure \[post-v27.1\]](https://docs.google.com/spreadsheets/d/1XCYraEJnMIG5AgmVCzZOpdWZZMlIG7_xq5LXbSY-9b8/edit?usp=sharing) ### ⚠️ Upcoming Breaking Changes **Upcoming Breaking Changes** **Upcoming breaking changes** in future versions may impact your current processes. We are announcing them here to provide ample time for you to adjust your processes accordingly. #### ⚠️ Snowflake Listing Migration Change expected in: **v30.0 / April 2025** **Previous Announcements**: [v29.0 / Jan. 2025](/changelog/january-2025-release-notes-v290#snowflake-migration) Products Impacted: **Snowflake Listings** | Products Impacted | | :----------------------------------------------------------------------- | | [Snowflake Data License Deliveries](/docs/data-delivery-using-snowflake) | In April 2025, we will be migrating all Snowflake customers with multiple listings to a single listing per customer. **Why this change?**\ Historically, Snowflake customers receiving multiple data entities (i.e. both Person and Company datasets) were assigned separate listings in Snowflake for each entity. As of August 2024, we transitioned all new customers to a single-listing approach that improved our ability to support and deliver customer data. By April 2025, we will be migrating our remaining Snowflake customers to a single listing. **Options for Migration**\ For customers with multiple listings, there are 2 options for migrating to a single listing: 1. **New Listing (recommended, default)**: PDL creates a new listing for the customer, and moves all data from the pre-existing listings into the new listing. All pre-existing listings will be removed. *Note that this is the recommended approach as it allows more time for customers to transition and ensures acceptance of the new format and listing. This is also the default option that will be applied unless customers request otherwise.* 2. **Merge and Deprecate**: Customers can choose to keep one of their existing listings (e.g. Person) and the data from the other listing (e.g. Company) will be moved over to the first listing. Once the data has been moved over, PDL will remove the second listing. As mentioned above, we strongly recommend the **New Listing** approach (option 1) for customers as it ensures proper configuration and consistency across the transition. If no action is taken, customers will automatically be migrated using the **New Listing** approach. To begin your migration process or specify your desired migration approach, please connect with your Technical Services and Customer Account team. #### ⚠️ (*New*) Deprecation of Skill Enrichment API Change expected in: **v30.0 / April 2025** **Previous Announcements**: [v29.0 / Jan. 2025](/changelog/january-2025-release-notes-v290#skill-enrich-deprecation) Products Impacted: **Skill Enrichment API** | Products Impacted | | :------------------------------------------------- | | [Skill Enrichment API](/docs/skill-enrichment-api) | In April 2025, we will be deprecating the and removing the Skill Enrichment API. **Why this change?**\ The Job Title and Skill Enrichment APIs were designed to help improve the user experience when working with our Person Search API. However, based on historical usage patterns we’ve decided to reprioritize our efforts on these APIs. Specifically, we will be sunsetting the Skill Enrichment API, which has had limited usage, in favor of improving our Job Title Enrichment API (details of this will be announced in a future release). For any questions, please contact your Customer Account Team. If you have feedback or product suggestions, please share them in our [Roadmap Feature Request Board](https://feedback.peopledatalabs.com/)! *** ## 🚀 Data Updates **February 2025 is a Minor Release** As a reminder, February 2025 is a minor release. This means that the information reported below is based off of the **last one month of updates** (rather than the 3 months of updates we typically report for the major releases). ### Freshness *The number of jobs and locations verified in our datasets over the past**month** (based on the `job_last_verified` and `location_last_updated` fields).* #### Job Changes *The number of person records where the primary job experience changed in our Person Dataset over the past**month** (based on the `job_last_changed` field).* | Dataset | Geography | Records Updated | | :------ | :------------ | :-------------- | | Resume | Global | 3,644,509 | | Resume | United States | 910,060 | ### Coverage (Full Stats: [Person](/docs/datasets), [Company](/docs/company-stats)) **[Resume Dataset](/docs/resume-stats)** | Linkage | Coverage in v29.0 | Coverage in v29.1 | Increase (%) | | --------------------------- | ----------------- | ----------------- | ------------ | | `total_records` | 736,325,366 | 737,689,989 | 0.19% | | `job_title_sub_role` | 91,464,350 | 204,340,539 | 123.00% | | `experience.title.sub_role` | 165,187,811 | 295,335,283 | 79.00% | | `headline` | 38,462,189 | 61,893,388 | 61.00% | | `job_title_role` | 156,985,217 | 251,442,098 | 60.00% | | `experience.title.role` | 238,896,469 | 338,651,421 | 42.00% | | `job_summary` | 60,915,374 | 73,561,906 | 21.00% | | `summary` | 115,792,801 | 139,702,380 | 21.00% | | `experience.summary` | 136,829,932 | 163,860,520 | 20.00% | | `education.summary` | 52,533,343 | 59,057,687 | 12.00% | **[API Dataset](/docs/stats)** | Linkage | Coverage in v29.0 | Coverage in v29.1 | Increase (%) | | --------------- | ----------------- | ----------------- | ------------ | | `total_records` | 2,458,046,594 | 2,461,673,017 | 0.15% | **[Email Dataset](/docs/email-stats)** | Linkage | Coverage in v29.0 | Coverage in v29.1 | Increase (%) | | :-------------- | :---------------- | :---------------- | :----------- | | `total_records` | 634,898,506 | 635,947,701 | 0.17% | **[Mobile Phone Dataset](/docs/mobile-phone-stats)** | Linkage | Coverage in v29.0 | Coverage in v29.1 | Increase (%) | | :-------------- | :---------------- | :---------------- | :----------- | | `total_records` | 485,553,309 | 486,275,248 | 0.15% | **[Company Dataset](/docs/company-stats)** | Linkage | Coverage in v29.0 | Coverage in v29.1 | Increase (%) | | :-------------- | :---------------- | :---------------- | :----------- | | `total_records` | 71,478,660 | 71,479,382 | 0.001% | ### Commentary * We saw significant improvements in our fill rates for roles (\~42%) and sub roles (\~79%) in our resume dataset as a result of the release of the new Role and Sub Role taxonomy. * We saw a 61% increase in our coverage of `headline` as we continue to backfill headlines for person profiles. * We saw a roughly 20% increase in fill rates for summaries in our resume dataset as a result of some improvements to our cleaning logic ([see below](#improvements)) *** ## 🛠 Improvements and Bug Fixes ### Improvements * Person * Our new Role / Sub Role Taxonomy has now been released, providing increased fill rates and greater granularity of job title roles across our Person, Company and IP datasets. * We improved our summary cleaning logic to be more tolerant of non-English characters (such as diacritics) in summaries. We saw an increase in our `summary` fill rates this month, which will continue to increase in future builds as we re-crawl and re-ingest data. * We made improvements to our entity resolution logic to better handle profiles where individuals had changed their maiden / former last name into their middle name, resulting in us being able to merge an additional 1M records during this month’s build. * Company * We have removed the `unemployed` role tag from our Company Insights headcount calculations as part of the release of our Role / Sub Role Taxonomy * We updated our model for estimating `inferred_revenue` values for our Company records to leverage the role tagging improvements from the new Role / Sub Role Taxonomy. ### Bug Fixes * We fixed a bug in our Person build that was causing us to incorrectly drop work experiences from the `experience` array. * We fixed a bug in our new Role / Sub Role taxonomy that was non-deterministically selecting a role / sub\_role classification when multiple classifications were applicable. We are now taking a conservative approach by not providing a tag when multiple tags can apply. * We fixed a bug in our name parser that was incorrectly including the Certified Global Sanctions Specialist certification in the name fields for a subset of person records. # February 2026 Release Notes Source: https://docs.peopledatalabs.com/changelog/february-2026-release-notes-v331 | Release Name | Dataset Version | Publish Date | | :------------ | :-------------- | :----------- | | February 2026 | `v33.1` | 02/17/2026 | **Welcome to our February 2026 release notes** February may be the shortest month of the year, but this release is packed with plenty of exciting updates for you to check out! Here's what's new: * **📊 Freshness Updates**: This past month, we [verified 49M+ jobs](#freshness) and [detected 7M+ job changes](#job-changes) across our global dataset * ** [Big Data Gains](#-improvements-and-bug-fixes)**: Big improvements in our fill rates for `headline` and role tagging * ** [Job Posting Daily Deliveries](#announcements)**: Clearer directory structure organization for Job Posting Daily Delivery customers * ** [Email Quality, Leveled Up](#announcements)**: We are continuing to improve our email validation to support better deliverability and more reliable outreach. * ** [Person Data x Industry V2](#person-industry-v2-fields-person)**: Modern industry classifications now in the Person Dataset ## Announcements **Reminder: Ongoing Email Validation Improvements** We're continuing to improve the quality and deliverability of our `work_email` and `recommended_personal_emails` fields to ensure more reliable email performance over time. See the full announcement here: [Email Deliverability Improvements](/changelog/november-2025-release-notes-v321#/email-deliverability-improvements-person) Additional Resources: * [Email Deliverability Improvements Guide](https://www.peopledatalabs.com/pdf/email-deliverability-improvements-guide.pdf) * [Email Data for Outreach](/docs/email-data-for-outreach) **Reminder for Daily Job Posting Customers (Beta)** As of February 10, 2026, customers receiving Daily Job Posting Deliveries (Beta) now receive both monthly and daily files in an updated directory structure: Monthly (Full) Delivery: `YYYYMMDD_{current_release_version}/full/` Daily (delta) delivery: `YYYYMMDD_{current_release_version}/daily/` For more details, please see the full announcement: [Job Posting Daily Deliveries: Directory Structure Update (Feb 2026)](#job-posting-daily-deliveries-directory-structure-update-feb-2026) ## Schema Changes ### Person Industry V2 Fields ([Person](/docs/person-data-overview)) **What's New?** This month we're adding two new industry-related fields to the Person Dataset: | FIELD NAME | FIELD TYPE | FIELD BUNDLE | FIELD DESCRIPTION | | :----------------------------------------------------------------- | :------------------------------------- | :----------- | :--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | [`job_company_industry_v2`](/docs/fields#job_company_industry_v2) | [`Enum (String)`](/docs/industries-v2) | Person Base | The v2 industry for the person's current company. Industry v2 is the self-reported industry from an expanded list of [Canonical v2 Industries](/docs/industries-v2). If no industry is found, the field will be `null` | | [`experience.company.industry_v2`](/docs/fields#experiencecompany) | [`Enum (String)`](/docs/industries-v2) | Person Base | The v2 industry for the person's company. Industry v2 is the self-reported industry from an expanded list of [Canonical v2 Industries](/docs/industries-v2). If no industry is found, the field will be `null` | We originally released the [`industry_v2`](/docs/company-schema#industry_v2) for our Company Dataset in [September 2025 (v31.2)](/changelog/september-2025-release-notes-v312#new-company-industry-field-company-), and based on the strong customer demand, we've now added it to our Person Dataset as well! These fields capture the most recently observed industry classification reported by the associated company, and include expanded support for external industry taxonomies. It ensures our dataset reflects modernized industry categories that may differ from the legacy classifications still in use by the legacy industry fields. **Comparison to the legacy industry fields** The legacy industry fields in the person dataset will continue to be available with their functionality preserved: * `experience.company.industry` * `job_company_industry` These legacy fields will provide PDL's [original canonical industry taxonomy](/docs/industries), while the `industry_v2` field will provide classifications from an [expanded industry taxonomy](/docs/industries-v2). For most users, we recommend using the new `industry_v2` fields. However, if you have existing workflows reliant on the original PDL industry classifications, then you should continue to leverage the legacy industry field. **Why It Matters** These new fields bring a refreshed set of modern industry classification to our Person dataset, making it easier to filter, search, and categorize person records using an up-to-date taxonomy of industry classifications. Some of the key benefits include: * **Improved workflow compatibility** → better results in targeting, search, and discovery use cases that depend on modern industry categories * **No manual mapping required** → reduces the need to build and maintain your own taxonomy or conversion logic For customers using both our Person and Company Datasets, this update now ensures that you can use the same industry values across both datasets. **Availability** These fields are immediately available to all Person Data Customers and will be automatically included in all new data deliveries moving forward. **We'd Love Your Feedback!** Your input helps shape what we build next. Share your thoughts on these fields or suggest new ones via our [Roadmap Feature Request Board](https://feedback.peopledatalabs.com/)! ## Data Updates ### Freshness The number of jobs and locations verified in our datasets (based on the `job_last_verified` and `location_last_updated` fields). **Monthly (v33.0 → v33.1)** *Freshness updates over the past month.* | Dataset | Geography | Field | Records Updated | | :------ | :------------ | :----------- | :-------------- | | Resume | Global | `experience` | 49,965,247 | | Resume | Global | `location` | 75,221,768 | | Resume | United States | `experience` | 24,657,830 | | Resume | United States | `location` | 30,173,859 | ### 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 (v33.0 → v33.1)** *Freshness updates over the past month.* | Dataset | Geography | Records Updated | | :------ | :------------ | :-------------- | | Resume | Global | 7,880,536 | | Resume | United States | 2,877,546 | ### Coverage (Full Stats: [Person](/docs/datasets), [Company](/docs/company-stats), Job Posting, [IP](/docs/ip-stats)) **Monthly (v33.0 → v33.1)** **[Resume Dataset](/docs/resume-stats)** | Linkage | Coverage in v33.0 | Coverage in v33.1 | Increase (%) | | :-------------------------- | :---------------- | :---------------- | :----------- | | Total Records | 784,969,022 | 798,953,930 | 1.78% | | `headline` | 118,319,457 | 186,300,358 | 57.46% | | `work_email` | 75,144,765 | 64,587,835 | -14.05% | | `experience.title.role` | 371,439,134 | 398,397,592 | 7.26% | | `experience.title.class` | 371,439,134 | 398,397,592 | 7.26% | | `job_title_class` | 276,907,792 | 295,046,030 | 6.55% | | `job_title_role` | 276,907,792 | 295,046,030 | 6.55% | | `experience.title.sub_role` | 325,919,031 | 343,396,186 | 5.36% | **[API Dataset](/docs/stats)** | Linkage | Coverage in v33.0 | Coverage in v33.1 | Increase (%) | | :------------ | :---------------- | :---------------- | :----------- | | Total Records | 2,438,436,297 | 2,453,435,765 | 0.62% | **[Email Dataset](/docs/email-stats)** | Linkage | Coverage in v33.0 | Coverage in v33.1 | Increase (%) | | :------------ | :---------------- | :---------------- | :----------- | | Total Records | 586,865,405 | 587,237,067 | 0.06% | **[Mobile Phone Dataset](/docs/mobile-phone-stats)** | Linkage | Coverage in v33.0 | Coverage in v33.1 | Increase (%) | | :------------ | :---------------- | :---------------- | :----------- | | Total Records | 479,691,773 | 479,855,809 | 0.03% | **[Company Dataset](/docs/company-stats)** | Linkage | Coverage in v33.0 | Coverage in v33.1 | Increase (%) | | :------------ | :---------------- | :---------------- | :----------- | | Total Records | 74,672,539 | 74,679,887 | 0.010% | **[Job Posting Dataset](/docs/jp-stats)** | Linkage | Coverage in v33.0 | Coverage in v33.1 | Increase (%) | | :--------------------- | :---------------- | :---------------- | :----------- | | Total Records | 22,291,965 | 24,056,411 | 7.92% | | Total Unique Companies | 45,421 | 48,059 | 5.81% | | Total Active Postings | 2,410,753 | 2,792,394 | 15.83% | ### Commentary * **Person** * We saw a 14% decrease in our fill rate for `work_email` as a result of our ongoing Email Validation efforts (see [Improvements](#improvements)) * We saw a 5-7% increase in fill rate for our role-related fields in the resume dataset this month as a result of some improvements we made to our role tagging processes (see [Improvements](#improvements)) * We saw a 57% increase in our coverage of headlines due to a bug fix we pushed this month (see [Bug Fixes](#bug-fixes)) * **Job Posting Data** * This month, we added another 3k unique companies to our Job Posting dataset. ## Improvements and Bug Fixes ### Improvements * **Role Tagging Improvements** * We expanded our [Class/Role/SubRole taxonomy](/docs/title-subroles-to-roles) to include additional job titles (e.g. "Member of Technical Staff", "Marketing Manager"), improving role tagging coverage. * We added enhanced logic to better handle roles associated with multiple industries. * **Updated Canonical Degrees** * Removed canonical degree values with no representation in the dataset (e.g. `master of community planning`) to keep classifications clean and relevant. ### Bug Fixes * **`headline` Character Validation** * Updated the character length and character-type constraints on the `headline` field that were incorrectly rejecting valid values and setting them to `null`. * **More Accurate Experience Locations** * We fixed an issue that caused some experience records to incorrectly display a company's headquarters in the `experience.location_names` field. ## Job Posting Daily Deliveries: Directory Structure Update (Feb 2026) **Effective date: February 10, 2026** We will be updating the directory structure for Job Posting Daily Deliveries to make it easier to distinguish between daily (delta) deliveries and monthly (full) deliveries. **Reminder:** As a Job Posting Daily customer you will receive Monthly full deliveries after each monthly build, and Daily delta deliveries on the other days. ## What changed Each release directory will now include a subdirectory that explicitly indicates the delivery type: **Monthly (full) delivery:** `YYYYMMDD_{current_release_version}/full/` **Daily (delta) delivery:** `YYYYMMDD_{current_release_version}/daily/` Previously, both monthly and daily deliveries were written directly to the release directory without a clear indication of which type of delivery they were. ## Impact This change affects customers ingesting **Job Posting Daily Deliveries**. Ingestion logic should be updated to check for the presence of a `full/` or `daily/` subdirectory and process the data accordingly. There are no changes to file contents or schemas. ## Why we made this change This update reduces ambiguity between daily and monthly deliveries and makes it easier to programmatically handle each delivery type. **Note:** Job Posting Daily Deliveries is currently in **beta**, and some iteration is expected as we incorporate customer feedback. ## Related Pages For additional information on Daily Deliveries for Job Posting Data, see these pages: # January 2022 Release Notes Source: https://docs.peopledatalabs.com/changelog/january-2022-release-notes-v17 | Release Name | Dataset Version | Publish Date | | :----------- | :-------------- | :----------- | | January 2022 | `v17.0` | 01/10/2022 | *Person v17 was released on 1/10/2022 to Data License Customers* Welcome to our January 2022 release notes! It’s a new year, and we are excited to share all the new updates we’ve been cooking up for you. We’re kicking things off with a bang this year, and here are some of the key highlights: * We have officially moved to [Monthly API Data updates](#monthly-data-updates-via-api) for our Person Data * Our new [Identify API](/docs/identify-api) provides enhanced matching functionality particularly suited for identity risk use cases * 29 new identity-risk-related fields added to our Person Schema with our new [Person Risk attributes](#person-risk-attributes) * 30 new fields added to our Company Schema including our new [Company Insights Fields](#company-insights-fields) targeted toward investment and market research use cases * We launched a public [roadmap](https://feedback.peopledatalabs.com/) for our users to see upcoming/completed product developments as well as suggest and vote for future feature requests. * Our new [AWS Data Exchange API Integration](https://aws.amazon.com/marketplace/pp/prodview-ywwmbzpvfjyqw?sr=0-3\&ref_=beagle\&applicationId=AWSMPContessa) allows users to authenticate API calls using their AWS credentials to centralize data purchasing and processing workflows. * Over [208 million jobs and 182 million locations](#freshness) updated this quarter.\ Millions of new linkages between [LinkedIn \<> Mobile Phone \<> Street Address](#coverage) data Excited yet? Read on to learn more, or jump to a specific section using the table of contents below. ## 📣 Key Announcements ### Deprecations \**DEPRECATION NOTICE -- v4 API ENDPOINT\** As of July 2021, support for the v4 (Schema 4) Person Enrichment API officially ended, and the Schema 4 Person Enrichment endpoint (`v4/`) began a gradual shut down. ❗️DEPRECATION NOTICE -- Canonical Data\ October 2021 was the final release to include "canonical" location, school, and company files in s3://pdl-prod-schema. We will continue providing access to this relational data via complimentary access to our [Cleaner Endpoints](/docs/cleaner-apis) and [Autocomplete API](/docs/autocomplete-api) for all customers. ❗️DEPRECATION NOTICE -- Version Status from API Responses\ As of this January 2022 release, we have now deprecated the Version Status field (along with it’s nested fields) as part of API responses. This is part of our new [monthly data update](#monthly-data-updates-via-api) service beginning with this release. We will continue to provide the Version Status field to our data license customers in our quarterly license releases.

Additionally, the ID Changelog provided to all customers through S3 will continue to be updated through our major quarterly releases, but will not be updated in monthly API releases for minor version updates.

Please reach out to your Customer Success team if you have any questions or concerns. ### Schema Changes This quarter, we are adding 2 new collections of fields to our data: 1. **Person Risk Attributes**: A collection of 29 new fields have been added to the [Person Schema](/docs/fields) targeting identity risk and fintech applications. 2. **Company Insights**: A set of 30 new fields that have been added to the [Company Schema](/docs/company-fields) combining our Person data with company data into aggregated statistics on a company. In 2022, we plan to add a significant amount of fields to our person and company data – this is just the beginning! New fields will only be available to enterprise clients based on use case and need. See the [Field Bundles](#field-bundles) section below to learn more about how to access these new data fields. *** ## New Products and Features ### Monthly Data Updates via API This release also marks our official transition towards supporting monthly data updates for our Person datasets. This has been in the works for a little while now, so here are the details: * Monthly data updates will only be available through API calls, meaning each month the data in our hosted index will be up to date. * Monthly updates will primarily include data updates and bug fixes. * New products and field bundles will be rolled out alongside monthly releases on an invite-only basis * We won’t be rolling out major changes that impact the wider customer base in our monthly releases. As such, we will not be providing monthly release notes. * For Data License customers, flat file deliveries will continue to be provided on a quarterly basis. We intend to provide new mechanisms for updating flat files like our [Retrieve API](/docs/person-retrieve-api). As we move into 2022, our goal is to push towards faster and faster updates, which make consuming and delivering flat files difficult. Instead, we invite flat file customers to provide us with feedback on our new mechanisms for data updates. This is an exciting update that opens up new possibilities for time-sensitive use cases. All API customers will automatically be upgraded to monthly releases, with the next update being in February 2022. For more information or questions, please reach out to your Customer Success team. ### Identify API This quarter, we are excited to announce the release of our new [Identify API](/docs/identify-api) endpoint.This endpoint enables enhanced matching functionality particularly suited for identity risk use cases and includes expanded query parameters and less strict requirements than our Person Enrichment API. It allows you to retrieve multiple strongly associated profiles related to an identity instead of a single best match. This endpoint also includes an improved scoring metric quantifying the matching strength between returned profiles and input parameters. To learn more about the Identify API or to request access please reach to your Customer Success team. ### Field Bundles With this release, we are also transitioning to providing curated collections of fields known as Field Bundles as opposed to providing selections of individual fields. These field bundles are designed to be tailored, use-case specific, packages of fields, allowing us to provide value more directly to the problems our users are solving. To support these new field bundles, we have also added over 50 new fields to our Person and Company Data this quarter (see the [Person Risk Attributes](#person-risk-attributes) and [Company Insights Fields](#company-insights-fields) sections below). Field bundles for person and company data consist of predefined selections of fields from these new additions respectively and complement a common set of base fields that customers universally have access to. As of this release, our Company data is fully bundled, meaning our Company Schema has been transitioned to a set of base fields plus field bundle packages available for purchase. Our Person data is not yet fully bundled, but will be later in 2022. #### Person Risk Attributes The [Person Risk Attributes](/docs/fields#person-risk-attributes) field bundle is an addition to the Person Schema consisting of a new set of premium fields designed for identity risk use cases. This field bundle provides new data points such as historically or loosely associated jobs, locations and contact information and enhanced sourcing information for various attributes (like time first/last seen and number of corroborating sources). These fields are provided as a bundle and are integrated into our existing Person-related endpoints (particularly our new Identify API) by providing extended information in the profiles returned. #### Company Insights Fields The [Company Insights fields](/docs/company-fields#company-insights-fields) are a set of fields added to our Company Schema. These fields were created to help our customers understand company health by looking at the people who make up a company. We used selections of these new Company Insights fields to construct targeted field bundles focusing on specific use cases in the investment and marketing research spaces. Some of the key data points included in this dataset are aggregated month-by-month employee headcounts as well breakdowns of employees by location, role, and seniority. The Company Insights data will be available in multiple bundles to allow you to tap into these fields in a more flexible manner. A highlight that many of our alpha customers have appreciated is the addition of company growth and churn rates, which can be used directly in the Company Search API as filtering criteria. ### Product Roadmap We recently introduced a new public-facing product roadmap at [feedback.peopledatalabs.com](https://feedback.peopledatalabs.com/). We wanted to give our customers a way to learn more about what we’re building, and to tell us what they need. Our Product Roadmap is our new interactive platform providing a transparent view of our product development, as well as opportunities to give feedback, submit feature requests, upvote requests, and make your voice heard. For more information on our Product Roadmap, please check out our [blog post](https://blog.peopledatalabs.com/post/introducing-pdl-canny). ### AWS Data Exchange API Integration Our Person Enrichment API has now been officially integrated into the Amazon Data Exchange Marketplace. This new integration allows users to centralize data purchasing and processing workflows and additionally allows users to authenticate their API requests using AWS credentials as an alternative to using their PDL API key. To sign up, you can find the Person Enrichment API listing on the [Data Exchange Marketplace](https://aws.amazon.com/marketplace/pp/prodview-ywwmbzpvfjyqw?sr=0-3\&ref_=beagle\&applicationId=AWSMPContessa). **People Data Labs at AWS Re:Invent 2021** This integration was also demoed at the AWS Re:Invent 2021 showcase this past quarter, check out the video below!