> For the complete documentation index, see [llms.txt](https://guides.apxor.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://guides.apxor.com/product-guides/analytics/paths.md).

# Paths

With Apxor’s Path Analysis visualize user flows in the app. You can check the paths that users took before uninstall, activation, conversion, feature discovery or drop offs. ​

The sunburst style view helps you know how users are exploring the app. Additionally, get to know the number of users who move from one step to another in a selected path when you hover or click on any flow.​

<figure><img src="/files/tGZrWU4vAH1Qk8mD18S7" alt=""><figcaption></figcaption></figure>

## Choosing Events

You can now choose a From Event or a To event.​ For example: Paths from Start Practice or Paths to App Uninstall etc.​

<figure><img src="/files/zoefm1tlJ9TqiDluwpCf" alt=""><figcaption></figcaption></figure>

Now, choose any event properties that you wish to apply here. ​

**Example:** Paths taken by users who activated Margin Plus on Mondays.​

<figure><img src="/files/tZJ0KCfqKGK6gc9cKABY" alt=""><figcaption></figcaption></figure>

Now just click on submit to be able to visualise the paths according to your Selected conditions.​


---

# 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://guides.apxor.com/product-guides/analytics/paths.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.