Skip to main content
Skip table of contents

Glossary - JENTIS Terms and Components

JENTIS Account: Your single point of entry to the JENTIS Data Capturing Platform (DCP). Managing multiple accounts with one login is currently not supported.

JENTIS Container: A single definition of a data processing unit for the JENTIS DCP. A JENTIS account consists of one or multiple containers. Each container is connected to a particular website (domain), while a single domain can hold one or multiple containers. Each container has a unique DNS A record and JS Code snippet. Please check JENTIS Accounts and Containers for more details.

Tools: ~ in JENTIS refers to the software or platforms used to manage tags on a first-party company’s behalf. A single tool instance (see below) is a configuration based on your settings for a given tool.

Tool Instances: A configuration of a tool in JENTIS Tag Manager. A single tool can be installed multiple times with different configurations. Unlimited tool instances of the same tool can be installed on the same container. Each tool instance consists of tags that define executable data transmission.

Tags: Tags are snippets of code (JavaScript) used to collect and send information to third parties. They are used for various purposes like tracking visitor behavior, persisting data and applying transformations, integrating third-party services (like analytics or advertising platforms), and monitoring website performance. JENTIS tags can be executed client-, server-side, or hybrid ( JENTIS Tags - Server-, Client- and Hybrid-Modes). A tag in JENTIS Tag Manager is always connected to a tool instance.

Triggers: Triggers are conditions that determine when a tag should be activated or fired. They are set within the tag management system and can be based on user interactions, such as clicks, form submissions, page loads, or other custom events. Variables determine these dynamic values in triggers.

Variables: Variables in tag management are named placeholders for values that can change, such as user IDs, transaction amounts, or any other dynamic data. They are used in tags and triggers to pass specific data points or to control the behavior of tags based on the variable's value. Variables are computed either on the client- or server-side based on their configuration.

JENTIS Event States: ~ refer to the various stages or conditions under which certain events are tracked or tags are fired. A state holds the technical definition that is the foundation to activate the framework. All triggers and variables are computed on each state, and trigger conditions are applied. The states guarantee a seamless integration of client- and server-side operation (so a single variable can be used on both ends without the need to define it on each end (client and server) anew). 

JENTIS Data Layer: A data layer is a central repository of structured data on your website or web application. It acts as a uniform data source that a tag management system can use to collect and send information to various analytics, marketing, and other third-party services. The data layer is typically implemented as an object in a site's global scope (window). JENTIS can connect to generic data layer definitions (such as Google Tag Manager) or to our preferred format of the JENTIS Data Layer (JENTIS Data Layer Fundamentals).

Plugins: ~ are additional modules or extensions that enhance the functionality of the tag management tool. They can provide extra features like generating a native integration for video tracking or customization that are not part of the core system.

Custom Code: This refers to any code written specifically for your website or application that goes beyond the standard functionalities provided by the tag management system. Custom code can be used for complex tracking setups, unique user interaction tracking, or integrations not natively supported by the system. Custom code can only be executed client-side.

Vendors: In tag management, vendors are third-party services or platforms for implementing tools and their tags. Examples include Google Analytics, Facebook Pixel, and various advertising platforms. Each vendor is connected to a Consent Management Platform with the JENTIS Consent Engine. At the same time, a tool instance in JENTIS is always connected to a vendor. Multiple tool instances can connect to the same vendor or each to a custom vendor.

Essential Mode: Each vendor has a setting of how to apply consent information. One of those options is the Essential Mode. This provides a fallback configuration on a tag-level configuration. In the fallback (of a situation where consent is not granted) a different configuration of that tag will be applied. See JENTIS Essential Mode.

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.