> 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/october-2026.md).

# October 2026

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

## Base Company data: adding funding rounds history

We are adding an `funding_rounds_legacy` array to the Base Company dataset that includes company's full funding history. Additionally, a breaking change is scheduled: the current `funding_rounds` struct will be deprecated and removed after the December 1, 2026 data dumps.

#### New fields

| Data field                                 | Description                                                                                                                                                                                                       | Data type        |
| ------------------------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------- |
| `funding_rounds_legacy`                    | Funding rounds history recorded for the company                                                                                                                                                                   | Array of structs |
| `funding_rounds_legacy[].id`               | Record UUID identifier                                                                                                                                                                                            | String           |
| `funding_rounds_legacy[].round_type`       | Funding round type                                                                                                                                                                                                | String           |
| `funding_rounds_legacy[].announced_date`   | Funding round date                                                                                                                                                                                                | String           |
| `funding_rounds_legacy[].money_raised`     | Amount of money raised in the funding round                                                                                                                                                                       | String           |
| `funding_rounds_legacy[].url`              | Funding round record URL                                                                                                                                                                                          | String           |
| `funding_rounds_legacy[].order_in_profile` | Section record order                                                                                                                                                                                              | Integer          |
| `funding_rounds_legacy[].created_at`       | Record creation timestamp in ISO 8601 format                                                                                                                                                                      | Date             |
| `funding_rounds_legacy[].updated_at`       | Record update timestamp in ISO 8601 format                                                                                                                                                                        | Date             |
| `funding_rounds_legacy[].deleted`          | <p>Record availability status: <br><code>1</code> – the record was publicly unavailable the last time we scraped the profile;<br><code>0</code> – the record was available and included in the profile's data</p> | Integer          |

#### Scheduled breaking change: `funding_rounds` deprecated

`funding_rounds` will be deprecated and removed after the December 1, 2026 data dumps. Update all integrations that use `funding_rounds` to use historical data from `funding_rounds_legacy`. Because `total_rounds_count` has no direct replacement, use the number of entries in `funding_rounds_legacy` instead.

| Data field       | Before                                                                                                                                                        | After                                    |
| ---------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------- |
| `funding_rounds` | Struct with the company's last funding round details: `total_rounds_count`, `last_round_type`, `last_round_date`, `last_round_url`, `last_round_money_raised` | Removed after the December 1, 2026 dumps |
| {% endupdate %}  |                                                                                                                                                               |                                          |

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

## Multi-source Employee data: adding new fields

We are adding a set of new fields to Multi-source Employee data covering posts insights and location.

**Adding `location` object**

We are also adding a `"location"` object. It's a coordinate object holding the employee's latitude and longitude, derived from the existing location data, so you can work with an employee's location numerically instead of parsing it from a text field.

| Data field           | Description                          | Data type |
| -------------------- | ------------------------------------ | --------- |
| `location`           | Employee's location coordinates      | Object    |
| `location.latitude`  | Latitude of the employee's location  | Float     |
| `location.longitude` | Longitude of the employee's location | Float     |

**Adding post insights**

Post-related fields let you build a comprehensive view of an employee's activity, including their posting habits, interaction patterns, engagement trends, their contacts, and how their engagement has evolved over time.

<table data-search="false"><thead><tr><th>Data field</th><th>Description</th><th>Data type</th></tr></thead><tbody><tr><td><code>comments_received_yearly</code></td><td>Number of comments received on posts published in the trailing 12 months</td><td>Long</td></tr><tr><td><code>reposts_received_yearly</code></td><td>Number of reposts received on posts published in the trailing 12 months</td><td>Long</td></tr><tr><td><code>reactions_received_yearly</code></td><td>Number of reactions received on posts published in the trailing 12 months</td><td>Long</td></tr><tr><td><code>post_frequency_change_percentage</code></td><td>Percentage change in number of posts published, comparing the trailing 6 months to the preceding 6 months</td><td>Double</td></tr><tr><td><code>engagement_received_change_percentage</code></td><td>Percentage change in total engagement received, comparing the trailing 6 months to the preceding 6 months</td><td>Double</td></tr><tr><td><code>total_posts_count</code></td><td>Number of employee posts</td><td>Integer</td></tr><tr><td><code>post_activity_monthly</code></td><td>Monthly posting activity</td><td>Array of structs</td></tr><tr><td><code>post_activity_monthly[].snapshot_date</code></td><td>Date when the monthly post count snapshot was recorded</td><td>Date</td></tr><tr><td><code>post_activity_monthly[].total_posts_count</code></td><td>The total number of posts on the profile observed at that snapshot</td><td>Integer</td></tr><tr><td><code>post_activity_monthly_inferred</code></td><td>Month-by-month posting activity for the trailing 12 months. Includes one entry per month, even months with no posts</td><td>Array of structs</td></tr><tr><td><code>post_activity_monthly_inferred[].month</code></td><td>First day of the month this entry covers</td><td>Date</td></tr><tr><td><code>post_activity_monthly_inferred[].posts_count</code></td><td>Number of posts published during the month</td><td>Integer</td></tr><tr><td><code>post_activity_monthly_inferred[].comments_received_count</code></td><td>Number of comments received on published posts</td><td>Integer</td></tr><tr><td><code>post_activity_monthly_inferred[].reactions_received_count</code></td><td>Number of reaction on published posts</td><td>Integer</td></tr><tr><td><code>post_hashtags</code></td><td>Hashtags the employee has used in their posts</td><td>Array of structs</td></tr><tr><td><code>post_hashtags[].hashtag</code></td><td>A used hashtag text. Value is without the leading "#" symbol</td><td>String</td></tr><tr><td><code>post_hashtags[].posts_count</code></td><td>Number of the employee's posts that used this hashtag</td><td>Integer</td></tr><tr><td><code>people_mentioned</code></td><td>Employees tagged in the employee's posts, via profile-page mentions</td><td>Array of structs</td></tr><tr><td><code>people_mentioned[].id</code></td><td>ID of the mentioned employee. <code>null</code> when the slug does not resolve</td><td>Long</td></tr><tr><td><code>people_mentioned[].full_name</code></td><td>Full name of the mentioned employee. <code>null</code> when unresolved</td><td>String</td></tr><tr><td><code>people_mentioned[].shorthand_name</code></td><td>Mentioned employee's public profile shorthand name</td><td>String</td></tr><tr><td><code>people_mentioned[].profile_url</code></td><td>Mentioned employee's public profile URL</td><td>String</td></tr><tr><td><code>people_mentioned[].mentions_count</code></td><td>Number of times this employee was mentioned across the employee's posts</td><td>Integer</td></tr><tr><td><code>companies_mentioned</code></td><td>Companies tagged in the record employee's posts, via company-page mentions</td><td>Array of structs</td></tr><tr><td><code>companies_mentioned[].id</code></td><td>Name of the mentioned company. <code>null</code> when the slug does not resolve</td><td>Long</td></tr><tr><td><code>companies_mentioned[].name</code></td><td>Company name. <code>null</code> when unresolved</td><td>String</td></tr><tr><td><code>companies_mentioned[].shorthand_name</code></td><td>Public company profile shorthand name</td><td>String</td></tr><tr><td><code>companies_mentioned[].company_url</code></td><td>Company public profile URL</td><td>String</td></tr><tr><td><code>companies_mentioned[].mentions_count</code></td><td>Number of times this company was mentioned across the employee's posts</td><td>Integer</td></tr><tr><td><code>people_engaged_with</code></td><td>Employees whose posts this employee liked, commented on, or reposted</td><td>Array of structs</td></tr><tr><td><code>people_engaged_with[].id</code></td><td>ID of the employee engaged with</td><td>Long</td></tr><tr><td><code>people_engaged_with[].full_name</code></td><td>Full name of the employee engaged with</td><td>String</td></tr><tr><td><code>people_engaged_with[].shorthand_name</code></td><td>Shorthand name from the employee's public profile</td><td>String</td></tr><tr><td><code>people_engaged_with[].profile_url</code></td><td>URL of the employee's public profile</td><td>String</td></tr><tr><td><code>people_engaged_with[].posts_reacted_count</code></td><td>Number of the author's posts this employee reacted on</td><td>Integer</td></tr><tr><td><code>people_engaged_with[].posts_commented_count</code></td><td>Number of the author's posts this employee commented on</td><td>Integer</td></tr><tr><td><code>people_engaged_with[].posts_reposted_count</code></td><td>Number of the author's posts this employee reposted</td><td>Integer</td></tr><tr><td><code>people_engaged_with[].last_signal_date</code></td><td>Date of the most recent engagement of any type</td><td>Date</td></tr><tr><td><code>people_engaged_with[].last_engaged_post_url</code></td><td>URL of the post of the most recent engagement</td><td>String</td></tr><tr><td><code>companies_engaged_with</code></td><td>Companies whose posts this employee liked, commented on, or reposted</td><td>Array of structs</td></tr><tr><td><code>companies_engaged_with[].id</code></td><td>Company ID</td><td>Long</td></tr><tr><td><code>companies_engaged_with[].name</code></td><td>Company name</td><td>String</td></tr><tr><td><code>companies_engaged_with[].shorthand_name</code></td><td>Public company profile page shorthand name</td><td>String</td></tr><tr><td><code>companies_engaged_with[].company_url</code></td><td>Company profile page URL</td><td>String</td></tr><tr><td><code>companies_engaged_with[].posts_reacted_count</code></td><td>Number of company's posts this employee reacted on</td><td>Integer</td></tr><tr><td><code>companies_engaged_with[].posts_commented_count</code></td><td>Number of company's posts this employee commented on</td><td>Integer</td></tr><tr><td><code>companies_engaged_with[].posts_reposted_count</code></td><td>Number of company's posts this employee reposted</td><td>Integer</td></tr><tr><td><code>companies_engaged_with[].last_signal_date</code></td><td>Date of the most recent engagement of any type</td><td>Date</td></tr><tr><td><code>companies_engaged_with[].last_engaged_post_url</code></td><td>URL of the post from the most recent engagement</td><td>String</td></tr><tr><td><code>post_commenters</code></td><td>Employees who commented on posts authored by employee in this record</td><td>Array of structs</td></tr><tr><td><code>post_commenters[].id</code></td><td>ID of the employee who commented the post</td><td>Long</td></tr><tr><td><code>post_commenters[].full_name</code></td><td>Full name of the employee who commented the post</td><td>String</td></tr><tr><td><code>post_commenters[].shorthand_name</code></td><td>Shorthand name from the employee's who commented the post public profile</td><td>String</td></tr><tr><td><code>post_commenters[].profile_url</code></td><td>Public profile URL of the employee who commented the post</td><td>String</td></tr><tr><td><code>post_commenters[].total_comments_count</code></td><td>Total number of comments made by this employee</td><td>Integer</td></tr><tr><td><code>post_commenters[].posts_commented_count</code></td><td>Number of distinct posts by this employee that they commented on</td><td>Integer</td></tr><tr><td><code>post_commenters[].last_commented_date</code></td><td>Date of the most recent comment</td><td>Date</td></tr><tr><td><code>post_commenters[].posts_commented</code></td><td>The individual posts this employee commented on.</td><td>Array of structs</td></tr><tr><td><code>post_commenters[].posts_commented[].post_url</code></td><td>URL of the commented post</td><td>String</td></tr><tr><td><code>post_commenters[].posts_commented[].post_date</code></td><td>Date the post was published</td><td>Date</td></tr><tr><td><code>post_commenters[].posts_commented[].comments_count</code></td><td>Number of comments on this specific post</td><td>Integer</td></tr><tr><td><code>post_resharers</code></td><td>Employees who reposted posts authored by employee in this record</td><td>Array of structs</td></tr><tr><td><code>post_resharers[].id</code></td><td>ID of the employee who reposted the post</td><td>Long</td></tr><tr><td><code>post_resharers[].full_name</code></td><td>Full name of the employee who reposted the post</td><td>String</td></tr><tr><td><code>post_resharers[].shorthand_name</code></td><td>Shorthand name from the employee who reposted the post public profile</td><td>String</td></tr><tr><td><code>post_resharers[].profile_url</code></td><td>Public profile URL of the employee who reposted the post</td><td>String</td></tr><tr><td><code>post_resharers[].posts_reposted_count</code></td><td>Number of distinct posts reposted by this employee</td><td>Integer</td></tr><tr><td><code>post_resharers[].last_reposted_date</code></td><td>Date of the most recent repost</td><td>Date</td></tr><tr><td><code>post_resharers[].last_reposted_post_url</code></td><td>URL of the post that was reposted</td><td>String</td></tr><tr><td><code>post_reactors</code></td><td>Employees who reacted on posts authored by employee in this record</td><td>Array of structs</td></tr><tr><td><code>post_reactors[].id</code></td><td>ID of the reacted employee</td><td>Long</td></tr><tr><td><code>post_reactors[].full_name</code></td><td>Full name of the reacted employee</td><td>String</td></tr><tr><td><code>post_reactors[].shorthand_name</code></td><td>Public profile shorthand name of the reacted post employee</td><td>String</td></tr><tr><td><code>post_reactors[].profile_url</code></td><td>Public profile URL of the reacted post employee</td><td>String</td></tr><tr><td><code>post_reactors[].posts_reacted_count</code></td><td>Count of unique posts the employee has reacted to</td><td>Integer</td></tr><tr><td><code>post_reactors[].last_reacted_post_date</code></td><td>Date when the employee's most recent reacted post was published</td><td>Date</td></tr><tr><td><code>post_reactors[].last_reacted_post_url</code></td><td>URL of the last reacted post</td><td>String</td></tr></tbody></table>
{% endupdate %}

{% update date="2026-10-10" %}

## Indeed Jobs data: changing data field's type

The `job_type` field in the Indeed Jobs dataset will now be provided as an array of strings rather than a single string. For postings with multiple employment types, such as roles suitable for both part-time and full-time candidates, all relevant values will now be listed instead of just one. This is a breaking change, so any integrations that interpret `job_type` as a plain string need to be updated before the cutoff date.

| Data field       | Before                                                  | After                                                                             |
| ---------------- | ------------------------------------------------------- | --------------------------------------------------------------------------------- |
| `job_type`       | <p>String <br><code>"job\_type": "Part-time"</code></p> | <p>Array of strings <br><code>"job\_type": \["Part-time", "Full-time"]</code></p> |
| {% 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/october-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.