# How HockeyStack Connects Anonymous, Personal and Business Identities ## Overview In complex B2B journeys, users often engage with both **personal** and **business** email addresses.\ A prospect might first interact using `@gmail.com` and later convert using `@company.com`. Without identity stitching, these actions appear as separate users in CRM or marketing systems, leading to: * Disjointed lead records * Incomplete attribution * Fragmented account journeys HockeyStack resolves these gaps automatically. *** ## Why Identity Fragmentation Happens Most data pipelines treat each email domain as a distinct identity. As a result, personal-domain interactions remain disconnected from later business-domain conversions. When marketing automation or CRM systems lack normalization and enrichment, account-level insights become incomplete. *** ## HockeyStack’s Approach to Identity Stitching HockeyStack unifies every touchpoint - anonymous, personal, or corporate - under the correct account.\ This process is fully automated and does not require manual setup. | **Layer** | **Description** | **Outcome** | | -------------------------------------- | --------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------- | | **1. Device & Network Fingerprinting** | Generates a persistent, cookie-less fingerprint from browser, device, and network attributes. | Recognizes returning visitors across sessions - even if they use different emails. | | **2. Reverse IP + Company Enrichment** | Uses IP intelligence and network metadata to map activity to company domains in real time. | Associates personal-domain visitors with their corresponding company accounts. | | **3. Cross-Identity Matching** | Merges all historical interactions when a user later identifies with a business email. | Maintains the full journey from anonymous visits through conversion. | | **4. Company-Level Journey View** | Consolidates all user interactions into one account timeline. | Enables unified reporting for Marketing, Sales, and RevOps teams. | *** ### Handling Every Identity Scenario HockeyStack’s stitching engine uses deterministic identity signals (hashed emails, CRM IDs, authentication events, device fingerprints) combined with reverse IP enrichment to maintain identity continuity across anonymous, known, and hybrid session types, including personal to business domain transitions. Reverse IP works when the network is identifiable in real time. In cases where a network cannot be resolved, device fingerprinting and identity signals still preserve journey continuity, even without IP attribution. | **Scenario** | **Example Path** | **How It’s Stitched** | **Result** | | ---------------------------------------- | ----------------------------------------------------- | ---------------------------------------------------------------- | --------------------------------------------------------- | | **Anonymous Visitor → Never Identified** | Visitor browses pricing page | Fingerprinting and reverse IP connect session to company network | Session appears in company timeline even without an email | | **Anonymous → Personal Email** | Visitor signs up with `jane.doe@gmail.com` | Fingerprint and metadata link both sessions | Complete activity history stitched to the account | | **Personal → Business Email** | Same user later fills a form with `jane.doe@acme.com` | Both sessions merged under the same device identity | Unified customer journey from first touch to conversion | | **Business → Personal Email** | User revisits and submits form with personal address | Fingerprinting preserves association with prior business domain | Journey continuity maintained | *** ## Why Competing Vendors Fall Short Traditional tools rely on cookies or explicit identifiers (form fills, CRM syncs) to link user sessions. These methods fail when: * Cookies expire or are blocked by browsers * Users alternate between personal and corporate domains * Privacy frameworks (ITP, GDPR, Chrome changes) restrict tracking HockeyStack uses **cookie-less fingerprinting** to maintain identity continuity - without dependence on cookies or manual reconciliation. | **Vendor Type** | **Limitation** | | ------------------------- | ------------------------------------------------------ | | **Cookie-based** | Lose visibility when cookies reset or expire | | **IP-only** | Cannot differentiate shared networks (home vs. office) | | **Declared-ID Dependent** | Require explicit form fills before linking journeys | ### HockeyStack’s Advantage HockeyStack combines: * **Cookieless fingerprinting** * **Network metadata enrichment** * **Identity resolution logic** This enables accurate cross-device and cross-domain stitching even when no declared identifier exists. *** ## Benefits * **Unified Identity Resolution**\ Automatically connects personal, corporate, and anonymous sessions under one account. * **Comprehensive Attribution**\ Ensures marketing ROI reflects the full multi-touch journey. * **Zero Maintenance**\ Fingerprinting and enrichment are pre-configured during onboarding - no additional setup required. * **Predictable Integration**\ Works natively with CRM and marketing systems through HockeyStack’s Atlas foundation and DataSyncs. *** ## Example When a visitor first engages using a personal email (`d1984@hotmail.com`) and later returns with a business email (`@nvidia.com`), HockeyStack links both sessions using fingerprint and enrichment data.\ All actions - ads, form fills, meetings, and pipeline events - consolidate under the same company journey.
*** ## Summary HockeyStack provides complete, privacy-compliant identity resolution across every domain, device, and data source. Every touchpoint rolls up to the correct company and opportunity, giving full visibility into how buying teams progress through the funnel. *** **Related Topics** * [Atlas Data Foundation](https://docs.hockeystack.com/documentation/the-hockeystack-data-model/hockeystack-data-foundation-atlas) * [Cookieless Tracking](https://docs.hockeystack.com/technical-details/tracking/how-does-cookieless-tracking-work)