> For the complete documentation index, see [llms.txt](https://docs.maker.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.maker.co/maker-greatstore/insights-and-usage/usage.md).

# Usage

The metrics behind your store, over any date range, with credits split by mode.

**Usage** is where you see what your store did over a stretch of time: how much it was used, by how many shoppers, and what that cost. Credits themselves are explained in [Credits](/maker-greatstore/insights-and-usage/credits.md).

## What you can measure

Five metrics run down the left. Each shows its total for the range you picked, with a small trend line under it.

| Metric            | What it counts                    |
| ----------------- | --------------------------------- |
| **Credits**       | What your store spent             |
| **Conversations** | Distinct chat sessions            |
| **Users**         | Distinct shoppers                 |
| **User messages** | Messages sent by shoppers         |
| **Voice minutes** | Time spent in voice conversations |

Select one and it opens as a full chart, with the previous period behind it so you can see direction as well as level.

## Credits by mode

On the **Credits** chart you can split the spend by how it was incurred: **All**, **Text**, **Voice**, or **Image**. This is the view to reach for when the bill is higher than you expected, since it tells you which kind of conversation is responsible before you change anything. How each mode is metered is covered in [Credits](/maker-greatstore/insights-and-usage/credits.md).

The other four metrics count one thing each, so they chart on their own.

## Controls

| Control                  | Effect                                                                                                  |
| ------------------------ | ------------------------------------------------------------------------------------------------------- |
| From / To                | The date range everything on the screen is measured over                                                |
| Incremental / Cumulative | **Incremental** shows each bucket on its own; **cumulative** shows the running total across the period. |
| Daily / Hourly           | How wide each bucket is                                                                                 |

## Tool usage

The assistant works by calling tools: searching the catalogue, looking up a product, invoking an app. The **Tool usage** tab ranks the tools, apps, and connectors it called most over the same range, so you can see what it leans on. To see the tools used in a single conversation, open that conversation in **Chats**, where each transcript shows the steps the assistant took.

{% hint style="info" %}
The split by mode is the useful view for cost control; the tool breakdown is the useful view for understanding *what the assistant is actually doing* with those credits.
{% endhint %}


---

# 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.maker.co/maker-greatstore/insights-and-usage/usage.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.