# February 2025

## Multi-source Company data

### 🗺 Mapping improvements

**Funding data mapping:**\
Improved entity matching between firmographic and funding datasets, resulting in:

* **110,000+** additional funding records now integrated into the dataset.

***

### 🔧 Field enhancements

**📍 Location data enrichment:**\
When unavailable in core records, location fields are now enriched from external sources, increasing coverage by over **1 million** companies.

**Impacted fields:**

* `hq_country`
* `hq_location`
* `hq_full_address`
* `hq_city`
* `hq_state`
* `hq_street`
* `hq_zipcode`
* `company_locations_full`

**👥 Employee count improvements:**\
Now includes profiles with blurred experience data for more accurate workforce metrics.

**Impacted fields:**

* `employees_count_by_country`
* `employees_count_breakdown_by_region`
* `employees_count_breakdown_by_seniority`
* `employees_count_breakdown_by_department`

***

#### 🐛 Bug fixes

* Resolved the mismatch between `active_job_postings_count` and `active_job_postings_titles`
* Fixed duplicate values in:
  * `employees_count_by_month`
  * `professional_network_followers_count_by_month`
  * `active_job_postings_count_by_month`

***

#### 📰 News category changes

**Impacting:** `num_news_articles`, `news_articles`\
**Cause:** Deprecation of the News category by a third-party data source\
**Effect:** Fewer or no updates for these fields in this release\
**Next steps:** Exploring alternative sources to restore coverage in future updates

## Multi-source Company API

### ⚠️ Data category deprecation: Company News

**Impacted dataset:** Multi-source Company API\
**Effective from:** February 2025\
**Fields affected:**

* `num_news_articles`
* `news_articles`

**Impact:**\
You may observe a noticeable drop in data updates for these fields due to the deprecation of the underlying News data category from our third-party provider.

**Next steps:**\
We are actively investigating alternative data sources to restore and improve Company News coverage in future releases.


---

# Agent Instructions: 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:

```
GET https://docs.coresignal.com/release-notes/february-2025.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.