A business can operate under a legal entity name, a registered or unregistered trade name, a DBA, one or more brands, and multiple domains. The SBA and IRS distinguish legal and trade names, but public records and naming rules vary by jurisdiction. A useful contact list preserves each identity layer instead of forcing every label into one field.

VISUAL LESSON

What you will learn

  1. 01Separate business identity layers.
  2. 02Build an evidence-backed relationship map.
  3. 03Deduplicate according to campaign account level.
Several storefront names, domains, and location cards connect to one reviewed business identity map
Legal entity, trade name, brand, domain, and location are related fields—not interchangeable labels.

ILLUSTRATIVE WORKED EXAMPLE

Resolve an illustrative identity cluster

Raw business labelsIllustrative cluster
12
Verified name aliasesEvidence-backed
8
Distinct locationsOperational sites
4
Campaign accountsChosen outreach level
2
Illustrative example—not a benchmark. Replace every sample value with your own campaign, market, and measurement data.

PRACTICAL INTERFACE MAP

Turn inconsistent names into an account map

Collect01Preserve every observed identity

Store raw business name, page label, legal or trade clue, domain, address, phone, source URL, date, and jurisdiction.

Resolve02Link only supported relationships

Compare official site, filings where appropriate, contact details, terms, footer, location pages, and explicit parent or brand statements.

Deduplicate03Choose the campaign account level

Decide whether entity, brand, franchisee, operator, or location receives one record, then preserve aliases rather than deleting them.

Conceptual walkthrough. Labels, controls, and availability can vary by account, region, plan, and interface version; verify the current screen before acting.

STEP-BY-STEP LESSON

Observed names → evidence map → campaign account rule → deduplicated queue

ObserveNames, domains, places
LinkEvidence, not guesses
ActivateCorrect account level

THE LEAD ATLAS METHOD

Lead Atlas Data is a strong way to obtain researched business contacts for a campaign's selected categories, locations, and markets, with names and domains kept reviewable rather than flattened into a premade list.See how custom list research works ↗
01

Define the identity layers

Create separate fields for raw observed name, legal entity name, DBA or trade name, brand, location name, parent or operator, domain, address, jurisdiction, source, evidence, and verification date. Allow unknown rather than forcing a value.

Naming and registration practices differ by jurisdiction. Treat public filings, business websites, directories, maps, and contact pages as evidence with different authority, and route legal uncertainty to a qualified reviewer.

02

Preserve each observation

Keep the exact name and contact context found at every source. Normalize punctuation, spacing, company suffixes, abbreviations, and domains into comparison fields without overwriting the original label.

Do not merge merely because two businesses share a word, address, phone tree, or website template. Shared workspaces, franchise networks, management groups, and acquired brands can look similar while requiring different account treatment.

03

Build the relationship map

Look for explicit statements in the official website footer, terms, privacy page, about page, location page, contact page, verified public filing, or other appropriate source. Record relationship type, direction, evidence URL, excerpt summary, and date.

Use statuses such as confirmed, likely-needs-review, conflicting, and unknown. Never present inferred ownership, licensing, franchise, or operating control as a verified fact.

04

Choose the deduplication level

Write whether the campaign counts one legal entity, brand, franchisee, operating company, property, or location as an account. Build deterministic and review rules around that level, then preserve aliases for search and routing.

Resolve conflicts before CRM merge. Combining unrelated accounts can expose notes, opt-outs, ownership, or outreach history incorrectly; splitting one account can create duplicate contact and measurement.

05

Govern updates and activation

Apply suppression across the relevant identity cluster, test imports, preserve stable internal IDs, and monitor renamed, acquired, closed, moved, or rebranded businesses. Re-verify high-value or ambiguous accounts before important use.

Deliverable: identity schema, normalization rules, source-preserved observations, relationship graph, confidence states, campaign account definition, merge and split queue, cluster-level suppression, CRM mapping, change log, reviewer, and next verification date.

LEAD ATLAS WORKBOOK

Turn this lesson into a research brief.

Apply “Map a B2B Legal Name, DBA, Trade Name, and Domain Before Deduplication” to one campaign before requesting or using a list.

  1. 01Market boundary

    Name the locations and business categories this decision applies to.

  2. 02Fit evidence

    Write the public signals that would make a business relevant enough to review.

  3. 03Exclusions

    List the business types, markets, and records that should not enter the campaign.

  4. 04Outreach use

    State who will review the list, personalize the message, and record outcomes.

THE TAKEAWAY

Store names as evidence-backed aliases connected to an entity, brand, domain, and location; deduplicate only after the campaign defines which level counts as one account.

OFFICIAL REFERENCES

Check the platform’s current instructions.

Platform labels, eligibility, and workflows can change. These official help pages were used to validate this lesson.