> For the complete documentation index, see [llms.txt](https://docs.jentis.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.jentis.com/data-capture/web-tracking-setup/set-up-jentis-data-layer/e-commerce-tracking/product-list-tracking.md).

# Product List Tracking

## Product List Tracking

The `productlist` tracking type is used when multiple products are displayed together in a list—for example, on a category page, homepage slider, or product grid.

Each product in the list should be tracked with `type: "productlist"`, and a summary `track: "productlist"` object defines metadata for the list context.

***

### Tracking Commands

* `product`
* `productlist`
* `submit`

***

### Product Example

```javascript
_jts.push({
  track: "product",
  type: "productlist",
  id: "12345567",
  name: "Product Name"
});
```

### Product List Object

```javascript
_jts.push({
  track: "productlist",
  listname: "main-slider",
  categorypath: ["category1", "category2"]
});
```

### Submit State

```javascript
_jts.push({ track: "submit" });
```

***

### Properties for `productlist`

| Name           | Description                                       | Type   | Mandatory | Example                      |
| -------------- | ------------------------------------------------- | ------ | --------- | ---------------------------- |
| `listname`     | A meaningful name for the product list            | string | yes       | `"main-slider"`              |
| `categorypath` | Breadcrumb-style path of categories for this list | array  | no        | `["category1", "category2"]` |

***

Make sure every product in the list uses the same `type: "productlist"`, and the summary object is submitted before calling `track: "submit"`.

For more on how this links to other product tracking types, see the [E-Commerce Tracking](/data-capture/web-tracking-setup/set-up-jentis-data-layer/e-commerce-tracking.md).


---

# 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.jentis.com/data-capture/web-tracking-setup/set-up-jentis-data-layer/e-commerce-tracking/product-list-tracking.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.