Consent Handling FAQ

What happens if CMP consent and JENTIS consent are out of sync?

JENTIS will resolve consent for users based on your Consent Management Platform. Where an API connection is established when the user visits a website. On consent default and update events the consent mapping is applied, so a vendor in JENTIS understands which consent status is currently confirmed by the CMP. This information is stored within JENTIS, so the consent can be applied as fast as possible on any future events without interruption and with less dependencies.

In regular cases the consent status can not be out of sync, as the priority lies with the default information of a CMP. Only in edge cases where a CMPs consent information is lost or deleted the systems can become out of sync (see next question).

What if the user deletes CMP storage?

A rare case might happen when the CMP consent status is lost (ie. the user deletes the CMP cookies or storages or a tracking prevention mechanism in the browser deletes the CMPs consent information). In which case the user will get presented the CMP consent banner anew to make a decision, all while JENTIS consent information is already resolved (as in this edge case we assume that only the CMPs cookies are deleted). Here it can happen that JENTIS will already apply consent with the configured data streams (tags and connectors) as of the last known state. When the new consent update signal arrives, the systems are again synchronized (JENTIS with your CMP).

What if JENTIS loses stored consent data?

The other way around (JENTIS loses consent information but the CMP maintains the correct consent state) is not an issue, as JENTIS will actively reach out the get the current consent default state (on page load and when the CMP is finished initialization). This happens in the background and is the regular process (JENTIS reads consent from the CMP always).