A contact receives at most two marketing emails from you in any 24-hour period, across all your campaigns combined. It applies to drip campaign steps and trigger emails. A contact in two of your campaigns still gets no more than two marketing emails from you in 24 hours.
#Rolling, not daily
This is the part that surprises people. The window is the last 24 hours from right now, not midnight to midnight. Someone emailed at 6pm and 11pm yesterday is not eligible again at 00:01, they are eligible at 6pm today, when the first of those two ages out.
#What happens to the third email
A step blocked by the cap is not retried tomorrow. It is skipped and recorded, and the sequence carries on to its next step on the normal schedule. The contact simply never receives that particular email.
This is why running two campaigns for one event at the same audience is worse than it looks, you are not slowing delivery down, you are permanently dropping messages. For a single event, build one campaign with more steps instead. Choosing Enroll in both when you add a contact to a second campaign does not lift the cap either, see Contacts in more than one campaign.
#Counted per address, per agent
| Situation | Effect |
|---|---|
| Two contact records share one email address | They share one cap, the address is what counts, not the record |
| A person is in more than one of your campaigns | One shared cap across all of them |
| A person is also emailed by another agent on EasyDigz | Unaffected. Your cap is yours alone |
| An email is queued but not yet sent | Still counts, so a burst cannot slip past |
#What is exempt
| Exempt | Not exempt |
|---|---|
| Emails you send from the composer, now or scheduled | Drip campaign steps |
| Welcome and workflow emails | Trigger emails |
| The daily or weekly digest | |
| Test and preview sends to yourself | |
| Emails to you about your own business, listings and deals |
Because composer sends are exempt, the cap never stops you emailing a client directly about their deal. It only governs automated marketing. Composer sends are still checked against suppression, so they will not reach someone who unsubscribed from you or whose address bounced.
#Seeing it before you send
The audience pre-flight card warns you about contacts already at their cap before you start a campaign, with a Capped today list, and the audience table marks them with a Daily limit badge. See The pre-flight check.
#When two are due at once
One slot left and both a trigger and a drip step due: the trigger wins. It relates to something that just happened, so it is more useful than the next step of a sequence.