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

# accountvars

### `accountvars` Property

The `accountvars` property contains all **constants** defined in the JENTIS Tag Manager (JTM).

#### Purpose

These constants represent the configured values for the **selected container** and **environment**. They are predefined and maintained in the JTM and can be accessed at runtime for use in your data collection setup.

#### Accessing Constants

Each constant is stored under a property key that corresponds to its **JENTIS internal ID**, which can be found directly in the JENTIS Tag Manager interface.

#### Example

If a constant with the internal ID `company_id` has been defined in the JTM, it can be accessed like this:

```js
const companyId = accountvars['company_id'];
```

This allows for flexible and environment-specific variable handling within your client- or server-side tracking setup.


---

# 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/accountvars.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.