# Create a new Tag

Navigate to the **Server Tag Manager** section in the main navigation.

<figure><img src="/files/c1sZcypY7qjYbD9yBFqd" alt=""><figcaption></figcaption></figure>

In the list of all tags configured in your account you have now the option to create a new tag (clicking on the "Add New Tag"-button, located at the lower right corner of the screen).

Every tag needs a name. A common syntax is to use the tool name combined with the template or event description, ie. “Google Analytics – Pageview”.

Additionally every tag is associated with a tool (that you previously created). This way any tag can access global configuration parameters and re use those values.

<figure><img src="/files/AjMxpKTmaxMRWM5fQacW" alt=""><figcaption></figcaption></figure>

Templates follow a tools data schema to capture data. For Google Analytics in this example the given templates follow GAs data model of Pageviews, Events and enhanced Ecommerce Tracking. Each JENTIS Tag Template will provide a different tag runtime and configuration options in the next steps.

<figure><img src="/files/4B779Z7dVFPWkx78SKHS" alt=""><figcaption></figcaption></figure>

The actual configurations of a tags parameters and their respective values is defined in the next step: “Configure Template”. Here you can define parameters values according to a template. Later this setup can be changed and adjusted.

<figure><img src="/files/hDwNU5U0r0lNiDsmn13y" alt=""><figcaption></figcaption></figure>

The last step is now to also select a trigger that will activate this tag newly configured.

<figure><img src="/files/SUiE15q87gDqHEOmrrL8" alt=""><figcaption></figcaption></figure>


---

# Agent Instructions: 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:

```
GET https://docs.jentis.com/jentis-dcp-elements/tags/create-a-new-tag.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.