Visitor Identification
Resolve the company behind an anonymous visit, within a consent and region policy you control.
Most people who visit your site never fill in a form. Visitor identification resolves the company behind those anonymous sessions from the network the visit came from, so an unattributed visit becomes an account you can recognise.
Logspot resolves companies, not people. There is no person-level identification of anonymous visitors.
Rolling out. Visitor identification is being enabled account by account. Contact us to turn it on for your organization.
What You Get
A resolved visit stamps the company onto the session, which means anonymous traffic starts appearing in Companies, feeds Signals, and counts toward the company view of your funnels and reports.
Resolution is not universal. Visitors on residential connections, mobile networks, and VPNs usually cannot be resolved to a company, because the network genuinely does not belong to one. Expect a meaningful share of traffic to stay anonymous. Any vendor promising otherwise is describing something other than what the data supports.
Consent and Regions
This is the part worth understanding before you turn it on, because it is where this feature differs most from comparable products.
A visitor who has given explicit analytics consent is resolved wherever they are. A real consent record is the strongest basis available, so no further geographic test is applied.
Without explicit consent, your organization's region policy decides by the visitor's location. Some regions resolve, and others are skipped entirely.
The default policy is US only: visitors in the United States resolve, and everywhere else requires consent first. Other presets tighten or widen that, and a custom policy lets you set rules region by region.
Two design details worth knowing. The consent and region check runs before any cached result is consulted, so tightening your policy takes effect immediately rather than after a cache expires, and a non-consenting visitor is never resolved just because someone on the same network was resolved earlier. And separately from all of this, whether you may use a resolved company for outbound purposes is decided at the point you act on it, not at the point it is resolved.
What It Costs
Each resolution attempt is metered. Both meters are checked before the lookup runs, so a shortfall skips the lookup rather than running it and billing you later. Topping up takes effect on the next event.
Results are cached for a period, including misses, so repeat visits from the same network do not each cost a lookup.
See Data Credits.