Skip to content

Frequency Cap and Cooldown

Protocol — instantiates Supernormal Cue Guardrail Design

Limits how many times a cue may be shown in a window and inserts a quiet period before it can be repeated, refreshed, or re-escalated.

Even a mild cue becomes supernormal by stacking — the same nudge fired forty times a day overwhelms not through strength but through sheer repetition. Frequency Cap and Cooldown governs the temporal budget of a cue: how many exposures are allowed per window, and how long a mandatory quiet gap must pass before the cue may fire again. Its defining idea is that the dimension under control is repetition over time, not per-instance strength and not reward structure. A single notification may be perfectly calibrated in loudness; the protocol still limits it to, say, three per day with at least four hours between them. The cap is the count; the cooldown is the enforced silence between counts. Together they keep a legitimate cue from turning into a drip that erodes attention.

Example

A retailer's mobile app has been optimizing push notifications by open-rate, and the machinery has crept upward: abandoned-cart pings, price-drop alerts, "you might like" nudges, and loyalty reminders now hit some users a dozen times a day. Engagement metrics look fine in the short run, but uninstalls are climbing and notification-permission revocations are spiking. A Frequency Cap and Cooldown protocol sets a per-user budget: at most three promotional pushes per rolling 24 hours, no two within four hours, and a hard 48-hour cooldown on any single campaign type after it has been shown twice without action.

Nothing about any individual notification changes — same copy, same visual weight. What changes is the cadence. The barrage flattens into a spaced, tolerable rhythm; the user stops feeling hunted; permission revocations fall. The retailer trades a burst of short-term opens for a channel that stays alive, because the cue was being burned out by its own frequency, not by its intensity.

How it works

  • Define the window and the budget. Choose the counting window (hour, day, rolling week) and the maximum exposures allowed within it, per user and per cue type.
  • Set the cooldown. Specify the minimum enforced gap between successive firings, and a longer cooldown that triggers after unacknowledged repeats — spacing that gives attention time to reset.
  • Count across channels. Aggregate exposures so the same cue arriving by push, email, and in-app banner does not each get its own budget and defeat the cap.
  • Slow rather than silence. When the budget is hit, the deamplification move is to defer or space the cue, not to escalate it; a blocked cue waits for its cooldown rather than jumping channels.

Tuning parameters

  • Budget size — exposures permitted per window. Tighter budgets protect attention but may starve a genuinely time-sensitive message; looser ones risk the drip returning.
  • Cooldown length — the enforced quiet gap. Longer cooldowns give more recovery but delay legitimately urgent repeats; shorter ones react faster but tire the responder.
  • Window shape — fixed calendar windows versus rolling windows. Rolling windows prevent end-of-window bursts but cost more to compute.
  • Cross-channel aggregation — whether the budget is per-channel or unified. Unified caps are honest to the user's actual load; per-channel caps are simpler but easily gamed.

When it helps, and when it misleads

Its strength is that it targets the stacking-and-repetition path to supernormality that intensity caps miss entirely — the classic case where each cue is individually fine but the sequence is punishing. Marketers have long known cues suffer wearout: past a point, more repetition yields diminishing and then negative returns as the audience habituates or resents the barrage.[n1] A frequency cap operationalizes exactly that ceiling.

Its failure mode is starving a signal that genuinely needs repetition: a real security alert, an expiring-benefit reminder, a safety recall throttled to look like promotional noise. It can also be gamed by an optimizer who rotates cue types to stay under each per-type cap while the user's total load is unchanged — which is why cross-channel, cross-campaign aggregation matters. The classic misuse is capping frequency while ignoring the reward schedule, so a variable-reward loop keeps the user checking voluntarily even without any push at all. The guarding discipline is to aggregate honestly across channels and to exempt verified-urgent signals from the promotional budget rather than letting the cap silence them.

How it implements the components

  • exposure_and_frequency_budget — it is the budget: a defined maximum number of exposures per window, enforced per user and cue type.
  • deamplification_rule — when the budget is reached, the prescribed action is to slow and space the cue (defer to cooldown), a concrete deamplification step.

It does NOT implement cue_intensity_metric or response_ceiling strength limits — capping how loud a single cue may be is Cue Intensity Cap Protocol's role; nor harm_and_compulsion_signal and substitution_pathway, the reward-loop levers of Variable-Reward Schedule Limit. This protocol budgets repetition over time, not strength and not schedule shape.

Editorial Notes

Form Classification

Form family: Control, Automation & Runtime

Rationale: Frequency Cap and Cooldown operates as a live operational control that automatically routes, enforces, adapts, or responds during execution because it limits how many times a cue may be shown in a window and inserts a quiet period before it can be repeated, refreshed, or re-escalated.

Independent corroboration: The frozen evidence defines Frequency Cap and Cooldown as 'Limits how many times a cue may be shown in a window and inserts a quiet period before it can be repeated, refreshed, or re-escalated', so its operative form is Control, Automation & Runtime.

Nearest alternative: Rule, Policy & Commitment — Cross-channel counts and cooldown timers enforce exposure budgets and quiet periods live; the declared limits are their policy.

Review outcome: Independent reviewer agreement; medium confidence.

Origin Attribution

Primary origin: Communication & Media Studies

Origin pattern: Convergent development

Present-day reach: Multi-domain

Rationale: Advertising and media practice provide the strongest primary provenance because frequency capping explicitly limits repeated exposures over a time window. HCI notifications, psychological habituation, and technology ethics independently motivate cooldowns; the generalized cap-and-cooldown mechanism is encyclopedia synthesis with multi-domain reach.

Related originating lineages:

  • Human-Computer Interaction — Notification and engagement design materially implements caps and quiet periods.
  • Psychology — Habituation, sensitization, and recovery after repeated salient cues are psychological processes.
  • Ethics of Technology & AI Governance — Responsible persuasive-technology governance contributes guardrails against supernormal cue exploitation.

Review resolution: Advertising and media practice provide the strongest primary provenance because frequency capping explicitly limits repeated exposures over a time window. HCI notifications, psychological habituation, and technology ethics independently motivate cooldowns; the generalized cap-and-cooldown mechanism is encyclopedia synthesis with multi-domain reach.

Encyclopedia synthesis: The exact catalogued form synthesizes established practice rather than reproducing a single standard historical label.

Review outcome: Researched adjudication after independent review; high confidence.

Sources consulted:

Notes

[n1] Advertising "wearout" and the related notion of effective frequency: repeated exposure to a message helps up to a point and then produces diminishing and eventually negative returns as audiences habituate or grow annoyed. It is the marketing-side expression of the general principle that repetition, not just intensity, has a proportional range.