> For the complete documentation index, see [llms.txt](https://docs.dapta.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.dapta.ai/dforms/results.md). # Submissions & Analytics Where the answers to your dForms land. Read them question by question in Summary or row by row in Responses, filter them, download them as a CSV, and measure views, completion and drop-off under Analy Every time someone opens, starts or finishes one of your forms, dForms records it. Two screens turn that into something you can use: **Submissions** holds the answers, and **Analytics** shows how many people got through and where they stopped. **Submissions** has two views, side by side under the page title: **Summary** reads the answers question by question, and **Responses** lists them row by row. Both screens always belong to **one** form. There is no combined inbox across forms, so the first thing you do is pick which form you want to read. *** ## Two ways in **From the left menu.** Click **Submissions** or **Analytics** in the sidebar and you get a picker: one card per form, with a quick figure on each (the number of submissions, or the completion rate). Click **View submissions** or **View analytics** to open that form.

The Submissions picker listing every form in the workspace with a submission count on each card — **Submissions** and **Analytics** in the sidebar open a picker: choose the form you want to read.

**From a form's pages.** On a form's **Submissions** and **Analytics** pages, the tab strip at the top moves you between **Edit**, **Analytics** and **Submissions** without going back to the list. **Back to forms** returns to the full list.

The top of a form's Submissions page: Back to forms, the Edit, Analytics and Submissions tabs with Submissions active, the Summary and Responses views and the Workspace timezone field — The same three screens for one form, one click apart. Inside **Submissions**, **Summary** and **Responses** are two views of the same answers.

> **💡 Tip:** The **Forms** list also has **Submissions** and **Analytics** links on every row, so you can jump straight from the list to the responses of a specific form. *** ## In this section * [Submissions](/dforms/results/submissions.md): the **Responses** table, the response panel, full screen, rows per page, selecting and deleting rows, and exactly what is stored with each answer. * [Summary](/dforms/results/summary.md): one card per question, with option shares, slider averages, the latest text answers and a search for each question. * [Filter & sort responses](/dforms/results/filter-and-sort.md): filter by date, status, score or answer from the column headings, and sort by date or score. The same filter drives **Summary** and the CSV. * [Uploaded files](/dforms/results/uploaded-files.md): open, preview and download the files people attached to a **File upload** question. * [Export to CSV](/dforms/results/export-csv.md): download the filtered responses, or only the rows you selected, as a spreadsheet, with the full column list. * [Analytics](/dforms/results/analytics.md): date ranges, the metric cards (**Views**, **Starts**, **Submissions**, **Completion rate**, **Time to complete**, **Partial submits**), the **Trends** chart and the question-by-question drop-off table. Every date on these screens is read in your **Workspace timezone**, which the whole workspace shares. See [Workspaces](/dforms/account/workspaces.md#workspace-timezone). ## What's next * [Partial submissions (lead capture point)](/dforms/builder/partial-submissions.md): save answers before someone reaches the end. * [Scoring](/dforms/logic/scoring.md): where the **Score** column comes from. * [Webhooks](/dforms/connect/webhooks.md) and [HubSpot](/dforms/connect/hubspot.md): push each response somewhere else as it arrives. --- # 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.dapta.ai/dforms/results.md?ask=&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.