Skip to main content

Signal key

name_change

Category

Identity

Source

Company Professional Network page (name field).
The company name string changed.

​
When it fires

Trigger condition

name string changed between snapshots.

​
Stored fields

This signal persists the following metadata you can read downstream:

​
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 use Name Change Signal?

The scenario. You run an SEO and web agency, and your highest-margin service is migration protection: keeping a company’s search traffic alive while its domain, brand, and site all change underneath it. The catch is timing. Companies call you after the rebrand ships and the traffic is already gone, when the cheap version of the project would have been beforehand. The goal. Catch renames the week they surface, while redirects, rankings, and brand equity can still be protected instead of resurrected. The signal fires. name_change fires for Harbourline, a B2B logistics platform now presenting itself as Arclight. The website still lives on the old domain, which tells you the migration is mid-flight, the most dangerous and most billable possible moment. What it tells you. A company mid-rename has a dozen technical decisions in front of it that marketing teams reliably underestimate: domain strategy, redirect mapping, backlink outreach, brand-query cannibalization. Handled well, the rename costs a few percent of organic traffic for a quarter. Handled naively, it costs half their inbound pipeline for a year, and someone gets blamed. The play.
  1. Confirm the migration state: new name live, old domain still primary means you are early enough to matter.
  2. Write to the marketing lead with the risk quantified and the fix framed as insurance:
Congrats on the Arclight rebrand. The riskiest part is still ahead: renamed companies that migrate domains without a redirect plan typically lose 30 to 60% of organic traffic. We protect exactly this transition, happy to sanity-check your plan for free either way.
  1. The free sanity-check is the wedge; almost no in-house plan survives it intact, and the gaps become the scope.
  2. Deliver the migration, then keep the retainer, renamed companies spend on visibility for a year after.
Automate it. A weekly Company Signals API pull on name_change in your market is a standing list of companies entering the exact two-month window your service exists for. Why it lands. Rebrand budgets are emotional; migration budgets are insurance. You are selling the insurance while the truck is still loading.

​
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

Investigate the cause. Update CRM records and re-confirm the account’s status.

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.