JENTIS NoConsent Mode
  • 31 Mar 2022
  • 2 Minutes to read
  • Contributors
  • Dark
    Light

JENTIS NoConsent Mode

  • Dark
    Light

JENTIS enables your tracking to be flexible in terms of a users consent. Consent is respected in terms of different tools and levels, such as consent for audience reach measurement that may operate on anonymized data. It is up to you and your requirements on measurement how you want data streams to operate. In which cases to anonymize data and run a tool consentless or in which cases a consent must be granted.

In this guide we will describe the technical terms and settings in JENTIS Tag Manager to achieve a consentless tracking. And which options you have to customize the defaults.

Please be aware that this only covers technical functionalities of integration and is not in any terms a legal assessment or consulting.

Data Persistence and Identifier Basics in JENTIS

When JENTIS is installed via the code snippet it will immediately set a user identifier to recognize multiple events (ie. “pageviews”) from the same device (users browser software). This is a cookie-based technology and the details on those are found here: JENTIS Cookies

By default this cookie is set automatically when the JENTIS code snippet is loaded. It is not technically connected to consent informations.

Any further data stream and tracking can be used with fully anonymized data that is not connected to each other. For example we can generate a random value as a client id for Google Analytics or pseudonymize that value, so it will not be random on every single hit but will be consistent (the value will be hashed in this hypothetical scenario). All options are available to your fingertips.

Another very important topic is the definition on data queues and setups where consent based decisions in data streams are applied even before a website visitor interacted with a consent management tool or banner. This is covered in a different section as it would blow up the scope of this guide. Please find more info here: NoConsent-Mode Data Stream Options

NoConsent Mode Setup

There are three steps in the configuration of the NoConsent Mode in JENTIS. The foundation is the definition what variables (parameter values) are PII (personally identifiable information). Next step is to activate NoConsent-Mode for single tools in JENTIS Tag Manager. Last but not least you can customize the settings of NoConsent-Mode in each tag individually.

PII Definition

Every single variable in JENTIS Tag Manager has a toggle switch to set this definition.

If a variable is considered to handle PII-data you must set this to “true”.

Please apply this to all variables to make sure every use case is covered.

Activate NoConsent-Mode

To activate the NoConsent-Mode per tool you have to navigate to the Consent Management section in JENTIS Tag Manager (1).

In the list of vendors select the tool that you want to activate with NoConsent-Mode (2).

Here you will find a toggle to activate this setting (3).

Customize Tags NoConsent-Mode Settings

Now that the NoConsent-Mode is active you can customize those settings per each parameter in all tags of this tool.

The tag editor view will now display for this tags a second column in the parameter definition. You can customize those settings individually per each parameter of that tool. The default will anonymize all variables that are marked as PII in all tags.

You can select the parameters values to be different in NoConsent-Mode, ie. apply a function to fully anonymize the variable value or pseudonymize it (it will remain same for a single user).

Next Steps

Now that we have the basics covered, how about discussing the actual configuration to customize what data is send when. Talking about NoConsent-Mode Data Stream Options.


Was this article helpful?