Frequency capping
ما هو Frequency capping?
هذا المصطلح متوفر حاليًا باللغة الإنجليزية فقط.
Frequency capping is a per-recipient limit on how many messages a contact receives within a rolling time window — for example, no more than three marketing messages per contact per day. When a send would exceed the cap, the platform holds or rejects it and returns when the next slot opens, protecting recipients from overexposure and protecting the sender's deliverability and brand trust.
More detail
Frequency capping protects both sides of a campaign: recipients are spared the overexposure that drives opt-outs and spam complaints, and the sender avoids the deliverability damage that repeated, unchecked sends to the same contact cause.
A channel-agnostic (global) cap counts one recipient's exposure across every channel in a single window — so three SMS plus one email still trips a 'four messages per day' rule — instead of tracking each channel in its own silo.
Category scoping keeps the control precise: a cap restricted to marketing sends still lets OTP, receipts, and other transactional traffic through even when the marketing window is full.
In Orbit, frequency-cap rules are managed through the `/frequency-caps` API and enforced before a send dispatches. A denied send returns a retry hint instead of failing silently, and a per-contact cap-status read shows current usage, remaining slots, and when the next slot opens — so the composer can warn before an operator attempts a send.
الأسئلة الشائعة
- What happens to a message that would exceed a recipient's frequency cap?
- The platform holds it and reports when the recipient's next slot opens, rather than sending it or dropping it silently. The response carries a retry hint so the sender can schedule the message for the moment the window frees up.
- Should transactional messages like OTPs count toward a frequency cap?
- Usually no — the cap scope can be restricted to marketing sends, so authentication codes, receipts, and other transactional traffic still deliver even when a recipient's marketing window is full. The cap choice is made per rule, not globally.
- How is frequency capping different from throttling or rate limiting?
- Throttling and rate limiting control how FAST messages leave the platform (a burst queue or an HTTP 429). Frequency capping controls how OFTEN one individual recipient may be contacted at all — a per-recipient exposure limit, independent of send speed.
See also
Build it on Orbit
Voice, messaging, email, video, and AI agents on one platform and one pay-as-you-go bill. Start free — no credit card required.