Build and publish a Feedback Page
Create a multi-question form, review its settings, and verify a submitted answer set.
Feedback Pages are multi-question forms hosted at /f/<organization-slug>/<page-slug>. They have a separate editor, response list and analytics from single-event widgets.
Create the form
- Open Feedback Pages and choose the brand.
- Start a new form, clone an existing one or import from Google Forms.
- Add questions, or describe the form to the AI builder and review the generated questions before saving.
- Edit prompts, descriptions, answer options, required flags and validation. Reorder questions to match the respondent's task.
- Preview the complete form, including narrow screens and the final submission.
AI output is a draft for review. Check question types, wording, scales, answer options and required fields. The question-type reference explains the 18 question and layout types.
Choose the respondent experience
Settings includes the title, description, URL slug, brand, introduction Markdown, submit-button text and thank-you behavior. Display modes are all questions or one question at a time. In the step-by-step layout, section headings travel with the associated question rather than becoming empty answer steps.
Review Require contact info, Allow anonymous and Single submission together. Single submission is a browser/session-oriented control, not proof that each human can respond only once. A dedicated email question is separate from the form-level respondent contact fields.
Publish deliberately
- Draft: not publicly accessible.
- Published: the public form can collect responses, subject to its submission controls.
- Archived: the public form is no longer accepting responses.
Save the form, publish it and submit a sample through the public URL. Open Responses and switch between Summary charts and the Table of individual responses. A respondent's autosaved draft is not a submission and will not appear as a completed response.
Review and export responses
The Responses tab shows total responses, page views and the response-to-view conversion rate. The Table view loads responses in batches. Use Load more to fetch additional rows before exporting: Export CSV exports the rows currently loaded in the table, not an automatic export of every historical response. Check the row count when preparing a complete export.
Reuse carefully
Cloning creates another form rather than moving historical responses. When editing a form already in use, keep the meaning of existing questions stable: replacing a question's purpose can make old answers difficult to interpret. Create a new form for a substantially different survey.
A shared form opened from another brand may create that brand's own copy when edited. Read the editor's copy notice before saving. See sharing and embedding and private sharing for the access differences.