📋Submissions
Read every response to a Dapta Form in one table: the Submitted, Status and Score columns plus one column per question, the All, Completed and Partial filters, pagination, deleting a row and exactly w
Submissions is the response table for a single form. It shows one row per person, newest first, with the answers spread across the columns. This page explains how to read it, how to narrow it down and what Dapta Forms keeps with each response.
Step 1: Open the form and click the Submissions tab (or pick the form from Submissions in the left menu). The header reads Submissions / Every response to this form.
Submitted
The date and time of the response, shown in your own timezone. For a completed response it is the moment it was finished; for a partial one it is the moment it was captured.
Status
Completed (the person reached the end) or Partial (the answers were saved before the end).
Score
The total points collected from the answers. It is 0 when the form has no scoring. See Scoring.
One per question
The header is the question text itself. An answer with several picks is joined with commas, and a question the person never reached is left blank.
Choice answers show the option Value, not the label on screen. If you want the table to read the way the question does, set matching labels and values in Question settings.
💡 Tip: A form with many questions makes a wide table. The table scrolls sideways inside its own frame, so drag it left and right to reach the last columns. The page itself never scrolls sideways.
Step 2: Narrow the list with the filter chips above the table: All, Completed or Partial.
A Partial row appears when your form has a Partial submit point and someone passed it without finishing. The row holds everything they had answered up to that moment, and the later columns stay empty. If that same person comes back in the same browser tab and finishes, the row is not duplicated: it is upgraded in place and its status flips to Completed. Read Partial submissions to set the capture point.
Step 3: Move through the pages. The table shows 25 responses per page. The counter under the table tells you which rows you are looking at and how many match the current filter, and Previous / Next step between pages. The filter stays applied while you page.
Step 4: To remove a response, click Delete at the end of its row and confirm in the Delete submission dialog.
⚠️ Note: Deleting a row removes it from the table, from the CSV export and from the counts on Analytics. It does not remove anything that was already sent to HubSpot or to a webhook.
What is stored with a response
Each row keeps only what it needs to be useful:
Every answer the person gave, under the field key of its question.
The Score, if the form has scoring.
The moment the person started and the moment they completed, plus the moment of the partial capture when there is one.
The
utm_*values that were in the link they arrived from. These travel inside the stored answers, so they reach HubSpot and your webhooks, but they are not columns in the table or in the export.
Dapta Forms does not record the respondent's IP address, browser or device, country or referring website. If you want to know where a response came from, put that information in the link with UTM parameters or with hidden fields and URL prefill.
There is no detail view for a single response: long answers are truncated in their cell, so hover the cell to read the whole thing in a tooltip, or export to CSV.
When there is nothing yet
A form nobody has answered shows No submissions yet / Responses will show up here as people complete the form. Publish the form, share its link, and the first row appears as soon as someone gets through it.
What's next
Export to CSV: the same rows as a spreadsheet file.
Analytics: how many people opened the form and where they stopped.
Security & Privacy: what Dapta Forms stores and who can see it.
Last updated