> For the complete documentation index, see [llms.txt](https://docs.guideflow.com/help/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.guideflow.com/help/collect-leads/get-leads-data.md).

# Get leads data

When you are using forms in your guideflow, the data collected will be displayed on your Leads tab.&#x20;

(e.g. request an email to let your user start interacting with your guideflow)

{% @guideflow/guideflow-embed requestedUrl="<https://app.guideflow.com/player/CV9zMXOBMHY>" %}

* Click on the "Leads" tab at the top of your editor.
* Select either "Start Leads" or "End Leads" depending on if you have set a start/end popup.&#x20;
* Analyze the list of leads collected and their information.
* Click on "Download" to download a CSV file with the information collected.

{% hint style="info" %}
Check out [the article about start/end popup](broken://pages/lsnSER2VhbLXgMdLl4fk) if you want to learn how to add a lead generation form to your guideflow.
{% endhint %}


---

# 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.guideflow.com/help/collect-leads/get-leads-data.md?ask=<question>&goal=<user_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.
