Skip to main content
Connect traffic-source attribution with account and device evidence to investigate repeat or self-referred signups.

​
Where to integrate

Identify the referred signup and retain the partner ID with the verified Identification ID. Start with the SDK for your stack and retrieve the result on your backend.

​
What to read

Compare referrer and invitee devices, multi-account groups and the campaign’s risky activity. Join this with your own conversion records. 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

Hold suspicious rewards for review and release qualifying rewards atomically. Shared workplaces can reuse devices or networks. Confirm the relationship before excluding a legitimate referral.

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