JENTIS data capture and load process revolves around submitting data to partners and networks. This consists of defining rules and configurations when to send what data to which partner. A pivotal part in this data load process are tags. They allow detailed configuration of individual parameters and values to be submitted to partner networks and tools.
JENTIS Tag Manager makes this process flexible and scalable. As you can configure different setups in a single tag configuration. But lets start with the basics.
Every tag in your JENTIS account consists of the following parts:
Tool: Select a tool that you previously created, which will hold global configurations for this tag.
Template: JENTIS include templates for tags that cover use cases per tool, ie. the “pageview” template for Google Analytics.
Trigger: Every Tag references a trigger which defines conditions on when to actually activate a tag and hence submit data to a partner.
Parameter Configuration: Here you will define every parameter that needs to be mapped to a value that will be submitted to the partner.
Tag Creation Process
Every tag needs a name. A common syntax is to use the partner network name combined with the template or event description, ie. “Google Analytics – Pageview”.
Every tag is associated with a tool that you previously created. This way any tag can access global configuration parameters and re use those.
Templates follow a tool schema to capture data. For Google Analytics for example the common templates follow GAs general tracking syntax of Pageviews, Events and enhanced Ecommerce Tracking.
Trigger define conditions on when a tag will be activated to submit data.
The actual configurations of a tags parameters and their respective values is defined in the last step: “Configure Template”. Here you can define parameters values according to a template. Later this setup can be changed and adjusted. Click “Finish” to make this tag available in your JTM account and preview the captured and loaded data to your partner network.
Mapping parameters of a Tag to technical references is key to receive the right data. All tools have custom parameters that fit their protocol. On the other side is your Jentis configuration that holds all the values that you implemented for tracking. Now you need to address these values to the parameters of a tool.
In every Tag you can follow a template that defines a parameter placeholder (ie. “Page Title” for Google Analytics). Now you can select any Variable value to submit it as the tag is activated for tracking.
You can select any Variable that you defined previously in the Data Sources area of your Jentis account. All Jentis integrations start with a rich set of default values.
add a variable to a placeholder: simply click in the empty space of a placeholder to open the Variable Selector
apply order of elements: drag & drop elements in place as required
apply functions on elements: drag & drop a variable into a function-box
add static text string: either CTRL+left-mouse-click (CMD+lft-mouse-click) to open text-input or add a text-input in the Variable Selector
delete elements: either SHIFT+left-mouse-click or right-mouse-click the element and select the “trash”-icon
more options: right-mouse-click an element to get a context-menu of an element
Some templates have dynamic parts in the configuration. The sender tag will allow you to select the best option in a use case with different tag options.
Tools like Google Universal Analytics have the option to submit ecommerce-data on different transport-methods (either in a pageview or event hit type). To respect this options the sender tag selection is available to you in JENTIS Tag Manager.
When selecting a certain sender tag option the configuration mask could slightly change. Opening up new parameters with a certain sender-option.
Elements in JENTIS are flexible in terms of customization. You can even edit all the default settings of tags, triggers, variables, etc.
This flexibility brings a new icon to the interface, so that you can see which parts are customized and which are on default settings.
Elements (such as placeholder configurations in tags) that have the JENTIS icon display that this element is maintained by JENTIS. So if this default is updated in a future version of the JENTIS Tag Manager it will be updated, too.
On the other hand side the user-icon is highlighting elements that are customized. This configurations will not update in the future. To make sure this settings are not updated to a default that doesn’t respect the customization.
No Consent Mode Tag Configuration
With the Consent Mode enabled in your JENTIS Tag Manager you will get new configuration options in a tag.
Now a tag has two columns for each placeholder configuration:
Each value of a parameter can be treated according to the consent of a user. Instead of configuring a tag twice (with two different triggers that act on consent and without) this makes each tag configuration more convenient. Simply select all parameters that must be anonymized or pseudonymised in the “No Consent Mode Value” column.
Some configurations have extendable parameters, like an index based dimension value.