> 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/getting-started-guide/integration.md).

# Integration

![](/files/6LkZSxHVC25SDexAUpWM)

Integration is a key part of implementation and requires support from your team. There are two primary ways to integrate your eCommerce site with FactFinder:

## REST API

Integrate server-side using the FactFinder REST API. FactFinder returns JSON with everything you need to render for your customers.

Swagger documentation can be found [here](https://api-docs.ff-labs.de/)

## Client SDK/Library

Use Swagger Codegen to generate a client SDK for our APIs in your preferred language. Documentation can be found [here](https://swagger.io/tools/swagger-codegen/)

The full FactFinder integration documentation can be found [here](https://docs.fact-finder.com/integration/)

## Tracking integration

***

### What is this and why is it important?

Tracking allows FactFinder to learn from user behavior, improving search results and providing personalized recommendations.

Tracking requires data such as:

* product clicks
* shopping cart events
* purchase/checkout events
* login events

Using this data with FactFinder is key to increasing sales and conversion rates and providing the best user experience.

***

### For which features is tracking crucial?

* **Analytics:** Without tracking, FactFinder receives far less data and you miss actionable insights for search optimization.
* **A/B testing:** Not possible without tracking.
* **AI/ML features:** Work only to a very limited extent without tracking. This negatively affects ASO, Semantic Enhancer, Recommendations, and Personalization and requires significantly more manual effort to maintain.

Read more [here](/integration/tracking-interface/tracking-interface-integration.md) about sending tracking data to FactFinder.


---

# 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/docs/getting-started-guide/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.