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.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:
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 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.
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.