WysLeap gives each browser a random, anonymous ID kept in localStorage, so return visits join up into one journey. No cookies, no names or emails, no cross-site profiles. We're also upfront about where it stops working.
Anonymous visitor
a8f3b2c1-d4e5-…
Random ID written to localStorage
Same browser, same stored ID
Journey joined up: 3 sessions
Private window, so no stored ID
Illustrative example, not a real visitor.
The problem
People research, leave and come back. If your analytics can't connect those visits, you see fragments instead of a path.
How it works
No signals about the device are combined to work out who someone is. The ID is simply created, stored and read back.
The tracker generates a random anonymous ID and stores it in the browser's localStorage. It contains nothing about the visitor or their device.
On later visits the tracker reads the same ID and attaches it to page views, so separate sessions join up into one visitor journey.
The ID lives in a single browser. A laptop and a phone appear as two visitors. There is no cross-device or login stitching.
{ "visitor_id": "a8f3b2c1-d4e5-…", "first_seen": "Mon 09:12", "last_seen": "Fri 10:05", "total_visits": 3, "browser": "Chrome", "country": "United States", "language": "en-US" }
Recognized by stored ID
Same anonymous ID found in this browser
Illustrative example profile.
Honest limits
Recognition depends on one thing: whether the browser still holds the same ID. These limits come from how browsers store data, and we don't try to work around them.
Laptop and phone are always separate visitors. WysLeap doesn't link visitors to accounts.
People sharing one browser profile, such as family computers or kiosks, appear as one visitor.
Mobile web browsers are supported. There are no native iOS or Android SDKs.
How much these affect your numbers depends on your audience's browsers, devices and how often they return. A visitor who can't be recognized is simply counted as new.
Privacy and compliance
One random ID, no personal data. Device fingerprinting is not used to identify anyone.
Collected
Measurement only
A canvas hash and WebGL renderer are checked for bot detection, then discarded. In a device-recognition measurement mode we are testing, device signals are hashed on the device; for EU/UK visitors this only runs with consent. None of it is used to identify visitors.
Never collected
WysLeap.setConsent(false) stops all tracking in that browser and removes the stored ID.Example scenario
B2B buyers and considered purchases rarely convert on the first visit. With a multi-session ID, the blog post someone read on day 3 is connected to the signup on day 5, so you know which content actually moves people forward.
One visitor · 3 sessions
ExampleWithout a multi-session ID, the day-3 blog visit looks unrelated to this signup.
Illustrative example, not measured results.
Compared
Same-browser recognition like a first-party cookie, without setting one. It's also steadier than guessing from IP addresses.
| Feature | WysLeap ID | Cookies | IP-based |
|---|---|---|---|
| Recognizes returning visitors | Same browser | Same browser | Unreliable |
| Sets cookies | |||
| Unaffected by cookie deletion Clearing all site data still resets the WysLeap ID. | |||
| Recognized in private browsing | Same IP only | ||
| Cross-device or cross-browser | |||
| Shared networks inflate or merge counts | |||
| EU consent may be required | Depends* | Usually | Depends* |
* GDPR and ePrivacy interpretation varies by jurisdiction, and localStorage can fall under the same rules as cookies. Consult legal counsel for your situation.
Already on Google Analytics? Some teams keep GA4 for its Google integrations and add WysLeap for cookie-free journey analytics side by side.
FAQ
Still have questions? Contact support
Recognize returning visitors in the same browser and follow multi-session paths to conversion.