> For the complete documentation index, see [llms.txt](https://docs.crobox.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.crobox.com/how-to-guides/sagent/analytics/dashboard.md).

# Dashboard

Track Sagent sessions, completion, and CTA engagement over time.

Use **Dashboard** to monitor Sagent performance trends. It shows default metrics for usage, outcomes, and action-taking behavior.

### How to use Dashboard

{% stepper %}
{% step %}

#### Open the Dashboard tab

Open **Analytics** and stay on **Dashboard**.
{% endstep %}

{% step %}

#### Choose your locale and date range

Use the **Locale** filter to focus on one market or language. Use the date picker to define the period you want to review.
{% endstep %}

{% step %}

#### Review the default metrics

The Dashboard tab shows default metric cards. Use them as a quick health check.
{% endstep %}

{% step %}

#### Compare changes across cards

Do not read one metric in isolation. Check whether multiple cards move together.
{% endstep %}
{% endstepper %}

### Default metrics

Dashboard includes four default cards:

* **Sessions**
* **Completion Rate**
* **CTA Clicks**
* **Conversion Rate**

Each card includes a chart area, a short description, and a three-dot menu.

#### Sessions

This card shows the total number of user sessions. Use it to understand overall usage volume. Changes can reflect updates to prompts or product selection.

Sessions come from recorded Sagent interactions. This metric measures conversation volume, not unique shoppers or website traffic.

#### Completion Rate

This card shows the percentage of users who complete the experience. It focuses on users who reach recommendations. Drops may indicate usability issues.

Completion Rate comes from recorded conversation outcomes. Completion does not confirm that shoppers accepted a recommendation or purchased a product.

#### CTA Clicks

This card shows how often users click CTA elements. Changes can follow prompt changes. Use it to understand action-taking behavior.

CTA Clicks come from recorded clicks in Sagent conversations. They show engagement with an action, not a completed conversion or purchase.

#### Conversion Rate

This card is part of the Dashboard layout. It is currently marked as **Coming soon**.

Do not use this card for reporting until it becomes available. It does not currently provide a conversion value.

### Read Dashboard trends

Start with these checks:

1. Compare the current period with the previous one.
2. Look for shifts across more than one card.
3. Match changes to recent prompt or catalogue updates.

For example:

* **Sessions drop** and **CTA Clicks drop** — usage may be lower overall.
* **Sessions stay stable** and **Completion Rate drops** — review the flow for friction.
* **Completion Rate rises** and **CTA Clicks rise** — users may move through the experience more effectively.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

```
GET https://docs.crobox.com/how-to-guides/sagent/analytics/dashboard.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.