Website visitor resolution: when to resolve to an account, a persona, or a contact

Website visitor resolution tools all promise the same headline: find out who is anonymously browsing your site. But 'who' means three different things depending on the tool, and most teams buy one without realising which kind they actually need. Account-level resolution tells you which company a visitor works at. Persona-level resolution adds a likely role or seniority on top of that company. Contact-level resolution goes further still and names the actual individual. Each is a genuinely different product, not a feature tier of the same one.

Account-level resolution is the easiest to get right and the hardest to act on alone. It works by matching a visitor's IP address against a database of known company IP ranges, which is reliable for office-based B2B traffic but says nothing about who at that company was looking, or why. We use it as a first filter -- did anyone from a target account show up at all -- rather than a trigger for outreach, because 'someone from a target account visited the pricing page' isn't a lead, it's a prompt to look closer.

Persona-level resolution is where most teams actually need to land, and where most tools quietly fall short. It infers a likely job function or seniority band from browsing behaviour and firmographic modelling rather than identifying a specific name, which is enough to route an account to the right sales motion -- a technical-evaluator browsing pattern gets a different follow-up than an economic-buyer pattern, even without a name attached. We've found this tier gives sales teams enough to act intelligently without over-promising a certainty the underlying data doesn't actually have.

Contact-level resolution -- naming the individual -- is the one clients ask for first and the one we push back on hardest, because it carries the most legal weight and the least reliability. In the US, resolving a visitor to a named person from browsing behaviour sits in a comparatively permissive regulatory environment. In the UK and EU, doing the same thing runs straight into GDPR and PECR: identifying an individual from their online activity without a clear lawful basis is a real compliance exposure, not a grey area. Any contact-level resolution used against UK or EU traffic needs a documented lawful basis before a single name reaches a rep's inbox.

Most of the programs we run land on persona-level resolution as the default, with account-level underneath it as the filter and contact-level reserved for accounts where a lawful basis genuinely exists. That layered approach is what keeps visitor resolution data feeding cleanly into the same verified 46M+ record database and intent signals we run everything else through, rather than sitting in its own disconnected tool nobody trusts enough to actually act on.