Skip to content
Knobase

Optimization

Relevance and trust before fill. No-fill is success. Fail open.

  • Optimize for relevance and trust before fill rate.
  • No-fill is a successful result.
  • Start with low frequency.
  • Never render consecutively.
  • Raise frequency only after trust and retention hold.
  • Measure eligible requests, fill, no-fill reasons, qualified clicks, conversions, complaints or dismissals, task completion, session completion, and holdout retention.
  • Decision target: 150ms retrieval/rank budget; 400ms total handler budget.
  • Never reserve blank UI while waiting.
  • Fail open on no-fill, timeout, malformed response, or network error.

Frequency modes

ModeCap
MinimalMax once per 20 turns
BalancedMax once per 10 turns; max twice per session
Revenue-focusedMax once per 5 turns; max four times per session

Frequency is enforced when a session.token is sent. Caps come from the app frequency preset.

Docs version v1 · implemented publisher API