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

# Notes: Tracking Integration

## Transfer test possibilities

If the JSON object is sent correctly, the interface returns the HTTP status code `200`. If there is a problem with the tracking request, the response returns HTTP status code `400` together with an error message such as `The parameter [id] is required and cannot be empty`. This makes it easy to validate the integration and confirm that all required parameters were sent.

Another good way to verify your tracking integration is to use the **Analytics Dashboard** in the FactFinder Management Interface.

## Sending of multiple events in one request

FactFinder NG lets you send multiple events in one URL or method request. This is especially useful for buy events, because it reduces the total number of requests and lowers network traffic.

Only events of the same type can be sent in a single request. For example, you can send multiple buy events together or multiple cart events together, but not a mix of both. To send multiple events, pass the relevant parameters multiple times.

See [Swagger-UI](/integration/tracking-interface/integrating-tracking-via-rest.md) for examples.

## “Add to shopping cart” feature on the result page

If users can add products directly to the shopping basket from the search results page, send both `click` data and `cart` data when that happens. That is the only way to determine that the item was added to the basket directly from a search result.

***

## Other

You can also trigger tracking events in the source code when the details page is opened. This avoids relying on JavaScript in the visitor’s browser. If you do this, make sure all required parameters are still sent.


---

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