> 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/integration/tracking-interface/suggest-tracking.md).

# Suggest Tracking

You can also add tracking to the FactFinder **Suggest module** to analyze user behavior and support optimization.

Tracking is usually already included in the example script available from FactFinder or on [GitHub](https://github.com/fact-finder). If you build your own Suggest integration, add the relevant tracking parameters yourself. In both cases, it is a good idea to verify the transmitted parameters once the integration is complete.

**Suggest Tracking** works by adding parameters to the follow-up FactFinder query. These parameters show whether the search was triggered from a suggestion and which letters the user entered before making the selection.

## Parameter

***

> **queryFromSuggest**

This parameter indicates that the FactFinder query was triggered by a selection from the suggestion list. In that case, send the value `true`.

***

> **userInput**

Use this parameter to send the letters the shop user entered before the search query was triggered.

***

> **sid**

This parameter is required when you use the **A/B Test module**. If no session ID (`sid`) is passed to FactFinder, the search always uses variant A, because the session ID decides which A/B test variant should run.

## Example

### REST interface

Assume the shop user enters `ri` in the search box and selects `Ring` from the suggestion list, which then triggers a search for *Ring*.\
The FactFinder search URL with the Suggest Tracking parameters then looks like this:

```language-plaintext
rest/{apiversion}/search/{channel}?query=Ring&...&queryFromSuggest=true&userInput=ri
```


---

# 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.fact-finder.com/integration/tracking-interface/suggest-tracking.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.