12. Generating an Alert

If a model works correctly, it will flag a fraudulent transaction and create an alert.

Alerts are generated when entities and/or transactions trigger the rule/model logic. Every agent in your team sees alerts based on the permissions and alert queues set by the system administrator.

An example:

  • Flag entity Laura Smith when she spends over $3000 in a 1 hr period
    • Alert on 06/18/21 for transaction "13299-gfdgf-34" sent to alert queue P0
  • Flag all instruments that are credit cards that spend over $3000 in a 1hr period
    • Alert on 11/22/20 for transaction "456545-gfaafe-23v-fd" sent to alert queue P0 and consumed by Agent Mark Smith

Our goal is to generate an alert for our model created back in step 9 and 10. Hopefully there is still time before the model is executed for the first time to introduce new transactions into the system.

Generate an Alert


  1. Log into your Dashboard.
  2. Navigate to the Data Explorer and go to the Upload File tab:
1200
  1. As per previous section, download the following JSON file and replace the event_time for both transactions with the current Unix timestamp:
[{
     "general_data": {
         "event_id": "baker-transaction-10",
         "event_type": "transaction",
         "event_subtype": "ach",
         "event_time": CURRENT EPOCH GOES HERE
     },
     "transaction_data": {
         "sent_amount": 13305.89,
         "sent_currency": "usd",
         "sender_entity_id": "Baker01",
         "sender_entity_type": "user",
         "sender_source": "internal",
         "sender_instrument_id": "cc-7291",
         "received_amount": 13305.89,
         "received_currency": "use",
         "receiver_entity_id": "371c4d7b-0563-aab1-4685",
         "receiver_entity_type": "user",
         "receiver_source": "internal",
         "receiver_instrument_id": "39405443-238938823-34347686",
         "amount": 13305.89
     }
 }, {
     "general_data": {
         "event_id": "baker-transaction-11",
         "event_type": "transaction",
         "event_subtype": "ach",
         "event_time": CURRENT EPOCH GOES HERE
     },
     "transaction_data": {
         "sent_amount": 28000.00,
         "sent_currency": "usd",
         "sender_entity_id": "371c4d7b-0563-aab1-4685",
         "sender_entity_type": "user",
         "sender_source": "internal",
         "sender_instrument_id": "39405443-238938823-34347686",
         "received_amount": 28000.00,
         "received_currency": "usd",
         "receiver_entity_id": "Baker01",
         "receiver_entity_type": "user",
         "receiver_source": "internal",
         "receiver_instrument_id": "cc-7291",
         "amount": 28000.00
     }
 }]
  1. Drag-n-drop it into the file uploader:
  2. Process the JSON file in the ... menu:
1200
  1. Head over to the Data Explorer to check for the new transactions:
1200
  1. Now let's go back to our model in the Detection Models page and select it from the *Live Models** tab:
1200
  1. Hopefully it has been an hour or so since the model was deployed live and it has finally executed. If not, wait patiently until the model has executed. If the timing worked out, the transaction from step 1 should have been flagged:
1200
  1. Take a look at the Triggered Alerts tab to view the generated alerts:
1200
  1. Click on the generated alert in the table to go to the alert detail page:
1200
  1. You can view the transactions that triggered this alert on the Transaction activity tab of the alert:
1200

As expected, Mr Baker's new transactions 10 and 11 were flagged.

Typically, as an agent, you would consume alerts from your Alert page. It is possible for you to receive this new alert generated using the Get More Alerts button:

1200 1200

Additionally, if you have Admin level visibility, you can check the Admin tab of the Alert page were you could also see this alert:

1200

Congratulations, your model has generated an alert! It is time to investigate it.