Person-Level vs Account-Level Identity Resolution

Account-level identity resolution maps a visitor or signal to a company. Reverse-IP tools like Snitcher, Leadfeeder, and Albacross sit here, answering 'which account is showing demand' rather than 'which person'. This is the right altitude for demand sensing across your whole funnel, because you can see an account warming up long before any individual fills a form. The tradeoff is that you cannot tell which of the 3000 employees at a large logo actually engaged.

Person-level resolution maps the same activity to a named human, usually with a work email and LinkedIn profile. RB2B, Warmly, and Koala live in this category and stitch first-party cookies to a cooperative identity graph. This is the altitude you need to run a real outbound play, because an SDR cannot email an account, only a person. The catch is that coverage is patchy, skews toward US traffic, and carries a heavier GDPR burden in the EU.

Account-level resolution degrades with remote work, VPNs, and shared residential ISPs. A buyer working from home often resolves to a consumer ISP block rather than their employer, so the signal evaporates. It also flattens a 20-person buying committee into a single account row, which means you lose the ability to multithread to the economic buyer, the champion, and the blocker as distinct people. Treat account-level coverage as a wide but shallow net.

Person-level resolution has the inverse weakness: match rates that dazzle in a demo shrink hard against real, geographically mixed traffic. In the EU, resolving an anonymous visitor to a named individual is processing personal data, so you need a documented lawful basis and transparent disclosure, not a quiet pixel. Many teams cap person-level resolution at high-intent pages like pricing and demo, where the value justifies the consent and compliance overhead.

Treat marketing like code: version the resolution logic and make it observable. Run account-level reverse-IP as your always-on demand sensor and person-level pixels as the sharp instrument on your highest-intent surfaces. Pipe both into Clay, dedupe against HubSpot or Salesforce, and let the richer person-level record win whenever it exists. The shared identity graph is the asset you own, not the individual vendor feed you rent.

Anchor the choice to your motion rather than to vendor hype. Enterprise teams with huge anonymous committees often get enough from account-level signal plus form enrichment. Fast mid-market outbound needs a named human to act on while intent is warm, which justifies the person-level investment. Allbound only works when inbound, outbound, paid, and content all read from this one identity layer instead of four disconnected tools.