> For the complete documentation index, see [llms.txt](https://support.quizkitapp.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.quizkitapp.com/building-a-quiz/results/outcome-types.md).

# Outcome types

Learn about the different outcome types for some results logic.

For some results logic, you can choose from several different outcome types. When you set up a new path, you need to set up the outcome type under the **Outcome** section.

* **AI generated:** Quiz Kit uses AI and your product selection to map any paths without manual results to an AI-generated outcome, based on your store data.
* **Product:** Provide product suggestions tailored to your customers' responses.
* **Collection**: Provide a specific collection of products tailored to your customers' responses.
* **Tags:** Choose tag(s) to be assigned to your customer according to their responses.
* **Text:** Write a message to appear on the results page according to your customers' responses.
* **URL redirect**: Based on their responses, the customer will be redirected to [a specific URL](https://support.quizkitapp.com/analytics-and-optimization/analytics-and-tracking/quiz-analytics/url-redirect-analytics).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://support.quizkitapp.com/building-a-quiz/results/outcome-types.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
