Skip to main content

Optimization

Optimization in Rinku lets you monitor traffic quality at the zone level and take action — manually or automatically — when performance drops below your thresholds.

How it works​

Rinku continuously evaluates your traffic against rules you define. Each rule watches a rolling time window (e.g. the last 24 hours) and checks specific metrics — cost, ROI, CPA, bot rate, conversions, CR, profit — per zone. When a zone crosses your conditions and has enough clicks to be statistically meaningful, Rinku fires an alert.

From that alert you can:

  • Block the zone — remove it from your campaign's active traffic
  • Dismiss — acknowledge and move on
  • Unblock — reinstate a previously blocked zone if it recovers

For sources connected to a supported ad network via integration, blocking can happen automatically through the network's API. For all other sources, you block manually by copying the zone ID and adding it to the network's blacklist.

Key concepts​

Zone — the smallest traffic unit tracked by Rinku, identified by net_source (the zone/publisher ID passed by the network). Each zone is evaluated independently per campaign.

Rolling window — the lookback period a rule uses to calculate metrics. A 24h window means Rinku looks at clicks from the last 24 hours, not from the start of the campaign.

Minimum clicks threshold — a zone won't trigger an alert until it has at least this many clicks within the window. This prevents false positives from zones with too little data.

Alert mode — controls how alerts are grouped. Individual mode fires one notification per zone the moment it triggers. Grouped mode batches all triggered zones into a single digest notification on a set interval (15, 30, or 60 minutes).

What you need to get started​

  1. At least one traffic source with campaigns running and clicks coming in
  2. One or more optimization rules configured
  3. (Optional) A Telegram integration or email notifications configured for alerts

Sections​