> 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/shopping-basket-and-purchase-information.md).
# Shopping basket and purchase information
The additional data for shopping basket and purchase information is the same. If you need to send multiple products, you can do that in one request or in several. In most cases, it is better to minimize the number of requests and send multiple events in a single call.
You do not need to know whether this action was caused by a search. That is determined later during analysis. Because this tracking event does not contain FactFinder-specific data, it can be sent directly from the shop code and does not need JavaScript.
| Parameter | | Description |
| ---------- | --------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| `count` | essential | Quantity of the purchased product. This value must be an integer. |
| `price` | essential | Product price. Always send the unit price, even if a customer buys several units of the same product or adds several units to the basket. If you support multiple currencies, the tracking data for a given channel must always use the same currency. Otherwise, statistical reports will be incorrect.
It is recommended to send this parameter because it adds value to the search analysis.
|
| `campaign` | essential | This field contains the campaign ID. When a user interacts with a product that came from a campaign, send that ID with the `campaign` parameter so the influence of Campaign Manager can be measured. |
> When you send multiple products in the same checkout event, include the `sid` value for each product.
## 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:
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.
Cart and checkout event documentation is available through the `cart` and `checkout` methods 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 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/shopping-basket-and-purchase-information.md?ask=&goal=
```
`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.