> ## Documentation Index
> Fetch the complete documentation index at: https://docs.flashduty.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Behavior analytics

> Behavior analytics turns the clicks and page views RUM already captures into a product view, answering with funnels, heatmaps and page paths where users drop off, what they click, and where they go next.

Behavior analytics turns the clicks and page views the SDK captures into a product view, to answer three questions: where users drop off, what they click on a page, and where they go after leaving it.

## Supported applications

Behavior analytics is available for **Web** and **Electron** applications only. Selecting an application of another type shows a notice that the application isn't supported yet and points you at a Web or Electron application.

Click data comes from the SDK's automatic click capture, so a Web or Electron application collects it as soon as the SDK is integrated; an element's name is taken from the text of the element that was clicked. If clicks on a page are missing, check the SDK's user-interaction capture first — see [Web SDK data collection](https://docs.flashduty.com/en/rum/sdk/web/data-collection.md).

## Where it lives

Select **Behavior analytics** in the RUM console's left menu; it opens on **Funnels**. Three tabs sit at the top, and **Events** at the top right is a page of its own:

| Page | What it's for | Details |
| - | - | - |
| **Funnels** | Put 2 to 10 steps in order and read arrival, conversion and drop-off at each | [Funnels](https://docs.flashduty.com/en/rum/behavior-analysis/funnel.md) |
| **Heatmaps** | See the click distribution, element click ranking and scroll depth on one page | [Heatmaps](https://docs.flashduty.com/en/rum/behavior-analysis/heatmap.md) |
| **Paths** | See which pages users visited before and after a page | [Paths](https://docs.flashduty.com/en/rum/behavior-analysis/paths.md) |
| **Events** | Define autocaptured clicks as business events for funnel steps to reference | [Events](https://docs.flashduty.com/en/rum/behavior-analysis/events.md) |

Switching tabs keeps the selected application and time range. Switching applications is a fresh query: the previous application's results and unsaved drafts don't carry over.

## Permission

Behavior analytics is gated by the RUM permission **Behavior analytics read**. Without it the menu entry doesn't appear. See [Permission design](https://docs.flashduty.com/en/platform/permission-design.md) for the full list of permission points.

## Where the data comes from

* **Page views**: views reported by the SDK, grouped by page path. One path with different query parameters is one page.
* **Clicks**: clicks the SDK captures automatically, carrying the page, element text, selector and click position.
* **Custom events**: actions reported from code through `addAction`, matched on the reported name.
* **Click map backdrop**: the heatmap's click map is drawn over a session replay frame, so it depends on replay data. Replay sampling rate is set in **Application settings** — see [Session replay SDK configuration](https://docs.flashduty.com/en/rum/session-replay/sdk-config.md).

Event rules match the raw clicks at query time and never rewrite stored data, so a new or edited event applies to historical data immediately, with nothing to re-report.

## Sampling on large ranges

On a large query the console samples by session and says so in place: the funnel and path pages state the share of sessions the estimate is based on, and the heatmap converts its click counts back to the whole population. When you see one of these notices the counts are estimates: the proportions still hold, but a single number shouldn't be used for exact comparison.

## Known limits

* Only Web and Electron applications offer the click map and scroll depth. The element ranking doesn't depend on replay and works as usual.
* Click positions are only collected from the day the SDK started reporting them; earlier clicks count in the element ranking only.
* Elements with fewer than 100 clicks get no frustration-click or post-click error rate, and the table labels them **Small sample**.
* When the time range is shorter than the conversion window, funnel conversion is understated and the console says **The conversion window is longer than the time range**.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.