When you configure a trigger in Canary, you have the option of adding Filters. Filters tell Canary what specific segments of your transaction data to monitor.

​

Applying Filters to a Trigger

To apply filters to a trigger in Canary:

1. When creating a new trigger or editing an existing trigger, scroll to the bottom and click +Add Filter. 2. Select a filter option from the drop-down menu. 3. Click the checkbox beside the parameter(s) you want to filter your data by. Learn more about the implications of selecting more than one parameter in the section below.

4. Click Apply Filters. 5. To add additional filters to your trigger, click More Filters, then repeat the steps to select a filter option and the desired parameters. At this time, you can only apply up to three filters to a Canary trigger.

​

Filter Options

You can apply up to two of the following filter options to a Canary trigger:

• AVS Line Code
• AVS Post Code
• BIN
• Card Brand
• Card Type
• Chargeback Status
• Chargeback Status Category
• Chargeback Reason
• Chargeback Reason Category
• Currency
• Customer Country
• CVV
• Data Source
• Deduplication - Retries
• Decline Code - Keep in mind, the decline code filter only functions for triggers with a selected Metric that includes declined transaction data (e.g. Transaction Count, Transaction Count Velocity, Average Order Value, and Total Processed Volume). This filter is a required parameter when configuring a trigger built around the Share of Declined metric.
• Fee Category
• Fee Code
• Fee Subcategory
• Issuing Bank
• Issuing Country
• Merchant Account ID
• Metadata - Contact your Pagos Account Manager to turn on this filter option!
• Payment Method
• Soft Descriptor
• Stored Credential

​

Filtering Triggers by More Than One Parameter

When you apply a Filter to a trigger and select more than one parameter for the chosen filter option, Canary effectively creates a different trigger for each data stream associated with those parameters. For example, imagine you created a simple threshold trigger to alert you if your approval rate drops below 95% and you applied the Card Brand filter with both the Visa and Mastercard parameters selected; you’d then receive a separate alert when your Visa card approval rate dropped below 95% as you would when the same happens to your Mastercard approval rate.

For relative percentile threshold triggers, Canary calculates a different threshold range for each data stream. For example, if your company processes transactions in three currencies (e.g. USD, CAD, and EUR), and you configure a relative percentile threshold trigger for Transaction Count that’s filtered by Currency with all three parameters checked, Canary will establish a threshold range for USD, CAD, and EUR transactions separately. You’ll then receive an alert every time your USD transaction count drops below the expected range for transactions made in USD; the same is true for CAD and EUR transactions.

​

Trigger Filters Example

If you wanted to create a trigger that monitors authorization rates for only recurring transactions made with Visa cards, you could set the following parameters when configuring your new trigger:

• Metric: Authorization Rate
• Filter 1: Stored Credential
  • Selected filter parameter: recurring
• Filter 2: Card Brand
  • Selected filter parameter: Visa