Outcomes are a great way to personalize an experience by directing users to the most relevant recommendations or content based on how they respond to questions. You can build outcomes in several ways and include multiple products within a single outcome.
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 can display dynamic elements like headings, descriptions, images, and products that change based on the specific Outcome the user matches.
Before you begin
Ensure you have a clear understanding of your experience's goals and the types of user responses you anticipate.
Outcomes use logic to determine which result is most relevant for a user.
Create outcomes
Follow the steps below to create an outcome -
Add an outcome screen to your experience from the screen library. 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.
Create your outcome buckets. Click the + icon on the bottom tab and fill in the dynamic outcome descriptors such as Outcome Name, Heading, Image, Description, and URL.
You can add outcomes in bulk by downloading the .csv file template, adding the information, and uploading it. This is recommended if you plan to create over 10 or 20 outcomes.
(Optional) Add additional products within an outcome by clicking the Add Products to this Outcome tab. A pop-up menu displays where you can add product elements. You have the option to categorize each product by marking the "Categorize this product" checkbox.
(Optional) Customize trigger texts, trigger emails, and social cards by selecting the options on the right side sub-panel menu.
Add Dynamic Outcome elements to the screen where you want the Outcome result to display. In the screen editor, click Add Elements, scroll down to the Outcomes category, and select the elements you wish to display. Ensure you add the correct elements, such as the "Products" element, for content like additional products to appear.
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.
Customize outcome elements
Outcomes are displayed using dynamic elements on a screen. You can customize several dynamic elements for each Outcome. These elements are mapped to specific placeholders or containers on your screens:
Outcome Name: An internal field essential for matching users to the correct Outcome and for reporting. This is the only required field.
Outcome Heading: The text value inserted wherever the {Outcome Heading} element is used in an experience.
Outcome Description: The text value inserted wherever the {Outcome Description} element is used. You can use HTML formatting, like <br> for line breaks or <b> </b> for bold text, within the description field.
Outcome URL: The URL users are directed to when they match with the Outcome. You need to add a Redirect URL node in the builder map and set it to the "Outcome URL" to enable redirection. You can match users to outcomes and redirect them without displaying any outcome elements.
Image, .gif, or Video: The content inserted wherever the {outcome image} element is used.
Trigger Text Message: The content for a text message that can be sent when a user matches the Outcome. This requires adding a Trigger Text node in the builder map.
Trigger Email: The subject line and HTML file for an email that can be sent when a user matches the Outcome. This requires adding a Trigger Email node in the builder map.
Social Share Card: Defines the content that appears when a user shares your experience on Meta (Facebook) and/or X (Twitter). You must add the Social Share Button element to a screen to allow users to share the Outcome-specific post.
Additional Products: You can add up to 24 additional products to an Outcome. These products display when the Products container element is added to a screen. You can add a total of 25 products per outcome, including the main outcome product and up to 24 additional products.
Product Categories: When adding additional products, you can categorize them. This allows Jebbit to group similar products together on the screen, for instance, categorizing products as "AM" and "PM" to show a routine.
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.
Refer to our Add products to an outcome guide if needed.
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.