> 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/dapta-forms/results/analytics.md).

# Analytics

Measure a Dapta Form: pick a date range, read the Views, Starts, Submissions, Completion rate, Time to complete and Partial submits cards, follow the Trends chart and find the question people abandon

**Analytics** answers two questions about one form: how many people got through it, and where the rest gave up. The header reads **Analytics** / **Funnel performance and question-by-question drop-off.**

***

**Step 1:** Open the form and click the **Analytics** tab (or pick the form from **Analytics** in the left menu). Choose the period you want with the range chips: **All time**, **Today**, **Last week**, **Last month**, **Last year** or **Custom**.

<figure><img src="https://3835013762-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FCy5rSNtQmtqYCGzJlNEB%2Fuploads%2Fgit-blob-c8b77091e72c73f9f3ba355ad4f36646ded6d155%2Fforms-analytics-01-range-chips.png?alt=media" alt="The Analytics page header with the All time, Today, Last week, Last month, Last year and Custom range chips"><figcaption><p>Every number and chart on the page follows the range you pick here.</p></figcaption></figure>

| Chip           | Period it covers                                            |
| -------------- | ----------------------------------------------------------- |
| **All time**   | Everything since the form was created. This is the default. |
| **Today**      | The current day.                                            |
| **Last week**  | A rolling window of the last 7 days, ending today.          |
| **Last month** | A rolling window of the last 30 days, ending today.         |
| **Last year**  | A rolling window of the last 365 days, ending today.        |
| **Custom**     | The exact **From** and **To** dates you choose.             |

**Step 2:** For a specific period, click **Custom**, pick a **From** date and a **To** date in the calendar, then click **Apply**.

<figure><img src="https://3835013762-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FCy5rSNtQmtqYCGzJlNEB%2Fuploads%2Fgit-blob-77b23ff4c7fb0fe4a03de7e51e40b674a45a8f08%2Fforms-analytics-05-custom-range.png?alt=media" alt="The Custom range fields with a From and To date picker open on a calendar and the Apply button beside them"><figcaption><p><strong>Custom</strong> adds <strong>From</strong> and <strong>To</strong> fields. Nothing changes until you click <strong>Apply</strong>.</p></figcaption></figure>

You can leave one side open: a **From** with no **To** runs up to now. If you enter the dates the wrong way around, they are swapped for you.

> **⚠️ Note:** Days are counted in UTC, not in your local timezone. That is deliberate: it means you and a colleague in another country read the same number for the same range. A response late in your evening may therefore land in the next UTC day.

***

**Step 3:** Read the metric cards. They sit above everything else and summarise the range in one line.

<figure><img src="https://3835013762-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FCy5rSNtQmtqYCGzJlNEB%2Fuploads%2Fgit-blob-b0c0dcfe6eebb5c0155ddd183591ceb0a3eb8de0%2Fforms-analytics-02-metric-cards.png?alt=media" alt="The Analytics metric cards showing Views, Starts, Submissions, Completion rate, Time to complete and Partial submits"><figcaption><p>The funnel, left to right, with <strong>Completion rate</strong> and <strong>Partial submits</strong> highlighted.</p></figcaption></figure>

| Card                 | What it counts                                                                                                                                                                              |
| -------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Views**            | People who opened the form. Counted once per browser session, so a refresh is not a second view.                                                                                            |
| **Starts**           | People who reached the first question. On a form with a cover screen, the gap between **Views** and **Starts** is how many people never clicked past the cover.                             |
| **Submissions**      | Responses that reached the end and were submitted.                                                                                                                                          |
| **Completion rate**  | **Submissions** divided by **Starts**, as a percentage. It is blank when nobody started in the range, because there is nothing to divide by.                                                |
| **Time to complete** | The median time from opening the form to submitting it, written as seconds, minutes and seconds, or hours and minutes. It is blank when no completed response in the range can be measured. |
| **Partial submits**  | Responses saved at the **Partial submit point** that never reached the end. See [Partial submissions](/dapta-forms/builder/partial-submissions.md).                                         |
| **Bookings**         | People who booked a meeting from a **Scheduler** step. This card only appears when there is at least one booking, so a form without a scheduler never shows a permanent zero.               |

***

**Step 4:** Follow **Trends** / **Daily movement over the selected range.** to see how the form performed day by day. Use the **Metric** select to switch between **Views**, **Starts**, **Submissions**, **Completion rate** and **Time to complete**.

<figure><img src="https://3835013762-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FCy5rSNtQmtqYCGzJlNEB%2Fuploads%2Fgit-blob-e6b519deecc773a7022bdf50eed69f519082f8aa%2Fforms-analytics-03-trends.png?alt=media" alt="The Trends chart with the Metric select open showing Views, Starts, Submissions, Completion rate and Time to complete"><figcaption><p>Switching the metric is instant: the chart already has every series for the range.</p></figcaption></figure>

Days with no activity are drawn as zero rather than skipped, so a flat stretch really means a quiet stretch. A range that covers a single day shows a single point. When the range holds no activity at all, the chart is replaced by **No activity in this range yet.**

***

**Step 5:** Scroll to **Question-by-question drop-off** / **How many people reach each step, and how many leave.** to find where people stop.

<figure><img src="https://3835013762-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FCy5rSNtQmtqYCGzJlNEB%2Fuploads%2Fgit-blob-960b995fb34bd9fddd243337ecca2a268209b39e%2Fforms-analytics-04-dropoff.png?alt=media" alt="The question-by-question drop-off table with a row per step, a bar showing how many people reached it and the number lost at each step"><figcaption><p>Each row loses a few people. The biggest loss is the question to fix first.</p></figcaption></figure>

* The first row is **Form views** on a form without a cover screen, or **Cover / landing** on a form that has one.
* Then comes one row per question, in order, with its position marked next to the question text.
* **Views** counts the people who reached that step; the bar makes the shape of the funnel visible at a glance.
* **Drop-off** shows how many people were lost between the previous row and this one, with that loss as a percentage. A row nobody left shows `0`.

On a [one-page form](/dapta-forms/builder/one-page-layout.md) the middle column is titled **Answered** instead of **Views**, and the subtitle changes to **How many people answer each question, and how many stop there.** Every question is on screen from the start there, so counting views per question would tell you nothing.

***

## The two empty states

The page tells you which kind of empty you are looking at.

**No activity in this range** / **This form has data, just not in the dates you picked. Try a wider range.** The form has responses, just none inside the dates you selected. Widen the range or switch back to **All time**.

<figure><img src="https://3835013762-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FCy5rSNtQmtqYCGzJlNEB%2Fuploads%2Fgit-blob-4b59c019ac230b7368530d43307e04dae1644a95%2Fforms-analytics-06-empty-range.png?alt=media" alt="The Analytics page with a custom range selected and the No activity in this range message"><figcaption><p>Nothing happened in these dates. The form itself is fine.</p></figcaption></figure>

**No data yet** / **Once people open and fill out this form, the funnel and drop-off will appear here.** Nobody has opened this form at all. Publish it and share its link.

<figure><img src="https://3835013762-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FCy5rSNtQmtqYCGzJlNEB%2Fuploads%2Fgit-blob-61764d4230f59fdb073231fb156190faad32e34f%2Fforms-analytics-07-no-data.png?alt=media" alt="The Analytics page of a form nobody has opened, showing the No data yet message"><figcaption><p>A brand new form, before its first visitor.</p></figcaption></figure>

***

## What Analytics does not show

There is no breakdown by outcome, no average score, and no device, browser or country reporting. Dapta Forms does not record those things about your respondents. To segment by traffic source, add `utm_*` parameters to the links you share: they are stored with each response and forwarded to HubSpot and your webhooks.

## What's next

* [Submissions](/dapta-forms/results/submissions.md): the individual answers behind these numbers.
* [Export to CSV](/dapta-forms/results/export-csv.md): take the responses into a spreadsheet.
* [Partial submissions (lead capture point)](/dapta-forms/builder/partial-submissions.md): capture the leads counted under **Partial submits**.
* [Scheduler step & Calendly](/dapta-forms/connect/scheduler-and-calendly.md): the step behind the **Bookings** card.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.dapta.ai/dapta-forms/results/analytics.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.