> For the complete documentation index, see [llms.txt](https://help.dscout.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.dscout.com/usability-tests/analyze-a-usability-test/view-usability-test-responses.md).

# View usability test responses

When participants start submitting responses to your usability test, you can view them on the **Responses** tab of your study.

![](/files/1e7882e14bf47ab02d34da1ca1b11557338bd18b)

When viewing participant responses, you can choose from three views:

* **Questions:** Displays a list of all questions in your mission as well as their cumulative responses. Use this view to get an idea of how participants responded compared to one another.
* **Participants:** Displays all responses from the selected participant. Use this view to see how a specific participant responded to your questions.
* **Tags:** Displays responses grouped by custom tags you’ve created. Use this view to quickly filter by responses you’ve deemed important. For more information, see [Create and manage tags](/study-basics/analyze-missions/create-and-manage-tags.md).

## View by question

By default, the **Responses** tab displays responses grouped by question, meaning you’ll see all responses for a given question at once. This view offers a birds-eye view of how everyone who participated in your mission responded to each question. For open-ended questions, you’ll see each individual response labeled by the participant who submitted it. For closed-ended questions, you’ll see a graphic representation (like a bar chart) of responses.

You can return to this view at any time by clicking the **Questions** icon in the left sidebar of the **Responses** tab:

![](/files/7ea796d18d9dfeebda491beab310e243f343be29)

## View by participant

To view responses by participant, click the **Participants** icon in the left sidebar of the **Responses** tab:

![](/files/6fdb6581d7c088bafa83a0a42a59520481639c2f)

Here, you’ll see the selected participant’s response to every question in the mission as well as their responses to any screener questions if your mission used a built-in screener. You can also view more details about the participant in the right side panel, including demographic information.

From this view, you can also view a participant’s entire session recording, including a transcript of their audio, their screen recording, and their camera recording (if applicable). To view a participant’s session recording, select the participant in the left sidebar, then click **View full recording**:

![](/files/8eff311662088816b2b63e55f17a7e1a4c4ca1c9)

{% hint style="success" %}
**Tip:** If you spot a particularly interesting response to a specific question, click the **Play** button in the top right corner of the question to go straight to that moment in the participant’s session recording.
{% endhint %}

For more information on viewing session recordings, see [View usability test session recordings](/usability-tests/analyze-a-usability-test/view-usability-test-session-recordings.md).

## View by tags

To view responses organized by your custom tags, click the **Tags** icon in the left sidebar:

![](/files/cb53021bbe77c2565be6d223ce5178224d2e164a)

For more information on tagging responses, see [Create and manage tags](/study-basics/analyze-missions/create-and-manage-tags.md).

## Filter responses

Across all views of the **Responses** tab, you can filter the data that’s displayed. For example, you can filter the data to only show responses from participants who made a particular selection from a given multiple choice question. Or, you can filter by participant attributes like age, gender, and more.

{% stepper %}
{% step %}
Navigate to the **Responses** tab of your study.

![](/files/1e7882e14bf47ab02d34da1ca1b11557338bd18b)
{% endstep %}

{% step %}
Click the **Filter** icon in the top right corner.
{% endstep %}

{% step %}
Select your desired filters.

![](/files/079d21a56de73782eff32ea8fad3eff6e6bcf98c)

Now, the responses displayed are filtered to only include those that meet your selected criteria. Return to the filters menu at any time to change your selections or click **Clear all** to reset your filters entirely.
{% endstep %}
{% endstepper %}

## Other resources

Analysis is never a one-size-fits-all task. Dscout offers many tools to help you analyze your data. Refer to the following articles for help and inspiration:

* [Analyze heat maps and click data](/study-basics/testing-prototypes/analyze-heat-maps-and-click-data.md).
* [Explore your data](/dscout-ai/dscout-ai-studio/explore-your-data.md).
* [AI summaries](/dscout-ai/built-in-ai-features/ai-summaries.md).
* [AI themes](/dscout-ai/built-in-ai-features/ai-themes.md).
* [AI notable moments](/dscout-ai/built-in-ai-features/ai-notable-moments.md).


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://help.dscout.com/usability-tests/analyze-a-usability-test/view-usability-test-responses.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
