Signal key
name_changeCategory
Identity
Source
Company Professional Network page (name field).
When it fires
Trigger condition
name string changed between snapshots.Stored fields
This signal persists the following metadata you can read downstream:| Field | Description |
|---|---|
from_value | The previous company name. |
to_value | The new company name. |
Magnitude
Treated as high-signal; names rarely change without a reason.For the full bucket definitions used across percentage-based signals, see Magnitude buckets.
Why it matters
Names rarely change without a reason, a rebrand, an acquisition, or a legal restructuring. A name change is a flag to re-investigate everything you know about the account, and it feeds the rebrand_signal and acquired_signal composites.How to read it
Always meaningful
Companies don’t rename casually; something structural happened.
M&A or rebrand
The two most common causes are acquisition and rebranding.
Composite input
Feeds rebrand_signal and acquired_signal.
Outreach playbook
Related signals
Name Change Drastic
A name change with almost no overlap to the old name.
DBA Added
The name now references a former name (dba/fka).
Rebrand Signal
A company executed a coordinated rebrand.
Acquired Signal
A company was acquired.
Track this signal with CUFinder
Surface
name_change across millions of companies, enriched with verified emails, phones, and full firmographics. Start free, no credit card required.