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

# stateContext

### `stateContext` Property

The `stateContext` property holds the **contextual value** passed to the currently executing state.

#### Purpose

When defining a state in the JENTIS Tag Manager, you can optionally assign a context value. This allows the state to behave differently depending on the condition or interaction that triggered it.

#### Default Behavior

If no context is provided, the `stateContext` value is `undefined`.

#### Use Case

Consider a state that listens to interactions on HTML form elements. This state might react to multiple behaviors such as `submit`, `change`, or `input`.

To differentiate between these behaviors, the state can pass a state context, which you can access within a client-side variable. This allows you to define trigger conditions that listen to that state, for example:

```js
// Client-Side Variable returning State-Context Property
function(arguments) {
    return arguments.stateContext.behavior;
}
```

This allows you to build **flexible triggers** that respond based on the specific behavior that caused the state to execute.

#### Example

You might define triggers like:

```js
[Client-Side Variable returning stateContext.behavior] 
contains 
"input"
```

This approach makes it easier to **reuse the same state definition** across different interaction types while tailoring logic to the specific context.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.jentis.com/developer-guide/variables/client-side-variables/function-arguments/statecontext.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.