> For the complete documentation index, see [llms.txt](https://docs.feathery.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.feathery.io/platform/launch-forms/analytics.md).
# Analytics
Track your core form conversion metrics natively in Feathery to understand how users interact with your forms.
Feathery has native analytics for tracking user form submissions, views, conversion, and drop-off over the entire form and on a per-step basis. Understand how your users are interacting with your forms.
Below is a list of a few metrics natively tracked within Feathery for each of your forms:
**New Submissions** - the # of new users who have submitted a step of your form over a period of time. This includes partial submissions.
**Step-by-Step Funnel Drop-Off:** The % of users that go through each step of your form (ex: 100% of users start at Step 1, then only 70% of those move to Step 2, 50% to Step 3, etc)
**New Viewers** - the # of new users who have viewed your form over a period of time.
**Average Time** - time (in seconds) that it takes on average for your users across a period of time to complete the form. This time is measured as the difference between when they first started the form and when they complete the form.
**Average Completion Rate** - the # of form completions divided by the # of new form sessions over a period of time.
---
# 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.feathery.io/platform/launch-forms/analytics.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.
