> ## Documentation Index
> Fetch the complete documentation index at: https://docs.instantcampaign.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Cadence policy

> Hold back marketing email from contacts who are getting too much of it, using fixed rules you can read and change. Each contact can also choose how often they hear from you.

Mailbox providers watch how people react to your mail. Gmail's subscription manager lists senders by how much they send and lets people unsubscribe from several at once, and mail that goes unread is shown less prominently. Sending every campaign to every contact is the fastest way to lose both.

The **cadence policy** holds back a marketing email from a contact when they have had enough recently, based on what they did with your previous emails. It is off until you turn it on.

## Turn it on

Go to **Settings → Send policies** and switch on **Cadence policy**. You need permission to change workspace settings.

The card shows **Estimated impact on the last 30 days**: how many of your recent marketing emails the weekly limit and your contacts' own frequency choices would have held back. The fatigue and dormant rules would hold back more, so treat it as a lower bound.

## The rules

Each marketing email is checked against these rules in order. The first one that applies is the reason recorded.

| Rule | Default | What happens |
| - | - | - |
| Recent spam complaint | 90 days | The contact is skipped until 90 days after they marked an email as spam |
| Soft bounce | 3 days | While their mailbox is soft-bouncing, the next attempt waits 3 days after the last one |
| The contact's own choice | — | Weekly, monthly or "only occasionally" (about once a quarter) |
| Dormant | 90 days → 1 per 30 days | No opens or clicks for more than 90 days: one re-engagement email every 30 days |
| Fatigue | 5 emails → 1 per week | Five marketing emails in a row with no open or click: the limit tightens to one per 7 days |
| Weekly limit | 3 per 7 days | Never more than three marketing emails to one contact in 7 days |

Contacts created in the last 7 days are exempt from the fatigue and dormant rules. Machine opens (security scanners, image prefetching) never count as engagement.

You can change every number, switch the fatigue and dormant rules off, or set a cooldown to 0 to turn it off.

## What it never does

* **It never touches transactional email.** Receipts, password resets and account messages sent with a transactional send policy are not checked.
* **It never unsubscribes or suppresses anyone.** A held-back contact misses that one email; the next send checks again.
* **It never uses AI.** The rules are fixed and every decision can be explained from your own sending data. No contact data leaves InstantCampaign.

## Contacts choose their own frequency

While the policy is on, the hosted preference centre asks **How often?** with four choices: every email, at most once a week, at most once a month, or only occasionally. The choice only ever lowers your limits; "every email" does not lift your weekly limit. The question is shown in every language the preference centre supports.

## Seeing what was held back

* **Send wizard**: the audience step shows *About N recipients will be held back by the cadence policy (estimate)*.
* **Analytics → Skipped**: every held-back recipient is listed with the reason, for example *Cadence (cadence\_cap): Reached the workspace limit of 3 marketing emails in 7 days.* Held-back recipients are counted as skipped, never as failed.
* **Contact page**: the contact's frequency choice, what the policy would decide for a marketing email right now and why, and the last time a send was held back.

## Urgent mail

For an email that must reach everyone, such as a service notice sent as marketing, turn on **Ignore cadence for this send** in the last step of the send wizard. The choice is recorded with your name.

## Automations

Send email steps in automations follow the same rules. A held-back contact's step is recorded as skipped with the reason, and the contact continues through the automation.

## How it works with warm-up and deliverability checks

Deliverability checks run first and can stop a whole send. The cadence policy then decides per contact, before the warm-up limit is applied, so held-back contacts never use up your warm-up allowance.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.