> For the complete documentation index, see [llms.txt](https://docs.coresignal.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.coresignal.com/release-notes/august-2026.md).

# August 2026

{% updates format="full" %}
{% update date="2026-08-01" %}

## Base Company data: adding a new field

We are adding the `affiliated_company_id` field to a new Base Company data schema and backfilling the values.

| Data field                           | Description                                                                | Data type |
| ------------------------------------ | -------------------------------------------------------------------------- | --------- |
| `affiliated[].affiliated_company_id` | Identification key relating to the company table for the affiliate company | Integer   |
| {% endupdate %}                      |                                                                            |           |

{% update date="2026-08-01" %}

## Base Jobs data: adding new fields

Adding `status_changed_at`, an array of structs that records when a job posting's status last changed (active, inactive, or deleted). This field supports job-duration and hiring-trend analytics.

| Data field                       | Description                                                                   | Data type        |
| -------------------------------- | ----------------------------------------------------------------------------- | ---------------- |
| `status_changed_at`              | Records when and how a job posting's status last changed                      | Array of structs |
| `status_changed_at[].status`     | Job status at the time of the change. Values: `active`, `inactive`, `deleted` | String           |
| `status_changed_at[].changed_at` | Timestamp of the status change                                                | Timestamp        |
| {% endupdate %}                  |                                                                               |                  |

{% update date="2026-08-01" %}

## Multi-source Employee data: adding new fields

We are adding two new fields to the `experience` and `education` arrays to identify each entry.

| Data field        | Description                                                | Data type |
| ----------------- | ---------------------------------------------------------- | --------- |
| `experience[].id` | Profile hash ID uniquely identifying each experience entry | String    |
| `education[].id`  | Profile hash ID uniquely identifying each education entry  | String    |
| {% endupdate %}   |                                                            |           |

{% update date="2026-08-18" %}

## Multi-source Jobs data: breaking changes

Breaking changes to Multi-source Jobs data: `employment_type` is changed to  `array<string>` with normalized values (`PER_DIEM` → `Temporary`, unmapped → `Other`), and `salary[].currency` now uses ISO 4217 codes instead of symbols.

#### Data type change

`employment_type` data type is changing to an array – update your flows accordingly.

| Data field        | Old data type | New data type    |
| ----------------- | ------------- | ---------------- |
| `employment_type` | String        | Array of strings |

#### Value normalization

Two data fields `employment_type` and `salary[].currency` values are now normalized.

**`employment_type`**

**Before:** A single value, selected via priority coalesce across contributing sources.

**After:** A distinct array of values aggregated from all contributing sources.

Value mapping changes:

| Before                    | After       |
| ------------------------- | ----------- |
| `PER_DIEM`                | `Temporary` |
| Missing / unmapped values | `Other`     |

**`salary[].currency`**

Data quality update to `salary[].currency` that can disrupt symbol-matching flows.

| Before                                                                    | After                                              |
| ------------------------------------------------------------------------- | -------------------------------------------------- |
| Raw currency symbol for Glassdoor-sourced entries (e.g. `$`, `£`, `k €`). | ISO 4217 currency code (e.g. `USD`, `GBP`, `EUR`). |
| {% endupdate %}                                                           |                                                    |

{% update date="2026-08-18" %}

## Glassdoor Jobs data: changing field values

`salary.currency` data field now has value normalization, where raw currency symbols are replaced with ISO 4217 codes.

| Before                             | After                                    |
| ---------------------------------- | ---------------------------------------- |
| Raw symbols (e.g. `$`, `£`, `k €`) | ISO 4217 code (e.g. `USD`, `GBP`, `EUR`) |
| {% endupdate %}                    |                                          |
| {% endupdates %}                   |                                          |


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.coresignal.com/release-notes/august-2026.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.