Alerts
When an optimization rule triggers, Rinku creates an alert notification. Go to Optimizations → Alerts to see all notifications, review the data that caused them, and take action.
Alert list
The alerts list shows notifications in reverse chronological order. Each entry displays:
- The rule that triggered it
- When it was triggered
- The traffic source involved
- How many zones are affected
- The current status
You can filter alerts by campaign or traffic source using the filters panel.
Alert statuses
| Status | Meaning |
|---|---|
| Triggered | The zone crossed the rule's conditions — action pending |
| Blocked | The zone has been blocked (manually or automatically) |
| Dismissed | The alert was acknowledged without blocking |
For grouped alerts (multiple zones in one notification), the overall status reflects the worst active state: if any zone is still triggered, the alert shows as triggered even if others are blocked.
Alert card
Clicking an alert opens its detail card, which shows:
- Rule — which rule fired and a summary of its conditions
- Triggered at — the exact time
- Reason — the metric(s) that crossed the threshold (e.g. "ROI < -20")
- Zones table — each affected zone with its metric values at the time of triggering
The zones table includes the metrics configured on the rule (cost, ROI, CPA, etc.) as recorded at the moment the alert fired. Use this to understand exactly why the zone triggered.
Actions
Block
Marks the zone as blocked and, for integrated sources with a connected account, calls the network's API to remove it from the campaign's active traffic.
For integrated sources: click Block in the modal — Rinku calls the API and updates the status automatically.
For custom sources or sources without a connected account: the modal shows the zone ID and step-by-step instructions for adding it to the network's blacklist manually. After completing the steps in the network, click I blocked manually to update the status in Rinku.
In grouped alerts, you can block zones selectively or use Block All to act on all triggered zones at once.
Dismiss
Marks the alert as dismissed without blocking the zones. Use this when you've reviewed the data and decided no action is needed (e.g. a temporary spike that already resolved).
Unblock
Available on blocked zones. Reverses the block — for integrated sources via API, for others manually. After unblocking, Rinku re-evaluates the zone against current data. If conditions are still met, the zone will re-trigger.
Automatic blocking
If a campaign has auto-optimization enabled and the source has a connected integration account, Rinku can block zones automatically without any manual step. When this happens, the alert appears with an "Automatically blocked" status. No action is required — the notification is informational.
If automatic blocking fails (e.g. due to an API error), the alert shows "Automatic blocking failed" and the zone remains triggered so you can act manually.
Conversions since block
In the alerts table, a Conversions since block column shows how many conversions came through after the zone was blocked. A non-zero value may indicate the block didn't take full effect on the network side.