---
title: "How to view scenario button interaction statistics?"
description: "The Button interactions tab in native statistics: KPIs, charts, button table, and filters for scenario analysis."
---

# How to view scenario button interaction statistics?

When you need to see which menu items and inline buttons clients actually press in the bot, open the **Button interactions** tab in native statistics. It shows aggregated metrics without manual log merging.

## When you need this

- Analyze button popularity in a scenario (menus, inline, reply).
- Compare channels: where clients press buttons more often.
- Check behavior after changing button labels or menu structure.
- Prepare scenario optimization: which branches are rarely used.

## What to know

- The tab shows **accepted button presses** during scenario execution (inline callback, reply text match, contact, location).
- It does **not** track clicks in Constructor, Operator Panel, or “open link” buttons when Engine does not receive an event back.
- The tab stays **hidden** until an administrator enables it in instance settings.
- Data collection is a separate toggle: without it, new presses are not recorded, and history from before it was enabled is not restored.
- The report period is **up to 90 days**; raw events are kept for 90 days (configurable).

## Before you start

- [x] You are signed in as supervisor, analyst, or administrator.
- [x] Native statistics is enabled on your instance (**Statistics** → **Main statistics**).
- [x] An administrator enabled the **Button interactions** tab in instance settings.

## Step-by-step

1. Open **Menu → Statistics**.
2. Go to **Main statistics**.
3. Select the **Button interactions** dashboard tab (if missing, contact your administrator).
4. Set **Date**, **Bot**, **Channel**, and other top filters, then click **Apply filters**.
5. Review KPI blocks:
   - **Total interactions** — sum of button presses for the period and filters.
   - **Unique users** — count of distinct clients (no personal data in the report).
6. Chart **Interactions over time** — trend by day (day boundaries follow the filter time zone).
7. **By channel** and **By confirmation type** — breakdown by messenger and how the press was recognized.
8. Table **Buttons** — per-button detail. A switch sits above the table:
   - **By button** (default) — one row per button: Translation ID, button name, section, source node, interactions, unique users, interactions per user. An inline and a reply button with the same translation are one row.
   - **By text** — one row per button caption; the **Buttons** column shows how many different buttons share that caption. Buttons without a caption go to the **(no label)** row.
   - Extra tab filters: **Section ID**, **Source node**, **Translation ID**, **Button**, **Language**, **Certainty**.

<!-- screenshot: Button interactions tab — KPIs, chart and the Buttons table with the By button / By text switch -->

9. If the selected period is longer than 90 days, the cards do not load and the message **Select a period of up to 90 days** appears instead — shorten the date range.

## Reading confirmation type

| Value | Meaning |
|-------|---------|
| **confirmed_click** | Structured callback, contact, or location — Engine recognized the button unambiguously |
| **matched_selection** | Reply button text matched the expected option |

## For administrators (enabling the feature)

In **Instance settings → Feature flags**, category **System**:

1. **Button interaction tracking** (`ff_button_interaction_tracking`) — record new presses.
2. **Button interactions statistics** (`ff_statistics_button_interactions`) — show the “Button interactions” tab to supervisors and analysts.
3. **Button interaction retention (days)** (`ff_button_interaction_retention_days`) — how many days raw events are kept (default 90; a new value applies to new events; a non-number or a value below 1 means 90).

After tracking is turned on, presses are not recorded right away: a background job first prepares the indexes, which usually takes a few minutes. If the tab still shows no new data after an hour, contact support.

Recommended rollout: enable collection first, validate data, then open the tab. See [Configure instance settings](/en/settings/how-to/configure-instance.md).

## Related materials

- [Statistics metrics reference](/en/statistics/reference/statistics-metrics.md) — definitions for this tab
- [View Metabase dashboards](/en/statistics/how-to/view-dashboards.md) — other statistics tabs
- [Appeals duration and reaction metrics](/en/statistics/how-to/view-appeals-duration-and-reaction-metrics.md) — SLA on the Appeals tab