Why your SFMC win-back journey can send after the customer returns.

Separate entry data from current state

In Salesforce Marketing Cloud Engagement Journey Builder, Journey Data comes from the entry event and represents the values captured when the contact entered. Contact Data can reflect newer values from the linked contact model when an activity evaluates it. A decision based on a stale entry value can miss a purchase made after entry.

Define the return signal

Decide exactly what counts as a return: an order, a deposit, a qualifying activity or something else. Confirm the source updates on time, identifies the same person as the journey's contact key and can be reached through the data relationships used by the decision or exit criteria.

• Check the contact key and the field used to join the activity back to the contact.
• Measure the delay between the real event and its arrival in Marketing Cloud.
• Add a clear rule for customers who should no longer receive the message.

Test the journey mid-flight

A clean entry test is not enough. Let a test contact enter, make them eligible for the wait, then update the return signal before the next decision. Confirm the journey sees the new state and exits or takes the correct branch. Repeat for a customer with missing or delayed data.

Protect the wider experience

Also check send eligibility and suppression at the point of execution. Another campaign may be speaking to the same customer. Your journey should make sense as part of the whole lifecycle, not only within its own canvas.