Trigger Evaluation Time
Legacy Content:
The following content is only relevant for Legacy Canary users who subscribed to this Pagos product before December 2024.
When configuring a trigger in Canary, you’ll select an Evaluation Time, or the specific time when you want Canary to review your data for an anomaly. How this field works depends on what value you selected for the trigger’s Aggregation Period.
Hourly Trigger Timing
When you configure a trigger with a Hour aggregation period, you’ll select the hour(s) each day (in the time zone specified in your account settings) when you want Canary to review your data for events. Given the hour you pick, Canary will actually review data from the previous hour and alert you of any unexpected changes. This ensures Canary has enough time to receive and analyze the payments data from all of your processors.
For example, let’s configure a trigger with the following settings:
- Metric - Approval Rate
- Aggregation Period - Hour
- Evaluation Time - 8:00am
Every day at 8:00am, Canary will review your approval rate data for transactions processed between 6:00am and 7:00am. If any anomalies exist outside of your chosen threshold, Canary will alert you via the configured alert settings.
Note: If you import payments data into Pagos from Dlocal, Chase, Vantiv, Paypal, Fiserv, or Klarna, we receive your payments data via SFTP once a day. As such, you can’t configure triggers with an hourly aggregation period.
Daily Trigger Timing
The same concept of giving Canary the time necessary to ingest and analyze your data also impacts triggers with a Day aggregation period. The Evaluation Time is the hour(s) each day when you want Canary to check for events; at that time, Canary will review your payments data from the last 24 hours, starting an hour back from the chosen time.
For example, let’s configure a trigger with the following settings:
- Metric - Chargeback Rate
- Aggregation Period - Daily
- Evaluation Time - 10:00am
Every day at 10:00am, Canary will review your payments data for chargebacks pertaining to the hours between 9:00am the previous day and 8:59am today. If any anomalies exist outside of your chosen threshold, Canary will alert you via the configured alert settings.
Daily Triggers for File-Based Processors
If you import payments data to Pagos via SFTP, Canary automatically sets the daily evaluation time for you based on when we ingest your data:
- Klarna - 7am UTC
- Paypal - 9am UTC
- Dlocal - 12pm UTC
- Chase - 2pm UTC
- Vantiv - 4pm UTC
- Fiserv - 8pm UTC
Keep in Mind: You can configure a trigger to monitor data ingested from multiple processors. The processors you select will determine the evaluation time:
- If your trigger monitors two file-based processors, the daily evaluation time will be that of the processor with the latest ingestion time. For example, if your trigger monitors Klarna and Chase data, the evaluation time will be 2pm UTC.
- If your trigger monitors a file-based processor and a processor with real-time data ingestion, the evaluation time will default to the file-based processor’s ingestion time. For example, if your trigger monitors Klarna and Braintree data, the evaluation time will be 7am UTC.
Weekly Trigger Timing
For weekly triggers, you can choose which day(s) of the week you want Canary to review the metric and search for events. On that day at 12pm UTC, Canary reviews your data from the previous week.
Monthly Trigger Timing
For monthly triggers, you can choose which day(s) of the month you want Canary to review the metric and search for events. On that day at 12pm UTC, Canary reviews your data from the previous month.
Trigger Evaluation Time
Legacy Content:
The following content is only relevant for Legacy Canary users who subscribed to this Pagos product before December 2024.
When configuring a trigger in Canary, you’ll select an Evaluation Time, or the specific time when you want Canary to review your data for an anomaly. How this field works depends on what value you selected for the trigger’s Aggregation Period.
Hourly Trigger Timing
When you configure a trigger with a Hour aggregation period, you’ll select the hour(s) each day (in the time zone specified in your account settings) when you want Canary to review your data for events. Given the hour you pick, Canary will actually review data from the previous hour and alert you of any unexpected changes. This ensures Canary has enough time to receive and analyze the payments data from all of your processors.
For example, let’s configure a trigger with the following settings:
- Metric - Approval Rate
- Aggregation Period - Hour
- Evaluation Time - 8:00am
Every day at 8:00am, Canary will review your approval rate data for transactions processed between 6:00am and 7:00am. If any anomalies exist outside of your chosen threshold, Canary will alert you via the configured alert settings.
Note: If you import payments data into Pagos from Dlocal, Chase, Vantiv, Paypal, Fiserv, or Klarna, we receive your payments data via SFTP once a day. As such, you can’t configure triggers with an hourly aggregation period.
Daily Trigger Timing
The same concept of giving Canary the time necessary to ingest and analyze your data also impacts triggers with a Day aggregation period. The Evaluation Time is the hour(s) each day when you want Canary to check for events; at that time, Canary will review your payments data from the last 24 hours, starting an hour back from the chosen time.
For example, let’s configure a trigger with the following settings:
- Metric - Chargeback Rate
- Aggregation Period - Daily
- Evaluation Time - 10:00am
Every day at 10:00am, Canary will review your payments data for chargebacks pertaining to the hours between 9:00am the previous day and 8:59am today. If any anomalies exist outside of your chosen threshold, Canary will alert you via the configured alert settings.
Daily Triggers for File-Based Processors
If you import payments data to Pagos via SFTP, Canary automatically sets the daily evaluation time for you based on when we ingest your data:
- Klarna - 7am UTC
- Paypal - 9am UTC
- Dlocal - 12pm UTC
- Chase - 2pm UTC
- Vantiv - 4pm UTC
- Fiserv - 8pm UTC
Keep in Mind: You can configure a trigger to monitor data ingested from multiple processors. The processors you select will determine the evaluation time:
- If your trigger monitors two file-based processors, the daily evaluation time will be that of the processor with the latest ingestion time. For example, if your trigger monitors Klarna and Chase data, the evaluation time will be 2pm UTC.
- If your trigger monitors a file-based processor and a processor with real-time data ingestion, the evaluation time will default to the file-based processor’s ingestion time. For example, if your trigger monitors Klarna and Braintree data, the evaluation time will be 7am UTC.
Weekly Trigger Timing
For weekly triggers, you can choose which day(s) of the week you want Canary to review the metric and search for events. On that day at 12pm UTC, Canary reviews your data from the previous week.
Monthly Trigger Timing
For monthly triggers, you can choose which day(s) of the month you want Canary to review the metric and search for events. On that day at 12pm UTC, Canary reviews your data from the previous month.