---
title: "Collected responses"
description: "Store answers submitted through an Experience."
search:
  tags: ["Features"]
  keywords: ["survey answers", "submit response", "form submission"]
---

Responses let you collect information from customers as part of an Experience. Ask about a goal during onboarding, gather preferences, or run a survey, then use the answers to personalize the next screen and understand your audience.

A collection defines the questions you want to collect. Each response belongs to a customer and Journey, so you can connect their answers to the path they took.

<span id="collect-an-answer" />

## Response fields

Open the Experience's **Responses** view, create a collection, and choose **Fields**. Give each field a unique key, such as `goal`, `weekly_sessions`, or `training_days`. Keys start with a letter and can contain letters, numbers, and underscores.

Choose the type that matches the answer:

| Field type | Use it for |
| --- | --- |
| **Text** | A written answer. |
| **Number** | A numeric answer, optionally limited by a minimum and maximum. |
| **True / False** | A yes-or-no choice. |
| **Single select** | One of your configured options. |
| **Multi select** | Several of your configured options. |
| **Date** | A date. |

You can add fields, change their keys and settings, and drag them into order. **Save changes** creates a new version of the collection. Earlier responses keep the field-definition version they were collected with, so changing a question doesn't change the meaning of an old answer.

## Connect a screen

Bind each input to the field it should update. For example, a goal selector writes to `goal`, and a weekly availability input writes to `weekly_sessions`.


You can use those answers immediately in the Experience. A training goal might appear in a heading or send the customer to a different introduction. See [Data and bindings](/docs/guides/data-and-bindings) to connect inputs, text, and conditions.

<span id="verify-submission" />

## Submission

Add **Submit response** to the flow after the customer's final answer and before the completion event or closing step. For example, a survey's Finish button can submit the collection and then show a thank-you screen. Selecting an option or moving between questions only changes the current answers; it doesn't submit them.

On the Canvas, drag a wire from the screen's output to an empty area, then choose **Submit response** under **Add to the Journey**. Connect the step that should follow it.

You can ask Nuxie to connect these steps:

**When the customer taps Finish, submit their onboarding answers, send `onboarding_completed`, and show the plan summary.**

> When the customer taps Finish, submit their onboarding answers, send `onboarding_completed`, and show the plan summary.

Responses can be **Submitted** or **Abandoned**. This lets you distinguish someone who answered one question and left from someone who finished. If your completion event is also a conversion goal, place submission before that event so the answers are submitted when completion is reported.

## Browse responses

In the editor's **Responses** view, choose **Collections** and open a collection. You'll see the customer, response state, answered-field count, response ID, and last update. Search by customer or response ID to find a particular answer set.

Open the published Experience's **Responses** tab to read individual values. Choose a schema, then filter by **All states**, **Submitted** or **Abandoned**. Selecting a row opens **Response Detail**, with the answers and their customer, Journey, and schema version.

The summary shows total, submitted, and abandoned responses. **Completion Rate** divides submitted responses by submitted plus abandoned responses.

<span id="use-answers-in-your-app" />

## Use responses

Read answers alongside [Journey history](/docs/guides/activity-and-journeys) to understand both what customers chose and what they did next.

To use an answer in your app, send it through an [App Action](/docs/guides/screens-and-interactions#app-and-connector-actions). For example, ask Nuxie:

**After submitting onboarding, send the App Action `start_workout` with `goal`, `weekly_sessions`, and `training_days` from the customer's answers.**

> After submitting onboarding, send the App Action `start_workout` with `goal`, `weekly_sessions`, and `training_days` from the customer's answers.

Your app handles `start_workout` and uses those values to open the first workout. Register the handler with your SDK's App Action callback. See the [iOS delegate example](/docs/ios-sdk/presenting-experiences#run-app-actions), [Android listener](/docs/reference/android#app-actions), or your platform's [SDK reference](/docs/reference). Collecting an answer in Nuxie doesn't update your app's data by itself.

For an answer you want to use in future targeting, also update the matching [Customer property](/docs/guides/customer-properties).

Responses keep the answers from a particular run. Properties hold the customer's current state. You can use both when an onboarding answer needs to become a lasting preference.