> 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/add-to-cart-tracking.md).

# Add to Cart Tracking

## Add to Cart Tracking

Use the `addtocart` tracking type to capture when a user adds a product to their shopping cart. This action marks a critical e-commerce event and should be accurately tracked with both product and interaction data.

### Tracking Commands

* `product`
* `addtocart`

{% hint style="info" %}
As defined, the `addtocart` event automatically activates the [JENTIS Data Layer State](/developer-guide/states/jentis-data-layer-state.md) in JENTIS using the `sendBeacon` sending method.
{% endhint %}

### Example

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

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

### Properties for `addtocart`

The `addtocart` command itself does not have additional properties. All relevant data should be submitted with the associated `product` object.

Make sure to use `type: "addtocart"` on the product to associate it correctly with this interaction.

For tracking product quantities, pricing, and custom variables, refer to 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/add-to-cart-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.