> 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/weekly-insights.md).

# Weekly insights

At the end of every week, Greatstore distils the week's conversations into **five insights** — a compressed digest of how shoppers used the store and how the assistant helped or struggled. The admin home surfaces the running list; **View all insights** opens the full history.

## How to use them

Each insight points at a fix somewhere else in the admin:

| Insight shape                              | Usually means                       |
| ------------------------------------------ | ----------------------------------- |
| Shoppers could not verify a product detail | A catalogue or connector gap        |
| Repeated questions about policy            | A missing knowledge source          |
| Shoppers hopping between categories        | Search or discovery needs attention |
| Guided flows completing successfully       | Working — leave it alone            |


---

# 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/weekly-insights.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.