> For the complete documentation index, see [llms.txt](https://docs.codegiganten.de/plugin-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.codegiganten.de/plugin-documentation/en/apps/search-intelligent-and-ai-optimized/feedback-and-commander.md).

# Feedback, support and cogi Commander

Feature board, support dialog, news and the search key figures in cogi Commander.

This page describes the buttons at the top of the plugin dashboard through which you give us feedback, get help and read news, as well as the connection to cogi Commander. You need it if you want to voice wishes, book an onboarding call or view the key figures of the search together with other plugins.

## Feature board

The **Feedback** button at the top of the plugin dashboard opens the feature board. It shows the features we are planning: "Here you will find features we are planning for the future. Vote and leave your feedback. The more votes, the higher the priority."

For each feature you see the title, the status and the number of votes for and against. The status shows how far a feature is:

| Status        | Meaning                           |
| ------------- | --------------------------------- |
| "Idea"        | We are still collecting opinions. |
| "Coming Soon" | The feature follows soon.         |
| "In Progress" | We are working on it.             |
| "Released"    | The feature is available.         |

### Voting and commenting

1. Click a feature. A window with the description opens.
2. Vote with "Upvote" or "Downvote". Clicking the chosen direction again withdraws your vote.
3. In the field "Your Comment", write what you think and click "Save". "Delete" removes your comment again.

Each user has one vote and one comment per feature.

## Support

The **Support** button opens the window "How can we help you?". It is also available in the plugin configuration. The window has up to three cards:

* **Onboarding:** "During the first three months after installation, we show you in a personal 30-minute call how to set up the plugin in the best way." "Book a call" opens the booking page in a new tab.
* **Support:** For technical questions or problems, "Technical support" opens our contact page.
* **Documentation:** "Go to documentation" leads to the guides for the plugin.

{% hint style="info" %}
You only see the "Onboarding" card in the first 90 days after the plugin was installed. Your user also needs the permission "Read plugins". Without that permission, or if the installation date is unknown, the card stays hidden.
{% endhint %}

## News

The **News** button with the bell shows the number of unread entries (up to "9+"). New features also carry a "New" label in the plugin dashboard.

The window "What's new in InsightSearch" has the list with date and title on the left (unread items are highlighted) and the detail view on the right. The filters "All", "Features", "Improvements" and "Fixes" narrow the list. The button "Go to feature" jumps to the matching place in the dashboard and briefly highlights it. At the bottom there are "Show news again", "Mark all as read" and "Close".

Counter and "New" labels can be switched off: in the plugin configuration, card "Admin dashboard", switch off "Show news in the admin" (default: on). You can still reach the news through the button. To read them, your user needs the permission "Read plugins".

## Key figures in cogi Commander

If **cogi Commander** ("cogi Commander | Analytics, Statistiken & mehr") is installed, the search plugin reports its key figures there. A tile "cogi InsightSearch Suche" appears with the text "Clicks, cart and revenue via search." and four key figures:

| Key figure              | Content                                                               |
| ----------------------- | --------------------------------------------------------------------- |
| Clicks from search      | split by target: product, cart button, wish list, quick view, content |
| Add to cart from search | products that went into the cart from the search                      |
| Orders via search       | orders with at least one product from the search                      |
| Revenue via search      | main figure, after proportional discount and in the default currency  |

Revenue counts only product lines from the search. A purchase counts per purchased product (or its variant) if that product was clicked in the search or put into the cart from there, with up to 72 hours between click and order in the same browser. Lines that also come from a recommendation count as recommendation revenue and not as search revenue.

### Without Commander installed

If the Commander is not installed yet, the plugin remembers daily totals without personal reference (per day, sales channel and key figure). It keeps them for 90 days. The Commander takes them over later. Visits by bots are not counted.

### Adding older orders

You add orders from before the installation of the Commander once. The command runs on the shop's server, for example by your agency:

```bash
bin/console cogi-insightsearch:suite-backfill
```

The prerequisite is that the Commander is installed and active, otherwise the command stops with a notice. Proceed in this order: install the Commander, start the backfill, after that the Commander takes over the values.

| Option              | Effect                                                                                         |
| ------------------- | ---------------------------------------------------------------------------------------------- |
| `--from=YYYY-MM-DD` | First day to be added. Without it, all orders are considered.                                  |
| `--force`           | Runs the backfill again. Only useful as long as the Commander has not taken over anything yet. |

Without `--force` the backfill runs only once. It ends on the day the ongoing reporting began, so nothing is counted twice. At the end it reports how many orders it read.

More about commands on the page [Commands](https://docs.codegiganten.de/plugin-documentation/en/apps/search-intelligent-and-ai-optimized/commands.md).

## Further reading

{% content-ref url="/pages/HsFAOG9ZITzp3esXXRtx" %}
[Statistics](https://docs.codegiganten.de/plugin-documentation/en/apps/search-intelligent-and-ai-optimized/statistics.md)
{% endcontent-ref %}

{% content-ref url="/pages/UbPgPTIvpH80zt0F5BMB" %}
[Permissions](https://docs.codegiganten.de/plugin-documentation/en/apps/search-intelligent-and-ai-optimized/permissions.md)
{% endcontent-ref %}

{% content-ref url="/pages/mU4m1YpoKatMe6lLhFMB" %}
[Commands](https://docs.codegiganten.de/plugin-documentation/en/apps/search-intelligent-and-ai-optimized/commands.md)
{% endcontent-ref %}


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.codegiganten.de/plugin-documentation/en/apps/search-intelligent-and-ai-optimized/feedback-and-commander.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
