B2C Website Visitor ID: What Actually Works

B2C website visitor ID resolves anonymous consumer traffic on your site to named individuals. A pixel captures visitor signals, matches them against a consumer identity graph, and hands back a real person with contact and demographic detail instead of a session ID. It's a different job from B2B visitor identification, which reads an IP address, guesses at a company, and leaves you to work out which of 400 employees was on the pricing page. Exact Match does this with Site ID: one install pixel that identifies 25-40% of verified human visitors, bots excluded, with full contact and demographic profiles delivered in real time.

Last updated: September 2026

Strip it back: three things this has to get right

B2C visitor ID has collected a lot of vocabulary it doesn't need. Identity graph, resolution layer, cookieless bridge, deterministic waterfall. Underneath all of it, three things decide whether the output is usable.

What the match is anchored to. Exact Match resolves deterministically, verifying each match against identity anchors like name, email, phone and address, instead of scoring a statistical likelihood that two sessions belong to the same person. In your CRM that's the difference between a record you can mail and a record you have to apologize for.

How fresh the data underneath is. A correct match to a real person is worthless if the phone number attached to them went dead two years ago. The graph behind Site ID refreshes daily across 250M+ verified U.S. consumer profiles.

What arrives after the match. An identified visitor with no attributes is a name. An identified visitor carrying demographics, behavior, interests, financial attributes and intent signals across 9 data domains is a segment you can actually target.

That's the whole discipline. Get those three right and the rest is configuration. For a closer look at what's happening on the page itself, see our visitor identification pixel guide.

Why B2B visitor ID gives a consumer site nothing

Most products in this category were built for B2B, and that matters more than the category page suggests.

Reverse-IP identification returns a company. On a consumer site, the "company" is Comcast, or Verizon, or the guest network at a coffee shop. You've learned nothing. You've learned nothing in a format that looks like data, which is how teams end up with a dashboard reporting identified traffic that never contained one addressable person.

Exact Match resolves at the individual level rather than company-level reverse IP, and runs a consumer-first graph rather than a B2B-primary database. I'd put that more strongly than the usual vendor framing does: for a consumer site, company-level resolution isn't a weaker version of the right answer, it's the wrong unit of measurement. A weaker answer degrades. A wrong unit stays wrong no matter how good the vendor's coverage gets.

It's not your fault if the numbers never added up. You were sold a B2B primitive for a consumer job, and it was reported back to you in a format that looked like it was working.

If you want the category boundaries laid out properly, the website visitor identification entry covers the terminology, and the website visitor identification tool comparison walks through what the different products in the space actually do.

The match rate, and the two words people drop when they quote it

Site ID identifies 25-40% of verified human visitors, bots excluded.

Both qualifiers there are doing real work, and both get lost the moment the number gets repeated in a meeting.

"Verified human" is the denominator. A rate quoted against all sessions, bot traffic included, is a rate against a population you don't care about. Bots don't buy anything. Inflating the denominator with them makes a match rate look worse; quietly matching against them makes it look better. Either way you're comparing numbers that were never measured the same way.

The range is a range on purpose. Where you land inside 25-40% moves with your traffic mix. Paid social landing on a product page doesn't behave like organic search landing on a blog post, and neither behaves like direct traffic from an email list. If a vendor hands you one flat percentage with no denominator attached, ask what it was measured against before you compare it to anything, including this.

Most people don't realize how much of the variance in these published numbers is definitional rather than technical.

What you actually do with an identified visitor

Identification is the input. It isn't the outcome, and treating it as the outcome is the most common way this gets wasted.

A resolved visitor arrives with contact and demographic profile attached, in real time. From there the useful moves are narrow and boring:

• Route high-intent page visits to a follow-up list while the visit is still warm
• Suppress people who already converted, so you could finally stop paying to re-acquire customers you already have
• Build a lookalike seed from people who behaved a specific way, not from people who happened to fill in a form
• Push identified profiles into your CRM or ESP through export templates with CRM-specific columns, so nobody hand-maps a spreadsheet at 6pm

That last one sounds like a small thing. It isn't. Every enrichment project I've seen stall has stalled at the column-mapping step, not the data step. Async export jobs with per-CRM column templates exist specifically because that's where the work actually dies.

The conversion mechanics after that point are their own subject, and the website visitor to lead conversion piece goes deeper than I can here.

Where this doesn't work, plainly

Three honest limits.

The consumer graph covers 250M+ verified U.S. profiles, so a U.S. consumer audience is what it's built around. Plan accordingly if most of your traffic isn't that.

At 25-40%, most of your visitors on any given day stay anonymous. This supplements your existing conversion work, it doesn't replace it, and anyone selling it as a replacement is selling you the top of the range as though it were the floor.

And identification tells you who, not why. A resolved visitor isn't automatically a buyer. Exact Match handles the "is this person in-market right now" question with a separate product, Predict ID, using Bayesian behavioral modeling rather than inferring intent from the fact that somebody loaded a page.

One flat Unlimited plan includes every product, every feature and unlimited credits, with no per-seat fees and no overage charges. Pricing is worked out on a short consultation. API and MCP access defaults to 30 requests per minute, raisable by agreement.