Skip to main content
Use Account sharing events and device history to identify one subscription used across multiple devices.

​
Where to integrate

Check the authenticated account before issuing or refreshing a session. Start with the SDK for your stack and retrieve the result on your backend.

​
What to read

Review the event confidence, device observations and legitimate device changes. Keep your session policy separate from the detector device count. 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

Offer account-holder verification, end an older session with consent, or show the appropriate plan. Families, replacement devices and normal phone-plus-laptop use need an explicit allowed path.

​
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.