The Dynamic Registration Portal’s Route Page allows you to send your visitors down unique sign-in paths depending on the answer(s) they give in a Branch or Form Page.
This is especially powerful with the Form Page as it allows you to create a unique sign-in path for any answer given on a single page, whether chosen via picklist or typed into the form by the customer.
The sections below include:
Related Content
Adding the Route Page
The Route Page can be added like any other page in the Dynamic Registration Portal. Simply drag and drop the Route Page block into the Experience flow. By default, the Route Page will only show one sign-in flow off to it’s right when first created.
Adding Conditions
To add a new branch, click on the Route Page’s Edit button, then ‘Add Condition’. This will create a new sign-in flow, branching off your Route Page. You can create as many branches as you like.
Editing Conditions
Each Branch has three required fields:
Data Name: The Data Name determines which form/branch page question is referenced from a previous point in the experience. This needs to exactly match the Data Name for that form/branch page question. NOTE: It's best practice to make all Data Names for form/branch pages in a single sign-in path unique. This will ensure that Route Page is always referencing the correct data point.
Operator: The Operator determines whether the visitor will be sent down the branch or not. If the Operator is set to ‘Equals’ and the visitor’s answer matches an exact value of your choosing (see Check Value below), then they will be sent down that branch. If the Operator is set to ‘Doesn’t Equal’ and the visitor’s answer doesn’t match, they will be sent down that branch.
Check Value: Your Branch will look for this value to determine whether a guest is sent down the branch.
If the Operator is set to ‘Equal’, then the guest’s given answer must match the Check Value exactly (this is case sensitive).
If the Operator is set to ‘Not Equal’, the guest will be sent down this branch if they give any answer that doesn’t match the Check Value exactly.
Example Use-Case
Let’s put these settings into context. Let’s say you have a form page question that asks “Have you experienced flu-like symptoms in the last 14 days"?" You’ve then created a picklist of three possible answers: ‘Yes’, ‘No’, and ‘I Don’t Recall’.
How would we set up the Route Page to allow your guest to complete their registration only if they’ve answered ‘No’?
First, we need to grab the Data Name from the Form Page question. This Data Name then needs to be copied into your branch’s Data Name field exactly. In the example below, both Data Names need to say ‘health_question’.
Form Page
Route Page
That branch now knows what Form Page question to reference. We can then select what answer will send the guest down this path. In this case, we want guests to proceed down the correct registration path only if they’ve answered '“No” to having experienced symptoms.
Put another way, if the answer equals ‘No’, we will send the visitor down the branch we’ve created from the Route Page. Therefore, our Operator must be set to ‘Equals’ and our Check Value must be set to ‘No’.
Note: Just like the Data Name, the Check Value must match the visitor’s answer exactly. If you are using a picklist, simply copy the exact value of your picklist answer into the Route Page.
Form Page
Route Page
The same principle applies in reverse if your Operation is set to ‘Does Not Equal’. In this case, if your Route Page is set to Does Not Equal the No value, then your guest will only be sent down the branch if they picked any other answer than No. In this example, this would be the Yes or I Don’t Recall Option from the previous Form Page.
Ordering Branches
Now that your Route page is configured, you can start adding pages down that path to fill out the rest of your experience. Additionally, you can add more branches to the same route page.
The order of these branches is important. If you have more than one branch, the Route Page will send your guest down the first branch that fulfills the requirements, ordered from top to bottom.
For example, if you have five different conditions/branches configured, the Route Page will only consider the fifth condition if none of the other four conditions are met.
If none of the conditions for your branches are met, the sign-in flow will take your guest down the default path from the Route Page.
To re-order branches, hover your mouse over the top-right corner of the specific branch in the editor. Click on the arrow icon to move it up/down the page.
When you are finished setting up the route page in an experience, the registration portal will automatically route visitors down a branch of the experience based on answers they have given previously in the experience.