Create Your First Container

1. To create a container, navigate to the Settings: Containers page and click "Add New Container" in the top right corner.

1. After this, you will need to name your container uniquely to differentiate it from others, and input the top-level domain on which you want to track with JENTIS. In the image below, you see an example domain being used for an example container.

1. You can specify which CMP you will be using for this container or do so at a later point in your implementation. Eventually, before publishing and going live, you will have to associate the container with at least one consent management solution.

2. After you click "Add" on the bottom right, the next step in your container creation is to display the DNS Address and the JENTIS JS Snippet.

Setting the DNS A-record for JENTIS and copying the JS code snippet onto your website´s code are two necessary steps to complete a container creation. You will not be able to publish any other changes with JENTIS until these two steps are complete. Typically, we recommend that our clients prioritize these tasks first and get these done within a week of receiving access to their JENTIS accounts.

Tracking Verification and Container Status

After you configure the DNS A Record and the HTML Code on your website, it will be automatically verified in up to 30 minutes. Alternatively, you can return to your container’s configuration and click on Verify.

Next to your container’s name, you will find the status of your container:

• If GREEN, the consent bar is selected, DNS A Record and HTML Code are verified, and the container is published.

• If BLUE, the consent bar is selected, DNS A Record and HTML Code are verified, but the container is not yet published.

• If GREY, at least one of the configuration steps (DNS A Record, HTML Code, or Consentbar) is not completed.

Edit a Container

You can easily edit your container’s configuration by going to your Containers menu and click on Edit:

You can change the following fields:

Basic Settings:

• Container name – A descriptive name for your container.

• Optional field: Consentbar (CMP) – Select from the list of supported consent bars.

Advanced Settings (Optional):

• Preview URL—For the container configuration preview session, set a custom URL instead of the website domain. If this field is left empty, the website domain configured in the basic settings will be used.

• Main Domain Cookie — This feature allows you to configure whether first-party identifiers (e.g., JENTIS User-ID) are implemented at your website’s main domain or subdomain level in your containers. This enables the identification of users across the main domain and its subdomains. For more information, read.

Once you change any of these fields, click Save and Publish your container again.

How to Grow and Scale

• To define the right number of containers on your account, please consider:

  • How many websites (domains) do you have? Are they similar in nature (same data, same requirements)? Can they be grouped where the requirements overlap (same tools with the same conversion goals)?

  • Do you want to split a single website (domain) into multiple sections (i.e., by subdomain)? Do they require separate management and have different requirements (e.g., different data, different tools, and different conversion goals)?\

• Once you consider these questions, you have some options to configure your containers:

  • Multiple containers for one same domain: We recommend that you use this option if your website has multiple subdomains with particular management requirements—different data, tools, and conversion goals. For example, on the main domain example.com, you have shop.example.com and blog.example.com. While the first has a clear purchase conversion type and an e-commerce structure, the second is a content website. You could configure one container for each of these.\

  • One container for the same domain and all its subdomains: We recommend using this option if your website has multiple subdomains that share the same type of data, tools, and conversion goals. For example, your main domain, example.com, has the subdomains de.example.com and at.example.com. These are all e-commerce pages with the same structure and purchase conversion goal, just varying their language. You only need one set of configurations for these.\

  • One unique container per domain: If you have different domains, you should configure one container for each one, as one container can not be used on multiple domains. For example, your company owns the websites example.com and mycompany.com. Each should be configured with a different container.

Remember: A container can hold multiple configured tools; it can be the same tool (e.g., GA4) with two different instances.

To continue with your step-by-step implementation, we recommend you now read into: DNS Setup.