> For the complete documentation index, see [llms.txt](https://docs.fact-finder.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.fact-finder.com/docs/analytics/analytics/analytics-personalise-search-and-product-view.md).

# Personalize search and product view

The search view provides an overview of the search terms received and their most important KPIs over a chosen period of time.

![Channel view](https://883583471-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FTV1CIVFU3DJKhWzkqLAG%2Fuploads%2Fgit-blob-360f0fd8e07ab123e38787f014ff6eee8a596a5f%2FChannel-3.png?alt=media)

The search terms are grouped by channel and can be sorted by KPIs. To sort, left‑click the column header. The entire channel appears above the search terms as a comparison value.

KPIs are divided into groups whose values can be collapsed or expanded by clicking the group name.

You can visualize your data with different diagram types.

### Hourly diagram

![Hourly diagram](https://883583471-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FTV1CIVFU3DJKhWzkqLAG%2Fuploads%2Fgit-blob-4ca757e6da5823b294f227356843c42eff67c4f0%2Fimage-1740128598439.png?alt=media)

The data can be visualized as an hourly diagram (above) or as a daily diagram (below).

### Daily diagram

![Daily diagram](https://883583471-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FTV1CIVFU3DJKhWzkqLAG%2Fuploads%2Fgit-blob-8bbe2955024d7bc2c1bc5c777af49fb32c370603%2Fdaily_diagram.png?alt=media)

### 24h diagram

You can choose the 24h diagram for a block view.

![24h diagram](https://883583471-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FTV1CIVFU3DJKhWzkqLAG%2Fuploads%2Fgit-blob-3d0a71aa2c0039c4c342882c3421206d2088ba39%2F24hdiagram.png?alt=media)

The KPI dropdown lets you set all search terms displayed in the diagram to a single KPI (e.g., searches or clicks).

The last option switches from an absolute to a relative view. This is useful, for example, to compare individual search terms against the daily trend.

### How to apply filters?

In the default setting all products or search terms are listed. However, it is also possible to filter this view.

You can apply filters by clicking the funnel icon below the KPI’s name:

![Filter button](https://883583471-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FTV1CIVFU3DJKhWzkqLAG%2Fuploads%2Fgit-blob-0a3701e673677d8d20e31f903cb0d2875c9f7d79%2Ffilter-1.png?alt=media)

Define one or more filter conditions, e.g., only show products with high search volume.

Click Apply filter to apply.

### Compare values

You can compare all possible metrics in the diagram. Just click and hold the desired value and drag it to one of the color fields in the diagram.

![Compare values](https://883583471-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FTV1CIVFU3DJKhWzkqLAG%2Fuploads%2Fgit-blob-6741fd167d53db8fa5c33d1f20cbb3e5eb70f56d%2Fimage-1740131934589.png?alt=media)

You can also compare several values of a search term, e.g. click and add-to-cart rate.

![Compare diagrams](https://883583471-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FTV1CIVFU3DJKhWzkqLAG%2Fuploads%2Fgit-blob-6756a2aa8de5b6732cbcacbdd662f9c33028c692%2Fcompare_diagramms.png?alt=media)


---

# 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.fact-finder.com/docs/analytics/analytics/analytics-personalise-search-and-product-view.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.