July 2024 Release Notes (v27.0)
| Release Name | Dataset Version | Publish Date |
|---|---|---|
| July 2024 | v27.0 | 07/02/2024 |
This data version was released on 7/2/2024.
Welcome to our July 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:
- Premium field bundles for our self-serve customers
- A Company Changelog to help track updates across releases
- New
linkedin_follower_countfield in our Company Schema - Nearly 200 million job updates and 12 million job changes tracked in our dataset over the past quarter!
Excited yet? Read on to learn more, or jump to a specific section using the table of contents below.
LinkedIn Follower Count (Company Schema)
| Field Name | Field Type | Field Description |
|---|---|---|
linkedin_follower_count | Integer (>=0) | The number of followers on a company’s LinkedIn profile |
We are adding a new linkedin_follower_count field to our Company Data schema that tracks the number of followers on a company’s LinkedIn profile.
This field is available in our Premium and Comprehensive field bundles, and is immediately provided to current customers using those bundles. To get access to this field, please reach out to your Customer Success team.
Previous Announcements: v24 / October 2023, v25 / January 2024, v26.0 / April 2024, v26.1 / May 2024, v26.2 / June 2024
As part of our new resume timestamps that were released last quarter, the job_last_updated field is now fully deprecated and has been removed from our Person Schema in the v27.0 release. Customers previously using this field should leverage our new job_last_verified field which provides the same functionality.
Please see this easy-to-follow guide prepared by our Technical Services team for detailed instructions and best practices on this transition.
Breaking Changes Guide: Deprecation of job_last_updated
For further support, please reach out to your Customer Success and Technical Services team.
Upcoming Breaking Changes
These are upcoming breaking changes in future versions that may impact your current processes. We are announcing them here to provide ample time for you to adjust your processes accordingly.
Change expected in: February 2025
Previous Announcements: April 2024
Products Impacted: Person / Company / IP Schema
| Person Fields Impacted | Company Fields Impacted | IP Fields Impacted |
|---|---|---|
job_title_rolejob_title_sub_roleexperience.title.roleexperience.title.sub_role | average_tenure_by_roleemployee_count_by_month_by_roleemployee_count_by_rolerecent_exec_departuresrecent_exec_hirestop_next_employers_by_roletop_previous_employers_by_role | person.job_title_roleperson.job_title_sub_role |
Over the next 2 quarters, we will be making significant changes to our Job Title Roles and Job Title Subroles enum values in order to improve our fill rates and categorization of job titles.
These changes will include a revamped taxonomy for role and subrole values containing additions, renamings, recategorizations, removals and other modifications to the current set of canonical role and subrole values. For the specific details on these changes see the Resources table at the end of this notice.
As indicated in the table above, this change will impact our Person, Company, and IP data fields. In particular, customers using the Company fields shown above (such as for visualization, modeling or other uses) will need to ensure that they update their code to handle the new / deleted / renamed role values. While this is a significant change for many of our customers, it is necessary to improve our data quality and to provide a better overall user experience.
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:
- July 2024 - Breaking Change Announcement and Resource Launch:
- Public notice of our planned role / subrole transition and initial resources provided (see below)
- 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
- We will open up beta access to the new role / subrole taxonomy as well as a new data field
- 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)
- 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.
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]
- Job Title Roles [post-v27.1]
- Job Title Subroles [post-v27.1]
- Mapping Job Title Class to Roles to Subroles [post-v27.1]
The mapping from the current role/subrole taxonomy to the improved taxonomy is here:
Sample records using the updated role / subrole taxonomy are here:
- Example Person Record [New Role / Subrole Taxonomy]
- Example Company Record [New Role / Subrole Taxonomy]
- Example IP Record [New Role / Subrole Taxonomy]
Change expected in: October 2024
Products Impacted: Person / Company / IP Schema
| Person Fields Impacted | Company Fields Impacted | IP Fields Impacted |
|---|---|---|
countriesstreet_addresses.countrystreet_addresses.countrypossible_street_addresses.countryjob_company_location_countryexperience.company.location.countryeducation.school.country | location.countryemployee_count_by_country | ip.location.countryip.company.location.country |
Next quarter, we will be updating the set of canonical 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 is here:
Additionally, a mapping from the current country values to the upcoming country values can be found here:
| Country (pre-October) | Change Type | Country (post-October) | 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 |
Change expected in: October 2024
Products Impacted: Person / Company Schema
| Person Fields Impacted | Company Fields Impacted |
|---|---|
job_company_typeexperience.company.type | type |
Next quarter, we will be updating the set of canonical company type values to include a new public_subsidiary value in the set of canonical values:
| Canonical Company Types (pre-October) | Canonical Company Types (post-October) |
|---|---|
• educational• government• nonprofit• private• public | • educational• government• nonprofit• private• public• public_subsidiary --> new type |
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.
This quarter, we are excited to release our Company Changelog into Beta for all customers. Similar to our existing Person Changelog, the Company Changelog allows users to see which company records have been updated across each build and keep track of record merges and deletions.
Beta Release
The beta release of this product is a feature-complete version of the Company Changelog that is publicly available. While we do not anticipate major changes to the product, we hope to collect customer feedback over the next few releases to determine any further improvements or refinements to make to this product.
If you have any feedback on the Company Changelog please reach out to us or share it with your customer success team.
The Company Changelog is a public list of company record IDs that are categorized into the following groups:
- Updated: Any record that had a value change to any non-insights field or had a record merged into it
- Merged: A record that was merged into another record (and as a result no longer exists in the dataset)
- Deleted: This record was deleted and no longer exists in the dataset
- Added: This record did not exist in previous dataset version and was added in the latest version
Note that Company Insights fields, which have expected changes due to new periods added each month, are among the fields whose changes are not factored into update calculation by design. See FAQs
The Company Changelog is helpful for customers looking to streamline their data update and ETL pipelines by filtering data ingestion to just the records that have changed in a release. In addition, the Changelog also allows customers to track which records and IDs have changed and how they’ve been updated across builds.
The Company Changelog is publicly available on our S3 bucket as a flat file and freely accessible for all customers to use. For more information, see our documentation.
We are excited to announce that our premium field bundles will be available in early July through the API Dashboard for all self-serve Pro plans. This means that self-serve customers will be able to access premium fields across our person and company datasets, such as job summary, company revenue data, company funding data, and more.
Previously, these fields were only accessible to enterprise customers. Each field bundle can be added on to a new or existing Pro plan so teams can immediately start building, testing and evaluating more of our data without committing to a large upfront package.
To get started, log into the API Dashboard and select the field bundles you would like to add on by clicking the Manage button on the Plans & Billing page.
Note that existing enterprise customers will not be able to self-serve premium fields through their API dash. Instead, please reach out to your Customer Success team for adding or updating your access to premium fields.
The number of jobs and locations verified in our datasets over the past quarter (based on the job_last_verified and location_last_updated fields).
| Dataset | Geography | Field | Records Updated |
|---|---|---|---|
| Resume | Global | experience | 198,448,154 |
| Resume | Global | location | 318,427,940 |
| Resume | United States | experience | 72,866,214 |
| Resume | United States | location | 103,534,938 |
The number of person records where the primary job experience changed in our Person Dataset over the past quarter (based on the job_last_changed field).
| Dataset | Geography | Field | Records Updated |
|---|---|---|---|
| Resume | Global | experience | 11,466,607 |
| Resume | US | location | 3,696,119 |
| Linkage | Coverage in v26 | Coverage in v27 | Increase (%) |
|---|---|---|---|
total_records | 744,191,278 | 721,091,212 | -3.10% |
name_aliases | 28,268,384 | 36,551,556 | 29.30% |
twitter_username | 10,345,484 | 11,774,688 | 13.81% |
phones | 69,139,249 | 76,973,049 | 11.33% |
job_company_ticker | 47,044,362 | 42,694,043 | -9.25% |
- We saw a decrease of ~40mm records in our resume data slice based on our improved internal profile validation process to remove inaccurate and low-quality data from our records
- We improved our matching and canonicalization logic for schools resulting in more accurate school data in our person records and School Cleaner API
- We now strip null terminators from all fields in our data
- We now provide gzip and json file formats for our Company Changelog
- 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