Skip to main content
Use device identification to connect returning activity even after browser storage changes.

​
Where to integrate

Identify on the page where personalization is needed. Start with the SDK for your stack and retrieve the result on your backend.

​
What to read

Look up the verified Device ID in your own experience records and read the current risk context. Use the current Risk Score and flags, plus High-Risk Events where relevant. Treat a missing or incomplete result as an explicit unverified state.

​
How to act

Restore non-sensitive preferences or a familiar experience after the backend verifies the result. Use authenticated sessions for access to private account data. Device recognition supports the experience; account authentication protects it.

​
Build the example

The runnable tutorial includes the starting app, the completed integration, and steps to test its behavior. Its application policy is stated separately from ShieldLabs detection. For implementation details, see Acting on results and Identification flow. Verify the expected domain, result age and account association, and consume protected actions atomically.