Optimization Rules
Rules define what Rinku monitors, under what conditions it fires an alert, and how that alert is delivered. Go to Optimizations → Rules to create and manage them.
Fields
Name
A label for the rule. Used to identify it in the rules list and in alert notifications.
Application scope
Determines which campaigns the rule applies to.
| Option | Behavior |
|---|---|
| All campaigns | The rule evaluates zones across every campaign in your account |
| Specific campaigns | The rule applies only to the campaigns you select |
| Specific traffic source | The rule applies to all campaigns using the selected traffic source |
Rolling window
The time period Rinku uses to calculate metrics. Options: 1h, 6h, 24h, 3d, 7d, 14d, 30d.
A shorter window (1h, 6h) catches problems faster but is more sensitive to short-term fluctuations. A longer window (7d, 14d) gives a more stable picture but reacts more slowly.
Minimum clicks threshold
A zone won't trigger an alert until it has at least this many clicks within the rolling window. Set this high enough that you're only acting on zones with meaningful traffic volume. The default is 100.
Trigger conditions
One or more metric conditions that must all be true for a zone to trigger. Each condition has three parts:
- Metric — the value to evaluate
- Operator — the comparison (
>,>=,<,<=,=) - Value — the threshold number
Available metrics:
| Metric | Format | Description |
|---|---|---|
| Conversions | integer | Total conversions in the window |
| Cost | currency ($) | Total spend in the window |
| CPA | currency ($) | Cost per acquisition |
| Bot Rate | percent (%) | Share of bot clicks |
| Profit | currency ($) | Revenue minus cost |
| ROI | percent (%) | Return on investment |
| CR | percent (%) | Conversion rate |
You can add multiple conditions — all must be met simultaneously for the alert to fire. Use this to avoid false positives (e.g. "bot rate > 30% AND cost > $5").
Alert mode
Controls how alert notifications are delivered.
Individual (immediately) — a separate notification is sent as soon as each zone triggers. Use this when you want to react to every zone the moment it crosses the threshold.
Grouped (every N minutes) — all zones that trigger within the interval are bundled into a single notification. Available intervals: 15, 30, or 60 minutes. Use this for high-traffic accounts where many zones can trigger at once and you prefer a digest.
Notification channels
Where Rinku sends the alert:
- In-app — always active, visible in the Alerts section
- Telegram — sends a message to a connected Telegram chat (see Telegram Setup)
- Email — sends an email notification
You can enable multiple channels simultaneously.
Telegram channel
Visible only when Telegram is selected as a notification channel. Choose a connected Telegram chat from the dropdown. If the list is empty, connect a chat first in Integrations → Telegram.
Enabling and disabling rules
Each rule has an active toggle in the rules list. Inactive rules are not evaluated — no alerts fire, no zone statuses update. Toggle a rule off to pause it without deleting it.
Rule description
The rules list shows a compact summary of each rule, for example:
For [all campaigns], monitor zones over the last 24h, starting from 100 clicks. If [ROI < -20] → Alert to [Telegram, in-app], send immediately.
Example configurations
Catch high-cost low-converting zones:
- Scope: All campaigns
- Window: 24h
- Min clicks: 200
- Conditions: Cost > $10 AND Conversions < 1
- Mode: Individual
Bot traffic alert:
- Scope: Specific traffic source
- Window: 6h
- Min clicks: 100
- Conditions: Bot Rate > 30
- Mode: Grouped, every 30 minutes
ROI drop warning:
- Scope: All campaigns
- Window: 7d
- Min clicks: 500
- Conditions: ROI < -15
- Mode: Individual