# JENTIS Core Components

### **JENTIS Container Manager** <a href="#jentiscorecomponents-jentiscontainermanager" id="jentiscorecomponents-jentiscontainermanager"></a>

The JENTIS Container Manager allows teams to operate within a single Container environment using the JENTIS Tag Manager and other components of the JENTIS SaaS.

The Account owner can manage different versions of a Container, including commenting, previewing, debugging, rolling back to previous versions, and publishing to stage and live environments. This aligns with industry best practices for efficient and organized data management.

### **JENTIS Consent Manager** <a href="#jentiscorecomponents-jentisconsentmanager" id="jentiscorecomponents-jentisconsentmanager"></a>

The JENTIS Consent Manager is where the teams store information about data subject consents, as well as administer Consent Management Platforms (CMP) connectors with information from Vendors and Tools.

JENTIS Consent Manager makes it possible to connect native third-party CMPs, ensuring that all consents given by the CMP are available, documented and used based on the applicable consent configuration. JENTIS Consent Manager includes a JENTIS Essential Mode feature enabling an Account owner to configure different scenarios of tracking based on the consent decision of the data subject.

### **JENTIS Tag Manager** <a href="#jentiscorecomponents-jentistagmanager" id="jentiscorecomponents-jentistagmanager"></a>

The JENTIS Tag Manager provides for a single location to easily add, update, or remove tags, states, triggers, variables and custom java script code for tracking data in the first-party context, as well as other tracking data, in alignment with data subject consents based on various website events in a centralized and tidy user-friendly interface .

### **JENTIS Tool Connector** <a href="#jentiscorecomponents-jentistoolconnector" id="jentiscorecomponents-jentistoolconnector"></a>

The JENTIS Tool Connector manages the 100+ out of the box connectors that send data to third party marketing and analytics Vendors that JENTIS supports. Account owners are able to easily create and connect Tools for various Vendors, such as Google Analytics, Meta, Tik-Tok, etc, and stream data to the Tool in accordance with a data subjects’ consent based on the applicable Consent configuration.

### **JENTIS Tracker** <a href="#jentiscorecomponents-jentistracker" id="jentiscorecomponents-jentistracker"></a>

The Account collects client side tags and first-party data based on the configurations in the JENTIS Tracker. JENTIS Tracker is then pushing this data to the server-side via the JENTIS Server Suite.

### **JENTIS Server Suite** <a href="#jentiscorecomponents-jentisserversuite" id="jentiscorecomponents-jentisserversuite"></a>

JENTIS Server Suite (or J-Suite) is the backbone and the engine of the JENTIS SaaS. JENTIS processes the data on behalf of the Account. With the standard and advanced features of the J-Suite enabled, teams can modify the data (anonymize and pseudonymize), enrich and/or synthesize the data before they share it with vendors. The J-Suite is based on the Twin Server Technology.

### **JENTIS Twin Server** <a href="#jentiscorecomponents-jentistwinserver" id="jentiscorecomponents-jentistwinserver"></a>

The JENTIS Twin Server is an integral part of the J-Suite and this is where the data is being processed, enriched and from where the data is streamed to vendors such as Google Analytics.


---

# 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/privacy-documentation/product-information/jentis-core-components.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.