Skip to main content
Use device identification and Multi-accounting detection to stop repeated claims of the same trial benefit.

​
Where to integrate

Identify the signup before creating a trial entitlement. Start with the SDK for your stack and retrieve the result on your backend.

​
What to read

Read the verified Device ID and check your trial ledger; review account-group evidence when available. 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

Create one qualifying entitlement or send a repeat claim to review. Trial eligibility belongs to the application ledger. Clear cookies and a new username should not erase a recorded claim.

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