Scenarios are a great way to connect with your customers at any point of their journey by using emails, push notifications or web hooks.
From sending a basic email to complex automated flows with multiple targeted segments and A/B testing, scenarios are easily created by drag & dropping various scenario components to a board.
By connecting with your customers you can increase their engagement and retention, bring back lost customers or offer highly targeted offers based on the past behavior for every customer. Even though scenarios are incredibly powerful when combined with analytics, they are an independent module of Exponea. This means you can use them even if you don’t plan on fully integrating your business with Exponea.
In the first step you create a scenario where you set up targeting, conditions and actions as you like.
In the second step you start the scenario and from that point on, Exponea handles the execution of the whole flow you have created (targeting of customers, sending messages, etc.).
In the third step you evaluate the success of your scenario. What was the open or click through rate in sent emails? Which group from the A/B split converted better? Did push notifications affect retention?
Exponea’s scenarios are a complex yet powerful tool. This guide helps you get started with them in no time.
You can create a new scenario by clicking the Create new button in the Scenarios section of Campaigns.
After creating a scenario you should see an empty board with the component panel on the left.
Every scenario is a set of components connected into a flow. Learn more about different components in Scenario components.
To add a component you can click on the component you want to add or you can drag & drop it onto the board with your left mouse button. The component should immediately appear on the board.
Scenario with two components added on the board:
To remove a component you should select the component by clicking it with your left mouse button and then hitting the Backspace or Delete button on your keyboard.
Every component you add on the board (with the exception of the Now trigger) is editable.
You can edit a component by double-clicking the component with your left mouse button. This will open a component-specific edit window.
Editing the On date trigger:
Editing the Email action:
After you edit the component you can save the changes you have made by clicking the Save button. Note that this only saves the changes for the edited component, not for the whole scenario.
By editing components you can change how the scenario should be executed, create conditions or use different actions for different segments of customers.
Learn more about editing components in Scenario components.
To create a meaningful scenario, components must be connected into a flow as components by themselves won’t do anything.
You can connect two components by creating a path between the output connector of the first component and the input connector of the second component.
Example of connecting of two components:
Input connector is always on the left side of components, output connectors are always on the right side or on the bottom of components.
Flow is a set of components connected by a path. Customers will pass through this flow starting from a trigger (e.g. On date) to operators (e.g. Condition) and finally into actions (e.g. Email).
Example of a flow with three connected components:
After you add all components and connect them into a flow, you can save the scenario. You can either save it for future editing by clicking Save as draft button or you can save and execute it by clicking Save and execute button.
Executing a scenario means that the scenario will become active and triggers will now start streaming customers into the flow. We call this that triggers go live. As customers pass through this flow along the designated paths, they can enter either Operator components or Action components.
There is a functionality called dry-run, which will be shawn upon launching a scenario. It will show a result of how many actions will be triggered (emails sent) with the current combination of all conditions and policies in the scenario. It allows one last check before making the scenario live.
Let’s have a closer look at how these components are handled during the execution.
There are four types of Triggers with these live behaviors:
Learn more about customer streaming in the Triggers section.
When a customer enters an Action component, an Action is executed. There are seven types of Actions:
Learn more in the Actions section.
Operators are generally used to change the way customers move through the flow. There are five types of Operators:
Learn more in the Operators section.
In this section we will talk about various components that you can use to create your own custom scenarios.
The board is the place where you add components and connect them into a flow. Every component can be dragged, re-positioned, edited or deleted.
Example of an empty board:
At the moment of the execution the Now trigger will stream all customers (present in your project at the time) into the flow.
After the trigger streamed customers into the flow
After all customers were streamed, this trigger becomes inactive. This is indicated by the trigger text turning gray with the word “(inactive)” being added at the end.
Important: Inactive Now trigger will not stream customers into the flow during repeated executions anymore.
Example of the Now trigger in use
This scenario will try sending all customers an email immediately upon execution.
Common usage is executing a one-time scenario immediately (e.g. sending a newsletter, setting a customer attribute for a segment).
On date trigger
At the moment of execution this trigger will become live. Live On date trigger will stream all customers into the stream at the specified time and date.
Editing the On date trigger:
You can edit the time and date of the trigger.
After the trigger streamed customers into the flow
After all customers were streamed, this trigger becomes inactive. This is indicated by the trigger text becoming gray with word “(inactive)” being added at the end.
Important: Inactive On date trigger will not stream customers into the flow during repeated executions anymore. It is also not possible to edit an inactive date trigger anymore.
Example of the On date trigger in use
This scenario will try sending all customers an email on the 2nd of June, 2015.
Common usage is executing a one-time scenario sometime in the future (e.g. sending a newsletter, setting a customer attribute for a segment).
At the moment of the execution this trigger will become live. Live Repeat trigger will stream all customers to the flow repeatedly based on the specified time condition.
Editing the Repeat trigger
The trigger is executed repeatedly during the time specified in the time range based on the options you choose inside the edit window of the trigger.
This Trigger will stream customers into the flow everyday at 5:12 AM of your local time:
Option Weekly let’s you choose selected days of the week when the trigger should be executed.
This trigger will stream customers into the flow every Tuesday and Friday at 5:12 AM of your local time:
Option Monthly let’s you choose only selected days of the month when the trigger should be executed.
This trigger will stream customers into the flow on the 1st, 16th and on the last day of the month, every month:
Editing the time range:
It is also possible to limit the time range during which the repeat trigger should be active. You can specify the time range after turning on the Time range picker.
Without specifying the time range the Repeat trigger will be active as long as the scenario is active.
The same customers can be streamed into the flow repeatedly. You can see how many times the trigger was executed in the View mode.
Unlike Now and On date triggers, Repeat trigger will not go inactive after its execution.
Example of a Repeat trigger in use
This scenario will try sending a reactivation email everyday to customers who match the condition (they were last seen exactly 30 days ago)
There are many usages for the repeated scenarios such as:
On event trigger
On event trigger becomes live when the scenario is executed. From this moment on, it will stream a single customer into the flow every time the specified event is tracked to the customer.
Editing the On event trigger
For the trigger to work, you must first specify the event in the edit window. It is possible to select only tracked event attributes.
On event execution
The same customer can be streamed into the flow multiple times. You can see how many times the trigger was executed in the View mode.
Unlike other triggers, the On event trigger always streams only a single customer into the flow. Similarly to the Repeat trigger, it will also not go inactive after its execution.
Important: Be careful when creating On event scenarios as this trigger will fire every time the specified event is tracked to a customer. You should use such scenarios only with events that happen occasionally (e.g. reading an article, session end, purchase).
Example of the On event trigger in use
This scenario will send the customer who ended his session a push notification after a two hour wait.
The On event trigger is the most flexible trigger available in Exponea’s scenarios. By using this trigger you are able to create automated scenarios for reactivation or engagement.
For example you can: