> For the complete documentation index, see [llms.txt](https://docs.crobox.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.crobox.com/how-to-guides/product-finders/finder-editor/answer-editor.md).

# Answer Editor

This guide provides detailed instructions on configuring answer options within the Answer Editor.

The Answer Editor allows you to configure answer options for each question in your Finder flow. Through this editor, you can define answer content and decide which visitors see each answer. The products an answer shows, and the benefits that explain them, are set with [Matching Rules](https://docs.crobox.com/how-to-guides/product-finders/matching-rules.md) on the **Matching** tab.

## Managing Answers

To add or modify answers within a question, access the Answer Editor by selecting an answer in the left-hand column. You can:

* Add a new answer by selecting the **+ Add Answer** button.
* Duplicate an existing answer to maintain consistency while making minor modifications by selecting the three dot menu of an existing column in the left column.
* Remove an existing answer by selecting the three dot menu of an existing answer in the left column.
* Edit answer settings in the right-hand column.

## Configuring Answer Settings

{% stepper %}
{% step %}

#### Answer Content and Descriptions

Each answer can be customized with supporting text and additional details:

* Answer Title – The primary text displayed for the answer option.
* Answer Description – Additional explanatory text visible under the answer title.
* Information Text – Supporting details that remain hidden behind an (i) icon, providing users with more information when needed.
  {% endstep %}

{% step %}

#### Define Answer Key

The Answer Key is a unique identifier for each answer option. It should be short, simple, and consistent across the Finder flow.

{% hint style="warning" %}
Changing an Answer Key after the Finder is live may affect tracking, analytics, and personalization logic.
{% endhint %}
{% endstep %}

{% step %}

#### Personalization & Conditional Logic

**Skip Answer for**

The **Skip Answer for** setting hides this answer from visitors who match a condition. This ensures that irrelevant answer choices are hidden from users, even if product data would typically include them.

Under **Do not show this answer for visitor that match**, add one or more conditions:

* **Finder Question Key:** The answers a visitor gave to an earlier question. Select the Question Key and Answer Key(s) that should skip this answer.
* **Market → Country** and **Market → Language:** The market the visitor shops on.
* **Visitor Location → Country** and **Visitor Location → Continent:** Where the visitor is, based on their IP address. These are not offered when **Disable storing visitor location** is turned on in **Settings → Website integration → General**.

Use this to refine the user journey and prevent unnecessary options from appearing.
{% endstep %}

{% step %}

#### Products and Benefits

Which products an answer shows, how it ranks them, and the benefits that explain them are the answer's **Matching Rules**, on the **Matching** tab.

The answer settings show a banner, **Products are now chosen on the Matching tab**. Click **Open Matching** to go straight to this answer's rules. See [Matching Rules](https://docs.crobox.com/how-to-guides/product-finders/matching-rules.md).
{% endstep %}
{% endstepper %}

The Answer Editor is a crucial part of structuring your Finder flow. Well-defined answer content, combined with clear Matching Rules, gives visitors more relevant product recommendations.


---

# 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://docs.crobox.com/how-to-guides/product-finders/finder-editor/answer-editor.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.
