Overview
Sometimes you might see a contact in your Visitor Feed who didn’t actually visit your site — and that’s not a bug, it’s the magic of Vector’s identity infrastructure.
Here’s how it works, why it’s possible, and how we’re constantly enhancing enrichment so you get more visibility into who’s showing intent across your digital presence.
How It Works: Device Fingerprinting
When someone lands on your website, Vector captures a device fingerprint — a unique signature based on things like browser type, operating system, screen resolution, and other metadata.
We then check that fingerprint against our identity graph. If we find a match, Vector will enrich the contact and surface them in your Visitor Feed, even if the session itself isn’t directly tied to a known email address.
This is how we’re able to recognize someone without requiring them to fill out a form or be cookied beforehand (and why you'll still get some anonymous visitors to your site!).
Even Smarter with Pixel Enhancements
With recent updates, Vector’s pixel has become even more powerful — thanks to two major features:
1️⃣ Vector Identify Support
You can now pass known contact data directly to the Vector pixel using the window.vector.identify method. This increases match rates and makes enrichment more accurate.
2️⃣ Form Fill Listening (New!)
Vector’s pixel now automatically listens for form submissions on your site — including dynamic forms like HubSpot or Marketo.
How it works:
When the pixel loads, it attaches event listeners to all detected forms.
When a user submits a form, Vector checks for email, first name, and last name.
If available, we immediately run our identify flow to enrich the contact in real-time.
What you need to do:
Nothing! This feature is on by default and already working for all Vector customers.
Why we built it:
To improve enrichment and help our customers identify more visitors without needing any extra setup.
TL;DR: Why You Might See Unexpected Contacts
Someone else using the same device previously visited your site
A match was made through our identity graph via fingerprint
A form was submitted on your site and we enriched that contact
A contact was identified via
dot.identifyfrom your backend or form flow
Still have questions? Boo 👻 us at [email protected] — we’re happy to explain how your ghosts (aka visitors) are being uncovered.