Identity Resolution is the process of stitching fragmented identifiers and signals across devices, channels, and tools into a single resolved person or account — collapsing many partial records into one canonical entity.
A real buyer leaves traces everywhere: a work email in the CRM, a personal email on a webinar form, a LinkedIn profile, an anonymous website visit tied to a cookie, an intent signal from a third-party provider. Identity resolution matches those scattered fragments — deterministically on shared keys like email or domain, probabilistically on weaker signals like name, company, and IP — and merges them into one record so the system knows it is all the same person, and that person belongs to a specific account. The account-level version, where individual people are rolled up to their company, is the backbone of account-based motions.
In 📝GTM Engineering identity resolution is the unglamorous plumbing that makes every other play possible. Enrichment, 📝lead scoring, routing, and personalization all assume a clean, deduplicated entity to act on; without resolution, the same buyer gets counted three times, scored inconsistently, and emailed by two reps at once. It is also what turns anonymous demand — a website visitor, an intent spike — into a named, reachable account that can enter a sequence.
The discipline relates closely to 📝data enrichment and CRM hygiene: enrichment adds attributes to a record, while identity resolution decides which records are the same record in the first place. Get resolution wrong and enrichment compounds the error, polishing duplicates instead of unifying them.
This is the layer nobody demos and everybody underestimates. Most "our data is a mess" complaints are really identity-resolution failures — duplicate accounts, orphaned contacts, anonymous traffic that never gets matched. Fix resolution first; every downstream play inherits the cleanliness or the chaos.