Traffic splits in Experiences by Jebbit allow you to divide your audience into targeted groups and deliver personalized experiences based on device type, user attributes, query parameters, and more. By routing users down different paths within a single experience, you can test variants, gather richer data, and improve performance through optimization.
Traffic split types
Device Type: Target based on mobile vs. desktop usage.
A/B Split: Test multiple screens or entire paths.
Launch Link: Direct users based on the link used to enter the experience.
Outcome: Display the highest-scoring outcome at that point in the experience.
Query Parameters: Route traffic based on parameters passed in the URL.
Attributes: Split based on known user attributes.
Rules Based: Personalize content based on responses to previous screens.
Date & Time : Automatically update experience paths based on a specific date or time.
Before you begin
Identify your testing or segmentation goal (e.g., comparing user journeys, tailoring outcomes).
Ensure all relevant experience screens or paths are created.
Determine what user characteristics, behaviors, or links will drive the split.
Create launch links and set up any attributes or query parameters you plan to use.
Create a traffic split
Navigate to the experience you want to configure. From the main builder view, identify the screen where you want to split traffic.
Click the open plus (+) button on the screen node.
From the dropdown menu, select Split Traffic.
Configure your traffic split
Select a split traffic type.
Connect each branch to the appropriate screen or experience path.
For example, for an A/B split, click into each group (e.g., Group A, Group B) to build or modify their paths independently.
Device Type
Target based on mobile vs. desktop usage.
Identify the screen where you want to split traffic.
Select the pathway or branch.
In the modal that appears, click on Split Traffic.
Select Device Type. You will see both Mobile and Desktop appear.
Click Create.
Connect the paths to their respective screens in your experience flow.
A/B Split
Test multiple screens or entire paths.
Identify the screen where you want to split traffic.
Select the pathway or branch.
In the modal that appears, click on Split Traffic.
Select A/B Split.
Adjust the percentages to determine the traffic split for each pathway (e.g., 50% for each).
Label each pathway clearly to identify the different variations you are testing.
If you want to test more than two options, select 'Add another branch'.
Click Create.
Connect the A/B paths to their respective screens in your experience flow.
For a detailed overview of A/B Splits, click here.
Launch Link
Direct users based on the link used to enter the experience.
Identify the screen where you want to split traffic.
Select the pathway or branch.
In the modal that appears, click on Split Traffic.
Select Launch Link. This will direct users based on the link used to enter the experience.
Click Create.
Connect the paths to their respective screens in your experience flow.
Launch Links in Experiences by Jebbit refer to a URL that opens an experience when clicked. Click here for more details on launching an experience.
Outcome Split
Display the highest-scoring outcome at that point in the experience.
Identify the Lead capture screen in your experience.
Click on the open node or branch after this screen.
From the modal that appears, select Outcome Split.
Click Create.
Connect the Outcome paths to their respective Outcome screens in your experience flow.
For a more detailed overview of Outcome Splits, click here.
Query Parameter
Route traffic based on parameters passed in the URL.
Identify the screen where you want to split traffic.
Select the pathway or branch.
In the modal that appears, click on Split Traffic.
Select Query Parameter. Enter the Parameter in the box provided. Enter the value or URL via the branch option.
Click Create.
Connect the paths to their respective screens in your experience flow.
Attribute
Split based on known user attributes.
Identify the screen where you want to split traffic.
Select the pathway or branch.
In the modal that appears, click on Split Traffic.
Select Attribute.
Under 'Has Attribute' select or search for the Attribute required for this split.
Click Create.
Connect the paths to their respective screens in your experience flow.
Learn more about how to set up Attributes at this link.
Rules Based
Personalize content based on responses to previous screens.
Identify the screen(s) where you want to split traffic.
Select the pathway or branch.
In the modal that appears, click on Split Traffic.
Select Rules Based. You’ll notice that only screens within the current pathway that are eligible for branching will be available for selection.
Once your screen is selected, you will choose the responses and the operator you’d like to use:
Any means that any of the responses selected will qualify for that path. You will sometimes refer to ‘any’ as being called ‘or’.
None means the opposite. It’s effectively an exclusion.
Name your branches at the top of each branch for better recognition of what rule is behind each branch. If the rule is met by the end user, they will be routed down the pathway you set up. If a rule is not met, they will branch to the ‘default’ path.
Click Create.
Connect the paths to their respective screens in your experience flow.
For a more detailed overview of Rules based branching, please refer to our help article here at the link.
Date & Time
Automatically update experience paths based on a specific date or time.
Identify the screen where you want to split traffic.
Select the pathway or branch.
In the modal that appears, click on Split Traffic.
Select Date & Time. You can update experience paths based on a specific date or time.
Select the date and enter time as needed.
Click Create.
Connect the paths to their respective screens in your experience flow.
Publish the experience
When ready, publish the experience to begin routing live traffic according to your configured splits.
Next steps
Refine experience content or screen flows based on test results.
Consider layering additional traffic splits or personalizations over time to further optimize performance.
FAQ
When should I use a device split?
A device split is often used by clients who have design elements that cannot be accomplished with the Style Independently toggle turned on. For example, wanting to set up a different button layout or adding in different elements for each device type.
When should I use an outcome split?
You would use an outcome split to add elements to the outcome screen that are not customizable in the standard outcomes menu. For example, if you want to include a secondary CTA on each outcome screen, then you would set up an outcome split and add the additional CTA as a static button with an outcome-specific outcome URL. The result is that users who match the outcome will see this specific screen and this secondary CTA.
Can I use a traffic split to autopopulate an email the second time a user takes a quiz?
To autopopulate an email the second time a user takes the experience, you will need to leverage a traffic split. You can learn more about this use case at this link.
I accidentally disconnected a branch and can't find several screens. Where did they go?
Jebbit does not delete screens when a branch is accidentally disconnected; instead, it archives them. To restore archived screens, go to the "Show Archived Screens" tab in the campaign builder view's bottom left corner. To unarchive, click on an empty branch node and choose to reconnect it to the experience with a branch.