consent levels

It's possible to set consent independently for three categories:

1. essential cookie consent
2. tracking cookie consent
3. tracking consent

essential cookie consent

cookies that are considered essential:

• xcEssentialCookieConsent=true|false  saves essential cookie consent (will never be false, because
  in that case it wouldn't be allowed to be set)
• xcTrackingConsent=true|false  saves tracking consent
• xcTrackingCookieConsent=true|false  saves tracking cookie consent
• xcSessId=node...  holds the curren session ID

tracking cookie consent

Saves tracking cookies if enabled. Tracks without cookies when disabled and when selected tracking
implementation(s) support tracking without cookies.

• xcVisitorId  for recognizing a user across sessions, advisors or pages (also used for commerce
  tracking)

matomo cookies

• _xcpk_ses.[matomoSpaceId].xxx , e.g. _xcpk_ses.33.1fff : matomo session data
• _xcpk_id.[matomoSpaceId].xxx , e.g. _xcpk_id.33.1fff : matomo visitor data

tracking consent

Tracks the user with the configured tracking imeplementation(s). If tracking cookie consent is
disabled and a tracking implementation doesn't support tracking without cookies, it does not track.

setting consent

conf key

use the following keys to set the default behaviour if no consent is set via integration URL explicitly (otherwise everything currently defaults to `true`):

• application.clients.xcAjaxClient.config.trackingConsent= true|false ,
• application.clients.xcAjaxClient.config.essentialCookieConsent= true|false ,
• application.clients.xcAjaxClient.config.trackingCookieConsent= true|false ,

integration URL

consent may be set initially via the following integration url parameters

• xcEssentialCookieConsent=true|false  for setting essential cookie consent
• xcTrackingConsent=true|false  for setting tracking consent
• xcTrackingCookieConsent=true|false  for setting tracking cookie consent

everything defaults to `true` if not set or to the conf key values if they exist.

global function (advanced)

Once the advisor has been initialised, there is a global function available for changing consent. This may be used to pass consent changes to the advisor:
window.xcSetConsent(consent) 
with

consent={
	trackingConsent: true|false,
	essentialCookieConsent: true|false,
	trackingCookieConsent: true|false,
}

not all options have to be set. anything that's not passed will stay on the previous setting.

example usage

enable essential cookies and tracking, disable tracking cookies

window.xcSetConsent({
	trackingConsent: true,
	essentialCookieConsent: true,
	trackingCookieConsent: false,
})

disable tracking, keep all other settings

window.xcSetConsent({
	trackingConsent: false,
})

custom implementation

custom implementation by excentos to connect an existing tracking tool via available interfaces to our consent
management

matomo notes

• matomo is able to run without cookies
• when opting out of matomo, the cookie `mtm_consent_removed` is set
  • however if tracking is disabled initially, matomo won't be initialized and thus the cookie won't be set - only if it's disabled lateron
• current implementation uses opt-out for matomo because when opt-in is required, cookie opt-in doesn' work anymore