logo

Account Identification

Account Identification

Account identification is the process of matching a newly identified company, often surfaced through website visitor identification, to an existing account record in your CRM, so that new activity attaches to the right existing history rather than creating a duplicate or orphaned record. Where visitor identification answers “who is this,” account identification answers “which of our existing accounts does this belong to.”

Key Benefits

  • Clean CRM data: Prevents duplicate account records from fragmenting a company’s activity history.
  • Unified account view: Gives reps a complete picture of all activity tied to a single account, old and new.
  • Better account-based reporting: Ensures engagement metrics roll up to the correct existing account, not a duplicate.
  • Faster context for reps: New activity surfaces immediately against the account’s existing relationship history.

Best Practices

  • Match on domain, not company name alone: Company names vary in formatting; domain matching is far more reliable.
  • Handle parent-subsidiary relationships deliberately: Decide upfront whether subsidiary activity should roll up to a parent account or stay separate.
  • Automate the match where possible: Manual matching doesn’t scale once identification volume grows.
  • Flag unmatched accounts for review: Route companies that don’t match an existing record into a clear new-account creation process, rather than letting them sit unassigned.

Account Identification vs. Website Visitor Identification

Website visitor identification determines which company an anonymous session belongs to, using reverse IP lookup or similar methods. Account identification takes that result and matches it against your existing CRM data, deciding whether this is a brand-new account or activity from a company you already have a record for. The first answers “who is this,” the second answers “do we already know them.”

Tools and Technologies

  • CRM matching and deduplication tools: Automatically match incoming identification data to existing account records.
  • Domain-based matching logic: Uses email or website domain rather than company name text for more reliable matching.
  • Data enrichment platforms: Standardize company data to improve match accuracy across sources.
  • Related: Website Visitor Identification and Website Visitor Tracking.

Challenges and Solutions

Inconsistent company naming is the most common cause of failed matches, where “Acme Inc,” “Acme Corporation,” and “Acme” all exist as separate records for the same company. Parent-subsidiary structures add further complexity when a subsidiary’s activity should logically inform decisions at the parent level, or vice versa. The fix is standardizing on domain-based matching wherever possible, and defining clear rules for how subsidiary relationships should be handled before volume makes manual cleanup impractical.

Frequently Asked Questions about Account Identification

What’s the best way to match identified companies to CRM accounts?

Domain-based matching is generally the most reliable method, since company name formatting varies too much for consistent text matching, while a website or email domain tends to stay consistent.

What happens when an identified company doesn’t match an existing account?

Most teams route unmatched companies into a review queue or automatically create a new account record, depending on how much confidence they have in the identification data and how they want to handle account creation governance.

Turn buyer behaviour into Salesforce intelligence

SalesWings helps teams capture first-party behavioural data, score leads and accounts, trigger actions, and surface revenue intelligence inside Salesforce.

Book a demo

Pin It on Pinterest