The Nurture Program That Over-Emailed
You run a 6-week nurture program with 5 emails sent via Engagement Program casts. The program has 8,000 members. Engagement settings: 'Communication Limits' is ON, cap is 1 email per day and 3 per week. Last month, a separate one-off batch campaign sent a promotional email to the same audience on a Tuesday. On Wednesday, the nurture cast went out. On Thursday, another batch campaign (a webinar reminder) also targeted the same list. Open rates on the Thursday nurture cast dropped 40% versus the prior cast, and you received 60 unsubscribes in one day versus a typical 8. A stakeholder asks why the nurture 'suddenly stopped working.'
1. Using the engagement program's communication limits, explain what actually happened and whether the limits should have prevented it.
Read the worked answer
What happened: The audience received up to three emails in three days (Tuesday promo, Wednesday nurture, Thursday webinar reminder). The nurture cast itself was not the problem - the surrounding batch sends saturated the audience.
Do communication limits help? Communication Limits in Engagement Programs govern how often a person receives emails from that engagement program, not from all of Marketo. A separate batch smart campaign sending a one-off email is outside the engagement program's cap and does not consume the nurture program's limit. So the Tuesday promo and Thursday webinar reminder bypassed the cap entirely.
Conclusion: The limits did not and could not prevent this. The 40% open drop and unsubscribe spike are classic fatigue signals from over-frequency, not a deliverability or content failure in the nurture itself.
Takeaway: Communication limits are program-scoped. Cross-program frequency management requires a separate mechanism (e.g., a global suppression or 'last emailed' field check).
2. Propose a concrete change to prevent recurrence without killing the nurture's cadence.
Read the worked answer
Recommendation: implement a global frequency guard using a data field and smart campaign logic.
- Create a custom field
Last Email Sent Date(or use a program-agnostic suppression list). - Add a smart campaign that stamps this field whenever any email is sent (trigger: 'Email is Sent', flow: change data value to today).
- In the batch campaign smart lists and the nurture cast audience, add a filter:
Last Email Sent Dateis not within the last 2 days (or whatever your policy is). - For the nurture specifically, keep the engagement program's Communication Limits but recognize they only protect within the program.
Alternative/complementary: Use a shared suppression segment that all senders must include, or route all promotional sends through a single 'send gate' smart campaign.
Rationale: The fix must operate at the person level across programs, not within one program, because the root cause is cross-program overlap. Also recommend a simple calendar review before launching batch sends to the same audience.