Form analytics and drop-off
Use Mokaform analytics to understand views, starts, completions, funnel metrics, question drop-off, time analysis, and traffic sources.
Analytics help you see where respondents arrive, start, slow down, and leave. Use them to improve completion and response quality.
PRO feature
Extended analytics are available on PRO. Free accounts can use shorter visits date ranges such as today, yesterday, last 24 hours, and last 7 days; longer visits ranges require PRO.
Core metrics
| Metric | What it means |
|---|---|
| Views | The form became visible in the browser. |
| Starts | The respondent interacted with the form. |
| Completions | The respondent submitted the form. |
| Completion rate | Completed submissions compared with views. |
| Drop-off rate | Started sessions that did not complete. |
| Completion duration | How long completed sessions took. |
A view is counted when the form is actually visible. If an embedded form sits far down a page and a visitor never scrolls to it, that visit may not count as a form view.
Funnel and page metrics
For multi-page forms, funnel metrics show how respondents move through each page.
Use page metrics to find:
- Pages where many respondents leave.
- Pages that take unusually long.
- Pages that receive views but few answers.
- Branches that are rarely reached.
When a page has high drop-off, check whether it contains too many required questions, unclear copy, sensitive fields, file uploads, payments, or a large jump in effort.
Question drop-off
Question drop-off shows where respondents get stuck at the field level.
Look for:
- A high view count with a low answer count.
- Questions that are viewed but skipped.
- Open text questions that follow easier choice questions.
- Fields that require information respondents may not have nearby.
Fixes that often help:
- Add help text.
- Make optional fields optional.
- Split a dense page into smaller pages.
- Replace long text fields with choices where possible.
- Move payment, signature, or file upload fields later in the form.
Time analysis
Time-on-page helps identify confusing sections. A slow page is not always bad; it may simply contain a long-answer question. Compare time with drop-off before changing the form.
Good signals:
- High time and high completion: people are engaged.
- High time and high drop-off: people may be confused or blocked.
- Low time and high drop-off: people may not understand the value or may hit friction immediately.
Traffic sources and device data
Mokaform can use respondent session metadata to help explain performance by context.
Useful dimensions include:
- Referrer.
- Device type.
- Browser.
- Operating system.
- Country.
- Browser language.
Use this to compare channels. For example, mobile social traffic may need a shorter form than desktop traffic from an email campaign.
What is not tracked
Mokaform avoids counting some events to keep analytics meaningful.
- Bot-like sessions may be excluded from tracking.
- Answer edits are not counted as new answers.
- Completed forms do not create abandonment events after submission.
- Initial page and question reach events are ordered after the respondent starts interacting.
Improve a weak completion rate
Check whether the problem is traffic quality, first-page clarity, or later-page friction.
Review the highest drop-off page and the first unanswered question on that page.
Remove non-essential required fields.
Add context before sensitive questions.
Test the form on mobile and publish the improved version.
Compare analytics after a meaningful number of new responses.
What to explore next
View form responses
Review Mokaform response summaries, inspect individual submissions, download PDFs, export data, analyze answers, and manage uploaded files.
Integrations and notifications
Connect Mokaform submissions to notifications, Google Sheets, Airtable, Notion, Jira, Linear, Asana, webhooks, Zapier, and Make.