The following content was translated using AI and reviewed by our team. Please note that some images are still being updated.

Update April 2024: It is now possible to set up tracking in incert, which will only be active upon receiving consent, without the need for the control described here. More information on this.

This article builds upon the general explanation of cookies and consent in incert. When the system is integrated into the website and the shop operator uses tracking tools, their cookies can be controlled through the website's consent mechanism.

This article is intended for web agencies. Therefore, the following explanations may not be entirely easy for non-experts to understand. However, they should be clear and straightforward for web agencies, without causing any excessive effort. In no case can or should incert work on the client’s website code. We kindly ask for your understanding that the integration cannot be carried out by incert.

Configuration by incert required. To use consent control as described below, a configuration must be set or checked in the system. Please contact service@incert.at beforehand.

Execution Delay

The integration script loads IncertClient.js asynchronously. Therefore, the execution of the following functions may need to be delayed. You can use the inc() wrapper to wait for the loading of IncertClient.js and the iFrame.

Description:

inc (function[, parameter, ...]);

Parameters:

• Function: Can be passed directly as a function or, for Incert functions, as a string.
• All additional parameters will be passed to the function upon execution.

Call with Incert function name as a string:

inc ("consentManager.setAll", false);

Call with your own function:

inc (function () {
  console.info("Both IncertClient.js and the iFrame have been loaded.");
  Incert.consentManager.setAll (false);
});

The default name for the wrapper is "inc", but it can be renamed as needed (see Integration Snippet).

Consent Control in incert

Consent for cookies and tracking in the incert system can be set for the iFrame, depending on the user’s consent or change of consent, as described below.

Example:

inc ("consentManager.setAll", false);

Alternatively:

inc (function () {
  Incert.consentManager.setAll (false);
});

setAll

Description:

setAll(bool value = false);

Activates or deactivates all optional services and their cookies.

Examples:

// disable optional cookies
Incert.consentManager.setAll(false);

set

Description:

set(string name, bool value = false);

Activates or deactivates the respective service and its cookies.

Examples:

// allow GoogleAds cookies
Incert.consentManager.set('GoogleAds', true);

reset

Description:

reset(string name = '');

Resets the respective service to its default setting. If the name parameter is omitted, all services will be reset to their default values.

Examples:

// reset GoogleAds to default
Incert.consentManager.reset('GoogleAds');

// reset all services to default
Incert.consentManager.reset();

setByPurpose

Description:

setByPurpose(string purpose, bool value = false);

Activates or deactivates all services according to their respective purpose.
A list of the most commonly used purposes can be found under Default values.

Examples:

// enables all services flagged as marketing
Incert.consentManager.setByPurpose('marketing', true);

Default values

Purposes:

• statistics
• marketing
• advertisement
• performance
• functional

Services:

• GoogleAds
• FacebookPixel