This integration guide covers the general steps of integrating with Sift Science.
Send User Events
Account creation and changes:
If your users can create accounts, send:
Orders and payments:
If your users place orders or you handle payments, send:
If your users post content, send:
Interactions with other users and your app
Send the following events that apply:
Add custom fields to capture differences between users (think about the form fields users submit, as well data about the user's account and the item, service or content). The more data points you provide, the better we can differentiate between good and fraudulent users.
Send Feedback to Sift
One of the key strengths of the Sift Science platform is that as you give it feedback it continues to learn and adapt to patterns. By providing continuous feedback on who your good and bad users are, we will evolve our detection and improve the accuracy of risk scores. You’ll be able to stop bad actors even as they change their attack vectors. In addition to sending an optional historical backfill:
- Create a Feedback focused Workflow where you review high scoring users and tell us how well we are predicting your fraudsters.
- If you are already doing manual review in your existing system, just send the outcome of each review to our Labels API
Once you’re up and running with Sift, continuing to send feedback will improve your score accuracy in real-time, catching bad users as soon as they appear. This is an important part of a successful integration.
Make Decisions with Sift
Scores are an indication of how risky a user is for a given abuse type. You can use these scores as a means to block bad users, add friction to users you are unsure about (e.g., SMS verification), and let good users sail right through. You’ll want to make this check at the key events where fraudulent users can hurt your business.
The two ways to do this are:
- Create a Sift Workflow You can build application logic into Sift with our Workflow product. Workflows let you set up criteria that get evaluated whenever specified events occur. Learn more in our Workflows tutorial.
- Build application logic in your system An alternate approach is to request abuse specific risk scores to be returned in the response of the user events you send. See our API documentation
Any questions? We're happy to talk it through.