# Flow Analytics

Flow Analytics lets you map and visualize visitor journeys through your site by defining a sequence of steps and comparing how different audiences move through them.

{% hint style="warning" %}
Flow Analytics is currently in **BETA**. Features and UI may change as the product evolves.
{% endhint %}

\
Overview

The Flow Analytics page has two main sections:

* **Flow Settings** — Where you configure the audience(s) and journey steps to analyze.
* **Analytics** — Where the resulting flow visualization and data appear after you generate the flow.

### Key Concepts <a href="#key-concepts" id="key-concepts"></a>

| Term          | Meaning                                                                                                 |
| ------------- | ------------------------------------------------------------------------------------------------------- |
| **Flow**      | A defined sequence of visitor steps (e.g., Homepage → Product Page → Cart → Checkout).                  |
| **Flow Step** | A single point in the journey, defined by a URL visit or event.                                         |
| **Audience**  | The visitor segment whose journey you want to analyze. You can compare multiple audiences side by side. |
| **Drop-off**  | The percentage of visitors who leave the flow at each step.                                             |

### Getting Started <a href="#getting-started" id="getting-started"></a>

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

{% stepper %}
{% step %}

### Select an Audience

In the **Audience** section, click the **Choose Audience** dropdown and select the visitor segment you want to analyze. To compare audiences, click **Add Another Audience** and select a second segment.
{% endstep %}

{% step %}

### Define Flow Steps

In the **Flow Steps** section, build your journey:

1. Each step has three parts:
   * **Condition type** — What to match (e.g., "Visited URL").
   * **Operator** — How to match (e.g., "contains").
   * **Value** — The specific URL pattern or event name to match.
2. Click **Add Condition** to add an alternative condition to the same step (OR logic).
   {% endstep %}

{% step %}

### Generate the Flow

Click **Generate Flow** to run the analysis. The platform will calculate how your selected audience(s) move through the defined steps and display the results in the **Analytics** section below.
{% endstep %}

{% step %}

### Review the Analytics

The Analytics section displays flow data showing:

* The number and percentage of visitors who reached each step.
* Drop-off rates between steps.
* Side-by-side comparisons if you selected multiple audiences.
  {% endstep %}
  {% endstepper %}

{% hint style="info" %}
Start with a simple 3-4 step flow to get a quick overview, then add more steps to drill into specific journey segments.&#x20;
{% endhint %}

<br>


---

# Agent Instructions: 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:

```
GET https://docs.abtasty.com/adaptivecx/getting-started/analyze/flow-analytics.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
