A: Automated journey logic is fairly easy to set up in a journey management platform. You use a visual drag-and-drop user interface (UI) where you can define parameters based on the metrics that you have to work with. But it’s possible for that to get as technical as needed. So if you have somebody who is technically well-versed and wants to script something very complicated, they have that option as well.
To set up automated journey logic, the first thing you do is define the event that you want to work from. That could be a customer clicking a link, viewing a product, visiting a website landing page, or entering a physical store.
Once you decide what event you want to use to trigger a next action, you take the API that will fuel the event and configure it within your journey orchestration by copying and pasting the output code from whatever source you want. From there, you can save and reuse the output code. For instance, if you know you have an event that involves clicking on something, you could save that event and reuse it for whatever journey you want to create in the future.
The second part involves configuring the actual action or actions that you want to happen. When you have those two elements, you can essentially use the drag-and-drop interface and draw out the journeys that you want. Every journey starts with an event. Then you can flag conditions. The logic is set up so that if certain criteria are met, the next action will happen automatically.
The final part of setting up automated journey logic is testing the configuration to make sure customers are receiving the right information and actually taking the next steps. Few journey orchestration platforms currently have built-in testing capabilities, so companies need to add some type of external software like Post Manager to test the APIs.