> 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/tags.md). # Tags The data capture and load process of JENTIS centers around the submission of data to partners and networks. This involves setting up rules and configurations that dictate when to send what data to which partner. Tags play a crucial role in this process by enabling detailed configuration of individual parameters and values to be transmitted to the intended data recipient. JENTIS Tag Manager allows for flexible and scalable tag configurations, enabling multiple setups in one configuration. Every tag in your JENTIS account consists of the following parts: * **Tool**: Select a tool you previously created that will hold global configurations for this tag. * **Template**: JENTIS includes templates for tags that cover use cases per tool, ie. the “pageview” template for Google Analytics. * **Trigger**: Every Tag references a trigger that defines conditions on when to actually activate a tag and submit data to a recipient. * **Field Configuration**: Here you will define every parameter that needs to be mapped to a value that will be submitted to the recipient. --- # 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/tags.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.