Library · Subscriptions · How to run this
Frequency caps can miss the send plan
Frequency caps can block planned sends. Miss % = capped ÷ planned × 100. Type capped sends and planned sends.
Pair: Frequency cap miss on Subscriptions. Fatigue: channel fatigue cost. Canvas: canvas step drop.
What you type
Capped sends — sends blocked by the frequency cap in the window.
Planned sends — sends the campaign / canvas planned in the same window.
Miss % = capped ÷ planned × 100. Raise the cap or thin the plan when miss % is material — do not invent a miss chip.
What not to do
Do not invent miss %. Do not mix unsubs into capped sends. Do not treat delivery fails as frequency caps. Do not average every canvas when one owns the miss.
Related: Subscriptions, channel fatigue cost, canvas step drop, SMS cap vs rebill.
Procedure
- Type capped sends and planned sends.
- Read miss %.
- Raise the cap or thin the plan when miss % is material.
Failure modes
- Inventing miss %.
- Mixing unsubs into capped sends.
- Treating delivery fails as frequency caps.
Worked example
None on this page yet. When one lands it will be a real case: what broke, the number, and what changed. Not a composite.
Glossary
- Frequency cap miss %
- Sends blocked by frequency cap ÷ planned sends × 100.
Work with us — We run this job on your accounts. Services
FAQ
- Is this channel fatigue cost?
- Sibling pressure. [Channel fatigue cost](/manuals/braze-channel-fatigue-cost) prices unsubs × revenue. This page is capped ÷ planned send miss %.
- Is this canvas step drop?
- Related leak. [Canvas step drop](/manuals/braze-canvas-step-drop) is step exits. This page is frequency-cap blocks vs the planned send count.
- What miss % should I invent?
- None. Type capped sends and planned sends from the ESP for the same campaign window.