Skip to main content
Use verified device and account associations to recognize repeated promotion use.

​
Where to integrate

Identify when an authenticated customer applies the promotion. Start with the SDK for your stack and retrieve the result on your backend.

​
What to read

Check first-order eligibility and prior claims in your order ledger; add group evidence for related accounts. 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

Reserve an eligible promotion and consume it with the completed order. Restore reservations consistently on cancellation. Keep retry handling separate from eligibility.

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