Real-time Journey - Skip to a step based on calendar date

(0) Share

Report

Posted on by MarissaT

Hi,

We're hoping to set up a series of emails within a Real-time Journey, based on form submissions.

Submit form > Wait for certain time > Send Email 1, 2, 3 (with some days between emails) > End Journey

Is there a way to reference to a specific date (maybe an event, or a calendar date to specify within the journey or somewhere else) and check if they have submitted the form close to that date, they skip to receive Email 3 in the series instead?

I have the same question (0)

All responses (4)

Answers (1)

Verified answer

PaulineKolde 732 Moderator on at

Like (1)

Report

Hi Marissa,

you could try doing this with an attribute in the journey. In the attribute you can reference the trigger and from that the created on date of the submission. Based on a fixed or relative date, you can then send the contact to the specific branch with Email 3 or to an empty path to end the journey

The journey looks like this then:

Hope this helps!

Was this reply helpful? Yes No
MarissaT 25 on at

Like (0)

Report

Hi Pauline!

Thank you for your reply. I apologize if I wasn't clear.

I was hoping to only send straight to Email 3, and they don't receive Emails 1 and 2, if they submitted close to that date. (For example, 1 week before the date)

Is that still possible?

Was this reply helpful? Yes No
Suggested answer

PaulineKolde 732 Moderator on at

Like (1)

Report

Hi Marissa,

in Outbound we had an expiration date for emails that would be useful for you. For real-time journeys this feature is still missing but I think it is one roadmap.

As a workaround you still use the attributes and add email 1 and 2 in the branch depending on the date. The other branch is empty and directly leads to email 3.

Was this reply helpful? Yes No
MarissaT 25 on at

Like (0)

Report

Ah, yes! This is actually a good idea. Thank you!

Would you happen to know if there's a way for that date value as separate from the journey? As we're hoping to make a workflow a seasonal thing. So we just need to update that specific value, without editing the journey?

This is because, we're also inclined to use Real-time segments as well for more conditions in the entry. This doesn't necessarily mean this is the same workflow as initially indicated here, but we do have multiple concurrent campaigns. And when a journey is segment-based, editing it is not possible. Only stopping it, and having to duplicate it. And that may not be sustainable in the long-run.

Was this reply helpful? Yes No