Layer 1 copy

Use-case

This guide helps on-demand businesses stop chargebacks, referral abuse, and other types of fraud.

Sending Data to Sift Science

Send User Activity
Send Key User Events
User creates an account
  • If users can create accounts, send a $create_account event with custom fields to capture differences between users, such as:
    • 'num_reviews' : 0
    • 'successful_ride_count' : 0
    • 'user_type' : 'partner'
    • 'orders_canceled' : 0
    • 'num_referrals_redeemed' : 0
  • If a user updates their account information outside of the checkout flow, send an $update_account event.
  • If users can checkout anonymously, follow our tutorial.
User places an order
  • When a user places an order, send a $create_order event. Fill in as many $items fields as you can and include custom fields such as:
    • 'num_reviews' : 4
    • 'successful_ride_count' : 9
    • 'delivery_method' : 'pickup'
    • 'order_message' : 'leave on the doorstep'
    • 'promo_code' : 'SpringPromo'
    • 'amount_after_credit' : 12.43 (how much the user spent after promos and credits, if different order $amount)
    • 'minutes_until_service' : 60
    • 'pickup_lat' : 35.360555
    • 'pickup_lng' : 138.727778
  • If a user can update an order (e.g. change the shipping address), send an $update_order event.
    • Custom field ideas:
    • 'address_changed' : True
When you interact with a payment gateway
  • Send a $transaction event for each payment gateway interaction, as well as each other payment method accepted for the order (e.g. gift card).
  • When a payment gateway informs you of a chargeback, send a $chargeback eventand a fraud label.
Referral Fraud

If you offer a referral promotion, do the following. When user B signs up using user A's referral:

  • Send '$referrer_user_id' : 'A' in the code '$create_account' event for user B.
  • Send a referral_redeemed custom event for user A with the following fields:
    • '$type' : 'referral_redeemed'
    • '$api_key' : 'your_rest_api_key'
    • '$user_id' : 'A'
    • 'referred_user' : 'B'
    • 'num_referrals_redeemed' : 3 (value including this redemption)

You'll also want to take advantage of our promotion object that can be sent with $create_account, $create_order, and $add_promotion.

Additonal events

The following events can be sent to capture a more complete picture of users when applicable: $submit_review, $send_message, $login, $order_status.

Set up your Business Decisions

In order to send Decision events you'll first have to create the specific Decisions your business takes in the Sift Science Console. While we start all accounts out with a few generic Decisions, Decisions are fully customizable so you can create a Decision for every action that your business takes. Some examples of Decisions are:

  • Ban Account (Block Category Decision)
  • Cancel Order (Block Category Decision)
  • Flag for Additional Review (Watch Category Decision)
  • Approve User (Accept Category Decision)

See the Decisions Intro for more context.

During your integration, you should send the Decisions that your business is currently making through any internal fraud engines or Manual Review processes to the Sift Decisions API. If you currently do not have in-house fraud logic or a manual review process, work with Sift to setup your initial Workflows within Sift's platform.

Get Started with Sift Scores

When you are initially integrating with Sift, your scores will be based on whatever data you’ve sent us. So if it is a brand new integration with no backfilled data, Sift will need a week or two of data to learn your unique fraud patterns. One of the key strengths of the Sift platform is that it consistently learns as you send more and more data to it. You should see a substantial increase in accuracy of your scores during these first weeks as you send more Decisions and User Events.

During this stage, you should be assessing your Sift Scores in the Sift Science Console and determining which actions you want to take for different score ranges. Since all businesses are different, finding your unique score thresholds that achieve your business goals is key.

To reduce the amount of time required in this initial learning phase, you can send a historical backfill so that Sift can learn about your user's fraud patterns.

Build Your Business Logic With Sift Scores

Now that you sending both user events and business decisions to Sift, you’re ready to start using Sift Scores in your business logic. At this point, you’ll have an understanding how scores correlate to different levels of risk. Based on the user’s risk score, you’ll set up different outcomes within your application (eg users with low score are automatically approved).

To build this logic, you'll want to evaluate a user's Sift Score at the key events where bad users can hurt your business or good users can have a more frictionless experience. typically $create_order for payment_abuse and $create_account if facing promo_abuse.

The two ways to use Sift Scores:

  • Create a Sift Workflow: Sift Workflows give you a powerful way to automate your Decisions without having to write business logic on your side. Workflows let you set up rules that gets evaluated whenever specified events occur. These rules enable you to route users to different outcomes based on Sift Score and other attributes of the user and transaction (eg User is from Canada, Order is greater than $500, and Sift Score is greater than 80). With Sift Workflows, you also get Sift Review Queues for fast, easy investigation so you won’t have to build your own queues. To learn more, see our Workflows documentation.
  • Build application logic in your system: You can synchronously request the Sift score of a user with any event you send to Sift. This score will take into consideration all data you’ve sent to Sift including the event you just sent. Sift Scores should only be requested at the key events where fraud or abuse occurs (eg ask for score when sending a Create Order event) To learn more, see our API documentation

Any questions? We're happy to talk it through.