In this article, we'll review the various elements of the workflow builder you can use to build out your website experiences..
On This Page:
How experiences work
Workflow enrollment
"Add" actions
"Update" actions
"Edit" actions
Last updated 01/23/2023
How experiences work
The workflow builder is where all of Justuno's features come together to form website experiences that are published to your website, including pop ups, banners, product recommendations, embedded page elements, and much more. Below, we'll take a look at the different components you can use to build and manage these experiences within the workflow builder.
Workflow Enrollment
Along with being able to rename your workflow, this panel offers three critical settings: re-enrollment frequency, workflow scheduling, and unenrollment/suppression settings.
Re-enrollment frequency
This determines at what interval visitors should be re-enrolled into this workflow if they still meet the enrollment trigger criteria: once per session, once per page load, or no re-enrollment.
⚡Notable note
Running simple workflows that contain only one type of design display, such as a banner, may allow you to set your re-enrollment frequency at once per page load assuming you want this banner to show on every page load. Another example of this is a single pop up, that may only require re-enrollment once per session.
Conversely, if you are running a longer workflow with mixed design types, we recommend setting your frequency based on how often you may want a visitor to be enrolled from the top of this workflow
Workflow scheduling
Let this workflow enroll visitors any time, or set a specific days and/or times visitors may be enrolled.
Unenrollment & suppression
This allows you to suppress visitors who enroll into this workflow from being enrolled in other workflows.
🤓 Pro tip
This setting can be an easy key to ensuring your visitors aren't enrolled in multiple workflows and therefore, seeing multiple pop ups at the same time.
Add actions:
If/then branches, designs, and multivariate tests
If/then branches:
These triggers split visitors into paths (or branches) based on the conditions defined in each branch. Multiple “if” branches are not required, and will retain visitors at this step until they meet the qualifying criteria to pass through, If/then branches are utilized anywhere in the workflow after the enrollment trigger and define the enrolled visitor’s path through the workflow.
⚡ Notable notes
When utilizing multiple "if" branches, our system will attempt to match the visitor from the first "if" branch, then the next, and so on, e.g. “first check if ‘X’, if not ‘X’ then check ‘Y’, if not ‘Y’ then ‘else’”.
Designs, such as pop ups, are managed within the Design Studio and are then published to your website based on the workflow configuration. Within the workflow builder, the design step offers quick links to preview, edit, or replace your design, along with the following options:
Display types: should this design be presented as an overlay, or should it be embedded into website pages?
- Advancing event: by default, closing the design will move visitors past the design step. You can also specify an additional action (i.e. form submission) that will advance visitors.
- Repeat previous if/then: when selected, visitors will continuously be cycled back on each page load to the previous if/then step before the design to determine re-qualification. These visitors will only be advanced once the specified advancing event occurs.
- Smart Frame: decide whether to enable the Smart Frame feature. With Smart Frame enabled, visitors who trigger a design more than once in a session will see the next frame in the design's sequence, while frames containing form fields with known visitor properties will be skipped.
🤓 Pro tip
In most cases, you will specify an advancing event and repeat the previous if/then branch in order to show a design on every page, such as a paywall age verification, or a banner that you'd like to show on each page. This option works well if you wish to cycle visitors through a certain section of your workflow, as opposed to re-enrolling them at the beginning - this happens when your re-enrollment is set to once per page load, or perhaps once per session.
👍 Syncing form design data to your apps: You'll see all designs that contain a form will show a "Sync to app" button within the design step. We recommend syncing your form designs to your integrated apps from this button instead of using the separate sync to app step.
Multivariate tests
Tests are built within the workflow builder, and variants can include any number or combinations of designs, if/then branches, and other workflow actions to create flexible testing scenarios, such as testing a single pop up against many pop ups, or certain audiences against each other.
1. Drag the Multivariate test step into your desired workflow branch
2. Create your test path(s) by specifying a number of variants you'd like to test, then filling each path with the desired steps
3. Complete the set up options by choosing a goal for the test, specifying variant weight (if not even), test schedule, and which variant you'd like visitors to pass through before the test begins.
⚡ Notable notes
While creating paths allows you to test full experiences and audience segments against one another, doing so will significantly increase the time to statistical confidence in your results, especially if this workflow is not receiving a lot of traffic.
Update Steps:
Sync to app, enroll in workflow, update segments & profiles
Sync to app
Justuno allows you to sync data collected from our app throughout various points in the workflow. As mentioned earlier in the article, there are two methods of initiating a sync data with a third party:
- Sync to app from a form design: syncs all data collected from a form design to the third party before advancing visitors to the next step
👍 This is the recommended method in most cases, especially when using a multistep form (email + sms), survey, or any design where the form is split among multiple frames.
- Sync to app workflow step: waits until visitors land on the sync to app step in order to execute the sync
✋ This method is meant to be used with specific use cases where the sync to app button within the form design step is not a viable option.
Enroll in workflow
Once this step in the workflow is reached, visitors will be automatically enrolled in the specified workflow. If this step is the last in it's branch, visitors will also be unenrolled from the current workflow.
Update segment
Once this step in the workflow is reached, visitors will be added to one of your segments,
Update profile
Once this step is reached, visitors' specified profile property will be manually updated by the value you specify in the step settings.
⚡ Notable notes:
In most cases, visitors are automatically added to segments, and their properties are automatically updated by Justuno's zero and first party data collection and profile building. By adding these respective steps to your workflow, you are indicating you want to manually update those properties and/or segments.
Edit Steps:
Delay, Connect to step, Webhook, and Custom code
Delay
This step will delay visitors from proceeding to the next step in the workflow for the specified amount of time.
Connect to step
This step allows you to connect one step of a workflow branch to another step in a separate branch, funneling qualifying visitors to an entirely separate branch of your workflow
Webhook
Once this step is reached, you can fire an automated request to an outside service, such as posting survey details to a custom database, or submitting a form to a .xslx file. You can fire four different requests from this step:
- Post - Sends data to a server to create or update a resource (ie: sync JU with Shopify email API)
- Put - update data on a server
- Get - Requests information from a specific resource.
- Delete - Deletes a specific resource
Custom code
This step allows you to fire custom javascript or css once visitors reach this step, and it has far-reaching use cases and effects that we cover in this article about using custom code within Justuno. Much can be done, but Justuno only verifies basic syntax, and will not test any functions of the code you have written.
Visit Justuno @ justuno.com