News Signals: Second Company Enrichment
We are introducing structured second company data to news signals that involve two parties. This applies to M&A, partnership, investment, integration, litigation, and talent movement events.
This is an upcoming change, targeted for early June 2026. We will communicate the exact rollout date in advance. No action is needed until then.
What is changing
News signals for certain event categories naturally involve two companies — an acquirer and an acquisition target, an investor and the company invested in, two partners, etc. Today, only the primary company is delivered as structured data. The second party is only available in the article text, meaning customers need to parse unstructured content to identify who was acquired, who received funding, or who the new partner was.
With this update, a new related_company object will be added to the signal record for all applicable event categories. It follows the same schema as the existing company field.
New field
| Field | Type | Description |
|---|---|---|
related_company.name | string | Name of the second company in the event |
related_company.domain | string | Domain of the second company |
Which signal subtypes will include related_company
related_company| Subtype | company (primary) | related_company (new) |
|---|---|---|
| Acquisition | Acquirer | Company acquired |
| Merger | Company A | Merge partner |
| Sells Assets | Seller | Buyer |
| New Customer | Vendor | The new client |
| Files Lawsuit | Plaintiff | Defendant |
| Invests Into | Investor | Company invested in |
| Integration | Company A | Integration partner |
| Partnership | Company A | Partner |
| Competitor Identified | Company A | The competitor |
| Executive Departure | (person-level) | Company departed from |
| Executive Retirement | (person-level) | Company retired from |
For Executive Departure and Executive Retirement events, the source data only provides the company being left (not the person's new employer). Currently these signals have an empty company object. With this update, the company will be correctly populated.
Expected impact
Based on recent delivery data:
- ~5,000 records per delivery (roughly 24% of all news signals) will include structured second-company data that is currently missing
- ~1,000 Executive Departure/Retirement signals that currently have no company data at all will be populated
- Customers will be able to filter, search, and cross-reference both companies in M&A, partnership, and investment signals without parsing article text
Schema example
{
"signal_type": "news",
"signal_subtype": "acquires",
"company": {
"name": "Acquirer Corp",
"domain": "acquirer.com"
},
"related_company": {
"name": "Target Inc",
"domain": "targetinc.com"
},
"data": {
"signal_name": "Acquisition",
"summary": "Acquirer Corp has acquired Target Inc for $50M.",
"category": "acquires"
}
}What stays the same
- Signal types without a second party (e.g., Funding, IPO, Launches, Headcount changes) are unchanged.
related_companywill not be present on those signals. - Existing
companyfield is not affected. Same schema, same data. - Delivery schedule and file format are unchanged.
What to update
Once this change goes live, if you ingest news signals, add handling for the optional related_company object. It will be present on the 11 subtypes listed above and absent on all others. No changes are needed for signals that do not include a second company.
