> For the complete documentation index, see [llms.txt](https://docs.formsort.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.formsort.com/analytics-and-attribution/built-in-analytics.md).

# Built-in analytics

Besides sending event data to your existing analytics tools, Formsort offers some built-in analytics tools to help identify performance bottlenecks and areas for improvement.

{% hint style="info" %}
Built-in analytics only measure traffic in production environments. 
{% endhint %}

## Variant performance

Accessing **Analytics** from the flow index page will show the conversion rate of the different variants within a flow.

Note that the notion of *conversion* is rather simple at this time: it is the measure of the ratio of the `FlowFinalized` to the `FlowLoaded`event, per responder UUID for a given variant, regardless of the path taken through the flow.

The default view shows this percentage.

![](/files/-MTwfubCfVZVBpqoN-q7)

Switching to the **raw** tab will show the raw numbers of users that have loaded variants within this flow:

![](/files/-MTwggYOBYlvAHHpp4OB)

The analytics are an aggregate: Completion rate is calculated on a per-responder basis. If the same responder loads the same flow twice, that is counted as a single flow load.

## Step performance

By accessing **Analytics** from *within a flow*, the performance of the steps in that flow will be shown in a table, including the step completion rate (aka the dropoff per-step).

![](/files/-MTxcHJXsi-5NeTzKIuI)


---

# 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.formsort.com/analytics-and-attribution/built-in-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.