> ## Documentation Index
> Fetch the complete documentation index at: https://docs.pagos.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Trigger Filters

<Warning>
  **Legacy Content**:

  The following content is only relevant for Legacy Canary users who subscribed to this Pagos product before December 2024.
</Warning>

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 [editing a trigger](/legacy-canary/triggers#managing-trigger-details), scroll to the bottom and click **+Add Filter**.
2\. Select a [filter option](#filter-options) 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](#filtering-triggers-by-more-than-one-parameter).

<Note>
  Depending on your configuration, you may see a text box instead of a list of parameters. In this case, enter the individual parameter values you want to filter your data by, hitting **enter** between each value. For a full list of the filter parameter values, refer to the [relevant filter](/legacy-peacock/legacy-peacock-data-filters#filter-options) in your Legacy Peacock account.
</Note>

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](/response-codes/avs-response-codes#avs-line-code)
* [AVS Post Code](/response-codes/avs-response-codes#avs-post-code)
* BIN
* Card Brand
* Card Type
* [Chargeback Status](/response-codes/chargebacks/chargeback-status-codes)
* [Chargeback Status Category](/response-codes/chargebacks/chargeback-status-category-codes)
* [Chargeback Reason](/response-codes/chargebacks/chargeback-reason-codes)
* [Chargeback Reason Category](/response-codes/chargebacks/chargeback-reason-category-codes)
* Currency
* Customer Country
* [CVV](/response-codes/cvv-check-response-codes)
* Data Source
* [Deduplication - Retries](/payments-basics/transaction-retry-deduplication)
* [Decline Code](/response-codes/transactions/transaction-response-codes) - Keep in mind, the decline code filter only functions for triggers with a selected [Metric](/legacy-canary/triggers#canary-metrics) 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](/response-codes/fees/fee-type-category-codes)
* [Fee Code](/response-codes/fees/fee-type-codes)
* [Fee Subcategory](/response-codes/fees/fee-type-subcategory-codes)
* [Issuing Bank](/payments-basics/issuing-banks)
* Issuing Country
* Merchant Account ID
* [Metadata](/payments-basics/labeling-transactions-with-soft-descriptors-and-metadata#metadata)  - Contact your Pagos Account Manager to turn on this filter option!
* Payment Method
* Soft Descriptor
* [Stored Credential](/payments-basics/the-stored-credential-field)

# 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](#filter-options), 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.

<Note>
  * A single trigger can monitor up to 100 data streams. If your applied filters create too many data streams, Canary will prompt you to simplify your trigger configuration.
  * With the **BIN**, **Currency**, **Issuing Bank**, **Soft Descriptor**, and **Issuing Country** filters, you can only select up to 12 parameters for a trigger.
</Note>

# 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](/payments-basics/the-stored-credential-field)
  * *Selected filter parameter*: recurring
* **Filter 2**: Card Brand
  * *Selected filter parameter*: Visa