For the complete documentation index, see llms.txt. This page is also available as Markdown.

πŸ“Š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.

The Analytics page header with the All time, Today, Last week, Last month, Last year and Custom range chips
Every number and chart on the page follows the range you pick here.
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.

The Custom range fields with a From and To date picker open on a calendar and the Apply button beside them
Custom adds From and To fields. Nothing changes until you click Apply.

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.

The Analytics metric cards showing Views, Starts, Submissions, Completion rate, Time to complete and Partial submits
The funnel, left to right, with Completion rate and Partial submits highlighted.
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.

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.

The Trends chart with the Metric select open showing Views, Starts, Submissions, Completion rate and Time to complete
Switching the metric is instant: the chart already has every series for the range.

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.

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
Each row loses a few people. The biggest loss is the question to fix first.
  • 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 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.

The Analytics page with a custom range selected and the No activity in this range message
Nothing happened in these dates. The form itself is fine.

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.

The Analytics page of a form nobody has opened, showing the No data yet message
A brand new form, before its first visitor.

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

Last updated