> 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.md).

# Tracking Interface

Track user actions such as clicks, basket events, and purchases to improve search and personalization.

Tracking data helps FactFinder Search learn automatically from user behavior.

The data provided through this interface supports several use cases, including events such as clicks on detail pages, adding products to the shopping cart, and purchases. This information forms the basis for automated search optimization and helps improve results over time.

Information about product clicks, shopping basket events, and purchases is required for the Personalization module, which provides tailored search results for each user. Purchase data can also be used by the Recommendation Engine. More detail is available in the corresponding [documentation](https://ng-demo.fact-finder.de/fact-finder/swagger-ui.html#/tracking).

The events you pass to FactFinder depend on your needs and objectives. ASO requires, at a minimum, shopping-basket and purchase events. Tracking product-detail clicks is recommended. Clicks provide an additional behavioral signal for ASO and enable click-based tracking and analytics insight. [Automatic Search Optimization (ASO)](https://docs.fact-finder.com/docs/modules/aso.md) documents how ASO records and weights click, shopping-cart, and checkout signals. The following events are supported:

* Clicking on the product details page
* Placing a product into the shopping basket
* Purchasing a product
* A user is logging into the shop
* Clicking on a product suggested by the Recommendation Engine
* User feedback for the search results
* Shop Cachehit

Personalization only works when a valid session ID is sent with each search request.


---

# 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/integration/tracking-interface.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.
