Visitor identification
Know who’s on your site
Vector resolves anonymous traffic to the company and the person—name, role, work email, and the pages they read—while the visit is still warm.
Contact-level de-anonymization
The person on your pricing page, resolved to a name, a role, and a work email, not just a company.
Account-level de-anonymization
Every visiting company matched to your target list, with pages, people, and visits rolled up.
Take credit for SEO, AEO, and content
The pixel ties every identified visitor back to the content they read, the webinars they joined, the guides they downloaded, and the search, ad, or AI answer that brought them.
FAQ
Visitor identification, answered
A first-party script resolves the visiting company from network signals, then matches known contacts through consented data partners. You control what is stored.
Both. Every visit is matched to the company, and where a consented match exists, to the person—name, role, and work email—with the pages they read.
It depends on your audience and where they browse from. Company matches are the norm for B2B traffic; contact-level matches are a smaller, higher-intent slice.
Into the account view alongside every other signal, and out to HubSpot, Salesforce, Slack, and the rest of your stack through native integrations.
Yes. Identification respects your consent banner, and every record has a documented source and retention window.