Jumping to another journey

Transcript

Hello everybody. I will present you with the way Jump works. So first what is Jump? Jump is activity in Journey Orchestration that allow you to Push a person from one Journey to another.

This is an action.

You can find it here.

And with this action, you can decide whenever you want to Push a person in another Journey. So here I give you an example. This is a Journey starting with AppLaunch and all the person using IOS 14 will go to these path above, and users using an older version than iOS 14 will be pushed to another Journey, that will go this way in the other path. And then go to another Journey called, Old iOS version.

Second scenario. So I continue the Journey for the person that use IOS 14 and you see that there is Wait for 10 days and then another Wait for 10 days. But you might know that Journeys cannot last more than 30 days. When you enter in a Journey as a person you cannot stay in it more than 30 days. So if you want to do longer Journeys you could use Jump to send a person from one Journey that here lasts about 20 days to another Journey that will continue.

Here you can see that this is my Journey starting an event as usual in the Jump activity. And it continues, and I can continue to send message to people, wait for more time, and some message. Because that’s the way you use Jump activity. You use it to Push people from one Journey to another.

So now how do you configure a Jump activity? It’s pretty simple. It really looks like other actions. When you configure together this one to push people from the Journey App launch message one to App launch message two.

What you have to do is to select the Journey you want to target. So here you have the list of all the Journey that start with the same name space, this is a constraint, you can only link Journeys that start with the same name space.

And here we’ll link it to the Journey App launch two. So if I search this Journey, you see it selected. So we are good. And there is a reminder of what is the first event of this Journey. And this event expects two parameters. So you must pass them when you fire people from one Journey to another. So you pass the parameters, just like you do usually using action parameters, just like in any other actions. You can decide to pass elements, just writing them, just what I did for demo purpose but you can instead get the data from some data sources or from the events, which is whatever field. It’s very simple. It behaves exactly like another action.

And one last thing I want to tell you is that when you do a Jump, so here imagine a person called Sophie enters a Journey. Sophie uses iOS 14, she will go there. And then after they receive a Push then wait up to 10 days, will be pushed to App launch to Journey. Here there is nothing after, it means that in this Journey, App launch message one.

Nothing will happen for Sophie when she reached this step. But if for some reason, the marketer wants to push Sophie to another Journey, that make her continue this current Journey, it’s totally possible.

Jump doesn’t remove person from the current Journey, push it to another Journey. But you can totally continue the path, with the current Journey, and here potentially, I want to send it to Sophie and people reaching this step, an email etc.

So Jump is very easy to configure, it behaves exactly like other actions and that’s it for the presentation. Thank you. -