Overview
Outcomes allow you to serve users a result based on how they interact with your experience. You add an Outcome screen to your experience, which displays dynamic elements — headings, descriptions, images, and products — that change based on the specific outcome the user matches.
Outcomes use logic to determine which result is most relevant for a user. There are two types of outcome logic: Matching and Scoring, covered in detail below.
Note: Always add an Outcome screen to your experience to ensure results display correctly. If an outcome screen is missing, users won’t see their matched result. Add the screen from the Screen Library and include the appropriate dynamic Outcome elements to present the result.
Before you begin
Ensure you have a clear understanding of your experience's goals and the types of user responses you anticipate.
Matching is best when the goal is a best-fit recommendation. No answer is right or wrong — responses just signal preference or affinity toward a result. Each outcome is a clear and well-defined category.
Scoring is best when there is a right answer. Users get points for correct responses and the total score places them in a result bucket. Use cases: trivia, product knowledge quizzes, certification-style assessments, education experiences.
Dynamic Product Feed is the right choice when the recommendation is a specific product from a catalog rather than a persona or category result.
Outcomes use logic to determine which result is most relevant for a user. Only one Outcome will display the content.
Create Outcomes
Follow the steps below to create an outcome -
Add an outcome screen to your experience from the Builder Map. While you can add Outcome elements to any screen, adding them on the last screen is recommended so you can redirect the end-user to your site.
Go to the Add Outcomes section in the main navigation bar of the Builder Map. Alternatively, you can access the Standard Outcome menu from the left side panel within the screen editor.
Click the + icon on the bottom tab to create an outcome. Fill in the dynamic outcome fields — Name, Heading, Image, Description, and URL.
Once outcomes are created, open the Outcome Logic tab in the left panel to connect user responses to outcomes.
Add dynamic Outcome elements to the outcome screen. In the screen editor, click Add Element, scroll to the Outcomes category, and select the elements you want to display — Heading, Description, Image, Products, etc. These will display in the screen between brackets: { Outcome Heading }
Tip: You can create outcomes in bulk by downloading the CSV template, filling in your outcome details, and uploading the file. This is recommended when creating more than 10–20 outcomes.
Outcome Fields
When creating an outcome, you can fill in the following fields. Only the Outcome Name is required — all other fields are optional.
Field | Description |
Outcome Name | Required. An internal label used for matching users to the correct outcome and for reporting. This value is not shown to users. |
Outcome Heading | The text displayed wherever the Outcome Heading element is placed on the outcome screen. |
Outcome Description | The text displayed wherever the Outcome Description element is placed. Supports HTML formatting — e.g., |
Outcome URL | The URL users are redirected to when they match this outcome. Requires a Redirect URL node in the Builder Map set to "Outcome URL." |
Image / GIF / Video | The media displayed wherever the Outcome Image element is placed on the screen. |
Trigger Text Message | Content for a text message sent when a user matches this outcome. Requires a Trigger Text node in the Builder Map. |
Trigger Email | Subject line and HTML content for an email sent when a user matches this outcome. Requires a Trigger Email node in the Builder Map. |
Social Share Card | Defines the content shown when a user shares the experience on Facebook or X (Twitter). Requires the Social Share Button element on a screen. |
Note: Outcomes will not auto-save if the Outcome Name is missing. Always enter the Name first before filling in other fields to avoid saving errors.
Configure outcome logic
After creating outcomes, access the Outcome Logic tab on the left-side panel menu.
This section is where you connect user responses to outcomes using either Matching or Scoring logic.
Matching Outcomes uses a points-based system to match users to relevant Outcomes. This logic is used to match users to their best-fit options by weighing their various responses. This type of Outcome is great for product and personality match experiences.
Scoring Outcomes are used to indicate correct and incorrect responses, and then match users to an Outcome based on several correct responses. Scoring Outcomes are great for Trivia and education-based experiences.
Tip: Refer to the related articles on Matching Outcomes and Scoring Outcomes for detailed guidance.
Additional Products & Categories
You can add up to 24 additional products to each outcome, for a total of 25 products per outcome (1 main outcome product + 24 additional).
Additional products are displayed using the Products element on the outcome screen. If you have added products to an outcome but they are not appearing, check that the Products element — not a Dynamic Product Feed container — is placed on the outcome screen.
Refer to our Add products to an outcome guide if needed, and our Outcomes with Products vs Dynamic Product Feed article to make sure you are choosing the correct one.
Product Categories
When adding additional products, you can optionally assign each product a category. Categories group similar products together on screen — for example, labelling products as "AM" and "PM" to display a skincare routine. Categories are a flat, single-level label with no nested structure. Each product can belong to one category.
Outcome Splits
If your experience requires a unique, fully customized screen for each outcome — rather than dynamic elements on a shared screen — use an Outcome Split. An Outcome Split creates a separate screen per outcome, giving you full design control over each result independently.
This is useful when different outcomes need significantly different layouts, additional content not covered by the standard dynamic fields, or secondary URLs and custom elements that the standard Outcomes menu does not support.
Next steps
Test your outcomes to ensure they align with user responses and experience goals.
Monitor user interactions and adjust outcome logic as needed to optimize personalization.
FAQ
How many outcomes can I create?
There is no limit to the amount of outcomes you can create. However, if you plan to create over thirty outcomes, then you may have an easier time using the import and export option instead. This would allow you to create your outcomes in a .csv file, and then import the file into Jebbit.
Are all the outcome fields required or are some optional?
Only the outcome Name is a required field. All other fields are optional and you can choose to customize them or not.
Is it possible to match a user to an outcome without showing the outcome in Jebbit?
Yes, you can certainly match users to outcomes without actually showing the user any outcome elements in Jebbit. Usually, a brand does this when they want to dynamically send users to a relevant URL onsite. In this case, you will create an outcome and only customize the URL field. Then, you will set up a Redirect URL node in the builder map that is tied to the "Outcome URL."
I've added Products to each outcome, but I don't see them populating on the outcome screen?
Make sure you've added the correct element to your outcome screen in order for the additional Products to display. The "Products" element is how the additional Products will be shown.
Am I able to customize more dynamic elements than what is shown in the outcomes' menu?
Yes! If you don't see the option to customize an additional dynamic element that you would like to serve alongside an outcome within our Standard Outcomes menu, then you will use an Outcome Split. An Outcome Split will allow you to create a unique screen for each Outcome, which in turn allows you to customize different elements on each screen. For example, you can add a secondary outcome URL if you'd like.
My outcomes won't auto-save?
If you are running into errors with our outcomes saving, it's likely because you did not add an Outcome Name to start. Refresh your page and rebuild your outcomes but make sure you always create the outcome Name first to avoid any more saving errors.
Why aren’t my outcomes showing at the end of my experience?
Outcomes may not appear if they haven’t been fully configured. First, go to the Add Outcomes tab to create each result (name, image, heading, etc.). Then, in the Outcome Logic tab, map your logic to those outcomes, so the system knows which one to show. Finally, ensure your final screen includes dynamic outcome elements (like Outcome Heading, Outcome Description, or Products Container) from the Add Elements > Outcomes section. Without all three, created outcomes, mapped logic, and outcome elements the results won’t display at the end of your experience.
How can I map complex outcome logic based on specific answer combinations in my experience?
Standard outcome logic is designed for basic matching or scoring use cases, where each answer contributes points (from -10 to 10) toward a final outcome. If your experience requires selecting an outcome based on a specific combination of answers across multiple questions, standard logic may not be the best fit.
For example, if a unique outcome should be shown only when a visitor selects a very specific sequence of answers, and multiple combinations lead to the same result, the system can struggle to evaluate that logic correctly.
The point-based system doesn’t support values outside the -10 to 10 range, using higher or lower numbers won’t function as expected.
When many combinations differ by just one or two answers, they may unintentionally score the same, leading to inconsistent or random outcomes.
To handle these more advanced logic scenarios, consider upgrading to a Dynamic Product Feed (DPF). With DPF, you can create rule-based filtering that matches visitors to outcomes or products based on their full answer set, without relying on point totals. If DPF isn’t available, try simplifying your outcome logic by reducing the number of branching paths, grouping similar combinations under shared logic rules and using broader scoring weights to distinguish between outcomes more clearly.
Why isn’t my experience reaching the outcome screen after form submission?
If your experience isn’t reaching the outcome screen, check the Builder Map to ensure your branch is correctly connected to the outcome screen. Click the plus (+) node following the last question or form screen, then choose “Connect to screen” and select your outcome screen. After making this change, be sure to publish the updated experience, so the change applies to your live launch links.
Why aren't my outcome products showing correctly in the quiz preview?
If the products you've configured in your Standard Outcome setup aren’t appearing in the quiz preview, it's likely because the outcome screen contains a Dynamic Product Feed container instead of Standard Outcome elements. To fix this, open the outcome screen, remove any dynamic product feed containers, and instead add elements from the “Outcomes” category like product image, title, and CTA button. These are required to display the correct products from your standard outcome mapping.
How can I remove unwanted header elements from the outcome screen?
To remove default headers (like outcome titles or category blocks) from your outcome screen, enter the screen editor, click on the element you want to remove, and press the trash can icon from the options menu. This allows you to fully customize the layout and keep only the elements you want, such as product image, title, and a CTA button.