> For the complete documentation index, see [llms.txt](https://docs.chord.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.chord.co/collect-data/tracking-plan/promotion-clicked.md).

# Promotion Clicked

User clicked on promotion.

**Suggested source:** website front-end

**Properties**

| Name               | Type       | Description                                                                                                                      | Required |
| ------------------ | ---------- | -------------------------------------------------------------------------------------------------------------------------------- | -------- |
| **creative**       | `string`   | <p>Promotion's creative (for example, top\_banner\_2)<br></p>                                                                    | no       |
| **name**           | `string`   | <p>Promotion's name (for example, "75% store-wide shoe sale")<br></p>                                                            | yes      |
| **position**       | `string`   | <p>Promotion's position (for example, home\_banner\_top)<br></p>                                                                 | no       |
| **promotion\_id**  | `string`   | <p>Promotion's ID (for example, promo\_1)<br></p>                                                                                | yes      |
| **bundle**         | `boolean`  | <p>Product belongs to a bundle<br></p>                                                                                           | no       |
| **description**    | `string`   | <p>Short description of the product<br></p>                                                                                      | no       |
| **option\_values** | `string[]` | <p>Option values of the product variant<br></p>                                                                                  | no       |
| **slug**           | `string`   | <p>Slug of the product, often used in URLs (for example, "product-red")<br></p>                                                  | no       |
| **affiliation**    | `string`   | <p>Product affiliation to designate a supplying company or brick and mortar store location (for example, "Google Store")<br></p> | no       |
| **brand**          | `string`   | <p>Brand associated with the product<br></p>                                                                                     | no       |
| **category**       | `string`   | <p>Product category<br></p>                                                                                                      | no       |
| **coupon**         | `string`   | <p>Coupon code associated with a product (for example, "MAY\_DEALS\_3")<br></p>                                                  | no       |
| **currency**       | `string`   | <p>Currency code of the transaction (for example, "USD")<br>Pattern: <code>^\[A-Z]{3}$</code><br></p>                            | no       |
| **price**          | `number`   | <p>Price ($) of the product<br></p>                                                                                              | no       |
| **product\_id**    | `string`   | <p>Database ID of the product<br></p>                                                                                            | no       |
| **quantity**       | `integer`  | <p>Quantity of the product<br></p>                                                                                               | no       |
| **variant**        | `string`   | <p>Name of the product variant<br></p>                                                                                           | no       |

**Example**

```json
{
    "creative": "top_banner_2",
    "name": "15% off spring seeds",
    "position": "home_banner_top",
    "promotion_id": "promo_1",
    "affiliation": "My Plant Store",
    "brand": "Green Thumb Nurseries",
    "bundle": false,
    "category": "Vegetable Seeds",
    "coupon": "SPRING15",
    "currency": "USD",
    "description": "High-quality heirloom carrot seeds that produce sweet and crunchy carrots, perfect for home gardening.",
    "image_url": "https://example.com/images/carrot-seeds.jpg",
    "option_values": [
        "Nantes",
        "Danvers",
        "Imperator"
    ],
    "price": 3.99,
    "product_id": "987654321",
    "quantity": 1,
    "sku": "CARROT-002",
    "slug": "heirloom-carrot-seeds",
    "url": "https://example.com/seeds/carrot",
    "variant": "Nantes"
}
```

## option\_values\[] array

Option values of the product variant

Option value (for example, "red")

**Item Type:** `string`\
**Example**

```json
"Nantes"
```

**Example**

```json
"Danvers"
```

**Example**

```json
"Imperator"
```


---

# 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.chord.co/collect-data/tracking-plan/promotion-clicked.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.