# JENTIS Account & Container Structure

JENTIS has a three-level hierarchy:

1. **JENTIS Platform Account:** This is the highest level of administration. In general, an account represents a single company and has one single point of contact. Here, you log in and can manage users, containers, and environments.
2. **Container:** A container is always directly connected to a domain and a JavaScript embed snippet.
3. **Container Environment:** Part of the JavaScript embed snippet is the definition of an environment. By default, a JENTIS Container will always have two: `stage` and `live`.

The JENTIS hierarchy and structure are mirrored in its code. In other words, the JENTIS server-side tracking architecture as a first-party solution forms the foundation for scaling across multiple sites. Each integration must be implemented in a first-party context, making having different JavaScript snippets, DNS A records, and containers inevitable.

Let's have a look at the generic short version of the JENTIS Code Snippet:

{% code overflow="wrap" lineNumbers="true" %}

```markup
<script>
(function (sCDN,sCDNProject,sCDNWorkspace,sCDNVers) {
            ... // shortened for brevity
        })("https://JENTIS_SUBDOMAIN.mydomain.com","JENTIS_CONTAINER_NAME","JENTIS_CONTAINER_ENVIRONMENT","_");
</script>
```

{% endcode %}

There are multiple dynamic parameters in that code:

* `JENTIS_SUBDOMAIN`: This is a dynamically generated value where you must map the DNS A record entry. All details are shared in your JTM account setup guide.
* `JENTIS_CONTAINER_NAME`: This refers to the name of your container, which will be used with the JS embed snippet.
* `JENTIS_CONTAINER_ENVIRONMENT`: Either `stage` or `live`.