Skip to main content
Use Account takeover and Impossible travel detections alongside the current login identification.

Where to integrate

Identify after credential validation and before granting a sensitive session or account change. Start with the SDK for your stack and retrieve the result on your backend.

What to read

Compare the triggering check with prior account observations. Exclude the current Identification ID from a known-device lookup. 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

Require a second factor or recovery verification before enabling the sensitive action. A new device or VPN alone needs account context; preserve a recovery route for the legitimate holder.

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.