Publish the form
Use a public or protected form so respondent activity can begin.
Form analytics
KinoForms keeps form analytics close to the builder and submission review flow so teams can see what is live, what is being started, and where response activity needs attention.
Problem
Views, starts, submissions, and completion signals are easier to act on when the team can move from the metric back to the form and submitted records.
KinoForms focuses on practical activity signals inside the workspace that owns the form.
Use cases
These examples keep the page focused on narrow form-workflow intent instead of broad form-builder copy.
Workflow steps
Use analytics to see which forms are active, which paths need attention, and where review teams should focus.
Use a public or protected form so respondent activity can begin.
Track starts, submissions, completion patterns, trends, and top forms.
Move from analytics back to the form, submissions, and review context.
Concrete examples
If starts rise but submissions remain low, the team can revisit conditional sections or required fields.
If one form dominates workspace activity, reviewers can prioritize that submission queue.
Event teams can monitor starts and submitted registrations as a deadline approaches, then inspect the underlying attendee records.
Related pages
Follow activity into submitted records and review context.
Keep analytics inside the workspace that owns each form.
Use analytics on a time-sensitive registration workflow.
Track application volume and review load for a program workflow.
Connect analytics-aware workflows to narrow submission integrations.
FAQ
The public pages describe practical activity signals such as views, starts, submissions, completion rate, trends, and top forms.
Yes. The analytics page frames metrics around the workspace that owns the form workflow.
Next step
Use analytics to see which forms are active, which paths need attention, and where review teams should focus.