How to Structure your Accounts

In your JENTIS Data Capturing implementation life cycle, you will soon be confronted with the question of how to set up your account, containers, and tools to maximize the efficiency and accessibility of the data pipelines.

In the next sections, we will discuss your options and the concepts behind them, helping you resolve the question of how many containers and tool instances you actually need.

Here are the topics you should consider when setting up your account:

Container Configuration

• 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.

Read more about tools and instances: Tools

Further, on the tool level, you can decide where to execute it with its configuration of tags, triggers, and variables.

A tool instance can be shared on multiple containers. So, the same configuration applies to multiple sites (with the same tags, triggers, and variables):

In conclusion, you can use a tool on multiple containers with the same configuration. It scales from bottom to top, hierarchy speaking. At the same time, you can have one container and run multiple tool instances on the same container, scaling from the top to the bottom. Both directions are possible.

So, it is up to you to see if a common tool definition applies to multiple containers, if you want to have a single container with multiple tools or even multiple containers with different tool definitions on the same website.