What counts as a match (and what doesn't).
The exact rule that decides when a visit bills you: what counts as a match, what we never charge for, and the billing edge cases other vendors won't write down.
On this page
Anyone selling website visitor identification will tell you they have great pricing. Almost nobody publishes the exact rule that decides whether a visit gets you billed. Here's ours.
What is a match?
A match is one US visitor we resolved to a full business profile, LinkedIn URL plus name, title, and company, and delivered to your dashboard. Everything else, bots, non-US visits, partial matches, errors, and repeat visits, never bills. The rest of this post is the fine print on that sentence.
Why publish the exact billing rule?
Visitor identification vendors have an obvious incentive to fudge the definition of a billable event. The cleaner the rule, the more predictable your bill, and the harder it is for us to surprise you with a $4,200 overage at the end of the month.
"You pay per identified visitor" isn't a definition. It hides three or four billing edges: bot traffic, partial matches, non-US visits, repeat visits. Some vendors charge for all of them. We don't.
What we count as a match
- The visitor is in the United States.
- The visitor passes our bot filter (no known crawlers, no prefetch, no UA-shaped junk).
- The identity step returns a full business profile: LinkedIn URL plus name plus title plus company.
- The result reaches your dashboard.
What we never count
- Non-US traffic. Identification is US-only; non-US visitors stay in analytics + replays without identifying.
- Bots and crawlers. Filtered before the identity step runs. They never hit your bill.
- HEM-only responses. If we only get a hashed email without a LinkedIn URL, the row is dropped, no profile, no charge.
- Errors and rate limits. 4xx responses from the identity step are never billed.
- Repeat visits. Once we've billed you for a visitor in a workspace, every future visit never bills again, for the lifetime of the workspace.
How VisitorLead fits
We publish this rule because the buyers we want, careful, margin-aware operators, read pricing pages with a calculator open. The clearer the rule, the easier the math. It's the same logic behind why we price by the match, not by the seat.
Turn anonymous traffic into named leads.
One pixel. <10s alerts. CSV export. Card required at signup, no free trial.
A note on the limits
Hard caps are first-class. Set a dollar or match ceiling under Settings → Billing and we stop calling the identity step the moment you hit it.
Next step
The full doc lives in the identification docs. The plan math lives on the pricing page.
Frequently asked questions
Does a repeat visitor count as a new match?
No. Once a visitor has been billed in a workspace, every future visit by the same person never bills again, for the lifetime of the workspace, no matter how many times they come back.
Do bots or crawlers ever count as matches?
No. Known crawlers, prefetch requests, and UA-shaped junk are filtered before the identity step runs, so they never reach your bill.
Do non-US visitors count as matches?
No. Identification is US-only. Non-US visitors stay in your analytics and session replays without being identified, and they are never billed.
What happens if only a partial match comes back?
Nothing bills. If the identity step returns only a hashed email without a LinkedIn URL, the row is dropped: no profile delivered, no charge. The same goes for errors and rate-limited responses.