Frequency cap
Limit how often one campaign contacts the same profile within a window of days.
A frequency cap limits how often a campaign contacts one profile within a window of days. You set it in the Delivery block of the campaign page, next to the consent purpose and silent hours. It is optional: leave it empty and the campaign has no cap.
Who uses it
Campaign managers and creators who set up delivery. Setting a cap needs campaign_editor, or another role your administrator has given access to this area — see Licences and roles.
Fields
| Field | Meaning | Valid values | Default |
|---|---|---|---|
| Max touches per profile | The most contacts this campaign makes with one profile within the window, across all channels. | Whole number of 1 or more, or empty for unlimited | Empty (unlimited) |
| Max per channel | The most any single channel may contribute to the total. Not shown for a one-off batch, which sends on one channel. | Whole number of 1 or more, not above the total, or empty for unlimited | Empty (unlimited) |
| Window (days) | How far back the campaign counts contacts. Required once you set a limit. | Whole number of 1 or more | Empty |
Leave all three empty for no cap. Set a total, a per-channel limit, or both. A window on its own caps nothing, and the form refuses it: Enter at least one limit plus a window, all as positive whole numbers. A per-channel limit cannot exceed the total.
What counts as a touch
Each contact this campaign makes with a profile counts once. A message is counted once on its way out, never twice: an inbound-offer campaign counts when an offer is decided, and every other campaign counts when a send is queued. Only this campaign's own contacts are counted. A cap protects within one campaign; to protect a customer across all campaigns, use a fatigue policy (see Channels and delivery).
A profile that has reached the cap is skipped. In a decision the offer is excluded with the reason Frequency capped, and in a pre-flight run the step Frequency cap shows how many people it removed (see Pre-flight).
One-off campaigns
A one-off batch contacts each profile once anyway, so a cap is not a frequency policy there. The field is named Re-send guard. A maximum of 1 stops a retried run from sending again to profiles it has already queued. Leave it empty unless you want that guard.
Examples
At most three messages a week. Max touches per profile 3, Window (days) 7. A weekly newsletter campaign never sends a fourth in any seven-day span.
No channel dominates. Max touches per profile 3, Max per channel 2, Window (days) 30. The campaign contacts a profile at most three times in 30 days, and no more than twice on any one channel, so a campaign on Auto (best channel) cannot send three emails in a row.
Re-send guard on a one-off. Max touches per profile 1, Window (days) 365. If a send is interrupted and retried, nobody receives it twice.
Common problems
- The form says to enter at least one limit plus a window. You set a window with no limit, or a limit with no window. Fill in both, or clear all three.
- Max per channel is rejected. It cannot be larger than Max touches per profile.
- The cap does not stop messages from other campaigns. It counts only this campaign's contacts. Use a fatigue policy for a cap across campaigns.
- I cannot find Max per channel. It is hidden on a one-off batch.