> 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/developer-guide/variables/client-side-variables/function-arguments/element.md).

# element

### `element` Property

The `element` property provides a reference to the DOM HTML element that triggered the execution of the current state.

#### Default Behavior

By default, this property is set to the global `window` object.

#### Triggered by Interaction

If a **CSS Selector Action Trigger** is used—executed through a specific JavaScript event such as a `click`, `hover`, or similar—the `element` property will instead reference the actual HTML element involved in that interaction.

#### Use Cases

This property allows you to extract contextual information directly from the DOM element that triggered the event. For example, you can:

* Access custom `data-*` attributes
* Read element-specific properties (e.g., `id`, `classList`, `innerText`)
* Use the reference in further JavaScript operations

#### Example

If a button is clicked and has a `data-product-id` attribute:

```html
<button data-product-id="12345">Buy Now</button>
```

You could use the `element` reference to access this value:

```js
const productId = element.getAttribute('data-product-id');
```

This makes the `element` property a powerful tool for context-aware data extraction in dynamic web tracking scenarios.


---

# 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/developer-guide/variables/client-side-variables/function-arguments/element.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.