Container Administration
This article explains how to administrate your containers according to the new experience currently available for beta customers. This will be available for all JENTIS customers on . If you wish to see the previous guide, check Deprecated Container Administration.
In your JENTIS Account Settings, you can easily create new containers, edit existing ones, and check their configuration status.
In this article, we will walk you through the basic steps to create and update container settings, check your configuration status, and explain the automatic verification of your implementation.
For details on the account and container basic concepts, read JENTIS Accounts and Containers
Create a Container
You can create a new container on the JENTIS Platform in three easy steps: Basic Settings, Advanced Settings, and Tracking Configuration. Navigate to the Settings menu, go to the Containers section, and click on Add New Container to start your new container configuration:
.png?inst-v=37c2eaaa-067e-497a-bb3d-ea9639bd11a8)
Basic Settings
In the basic settings, you will configure:
Container name – A descriptive name for your container.
Website domain – The URL of the domain to connect to the container, f.e.,
example.com.
Be aware that you can not change the website domain once the container is created.
Optional field: Consentbar (CMP) – Select from the list of supported consent bars. To activate tracking, you must configure your CMP on the Legal Hub menu. For more information, read JENTIS CMP Connectors
Advanced Settings (Optional)
In the advanced settings, you can optionally configure:
Preview URL – Set a custom URL instead of the website domain for the container configuration preview session. If this field is left empty, the website domain configured on 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.
Click on the Create button to save your new container.
Tracking Configuration
Once your container is created, the next step is to configure your tracking. On the Tracking Configuration tab, you will find your unique DNS A Record and HTML Code:
.png?inst-v=37c2eaaa-067e-497a-bb3d-ea9639bd11a8)
Follow the instructions described on the screen or read DNS Setup and JENTIS Code Snippet for more information on how to configure each.
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.
.png?inst-v=37c2eaaa-067e-497a-bb3d-ea9639bd11a8){kind=tracking}
After creating your container and correctly configuring your DNS A Record and the HTML Code, make sure you publish your changes on the Publish menu.
Edit a Container
It is only possible to edit your container once the DNS A Record and HTML Code are verified.
You can easily edit your container’s configuration by going to your Containers menu and click on Edit:
You are able to 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.
Once the container is created, you can not change the website domain.
Advanced Settings (Optional):
Preview URL – Set a custom URL instead of the website domain for the container configuration preview session. If this field is left empty, the website domain configured on 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.
Delete a Container
In case a container hasn’t been published yet, you can easily delete it by selecting the three dots and clicking on Delete.
Users can not delete published containers. If you want to delete a published container, please contact our customer support.
Best Practice on Container Environments
Many JENTIS users find that one container alone is insufficient to enable a full dev/stage/production process.
Generally, a container has an environment setting that is either "live" or "stage". However, there are situations where this setting alone can not be used. Also, for migration and release processes, we must discuss some best practice concepts.
Regular Use of Environments
In the easiest scenario, you have one website and domain. The stage environment of your frontend website lives on this same domain, i.e., "http://stage.mywebsite.com ," while the production environment is found on "http://www.mywebsite.com ”.
In this case, we recommend one single JENTIS container for this website. In this container, you can use two slightly different JS code snippets to embed the right environment: JENTIS Code Snippet
Above the code snippet in the left corner, you can select the environment: live or stage. This will generate two different code snippets for each.
This is the best practice for one domain. You must not migrate (copy paste) any setting from one place to the other, just release to the right environment in the Versions and Preview.
Advanced Use of Environments
In some cases, a single container can not work for a website. In that case, it is or may be mandatory to create a container for each environment.
Multiple containers have references to the environment in the names "my website PROD" and "my website STAGE", and both containers have their own DNS A Record and JENTIS Code Snippet.
With this setup, you can work similarly to the regular environment, with only slight differences in publishing and migration.
Migration on Multi Container Environment
Now, with multiple containers, JENTIS scales as it does with regular environments. There is just one setting for the elements that are local to containers. As you might remember from our introduction article to containers, the following elements are on a per-container basis: tools, tags, custom code, and CMP connections.
To move a setting, you must select the container you want to use in a certain environment:
With this configuration, you can control what is executed on which container (that represents a certain environment). This must be set for each local element:
Tools (and hence all tags associated with this tool)
When a setting is ready for an environment, the regular process of releasing that container version is again performed. You must select both environments when publishing, as this container-environment setting is not used in this scenario.
If you have any questions or suggestions, contact us through our Helpdesk.