consent.get

Method to receive TrustCommander consent and consent metadata OnSite via JavaScript.

The Commanders Act OnSite API stub has to be installed before using any of the OnSite API functions.

cact('consent.get', function (result) { ... });

The consent.get method takes one callback JavaScript function as an argument that gets called with the Consent Object that is currently stored on the browser. The callback is called once after TrustCommander JavaScript loaded and validated the stored consent.

The OnSite API works asynchronous. In case you need the consent synchronous (e.g. in the <head> of a document for AB Testing or personalisation solutions) it is recommended to cache the object in the localStorage of the browser. In this case it is crucial to implement the consent.onUpdate method to keep the cached consent in sync.

Examples

In this example the Analytics category was configured with the consent category id 2 in TrustCommander.

cact('consent.get', function (result) {
const ANALYTICS_ID = 2;
const analyticsCategory = result.consent.categories[ANALYTICS_ID] || {};
if (analyticsCategory.status === 'on') {
// Consent was provided for the category.
} else {
// Consent was not provided for the category.
}
});

In this example the Analytics category was configured with the consent category id 2 and the vendor Google with vendor id 5 in TrustCommander.

cact('consent.get', function (result) {
const ANALYTICS_ID = 2;
const analyticsCategory = result.consent.categories[ANALYTICS_ID] || {};
const GOOGLE_ID = 5;
const googleVendor = result.consent.vendors[GOOGLE_ID] || {};
if (analyticsCategory.status === 'on' && googleVendor.status === 'on') {
// Consent was provided for the category.
} else {
// Consent was not provided for the category.
}
});
cact('consent.get', function (result) {
if (result.consent.status === 'unset') {
// Consent was not yet provided.
} else {
// Consent was accepted or refused.
}
});
cact('consent.get', function (result) {
const dateExpires = result.meta.dateExpires;
});