Score Tiers & Outcomes
FluoTest decides what a respondent sees after finishing a quiz using one of two systems: score tiers, which split a single score into up to 3 ranges, or custom outcomes, which matches any number of named outcomes against conditions over multiple scores, tiers, and answers.
Last updated
What's the difference between score tiers and the outcome engine?
Score tiers split one overall score into up to 3 ranges, each with its own message or action. Custom outcomes replace that with any number of outcomes, each matched by a condition tree that can combine multiple score categories, tiers, and individual answers, evaluated in priority order.
Score tiers (default)#
By default, a quiz has a single overall score (0–100%) split into up to 3 tiers, each defined by a minimum and maximum, a label, a color, and a message. The tier whose range contains the respondent's score determines what they see: a message, an email-collection step, a booking-calendar embed, a redirect, or any of the same generic actions the outcome engine uses (embed, forced download, coupon reveal, rich text).
Multiple score categories#
A quiz can calculate more than one independent score category — for example "Fit" and "Urgency" — instead of a single overall score. Each category has its own tiers, a range mode (percentage or points), and can be marked primary (it drives the headline score shown in analytics) or set to show or hide its numeric score and benchmark. Each question then carries a per-category contribution: choice-type questions assign a score per option per category, and numeric or yes/no questions assign a weight per category.
Custom outcomes#
Once a quiz's results mode is switched to "Outcomes," respondents are routed by a list of outcomes instead of score tiers directly. Each outcome has a priority (lower numbers are evaluated first), an enabled flag, a condition tree, a result (title, description, and a Markdown body), and a list of actions.
Condition rule types#
An outcome's condition tree combines AND/OR groups of the following rule types:
| Type | Description |
|---|---|
| score | A score category compared (≥, >, ≤, <, =, or between) against a percentage or points value. |
| tier | Whether a score category's matched tier is a specific tier. |
| answer | A specific question's answer compared (equals, not equals, includes, one of, greater than, or less than) against a value. |
| disqualified | True if the respondent was disqualified by a disqualifying answer. |
How an outcome is chosen#
Enabled, non-default outcomes are evaluated in priority order, lowest first. The first outcome whose condition tree evaluates true is used as the match. If none match, the outcome marked as the default is used as a fallback. If nothing matches and no outcome is marked default, no outcome is shown.
Outcome actions#
An outcome can carry one or more actions, shown alongside its result:
| Action | Description |
|---|---|
| cta | A labeled button linking to a URL. |
| open_url | Opens a URL, without a styled button. |
| redirect | Redirects the respondent to a URL, optionally after a delay. |
| embed | Embeds a URL in an iframe — for example a booking scheduler — with a configurable height or aspect ratio. |
| download | Forces a real browser download of a creator-hosted file (e.g. a PDF), instead of opening it in a new tab. |
| coupon | Reveals a discount or coupon code, with a copy-to-clipboard button. |
| rich_text | A custom formatted Markdown text block, for next-step instructions that don't need a whole file. |
| collect_contact | Asks for an email or phone number, optionally required, before or alongside the result. |
Referencing answers in result copy#
A result's title and body — and an action's text, like a rich-text block — can reference the respondent's own data with "@" mentions: @respondent.name, @score.percent, and @answer.budget (one per question, named after its text) insert the resolved value when the result is shown. Answer mentions are offered for structured questions (multiple choice, yes/no, slider, star, number) so the inserted value is always one of the question's known possible answers. The same mention system also drives the customizable results email.
Converting tiers to outcomes#
A quiz built with score tiers can be switched to the outcome engine. Doing so can generate one outcome per existing tier, using an equivalent tier condition on the primary score category, as the starting point for further configuration.
Frequently asked questions#
What's the difference between score tiers and outcomes?
Score tiers split one overall score into up to 3 fixed ranges. Custom outcomes are an unlimited, priority-ordered list of named results, each matched by a condition tree that can combine multiple score categories, tiers, and individual question answers.
How does FluoTest decide which outcome to show?
Enabled outcomes are checked in priority order, lowest first; the first one whose conditions evaluate true is shown. If none match, the outcome marked as default is shown instead.
Can an outcome depend on a specific answer, not just the score?
Yes. An outcome's condition tree can include answer rules that compare a specific question's response, combined with score and tier rules using AND/OR groups.
What happens if no outcome's conditions match?
The outcome marked as the default is shown as a fallback. If no outcome is marked default and nothing matches, no outcome is shown.
See also