> ## Documentation Index > Fetch the complete documentation index at: https://www.mintlify.com/docs/llms.txt > Use this file to discover all available pages before exploring further. # Analyze user engagements > Use engagement analytics to measure content actions, CTA click-through rates, user flows through your docs, and search and assistant funnels. Analytics require a [Pro or Enterprise plan](https://mintlify.com/pricing?ref=analytics). The **User engagements** view of the [analytics](https://app.mintlify.com/analytics) page shows how visitors interact with your content and calls to action. It includes interaction trends by page, common paths through your documentation, and search and assistant funnels. All cards use the time range selected for this view. Use engagement analytics to: * **Identify high-intent pages**: Pages with a high CTA click-through rate often indicate visitors who are ready to take the next step, such as signing up for your product or talking to your sales team. * **Understand which content matters**: Review high-intent pages to learn what motivates users to engage more deeply. Keep these pages up to date and consider adding related content. ## Overview The overview displays: * **Total interactions**: CTA clicks and page-level actions combined. * **Average interactions per session**: Total interactions divided by sessions with CTA, action, or page-view activity. * **CTA click rate**: CTA clicks divided by human page views, capped at 100%. Each metric includes a delta badge comparing the selected period with the preceding period of the same length. ## Actions taken over time The actions taken over time chart tracks two separate series: * **CTA clicks**: Clicks on the [primary navbar button](/docs/organize/settings-structure#navbar). Configure a `navbar.primary` button in `docs.json` to populate this series. * **Actions**: Context-menu actions, code-block copies, API playground requests, and thumbs-up or thumbs-down feedback. The table ranks pages by combined clicks and actions. It includes page views, clicks, CTA rate, actions, and action rate. CTA rate is CTA clicks divided by human page views. Action rate is actions divided by human page views. ## User flow The user flow shows the paths visitors take after entering your documentation from a selected page. The entry-point selector lists up to ten pages with the most starting sessions. The chart follows sessions through the entry page and up to three subsequent page interactions. To interpret a user flow: 1. Select an entry point. 2. Hover over a node to view the number of sessions entering it (**In**), the number continuing to another page (**Out**), and the drop-off rate when applicable. Each interaction column shows up to six named pages ranked by arriving sessions. An **Other (N pages)** node at the bottom of the column groups the remaining pages. Grouping these pages preserves onward sessions so drop-off reflects visitors who do not continue. The final interaction column does not show drop-off because the chart does not display another page after it. Use user flows to identify common navigation paths, find pages where visitors stop, and compare navigation patterns across entry points or time ranges. You do not need to configure your site. When User flow is available for your deployment, data appears after your documentation receives visitor traffic. ## User funnel The user funnel counts sessions at each stage and displays how many reached the stage or dropped off before it. Use the selector to switch between **Search-to-answer**, the default view, and **Assistant conversation**. ### Search-to-answer | Stage | Description | | -------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Opened search** | The session opened the search interface. This stage appears only for ranges beginning July 31, 2026 or later that contain search-open events. | | **Entered a query** | The session submitted a search query. | | **Clicked a result** | The session clicked a search result. | | **Landed on a page** | The session viewed the page opened from a search result. | | **Taken an action** | After landing, the session clicked a CTA or used a context-menu action, copied a code block, sent an API playground request, or submitted thumbs feedback. | Use the drop-off between stages to identify whether visitors struggle to search, choose a result, reach its page, or continue interacting after they land. ### Assistant conversation The assistant conversation funnel excludes sessions flagged as spam. | Stage | Description | | --------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------- | | **Started a conversation** | The session contained assistant activity. | | **Got an answer** | The assistant completed at least one answer in the session. | | **Asked a follow-up** | The assistant completed at least two answers in the session. | | **Engaged with the answer** | The same session contained at least one completed answer and a source click, response copy, web-search-result click, or thumbs feedback. | The engaged stage counts these events regardless of whether the interaction occurs before or after the completed answer. It does not require a follow-up. ## Related topics - [Analytics overview](/docs/analytics/index.md) - [Collect page feedback from users and AI agents](/docs/optimize/feedback.md) - [Amplitude](/docs/integrations/analytics/amplitude.md)