How company identification works

You place one small snippet on your website, served first-party through your own domain. When someone opens a page, the snippet reports the basic facts of that pageview: the URL, the page title, the referrer and the timestamp. It also keeps a first-party functional identifier on your own domain so several pageviews of the same browser session can be stitched into one visit instead of appearing as unrelated hits.

That is the whole browser-side job. The snippet does not try to recognise the person behind the browser, and it does not build a profile that other sites could read. Everything that turns a visit into a company happens afterwards, on the server side, where lead.box can work with contracted data sources instead of guessing in the browser.

Each incoming visit arrives with the network address of the connection it came from. lead.box resolves that connection to the organisation behind it and checks the result against verified, GDPR-compliant B2B data sources. If the match is good enough, the visit gets a company: name, industry, size band and coarse location. If it is not, the visit stays without a company badge.

The lookup is transient. The address is used at the moment of resolution and is not persisted as a raw address afterwards; what your workspace stores against the visit is the resolved organisation plus coarse geographic metadata. That is a deliberate design decision, not a setting you have to switch on.

Identified companies appear in your live feed within seconds of the visit and are grouped into a company profile: which pages were viewed, how long the session lasted, how often the company came back, and which campaign or referrer brought them in. Repeat visits accumulate on the same profile, so a company that reads your pricing page three times in a week looks different from a one-off visitor.

From there the signal can leave lead.box: webhooks, Slack, Zapier, HubSpot or an export. Most teams use it to prioritise accounts they already know and to notice new ones early, rather than as a replacement for their CRM.

Identification ends at the legal entity. lead.box resolves organisations, not natural persons: no names, no email addresses, no person-level profiles attached to a session. When a connection cannot be attributed to a company — home broadband, mobile carriers, VPNs — the visit stays anonymous instead of being matched to a plausible-looking guess.

That is why identification rates land in a realistic range rather than at a hundred percent. For B2B sites, roughly 20% to 45% of sessions typically resolve to a company, with high-intent pages at the upper end.