Skip to content
Browse documentation

KPI alerts

Get notified in-app or by e-mail when a metric such as CVR, profit or EPC crosses a threshold over a rolling window, for the whole scope or per offer, partner or advertiser.

Last updated 3 min read

On this page

A KPI alert runs a small report on a schedule — "CVR below 1 % over the last 24 hours, per affiliate" — and notifies you about every row that matches. Alerts use the same report engine and metric definitions as the report builder.

Create an alert#

  1. Open Reporting → Automation → KPI alerts (/app/automation/alerts).
  2. Click New alert.
  3. Name — e.g. "Offer CR below 1 %".
  4. Scope — leave Offers, Affiliates and Advertisers empty for everything ("All offers"…) or pick specific ones.
  5. Evaluate:
    • The whole scope (one total)
    • Each offer separately
    • Each affiliate separately
    • Each advertiser separately
  6. Conditions — match all or any of up to 10 conditions. Each is a metric, a comparison (greater than, at least, less than, at most) and a threshold.
  7. Look back (hours) — 1–720 (default 24): the rolling window ending at each check.
  8. Check every (hours) — 1–168 (default 1).
  9. Notify — In-app and/or E-mail; Team members (empty = "Everyone on the team (in-app)") and Other e-mail addresses (up to 25). E-mail alerts need at least one recipient.
  10. Click Preview current values to see the current value of every condition and which rows would match now.
  11. Click Save alert.

Units of thresholds#

Metric formatEnterExample
Percent (CTR, CVR, Margin)Percent1.5 = 1.5 %
Money (Revenue, Payout, Profit, EPC, RPC, CPC, Avg. sale, Sale amount)Amount in the workspace currency500
Counts (Clicks, Conversions…)A number1000

Every network metric can be used — see Dimensions and metrics. Custom metrics cannot.

How alerts are evaluated#

  • The worker ticks every minute; an alert is checked when its next check time has passed, then scheduled Check every hours later.
  • The window is [now − look back, now), rounded down to the minute.
  • With Each … separately, up to 500 rows (offers, affiliates or advertisers) are checked per run.
  • A metric without a value — a ratio with a zero denominator, such as CVR without clicks — never matches.
  • Each check that matches notifies once. An alert that keeps matching notifies at every check; set Check every accordingly.

What you receive#

  • In-app: a notification "Alert: <name>" for the chosen team members, or for all staff when none are chosen, with the conditions, the window and the first matches; it links to the alerts page.
  • E-mail: subject "Alert: <name> (<workspace>)", the conditions and the list of matches, with an Open alerts button.

Every trigger is recorded; the list shows Last triggered, and the overview counts triggers of the last 7 days.

Manage alerts#

The list shows Alert, Scope, Window ("last 24 h · every 1 h"), Channels, Last triggered and Status (Active, Paused, or an error badge with the message). Row menu: Edit, pause/resume and Delete. Changes are audited.

Example alerts#

GoalEvaluateConditionsWindow
Partner sends clicks that never convertEach affiliateClicks ≥ 1000 and Conversions < 124 h, every 6 h
Offer conversion rate droppedEach offerCVR < 1 and Unique clicks ≥ 50024 h, every 1 h
Negative marginWhole scopeProfit < 024 h, every 24 h
Bot traffic spikeEach affiliateBot clicks > 2001 h, every 1 h
Something unclear or missing in this article?Tell us