> ## Documentation Index > Fetch the complete documentation index at: https://docs.peopledatalabs.com/llms.txt > Use this file to discover all available pages before exploring further. # July 2023 Release Notes | Release Name | Dataset Version | Publish Date | | :----------- | :-------------- | :----------- | | July 2023 | `v23.0` | 07/10/2023 | *This data version was was released on 7/10/2023.* Welcome to our July 2023 release notes! We’re rolling out some exciting updates with this release. Here are some of the key highlights: * Get up-to-date information on a unique IP with our new [IP Enrichment API](#ip-enrich). * The Person Retrieve Webhook now supports the [`filter_updated` parameter](#webhook-filters). * We’ve added [six new filters](#six-filters) for the Person Retrieve API `filter_updated` parameter. * We’ve [improved the reliability](#company-website) of our company `website` and `alternative_domains` fields. * [Huge increases in `work_email` linkages](#coverage) across multiple datasets. * We’ve added [over 60 million new contact information linkages](#coverage) in the API dataset. Excited yet? Read on to learn more, or jump to a specific section using the table of contents below. ## 📣 Key Announcements ### Six New Filters for [Person Retrieve API](/docs/person-retrieve-api) `filter_updated` Parameter A few quarters ago ([October v20](/changelog/october-2022-release-notes-v20#person-retrieve-api)), we introduced a new input parameter for our [Person Retrieve API](/docs/person-retrieve-api) called [`filter_updated`](/docs/input-parameters-person-retrieve-api#filter_updated), which selects the criteria to determine which changes to a record count as an “update.” Only updated records will be charged when using the Person Retrieve API. Due to extensive customer feedback, we’re excited to launch six new filters in this release:
Filter Name Update Based On
`location` [`location_name`](/docs/fields#location_name)\ [`location_locality`](/docs/fields#location_locality)\ [`location_metro`](/docs/fields#location_metro)\ [`location_region`](/docs/fields#location_region)\ [`location_country`](/docs/fields#location_country)\ [`location_continent`](/docs/fields#location_continent)\ [`location_street_address`](/docs/fields#location_street_address)\ [`location_address_line_2`](/docs/fields#location_address_line_2)\ [`location_postal_code`](/docs/fields#location_postal_code)\ [`location_geo`](/docs/fields#location_geo)
`social_profile` [`linkedin_url`](/docs/fields#linkedin_url)\ [`linkedin_username`](/docs/fields#linkedin_username)\ [`linkedin_id`](/docs/fields#linkedin_id)\ [`facebook_url`](/docs/fields#facebook_url)\ [`facebook_username`](/docs/fields#facebook_username)\ [`facebook_id`](/docs/fields#facebook_id)\ [`twitter_url`](/docs/fields#twitter_url)\ [`twitter_username`](/docs/fields#twitter_username)\ [`github_url`](/docs/fields#github_url)\ [`github_username`](/docs/fields#github_username)
`work_email` [`work_email`](/docs/fields#work_email)
`personal_emails` [`personal_emails`](/docs/fields#personal_emails)\ [`recommended_personal_email`](/docs/fields#recommended_personal_email)
`education` [`education`](/docs/fields#education)
`phone_number` [`mobile_phone`](/docs/fields#mobile_phone)\ [`phone_numbers`](/docs/fields#phone_numbers)
For example, by using the `phone_number` filter, you will receive/be charged for the record only if the `mobile_phone` or `phone_numbers` fields for that ID have changed since the last data refresh. The Retrieve API also supports using [**multiple filters**](/docs/input-parameters-person-retrieve-api#using-multiple-filters) in the same request. For example, if you use both the `personal_emails` and `work_email` filters, a match will be returned if any of the associated fields for either filter have been updated. ### Retrieve Webhook Filter Support This quarter, we’re excited to continue improving the [Retrieve Webhook functionality](/docs/webhook-for-person-retrieve-api) by adding support for the `filter_updated` parameter. For example, you can now have the webhook automatically send you a list of only the Person IDs that changed jobs in the monthly data release out of all records you’ve ever pulled. This gives you even more control to narrow in on the updates that are valuable to you, and ultimately on the updates you pay for. All 7 filters and multi-filter support are available with the Retrieve Webhook for both API and Data License customers. ### Improvements to the Company `website` Field Our engineers have been hard at work making various improvements to increase the reliability of our company `website` and `alternative_domains` fields. This release includes the following changes: * **Enhanced update processes** for companies that rebrand or change their name over time. * **Added previously non-exposed website field data** to the `alternative_domains` field. In the past, we had stored historical domains in a non-visible field to enable users to match to a profile even when using an old company website in their query. We’ve now added this additional website data to the `alternative_domains` field. * **Added full website path and subdomain data** for certain websites. There are many legitimate businesses that rely on web hosting platforms and social networks to promote their services. We’re now allowing for full URLs (compared to stripped root domains) for popular hosting platforms like Facebook, Blogspot, Wix, and others. Business websites like `samspizza.blogspot.com` or `etsy.com/sams-pizza` will now show the correct website (including the “sams-pizza” subdomain/path in this example). Websites using **link shortening services** like Bit.ly, TinyURL, ShortURL, etc. will now also appear represented in full. * **Incorporated domain redirects data into our`website` and `alternative_domains` fields**. To identify changes in websites, we are now capturing website redirect data in order to update a new primary domain for many company profiles. In cases where we can identify a new primary website using these methods, we will store the previous website(s) in the `alternative_domains` field. With these changes, v23 has: * **2.6 million** more company records with a `website`, an increase of **+15.2%** * **4.0 million** increase in the total number of websites in the `website` and `alternative_domains` fields, representing growth of **+21.1%** * **54,909** company records where an existing `website` was replaced with an updated website using new redirect and version logic *** ## ✨ New Products and Features ### eta] I IP Enrichment API **Warning: Beta API** This API is in **beta** and is subject to change. This release, we’re excited to announce the launch of our [IP Enrichment API](/docs/ip-enrichment-api) that provides a one-to-one IP match, giving you up-to-date information on a unique IP. This will allow you to link website visitor IPs with company information, enable personalized web experiences, create target lists, identify website traffic sources, and more. By providing an IP address to the IP Enrichment API, you will receive the location and company associated with it. Additional metadata about the IP address is available as a premium add-on. You can use this information as-is to learn about visitors or feed the relevant information to our [Company Enrichment](/docs/company-enrichment-api) or [Person Search](/docs/person-search-api) APIs to get even more detailed data. The IP Enrichment API is currently in beta, if you’d like to request access, please [reach out to us](https://www.peopledatalabs.com/talk-to-sales). *** ## 🚀 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` | 121,244,348 | | Resume | Global | `location` | 35,311,851 | | Resume | United States | `experience` | 43,078,522 | | Resume | United States | `location` | 17,057,015 | ### Coverage **[Resume Dataset](/docs/resume-stats)** | Linkage | Coverage in v22 | Coverage in v23 | Increase (%) | | --------------- | --------------- | --------------- | ------------ | | `total_records` | 741,406,022 | 753,962,445 | 1.69% | | `work_email` | 74,871,589 | 86,206,056 | 15.14% | **[API Dataset](/docs/stats)** | Linkage | Coverage in v22 | Coverage in v23 | Increase (%) | | ------------------------- | --------------- | --------------- | ------------ | | `total_records` | 3,161,998,162 | 3,192,479,170 | 0.96% | | `emails.address` | 1,069,877,598 | 1,098,690,191 | 2.69% | | `location_street_address` | 779,880,318 | 800,966,868 | 2.70% | | `personal_emails` | 708,085,315 | 729,521,527 | 3.03% | | `work_email` | 77,661,874 | 88,969,647 | 14.56% | **[Email Dataset](/docs/email-stats)** | Linkage | Coverage in v22 | Coverage in v23 | Increase (%) | | -------------- | --------------- | --------------- | ------------ | | `linkedin_url` | 194,405,433 | 204,749,011 | 5.32% | | `work_email` | 73,430,807 | 84,845,517 | 15.54% | **[Company Dataset](/docs/company-stats)** | Linkage | Coverage in v22 | Coverage in v23 | Increase (%) | | --------------------- | --------------- | --------------- | ------------ | | `total_records` | 28,212,381 | 29,813,505 | 5.68% | | `alternative_domains` | 243,164 | 2,773,754 | 1,040.69% | | `website` | 17,203,521 | 19,822,807 | 15.23% | ### Commentary * `work_email` linkages in the Resume, API, and Email datasets increased by 15% * Huge increases in contact information linkages in the API dataset * `emails.address` linkages increased by 28.8M * `location.street_address` linkages increased by 21M * `personal_emails` linkages increased by 21.4M * As detailed in [the previous section](#company-website), the website and alternative\_domains fields in the Company dataset saw significant growth (2.6M and 2.5M increases respectively) as a result of our new logic. *** ## 🛠 Improvements and Bug Fixes ### Improvements * Improved nickname alias (Robert → Bob, Bobby, Rob) to improve profile resolution and matching. * Improved our Chief Executive Officer (CXO) [job level](/docs/job-title-levels) tagging by filtering out support roles (Assistant to the CEO, Chief of Staff to the President, etc.) * “Instructor” roles were exclusively mapped to the “Professor” subrole. This meant titles such as “Swim Instructor” or “Tennis Instructor” had a subrole of “Professor”. We’ve removed this mapping and added a new “Instructor” subrole. ### Bug Fixes * In the location cleaner, “Stockholm, Sweden” no longer erroneously cleans to “Saintckholm, Sweden.” * Changed `education.summary` to be text indexed instead of keyword indexed. ## Related topics - [January 2023 Release Notes](/changelog/january-2023-release-notes-v21.md) - [April 2023 Release Notes](/changelog/april-2023-release-notes-v22.md) - [October 2023 Release Notes](/changelog/october-2023-release-notes-v24.md) - [July 2020 Release Notes](/changelog/q2-2020-release-notes.md) - [July 2024 Release Notes](/changelog/july-2024-release-announcement-v270.md)