> 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/jentis-dcp-elements/codes/add-a-code-element.md). # Add a Code Element To add a JavaScript code snippet to your JENTIS Tag Manager container, please follow these steps.

Navigate to the “Server Tag Manager: Codes” section in your JENTIS DCP account. Click the "Add Code Element"-button to add a new element.

In a code element, you must provide the following fields: * **Name**: a descriptive short name of the code element. * **Order**: a number that defines the execution order on initialization (Integer). Low numbers are executed first, starting with 0. * **Containers**: select the containers in your JENTIS Tag Manager account, that will include this code element when loaded. * **Javascript Code**: the actual code. Please be aware that this code will be interpreted in a closure and minified, so always consider the scope you are working with. * **CSS Code** (optional): You can add custom CSS to publish to your webpage with this element. * **Trigger**: Select a trigger that activates this code. Leave it on the default "**JENTIS Framework Load**" to execute immediately. --- # 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/jentis-dcp-elements/codes/add-a-code-element.md?ask=&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.