To build a Workflow in Localytics, head to the Workflows tab from within your Dashboard. Click the Create New button in your Workflows dashboard to get started.
First up, you'll need to name your Workflow. Make sure to pick a clear, descriptive name so you can find the Workflow again in the future.
When you've chosen your name, click Continue to setup to head to the next step.
You'll need to select an Audience for your Workflow to include. Select an App Group from the drop-down menu.
Once you've chosen an App Group, select Confirm Audience.
Finally, you'll want to configure an Entry Event for your Workflow. The Entry Event is the event an end user needs to complete in order to qualify for the Workflow. Entry events are based on the Global Events you made during your setup process.
Click Create Workflow to start building your Workflow.
Now that you've named your Workflow, selected the App Group and the Global Event, it's time to build the workflows.
At the top of the Workflows page, you'll see an option to configure re-entry. Changing the Re-entry Limit allows you to limit the number of times an end user can enter a Workflow based on their actions within your app.
For example, if you're building an Onboarding Workflow meant for new users, you would want to set the re-entry limit to 0. Alternatively, if you were building an abandoned cart Workflow, you would want to Remove Limit entirely, so that users can qualify for the Workflow whenever they add an item to their cart.
Add any action to your Workflow by clicking the + button.
After a user qualifies for your Workflow (ie, triggers your entry event), you can trigger one of three events:
- Event listener
- Wait timer
- Push message
An Event Listener allows you to put users on a different path based on their interaction (or lack thereof) with your app during a certain period of time. Say you wanted to send a push message to a group of users who haven't yet performed checkout. You could use an event listener to check to see if the user had successfully checked out before messaging them.
Add an Event Listener to your Workflow by clicking the + button.
Select Add event listener from the pop-up modal.
If a user doesn't perform the event within the selected time period, they'll be sent down the Did Not path for the Workflow. If they do perform the event, they'll be sent down the Did path.
Select the Global Event you'd like to listen for from the drop-down menu. Then, choose the amount of time you'd like to listen for the event. You'll be able to choose hours or days for your unit of time (from the drop-down menu), and fill in a number on the left.
When you've finished setting up the Event Listener, click Add to add it to your Workflow.
A Wait Timer allows you to put users in a holding pattern for a defined period of time. For example, you could add a wait timer as soon as the user qualifies for the Workflow, to avoid over-messaging them.
A Wait Timer will begin after the previous step completes. Those steps might be:
- Another Wait Timer completes
- The user qualifies for a Workflow
- The user performs an event within a listening window
- The user fails to perform an event within the listening window
Add a Wait Timer to your Workflow by clicking the + button.
Select Add wait timer from the modal.
Fill in the number on the left, and select the unit (hours, days) from the drop-down menu. When you've finished, click Add to add it to your Workflow.
A Push Message allows you to build a push using the typical message functions like title, deep link, key/value pairs, and creatives.
To add a push message to your Workflow, click the + button.
Select Send push message from the pop-up modal.
This will open another modal where you'll be able to craft your message.
Make sure to give your push message a name by clicking the Untitled Message copy at the top of the modal. We'll use this name to identify the message's "push sent" event in the Events section of your Localytics Dashboard.
You'll be able to edit individual push messages, based on the app they're being sent to, by clicking the app's name in the modal.
The message title and body are both copied across every app within the targeted App Group. However, because of the differences between iOS and Android operating systems, rich media, deep links, and key/value pairs are not copied across apps.
After you've crafted your push message (and checked it between all of your grouped apps), click the Add button to add the push to your Workflow.
As you build your Workflow, it will remain in Draft mode (we'll talk more about versions in the next section). No users can enter the Workflow in Draft mode.
After you've built your Workflow (and reviewed it), you'll want to activate to begin funneling users through it. To activate, hover over the Draft button (next to your Workflow name) at the top of the page—you'll see it become an Activate? button instead.
Confirm that you're ready to launch the Workflow, and immediately begin qualifying users, and click Yes, I'm sure.
When the Workflow is active, you'll see the button at the top stay in the Active state.
To deactivate a Workflow, click the Active button at the top of the page (it will turn into a Deactivate button on hover).
Clicking Yes, Deactivate will prevent additional users from entering your Workflow. Users who have already entered will continue to move through the Workflow until they exit naturally.
If you need to end the Workflow entirely, you can choose to Disable to remove all users and stop all actions immediately.
Active, deactivated, disabled, and draft are all Workflow statuses. When you create a new Workflow version, it will be in Draft mode. While in Draft mode, you can create multiple drafts of your Workflow.
After you activate it, it will become Active and you can no longer change the version. Deactivating a Workflow gives you two options: deactivate or disable. Disabled Workflows will remove all users from the Workflow immediately, while deactivated Workflows will let the users finish the Workflow while no longer enrolling new ones. Here's a handy chart to clarify:
|Draft||Workflow version is not live and is able to be edited.|
|Active||Workflow version is live and users can enter the Workflow. Workflow version is no longer able to be modified.|
|Deactivated||Workflow version has been stopped. Users currently in the Workflow version will continue through until they have exited.|
|Disabled||Workflow version has been stopped and all users in the flow have been removed.|
You can also filter your Workflows on the Workflows Dashboard by their status.
At times, you may want to change a Workflow without interrupting the active flow of users. That's where Workflow versions come in. Versions allow you to create different variations without having to deactivate a Workflow.
To create a new version, click Draft 1 at the top of your page to access all drafts. You'll see an option for New Draft in the drop-down menu. Click New Draft to create a new version.
Keep in mind, a Workflow can only have 1 active version at a time, and a user can only flow through 1 version of the Workflow at a time.
If you're iterating on your Workflow by building multiple versions, a user will need to exit an active (or deactivated) Workflow naturally before being re-enrolled in a new version. A disabled Workflow will automatically remove everyone immediately.
On your Workflows Dashboard, you can view high-level metrics. Here we'll show you things like the number of users currently active in the Workflow, and the total number of users that have ever flowed through the Workflow.
If you need more detailed metrics on all of your Workflow versions, you'll want to download the CSV export. Click the ellipsis on the far right of the Workflow table and choose Download CSV from the drop-down menu.
For more information on interpreting that data, see the chart below:
|Workflow Name||Workflow name|
|Activated Date||Workflow version activated date|
|Version Number||Version number|
|Version Status||Draft, Active, Deactivated, or Disabled|
|From Node||Previous step (wait timer, push message, or event listener) completed by users|
|To Node||Current step (wait timer, push message, or event listener) of users|
|Action||Action taken at From Node that lead to To Node (ie, event name, Did, Did Not)|
|User Count||Number of users at this step|
|Unreachable||If a message, number of users who were unreachable (ie, push disabled)|
|Message Sends||If a message, number of total sends|
|Message Opens||If a message, number of total opens|
If you're looking for more information on use cases—like a full walkthrough of setting up an Abandoned Cart Workflow—check out this article.
If you'd like to learn more about Workflows, contact our Support team or get in touch with your Mobile Engagement Consultant.