> 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/click-on-the-details-page.md).

# Click on the details page

Send product click tracking data with query, position, paging, and campaign context.

If you want to send product click information, also pass the following parameters in addition to the [general parameters](https://docs.fact-finder.com/integration/tracking-interface/general-parameters.md):

| Parameter  |           | Description                                                                                                                                                                                                                                                                      |
| ---------- | --------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `query`    | essential | The search term entered by the user. For a navigation click, send the full category path as the query value.                                                                                                                                                                     |
| `pos`      | essential | The absolute position of the product in the search results. For example, the first product on page 2 is position 11 if each result page contains 10 products. The first product on page 1 is position 1.                                                                         |
| `page`     | essential | The number of the search result page on which the selected product was displayed. The first page has the number 1.                                                                                                                                                               |
| `pageSize` | essential | The number of products per search result page at the time the click was executed.                                                                                                                                                                                                |
| `campaign` | essential | A product contains the field `_FFCampaign_` if it reached the search results through a campaign. This field contains the campaign ID. When the user interacts with that product, send the ID with the `campaign` parameter so the influence of Campaign Manager can be measured. |

## REST

The REST API documentation is part of the search application and is available at \[your NG server]/fact-finder/swagger-ui.html. You can also access it here:

Swagger Link: <https://ng-demo.fact-finder.de/fact-finder/swagger-ui.html>

In addition to the parameter documentation, you can test requests and inspect the results directly. Because the documentation is built with Swagger, you can also use Swagger Codegen to generate a client.

Product click event documentation is available through the `click` method in the `tracking` resource.


---

# 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/click-on-the-details-page.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.
