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

# Experience & Location Updates

As described in [Data Updates](/docs/data-updates), keeping our `experience` and `locations` objects current is one of our primary focuses. Here we outline how we communicate these updates to customers across both fields.

## `job_` and `location_` fields

Every `experience` and `locations` object has an `is_primary` field that contains a boolean value. For a single profile, there will be *at most* one profile tagged as primary. This profile will appear in the flattened `job_` and `location_` fields. The primary values are the ones we believe to be the most recent/relevant object from the `experience`/`locations` array.

## `last_updated` Field

The `last_updated` field exists for both `locations` objects and the top-level experience object (as the [`job_last_verified`](docs:fields#job_last_verified) field). It indicates the last time one of our [Data Union partners](/docs/data-sources) saw a person's location and/or current job "in the wild." Since many of our data partners are themselves focused on data accuracy, we are able to utilize their timestamps to accurately map when this value was last seen. The `last_updated` date does not necessarily indicate that a change in the field occurred but when the most recent data source was provided this data and confirmed its accuracy.


## Related topics

- [Person Schema](/docs/fields.md)
- [June 2025 Release Notes](/changelog/june-2025-release-notes-v302.md)
- [July 2024 Release Notes](/changelog/july-2024-release-announcement-v270.md)
- [September 2024 Release Notes](/changelog/september-2024-release-announcement-v272.md)
- [August 2024 Release Notes](/changelog/august-2024-release-announcement-v271.md)