Matching Outcomes in Experiences by Jebbit allows you to personalize user experiences by aligning their responses to the most relevant outcomes. This feature is ideal for creating personality quizzes, product match experiences, and guided navigation flows.
Before you begin
Ensure that you’ve created the desired outcomes within your experience.
Access the outcome menu
Navigate to the Builder Map or a specific screen in your experience.
Select the Outcome menu via the Builder Map or select Add Outcomes via the Editor.
Click the Matching tab.
Fill in the details for the outcome such as, Outcome Name, Heading, Outcome Description and the URL.
Note: On the right-hand side of your screen, you'll be able to see a preview of your outcome.
Map matching logic
Navigate to Outcome Logic tab in the left navigation bar.
In the Outcome Logic table:
Rows represent each question and its possible responses.
Columns represent the available outcomes.
Assign a point value for each response-outcome pair:
Use a scale from -10 to 10.
Positive values increase the chance of an outcome being selected.
Negative values decrease the chance.
Click Save to apply the logic.
Tip: You can only assign values between -10 and 10. Using values outside this range will not be accepted in the platform.
Import outcome logic via CSV
If your experience includes numerous outcomes, importing logic via a CSV can speed up setup.
To import logic:
From the Outcome Logic page, scroll to the bottom and click Download CSV.
Open the file in a spreadsheet editor (e.g., Excel or Google Sheets).
Do not modify structural or metadata fields, only enter values in the scoring cells.
Assign point values for each response, just as you would in the platform (scale: -10 to 10).
For example: Use “3” for responses that are highly influential toward an outcome.
If you make changes to your experience after downloading the CSV, re-download the file before continuing to avoid mismatches.
Once updated, save the file in CSV format.
Return to the experience and upload the file via the Outcome Logic page. A prompt will confirm that existing logic will be overwritten.
Once uploaded, your outcome mappings will be populated instantly.
Note: Always use the most up-to-date CSV. Re-download the file if you make edits in the platform before importing again.
Next steps
Use the outcome validator if you're using a liner campaign to test that your outcome logic is working as expected.
Explore scoring outcomes if your experience is based on right/wrong answers or scoring logic.
FAQ
Is it possible to ensure an Outcome is never served based on particular responses?
Using -10 nearly guarantees that a user will not see a given outcome. This is because Standard Outcomes use a point system, and we match users to the outcome that they earn the most points toward. If a response should deter a user from being matched to an outcome, then -10 will mean that 10 points are removed from that outcome for the user.
What happens in the case of an Outcome tie if a user is matched to more than one Outcome?
In the case of a tie, Experiences by Jebbit serves one of the highest scoring outcomes at random. This is because is a user earns five points towards outcome A and five points towards outcome B, and fewer points toward any other outcome, then outcomes A and B are equally relevant to the consumer. In this case, it would make sense for experiences to show either outcome A or B.
Does the outcome validator work with branching experiences?
No. The validator works only with linear flows.