> For the complete documentation index, see [llms.txt](https://docs.hackle.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hackle.io/en/data/example/funnel-example.md).

# Funnel Analysis Example

Examples of analyzing drop-off points at each conversion step.

User funnel analysis can answer the questions below.

### Product acquisition

* **What percentage of users converted through the sign-up acquisition path within 7 days?**
* **How did the sign-up conversion rate change after a major update?**

### Product usability

* **At which step of the sign-up acquisition path do most users drop off?**
* **How many users convert to a purchase after accessing the service?**
* **Which path do users take to reach payment?**
* **Which area should we improve first to increase revenue?**

### Payment and revenue

* **How did the payment funnel conversion rate change in specific regions such as Japan or the United States?**
* **Which path has the highest payment funnel conversion rate?**
* **Where in the purchase process do users drop off the most?**


---

# 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.hackle.io/en/data/example/funnel-example.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.