Beta. Survey blocks are in beta for Flows 2.0 and Embeds. To build a survey in a classic Flow, see Create Forms and Surveys.

Add survey questions to a Flows 2.0 or Embed step to collect ratings, choices, and written feedback from your users, then review the answers in the experience analytics page or export them to a CSV. Surveys all use the same four blocks.

Prerequisites

• A draft Flows 2.0 experience (Modal or Tooltip steps) or an Embed.

Add a question

1. Select an empty cell and click +. The Blocks picker opens.
2. Under Survey, choose a block. The block is added to the cell and its settings open.
3. On the General tab, open Reporting and enter a Name. The name labels this question's column in your responses and exports, so make it something you'll recognize later, such as role or setup_rating.
4. Open Content and write the question in Title.
5. Repeat for each question. You can put several questions in one step, or spread them across steps. All the questions in one experience belong to the same survey.

Choose a question type

Make a question required

1. Select the question and open Validation on the General tab.
2. Turn on Required.
3. Edit the Error message. The default is "Invalid field", so replace it with something that tells users what to fix, such as "Pick at least one option."

On a Text input, Required also shows Min characters. Max characters is available whether or not the question is required, and a blank value means unlimited. An Email Text input shows its error message when the address isn't valid.

Error messages appear only after a user tries to submit, and each one clears once the user fixes that answer.

Add a submit button

A survey only records answers when a user clicks a button with Submit survey responses turned on.

1. Add a button to the step containing survey blocks.
2. Under Action, turn on Submit survey responses. The toggle only appears on steps that contain survey blocks.
3. Keep or set the button's main action, such as Next step or Dismiss.

When you add a new button to a step that has questions but no submit button, Submit survey responses is already on. Images and text links have the same toggle.

When a user clicks the button, Appcues checks the answers first. If any answer is invalid, the button's other actions don't run, so the user stays on the step until they fix it.

Until a step with questions has a submit button, the step shows the warning A submission action is required to submit the survey in this step. You can still publish, but no answers are recorded.

Send users down different paths with conditional actions

Conditional actions run a different action depending on how a user answered. For example, users who rate you 4 or 5 can go to a step asking for a review. To set one up, see Set up conditional actions in Flows 2.0 and Embeds.

Style your questions

Open a question's Design tab:

• Theme variant applies a saved survey style from your theme. See New Themes and advanced styling.
• The sections below it override the theme for this question: the title, the field or options, the description, and the error message. Rating also has Hover background and Selected background for its options.
• The Advanced tab takes custom CSS for each part of the question.

Style the error message

Error messages from required questions have their own styling sections on the Design tab. Changes you make there apply to that question only and override its theme variant.

1. Select the question on the step.
2. Open the Design tab.
3. Expand Error message to style the message users see when an answer is invalid.

To change the error message text, go to the General tab and edit Error message under Validation. See Make a question required.

Translate a survey

Question titles, descriptions, placeholders, option labels, and error messages translate like the rest of your content: inline in the builder, with XLIFF files, or with AI translation. See Translate Web Experiences.

Add, delete, and reorder options in the default language. Those controls are turned off while another language is selected.

Build or restyle a survey with Appcues AI

Ask Appcues AI to add survey questions to a Modal or Embed step, or to convert the survey in a classic Flow. It adds the questions and a submit button. It can also restyle questions, for example "give the rating options rounded corners and a blue selected background."

Appcues AI doesn't add questions to Tooltip steps or set up conditional actions. Do those in the builder.

View and export responses

1. Open the experience's analytics page.
2. Scroll to Survey Responses. Each question has its own column, labeled with its reporting name, plus Date received.
3. Filter by date range or segment.

The table shows up to 1,000 responses. To get all of them:

1. Click Export. The Export a CSV dialog opens.
2. Choose Survey.
3. Start the export. Appcues emails you the CSV.

The CSV has one row per user, with a column for each question, the user's ID, the time they submitted, and the user properties recorded when they answered.

Confirm it worked

1. Publish the experience to a test segment and complete the survey as a user.
2. Open the experience's analytics page and check that your answer appears under Survey Responses.

Troubleshooting

No responses are showing up

• Check that the step has a button, image, or link with Submit survey responses turned on. A button that only goes to the next step moves the user along without saving anything.
• Check that you're looking at the right date range, and that you haven't filtered to a segment the test user isn't in.

Users can't move past the survey step

A required question is unanswered or an answer is invalid, so the submit button won't run its other actions. Preview the step and answer each required question to find the one that fails.

I can't add an option in another language

Switch to the default language in the language dropdown. Options can only be added, deleted, or reordered there.

The responses table stops at 1,000 rows

The table shows up to 1,000 responses. Use Export to get every response.

Still stuck?

Collect the following and contact support:

• The experience URL.
• The affected user's User ID.
• Which question block isn't working, and its reporting name.
• A screenshot or screen recording of the problem.
• Any console errors from your browser's developer tools.