> ## 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.

# June 2025 Release Notes

| Release Name | Dataset Version | Publish Date |
| :----------- | :-------------- | :----------- |
| June 2025    | `v30.2`         | 06/17/2025   |

**Welcome to our June 2025 release notes!**

We're halfway through the year and going full throttle launching features, cleaning data, and squashing bugs.

Here's what's new:

* **📊 Freshness You Can Count On**: This month, we [verified 62M+ jobs](#freshness) and [detected 25K+ job changes](#job-changes) across our global dataset.
* **<Icon icon="graduation-cap" /> Smarter School Canonicalization**: We've [upgraded how we canonicalize educational institutions](#improvements), improving filtering and search across the dataset. This change [increased our coverage by 25%](#commentary) - more schools, less guesswork.
* **<Icon icon="globe" /> Autocomplete API Gets a Boost**: You asked, we delivered! Our [Autocomplete API now supports countries and regions](#updated-autocomplete-api-location-parameters) (not just localities) giving you more control when completing location data.

## Upcoming Breaking Changes

<Warning>
  Upcoming breaking changes may impact your current processes. We are announcing them here to provide ample time for you to adjust your processes accordingly.
</Warning>

### Deprecation of Legacy Employer Insights Fields ([Company](/docs/company-schema))

**Change expected in:** v31.0 / July 2025
**Previous Announcements:** [Apr 2025 (v30.0)](/changelog/april-2025-release-notes-v300#legacy-insights), [May 2025 (v30.1)](/changelog/may-2025-release-notes-v301#legacy-insights)

**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)

In April 2025, we deprecated 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 in April](/changelog/april-2025-release-notes-v300#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 instead of IDs, which makes it much easier to build visualizations like Sankey charts or other talent flow views without needing additional API calls to resolve Company IDs. The result is a simpler implementation experience and reduced API credit usage.

**Migration Plan**

* July 2025 (v31.0): Legacy fields will be removed.
* April - July 2025 (v30.0 - v31.0): Both legacy and new fields are available in the Company Schema to support a smooth transition.
* April 2025 (v30.0): New fields are available.

**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

### Updated: Autocomplete API Location Parameters ([API](/docs/autocomplete-api))

This month, we're releasing some exciting enhancements to our [Autocomplete API](/docs/autocomplete-api) to give you more flexibility when working with location data. Based on customer feedback, we've added two new field options that make it easier to autocomplete not just localities but also countries and regions.

**What's New**

You can now use the following `field` values when calling the Autocomplete API:

* `all_locations`: This is a new option that autocompletes across *all* location types: countries, regions and localities. For example, searching `swed` can now return `sweden` instead of localities like `stockholm, stockholm, sweden`
* `location_name`: This is the new name for the original `location` field. It autocompletes only [locality-level](/docs/fields#location_name) locations (e.g., `berkeley, california, united states`). Using this parameter is functionally identical to the previous `location` field, but has been renamed for clarity.

<Note>
  **Heads Up!** `location_name` now replaces the previous `location` parameter

  If you're currently using `field=location` in your Autocomplete API requests, please update your implementation:

  * Use `field=all_locations` to expand suggestions across all location types
  * Use `field=location_name` to maintain the same functionality
</Note>

**Why This Change?**

Until now, autocomplete for locations only worked at the locality level - even if you were trying to find a country or region. With this update, you can now tailor results to better match your use case, whether you're looking for cities, states or countries.

No Breaking Changes: We designed this update to be backward compatible while also providing additional flexibility. The original `location` field has simply been copied to the new `location_name` parameter, without any change to functionality. You can still use the `location` parameter as well, but it is considered deprecated and we encourage you to use one of the alternatives instead.

If you have any questions or suggestions, please [let us know](https://feedback.peopledatalabs.com/feature-requests?selectedCategory=autocomplete-api)! We are continually striving to improve our products to ensure we deliver the best possible experience for 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 (v30.1 → v30.2)**
*Freshness updates over the past month.*

| Dataset | Geography     | Field        | Records Updated |
| :------ | :------------ | :----------- | :-------------- |
| Resume  | Global        | `experience` | 62,377,902      |
| Resume  | Global        | `location`   | 96,411,234      |
| Resume  | United States | `experience` | 19,152,230      |
| Resume  | United States | `location`   | 24,628,272      |

### 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 (v30.1 → v30.2)**
*Freshness updates over the past month.*

| Dataset | Geography     | Records Updated |
| :------ | :------------ | :-------------- |
| Resume  | Global        | 25,111          |
| Resume  | United States | 9,607           |

### Coverage

(Full Stats: [Person](/docs/datasets), [Company](/docs/company-stats), [IP](/docs/ip-stats))

**Monthly (v30.1 → v30.2)**

**[Resume Dataset](/docs/resume-stats)**

| Linkage                              | Coverage in v30.1 | Coverage in v30.2 | Increase (%) |
| :----------------------------------- | :---------------- | :---------------- | :----------- |
| Total Records                        | 755,661,436       | 764,120,525       | 1.12%        |
| `education.school.linkedin_id`       | 213,464,934       | 268,160,770       | 25.62%       |
| `education.school.location.locality` | 241,507,415       | 216,847,815       | -10.21%      |

**[API Dataset](/docs/stats)**

| Linkage       | Coverage in v30.1 | Coverage in v30.2 | Increase (%) |
| :------------ | :---------------- | :---------------- | :----------- |
| Total Records | 2,421,432,261     | 2,428,086,973     | 0.27%        |

**[Email Dataset](/docs/email-stats)**

| Linkage       | Coverage in v30.1 | Coverage in v30.2 | Increase (%) |
| :------------ | :---------------- | :---------------- | :----------- |
| Total Records | 593,445,009       | 592,343,042       | -0.19%       |

**[Mobile Phone Dataset](/docs/mobile-phone-stats)**

| Linkage       | Coverage in v30.1 | Coverage in v30.2 | Increase (%) |
| :------------ | :---------------- | :---------------- | :----------- |
| Total Records | 483,070,596       | 482,439,772       | -0.13%       |

**[Company Dataset](/docs/company-stats)**

| Linkage               | Coverage in v30.1 | Coverage in v30.2 | Increase (%) |
| :-------------------- | :---------------- | :---------------- | :----------- |
| Total Records         | 71,543,406        | 71,604,491        | 0.085%       |
| `affiliated_profiles` | 194,816           | 140,767           | -27.74%      |

**[Job Posting Dataset](/docs/jp-stats)**

| Linkage                | Coverage in v30.1 | Coverage in v30.2 | Increase (%) |
| :--------------------- | :---------------- | :---------------- | :----------- |
| Total Records          | –                 | 10,178,495        | –            |
| Total Unique Companies | –                 | 31,152            | –            |
| Total Active           | –                 | 2,042,504         | –            |

### Commentary

* **Person**
  * We saw a 25% increase the number of schools we could associate to education experiences in our Resume slice as result of our School Cleaning Improvements (see [below](#improvements))
* **Company**
  * We saw a 27% decrease in the number of affiliated profiles we have in our Company dataset, which is consistent with [previous updates](/changelog/april-2025-release-notes-v300#commentary). This is a low fill-rate field that is scheduled for future improvements and sourcing enhancements.
* **Job Posting Data**
  * We're now publishing stats related to our Job Posting Dataset

## Improvements and Bug Fixes

### Improvements

* **School Cleaning Improvements**
  * We improved the canonicalization in our school dataset to improve school filtering and searching by education in the dataset. This resulted in a 25% increase in the number of school objects we are able to canonicalize.
* **Updated `full_name` logic**
  * We updated the `full_name` field to include the `middle_name` when the `first_name` is one character, for example `A William Barns`.
* **Updated Job Title Role, Sub Role and Level Classifications**
  * We improved our categorization of C Suite, Senior HR, Product/Data Owner and other job titles to support more accurate `role` and `sub_role` tags

### Bug Fixes

* **Embedded null characters in Company fields**
  * We implemented a fix to remove embedded null bytes in the `description` and `headline` field of Company records that was causing ingestion and parsing issues for some customers.
* **Invalid `founded` year**
  * We added some additional cleaning logic to our Company records to remove founded dates that were set in the future
* **Location Standardization**
  * We fixed a bug in our location standardization process that was leading to inflated population counts for US-based towns that have international city names (e.g. "Brisbane, California", "London, Ohio"). This was caused by an incorrect assumption that a specific data source was only providing US-based records.


## Related topics

- [December 2025 Release Notes](/changelog/december-2025-release-notes-v322.md)
- [June 2024 Release Notes](/changelog/june-2024-release-announcement-v262.md)
- [June 2026 Release Notes](/changelog/june-2026-release-notes-v342.md)
- [November 2025 Release Notes](/changelog/november-2025-release-notes-v321.md)
- [January 2025 Release Notes](/changelog/january-2025-release-notes-v290.md)