Journey Re-Entry Floods a Nurture Sequence
Adventure Works runs a 6-week nurture journey with 8 emails. The trigger is 'Contact is added to segment EngagedLeads'. Re-entry is enabled because marketing wants contacts who re-engage to restart the sequence. The segment is built on a rolling 30-day engagement window, so contacts drop out when they go quiet and re-enter when they open an email. The journey has no exit criteria beyond the segment. Analytics show 22% of contacts receive email 1 more than once, some four or five times, and the unsubscribe rate on email 1 is 3x the rate on email 2. Marketing wants to keep re-entry but stop the repeats.
1. Explain the mechanism producing repeated email 1 sends, and why the unsubscribe spike is concentrated there.
Read the worked answer
The segment is a rolling window, so membership is volatile by design: a contact who opens an email is in, goes quiet and drops out at 30 days, then re-enters on the next open. With re-entry enabled and no exit criteria other than the segment, each re-entry starts a fresh journey instance at step 1 - email 1.
The 22% repeat rate and the 4–5x cases follow directly: a highly engaged contact oscillates in and out of EngagedLeads repeatedly over six weeks, and each oscillation restarts the sequence. Contacts deep in the sequence (on email 5) are the ones most likely to open, so they are the most likely to re-enter - the mechanism preferentially punishes the most engaged people.
The unsubscribe spike on email 1 is the consequence: email 1 is the only message repeat recipients ever see, and they see it again and again. They are not unsubscribing because email 1 is bad; they are unsubscribing because it is the fourth time they have received it. Email 2's low rate reflects that few people reach it twice.
The core error is using a volatile segment as a journey trigger while also enabling re-entry. Those two settings are individually reasonable and jointly destructive.
2. Design a configuration that preserves re-entry for genuinely re-engaged contacts without repeating email 1.
Read the worked answer
Separate 'who is in the audience' from 'who should start a sequence'.
Stabilize the trigger. Trigger on an explicit event - for example a form submission, a demo request, or a score threshold crossing - rather than on rolling segment membership. Events fire once per real action; membership oscillates.
If the segment must remain the trigger, add re-entry suppression. Add an exit criterion on 'completed the journey' and a suppression segment of contacts who received email 1 in the last 90 days, excluded from the journey audience. Re-entry then only occurs for contacts who have genuinely cycled out of the suppression window.
Gate re-entry on a meaningful action. Where re-entry is enabled, pair it with a condition at the first step: only proceed if the contact performed a qualifying action (visited pricing, requested a demo) since the last completion. A passive open should not restart an 8-email sequence.
Add an exit on conversion. Any purchase or demo booking should exit the journey immediately, not wait for the segment to drop them.
Fix the measurement. Tag journey instances with a run ID so repeats are attributable, and monitor email 1 send count per contact as a standing metric.
The principle: re-entry is a statement about intent, and intent must be evidenced by an action, not inferred from a window sliding past a contact.