Skip to main content
ShieldLabs runs in modern browsers through its JavaScript snippet or browser SDK. It supports desktop and mobile web, including Chrome, Edge, Firefox, Safari, Brave, Opera and Samsung Internet.

​
Supported browsers

The browser must be able to load the module and reach ShieldLabs endpoints. Available device and network evidence varies with the browser, operating system, privacy settings and extensions. Validate the browsers your customers use on your registered domain.

​
How persistence behaves per browser

  • User HID is the stable pseudonymous account value supplied by your application.
  • Device ID is derived on the server from device evidence.
  • Visitor ID is used to recognize a visitor based on a cookie and a device.
See Identifiers for the boundaries. Browser or device counts are not exact counts of people.

​
Safari

Browser storage restrictions can affect Visitor ID continuity. Test returning and signed-in activity under your actual Safari and mobile configurations.

​
Brave

Privacy settings and extensions can block connections or alter available attributes. Inspect the browser network log and keep signed-in activity associated with a stable User HID.

​
Incognito and private mode

Private browsing is supported. Device recognition uses server-side evidence; the private session has separate or temporary browser storage. Incognito is an informational detection with weight 0.

​
Keeping identification accuracy high

Test a normal visit, a returning visit, private browsing and signed-in activity. Verify server-side results, not just the browser’s Identification ID callback. Allow the required CSP connections and handle a missing or unavailable result explicitly.

​
Mobile and platforms

Use the same browser integration on mobile websites and in app WebViews that load your web pages. Test storage, navigation and network-check behavior in the target WebView; the host application can restrict browser capabilities. Next: Snippet installation, Accuracy, Troubleshooting.