30-second answer: Visitor identification (also called website de-anonymization) resolves anonymous web visitors to companies and people. The vocabulary spans resolution methods (reverse IP lookup, deterministic cookie match, probabilistic device match, account graph stitching), tag-class terms (first-party, third-party, server-side, edge), data-class terms (firmographic enrichment, technographic enrichment, persona inference), and operating terms (match rate, fingerprinting, GDPR posture, latency). This glossary defines 22 visitor-identification terms.
See first-party visitor identification with account orchestration inside Abmatic AI, book a demo.
Reverse IP lookup resolves a website visitor's IP address to the company that owns it, enabling account-level identification without a logged-in session. It is the simplest and most common identification mechanism. See reverse IP lookup.
Deterministic cookie match identifies a visitor by reading a first-party cookie set on a previous identified session (form fill, login). When the cookie is present, the match is high-confidence.
Probabilistic device match resolves a visitor using device characteristics (user agent, screen size, language, time pattern). It is wider in coverage but lower in confidence than deterministic methods.
Email-to-domain match resolves a known contact (from form fill or marketing email click) to a company by parsing the email domain. It is the cleanest deterministic match for B2B.
Browser fingerprinting derives a probabilistic identifier from browser configuration. It is increasingly limited by browser-vendor anti-tracking measures (Safari Intelligent Tracking Prevention, Firefox Enhanced Tracking Protection) and is GDPR-sensitive.
Account graph stitching combines multiple identification signals (IP, cookie, email, fingerprint) into a single account record. See account graph and identity resolution.
A first-party tag is JavaScript or pixel code served from the vendor's own domain that captures visitor activity. First-party tags are not blocked by mainstream ad blockers and survive third-party cookie deprecation.
A third-party tag is code served from a domain other than the host site's. Third-party tags are increasingly blocked by browsers and ad blockers, eroding their reliability for visitor identification.
A server-side tag fires from the host's own backend rather than from JavaScript in the browser. It is not blockable by client-side tools and is the modern best practice for high-fidelity identification.
An edge tag fires from a CDN edge node, combining server-side fidelity with low latency. Cloudflare Workers, Fastly Compute, and Vercel Edge Functions are common edge runtimes.
A Google Tag Manager server container runs server-side tag firing through Google's tag-management interface. It is the most common server-side tag manager in production B2B sites.
Firmographic enrichment appends company attributes (industry, employee count, revenue, geography) to the resolved visitor record. It turns a company name into a usable targeting record.
Technographic enrichment appends technology stack data to the resolved company record. It is the second-most common enrichment after firmographic.
Persona inference predicts the role of an unidentified visitor (engineer, marketer, executive) from device, content path, and time-on-page patterns. The inference is probabilistic and used mainly for content recommendation.
Page-path enrichment tags the visitor record with the pages they viewed in sequence, building a content-engagement signal at the company level.
Match rate is the percentage of total visitors successfully resolved to a company. Mainstream B2B sites in 2026 see match rates between 30 and 60 percent depending on traffic mix and provider quality.
Latency is the time between visitor arrival and the resolved record being available downstream. Real-time personalization requires sub-200ms latency; sales alerting tolerates seconds.
Identification coverage is the percentage of target accounts that triggered at least one identified visit in the period. It is the basic execution metric for visitor identification programs.
False-positive rate is the share of resolved companies that are wrong (the IP belonged to an ISP, a coworking space, or a different company). Quality programs publish their false-positive rate; cheap providers do not.
GDPR posture describes how the identification program handles data captured in the EU and EEA: the lawful basis (legitimate interest versus consent), the consent mechanism, and the data residency. Reverse IP lookup is generally legitimate-interest in B2B but the legal interpretation continues to evolve.
Cookieless identification resolves visitors without third-party cookies, using server-side IDs, email-to-domain match, and IP enrichment. It is the dominant pattern in 2026 because third-party cookies are deprecated. See how to de-anonymize website traffic.
A first-party data strategy is the operating plan for collecting, storing, and acting on data the vendor owns. It is the foundation of cookieless visitor identification. See first-party data strategy.
Identity resolution is the process of stitching all identification signals into a single canonical record. It is the architectural backbone of modern visitor-identification stacks.
Ready to see visitor identification driving real routing? Book a demo of Abmatic AI.
Modern reverse-IP providers achieve 60 to 80 percent accuracy on small-and-mid-market business IPs and lower on residential or coworking traffic. Quality varies by provider and by region. Always pair reverse IP with email-to-domain match where available for higher confidence.
Visitor identification can be run compliantly under GDPR with the right lawful basis (typically legitimate interest for B2B), proper notice in the privacy policy, and appropriate data-subject rights handling. The specific compliance posture depends on jurisdiction and use case; legal review is essential before deployment.
RB2B identifies individual people who visited the site (name, LinkedIn) using deterministic match. 6sense identifies in-market accounts using a combination of intent data, account graph stitching, and predictive scoring. Different problems, different methods. See RB2B alternatives and 6sense alternatives.
Yes. Identified visits are first-party engagement signals and feed engagement scoring directly. The right pattern is to weight identified-account visits higher than anonymous visits because the account match is confirmed.
Visitor identification is the trigger; personalization is the action. Identification answers who is here; personalization answers what to show them. The two systems share a single account record. See how to personalize the ABM website experience.
Visitor identification stacks settle into one of three patterns. The single-vendor pattern uses one identification provider for everything: tag, resolution, enrichment, and account-graph stitching. It is fast to deploy and adequate for most early-stage B2B programs, but creates platform lock-in. The decoupled pattern separates the tag layer (often a server-side GTM container), the resolution layer (one or more reverse IP and contact-match providers), and the enrichment layer (firmographic and technographic vendors), with the account graph stitching done in the data warehouse. It is more flexible and avoids lock-in but requires deeper engineering ownership. The hybrid pattern combines a primary identification vendor with a warehouse-side audit and override layer that lets the team correct, suppress, or amplify specific resolutions.
Production teams selecting between these patterns should look at engineering capacity, multi-vendor compliance posture, and the planned lifetime of the stack. The decoupled pattern wins for mature programs with strong data engineering; the single-vendor pattern wins for fast-moving teams without dedicated engineering capacity.
Visitor identification is a foundational capability for modern B2B revenue programs because the buying committee researches anonymously before they fill out forms. The cleanest stacks combine first-party server-side tagging, reverse IP lookup, deterministic cookie match where available, and a unified account graph. Use this glossary as a reference when reading visitor-identification vendor documentation.
See first-party visitor identification combined with orchestration. Book a demo of Abmatic AI.