> For the complete documentation index, see [llms.txt](https://docs.luciq.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.luciq.ai/kmp/setup-luciq-for-kmp/setup-application-performance-monitoring/flows-and-ui-traces.md).

# Flows & UI Traces

Measure user journeys with named APMKmp flows and flow attributes in your KMP app, and track screens or modals with manual or automatic UI traces.

### Flows (user journeys)

Start and end named flows to measure how long users spend on a journey:

{% code title="Kotlin" %}

```kotlin
APMKmp.startFlow("checkout")
// ... user goes through checkout ...
APMKmp.endFlow("checkout")
```

{% endcode %}

Add attributes to a flow for filtering or segmentation:

{% code title="Kotlin" %}

```kotlin
APMKmp.setFlowAttribute("checkout", "payment_method", "card")
APMKmp.setFlowAttribute("checkout", "discount", null)  // remove attribute
```

{% endcode %}

### UI traces

Track a named UI operation (e.g. a screen or modal):

{% code title="Kotlin" %}

```kotlin
APMKmp.startUITrace("SettingsScreen")
// ... screen is visible ...
APMKmp.endUITrace()
```

{% endcode %}

Only one UI trace is active at a time; `endUITrace()` ends the current one.

### Automatic UI traces

You can enable or disable automatic UI trace tracking:

{% code title="Kotlin" %}

```kotlin
APMKmp.setAutoUITraceEnabled(true)
```

{% endcode %}


---

# 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.luciq.ai/kmp/setup-luciq-for-kmp/setup-application-performance-monitoring/flows-and-ui-traces.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.
