WysLeap
Guide · Visitor identification

How do you identify anonymous website visitors without cookies, and what's legal under GDPR?

It depends on what you mean by identify. Recognizing the same anonymous visitor when they come back is possible without cookies: WysLeap keeps a random ID in the browser's local storage and, when that storage is cleared, can link the browser back to its earlier ID on the same site and network. Naming the person or company behind a visit needs a login, a form or a company-identification tool, and in the EU, UK and Switzerland any of these needs a legal basis, usually consent. WysLeap never collects names or emails unless your site sends them when someone logs in.

Updated

“Identify” means three different things

  1. Recognize a returning visitor: know that the person on your pricing page today is the one who read your guide last week, without knowing who they are.
  2. Identify a logged-in person: once someone logs in or signs up, connect their visits, on every device, to your own record of them.
  3. Look up a company or person: match an anonymous visit to a business (from its IP address) or a person (from identity data), usually for outbound sales.

Most teams asking this question need the first one, sometimes the second. The third is a separate category of tool with its own costs and privacy questions.

Recognizing visitors without cookies

Cookies used to be how analytics recognized a returning browser. WysLeap uses a random visitor ID stored in the browser's localStorage instead. It works per browser: a different device, or private browsing, starts a new ID.

When a browser's storage is cleared, WysLeap's device recognition can link the new ID back to the earlier one. It only does this within one site, on the same network and with the same or a newer browser version, and the link can be undone. It never runs on Safari or iOS browsers, or under Global Privacy Control or Do Not Track. It doesn't reveal names or emails. See recognizing returning visitors for the details.

Identifying logged-in people

When someone logs in, you already know who they are. With WysLeap's Known People feature, your site calls WysLeap.identify(userId) and their visits on every device count as one person. The ID (and an optional email) is hashed in the browser before it's sent, and it's off until you switch it on and update your consent wording.

Company and person lookup tools

Tools such as Leadfeeder, Snitcher and RB2B match visits to companies from IP addresses, or to people from identity data, so sales teams can reach out. WysLeap doesn't do this. If outbound sales is your main goal, one of those tools is the right fit, and you'll want a privacy review first.

What GDPR and ePrivacy mean in practice

  • No cookies isn't the same as no consent. EU and UK ePrivacy rules cover storing anything on a visitor's device, local storage included.
  • Recognizing a visitor is still personal data under GDPR, even without a name.
  • Naming people raises the bar: you need a clear legal basis and must tell visitors what you do.

WysLeap is built for this: in the EU/EEA, UK and Switzerland it stores and sends nothing until your consent banner calls setConsent(true), and sites that qualify for an audience-measurement exemption can use exempt measurement. This isn't legal advice; check with your privacy advisor.

What to do once you recognize visitors

Recognition matters because of what it lets you see: which returning visitors are close to buying. WysLeap gives every visitor an intent score; read how to find high-intent visitors without identifying companies. Pro is $30 a month after a 90-day free trial, and the anonymous visitor identification guide on our blog goes deeper on the methods.

Side by side

Three levels of visitor identification

What each approach knows, what it collects and what it takes.

FeatureRecognize returning visitorsIdentify logged-in peopleCompany or person lookup
Knows it's the same visitor as last time
Knows the visitor's name or company
Your own user ID
Works for every visitor
Per browser
Only logged-in
Only matchable visits
Works without cookies
Varies
In WysLeap

Company or person lookup: tools such as Leadfeeder, Snitcher and RB2B, which match visits from IP and identity data. In the EU/EEA, UK and Switzerland, all three usually need consent; check with your privacy advisor.

FAQ

Frequently asked questions

Can I identify website visitors without cookies?
You can recognize returning visitors without cookies, with an ID in the browser's local storage, which is what WysLeap does. Knowing who a visitor is takes something they give you, such as a login or a form, or a tool that matches visits to companies or people from IP and identity data.
Is anonymous visitor identification legal under GDPR?
Recognizing a visitor across visits still processes personal data, and EU and UK ePrivacy rules cover storing anything on the visitor's device, not only cookies. For most sites that means consent in the EU/EEA, UK and Switzerland. Matching visits to named people is a bigger step that needs a clear legal basis and transparency. This isn't legal advice; check with your privacy advisor.
Does WysLeap tell me which company visited my site?
No. WysLeap doesn't look up companies or people from IP addresses. It recognizes returning anonymous visitors, gives each one an intent score, and links visits to a person only when your site tells it who they are at login.
How does WysLeap handle consent?
In the EU/EEA, UK and Switzerland, WysLeap stores and sends nothing until your site records consent with setConsent(true). Device recognition never runs on Safari or iOS browsers, or under Global Privacy Control or Do Not Track. Sites that qualify for an audience-measurement exemption can count page views without consent, without device recognition or replay.

Recognize returning visitors, no cookies.

Returning visitors, intent scores and journeys, consent-first. 90-day free trial.