Skip to main content
Use device recognition to maintain a content allowance across storage resets.

​
Where to integrate

Identify before granting the protected content entitlement. Start with the SDK for your stack and retrieve the result on your backend.

​
What to read

Read the verified Device ID and your content-access ledger. 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

Grant an eligible free read or show the subscription offer. Deliver protected content from an authorized server route; hiding already-delivered content in the browser does not enforce an entitlement.

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