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

# Promotion Tracking

## Promotion Tracking

Promotions represent internal marketing elements such as banners, creatives, or call-to-action buttons. JENTIS supports tracking **impressions** and **clicks** for these promotions.

### Supported Tracking Commands

* `promotion`
* `promotionimpression`
* `promotionclick`

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

### Properties for `promotion`

| Name       | Description                                           | Type   | Mandatory | Example                 |
| ---------- | ----------------------------------------------------- | ------ | --------- | ----------------------- |
| `type`     | Either `promotionimpression` or `promotionclick`      | string | yes       | `"promotionimpression"` |
| `id`       | Promotion identifier                                  | string | yes       | `"12345"`               |
| `name`     | Name of the promotion                                 | string | yes       | `"Summer Sale"`         |
| `creative` | Creative name or version                              | string | no        | `"banner_v1"`           |
| `position` | Position reference of the promotion (ideally numeric) | string | no        | `"1"`                   |

### Promotion Impression – Example

```javascript
_jts.push({
  track: "promotion",
  type: "promotionimpression",
  id: "1234",
  name: "Promotion A",
  position: "1",
  creative: ""
});

_jts.push({
  track: "promotion",
  type: "promotionimpression",
  id: "5678",
  name: "Promotion B",
  position: "2",
  creative: ""
});

_jts.push({ 
  track: "promotionimpression" 
});

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

### Promotion Click – Example

```javascript
_jts.push({
  track: "promotion",
  type: "promotionclick",
  id: "5678",
  name: "Promotion B",
  position: "2",
  creative: ""
});

_jts.push({ 
  track: "promotionclick" 
});

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

### Deprecated Format (Legacy)

The following format is **deprecated** and should not be used in new implementations:

#### Deprecated Example

```javascript
// DO NOT USE – Legacy Format
_jts.push({
  track: "promotionimpression",
  id: "1234",
  name: "summer promotion",
  creative: "a42 banner",
  position: 1
});

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

> 🚫 Avoid using the legacy format—future support will be removed.

Always use `track: "promotion"` with the `type` field to distinguish between impressions and clicks.

For an overview of how this integrates with product tracking, 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/promotion-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.