Optimisation rules

Optimisation rules automate what a media buyer does by hand: look at each source after enough clicks, and cut the ones that do not convert. Every hour the worker evaluates each active rule per offer and per value of the variable you choose (a partner, a sub ID value or a source ID), and applies the rule's action to the values that miss your thresholds.

Create a rule#

1. Open Reporting → Automation → Optimisation (/app/automation/optimisation).

2. Click New rule and fill in:

   Field	Notes
   Name	Required.
   Offers	The offers the rule watches; empty = all offers.
   Judge each	Affiliate, Sub 1 … Sub 5 or Source ID. Sub and source values are judged per partner (sub1 abc of partner A is separate from abc of partner B).
   Minimum clicks	A value is only judged with at least this many clicks in the window (default 100).
   KPI	Conversion rate (%), Conversions or EPC (revenue ÷ clicks).
   Below / Above	At least one threshold. The rule matches when the KPI is below Below or above Above.
   Look back (hours)	1–720 (default 24).
   Conversion delay (hours)	0–720. "Skip the most recent hours so late conversions can arrive."
   Then	Notify the team, Block the source or Pause the offer.

3. Save. Rules start active; the list shows Rule (with a plain-language summary such as "Sub 1 with ≥ 100 clicks and cr < 0.5% over 24 h (ending 2 h ago)"), Action, Offers, Last run and Status.

How a rule is evaluated#

• Window: [now − delay − look back, now − delay).
• Clicks: all clicks of the offer and value in the window (compliance probes excluded); CR uses unique clicks.
• Conversions: approved conversions whose click happened in the window (conversions without a click count by conversion time).
• KPIs: CR = approved conversions ÷ unique clicks; Conversions = approved conversions; EPC = approved revenue ÷ clicks.
• Values with fewer clicks than Minimum clicks are skipped.
• Values on the Exclusions list are never acted on.

Actions#

Blocks and pauses are applied once (an existing block or pause is not repeated), each change is written to the audit log under the rule creator's name, and staff get a notification such as "Optimisation rule "<name>": block applied to N source(s)". Every run is logged with how many values were evaluated and matched.

To undo a block, set the partner's access back on the offer's Affiliates tab, or delete or edit the traffic control under Offers → Traffic controls. To undo a pause, activate the offer.

Exclusions#

Under Exclusions add values rules must never act on — "your own test sources, a strategic partner…": choose the variable (Affiliate — enter the affiliate ID — or a sub/source field), enter the Value and add it. Exclusions apply to every rule that judges that variable. Remove one with its ×.

Examples#

Start with Notify the team for a few days and check the matches before switching a rule to blocking.

Permissions#

Creating, editing and deleting rules and exclusions needs a manager role or higher; analysts can view.

Related#

• Fraud and fail traffic reports
• KPI alerts