> 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/triggers/trigger-creation-process.md).
# Trigger Creation Process
In your JENTIS DCP navigate to the Server Tag Manager: Trigger to create new triggers or adjust conditions in existing triggers. The basics that you need to define are:
* **Name**: This is the value that will appear in the selection in a Tag configuration. You should use a descriptive name here.
* **ID**: This technical reference can be used to reference a trigger explicitly, as this ID is unique per JTM account.
* **Description**: Feel free to give a Trigger a description to understand better the motivation to handle certain conditions.
* **State**: You can choose between predefined states, such as the "loaded document" (domload) or something pushed into the datalayer ("jts\_submit"). There is also the possibility to choose a CSS-selector with an action (SELECTORACTION) like `.button click`
* **Exclude Trigger:** These Triggers define that if they trigger, this trigger shouldn’t trigger. For example, a Google Analytics product view tag also includes the pageview. In the case of a product view, a page view and a product view event will be sent to the server. Therefore, the pageview trigger needs the exclude triggers, which exclude the product view, leading to unique events.
* **Conditions**: Here, you can select the parameters to check and how the value is validated. The following section describes this in detail.
---
# 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/triggers/trigger-creation-process.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.
