I'm building a Marketing Cloud Next (Growth/Advanced Edition) flow with this logic:
- Send an email to a segment. The email contains 6 links total, but only 3 specific links are "qualifying" engagement signals.
- Wait 7 days.
- If the contact has not clicked any of those 3 specific links, resend the same email.
- Wait 7 days again.
- If still no click on those 3 links, send the email one final time, then stop.
- If a contact clicks any of the 3 qualifying links at any point, they exit immediately and receive no further sends.
Where I'm stuck:
The
Wait Until Event → Email Link Click element only lets me select either "every link" (all 6, which is too broad) or "one specific link" (only 1 at a time). There's no option to select a subsetof 3 specific links as a single OR condition inside that element.
My question: Is there a supported way to configure Wait Until Event (or any other element) to listen for a click on any one of several specific links
(not all links, not just one), so contacts who engage early can exit the wait immediately? Or is the fixed-Wait + Decision-with-Count approach the correct/only pattern for this in MCN today? Would appreciate a full recommended flow architecture if I'm missing a cleaner element for this.
#MarketingCloudNext
As far as I can tell from the current documentation and community write-ups, you're not missing an element: the Email Link Click event in Wait Until Event is configured as either "any link in the email" or "one specific link", and there is no multi-select/OR list of links inside a single event condition.
The good news is that for your requirement the fixed-wait + decision pattern gives exactly the same outcome as an early exit. In your design the only actions happen at day 7 and day 14, so a contact who clicks a qualifying link on day 2 and a contact whose click is checked on day 7 both simply receive no further emails. Exiting early only changes when the contact leaves the flow, not what they receive. So I would treat it as the correct, supported pattern:
1. Send Email (version A).
2. Wait 7 days (fixed duration).
3. Decision "Clicked a qualifying link?": check the contact's email engagement for this email/flow for a click on link 1 OR link 2 OR link 3 (use the engagement/link click data available in your decision criteria, filtered to this email and the three URLs). If true, go to End.
4. Otherwise Send Email again, Wait 7 days, repeat the same Decision.
5. If still no qualifying click, Send Email the final time, then End.
If your org lets you add more than one event path to a Wait Until Event element, you can also get true early exits: add three paths, each an Email Link Click on one of the three specific links, all leading to End, with the 7-day timeout path leading to the resend. Check whether the element in your release shows "Add Event"/multiple paths; if it only allows one, use the fixed-wait version above.
Tips:
1. Give the three qualifying links distinct, stable URLs (e.g. unique UTM parameters) so they're easy to match in the decision and in reporting, and so the three non-qualifying links can't match accidentally.
2. Because engagement data can arrive with some delay, a fixed 7-day wait followed by a decision is actually more reliable than racing a real-time event.
3. Add a frequency/suppression rule or segment exclusion so contacts who unsubscribe or bounce also stop receiving the resends.
References:
Trailhead, Event-Triggered Flows in Marketing Cloud Next:
https://trailhead.salesforce.com/content/learn/modules/automation-events-in-marketing-cloud-next/explore-event-triggered-flows-in-marketing-cloud-nextCommunity article on Wait Until Event in MC Next flows:
https://medium.com/@marketingcloudtips/marketing-cloud-next-waiting-for-events-in-form-triggered-flows-db08c98630cdAssumption: I couldn't find official documentation confirming whether multiple event paths are supported in a single Wait Until Event element in your edition, or the exact field names for link-click criteria in the Decision element, so please verify those two points in your org; the overall recommendation (fixed wait + decision) doesn't depend on them.
