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 Cookies that are considered essential:

• xcConsent holds information about consent levels:

  xcEssentialCookieConsent

  • essentialCookieConsent=true

  |false  saves

  •  saves essential cookie consent (will never be false, because

  
  

  • in that case it wouldn't be allowed to be set)

  xcTrackingConsent

  • trackingConsent=true|false

    saves

  • saves tracking consent

  xcTrackingCookieConsent

  • trackingCookieConsent=true|false

    saves

  • saves tracking cookie consent

• xcSessId=node...  holds the curren current 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 imeplementationimplementation(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 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

configured explicitly, everything defaults to true. If another default behavior is required, please ask excentos to configure it to your needs.

Integration URL

Consent 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.

...

 Code Block
language
xml
linenumbers
true
<!-- begin excentos integration code -->
<script 
	src="//stage.excentos.com/demo/DE/app_Bike-Advisor/de_DE/loadadvisor?theme=default&xcEssentialCookieConsent=false&xcTrackingConsent=false&xcTrackingCookieConsent=false"> 
</script> 
<!-- end excentos integration code // start content area where Product Guide is displayed -->
<div id="xc_application">
	<div id="xc_application_pane"></div>  
	<div id="xc_loader"></div>
</div>
<!-- end excentos content area -->

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
 Code Block
language
js
consent={
	trackingConsent: true|false,
	essentialCookieConsent: true|false,
	trackingCookieConsent: true|false,
}

not Not all options have to be set. anything that's not passed will stay on the previous setting.
...
Example usage
enable Enable essential cookies and tracking, disable tracking cookies:
 Code Block
language
js
window.xcSetConsent({
	trackingConsent: true,
	essentialCookieConsent: true,
	trackingCookieConsent: false,
})

disable Disable tracking, keep all other settings:
 Code Block
language
js
window.xcSetConsent({
	trackingConsent: false,
})
...
Custom implementation
custom Custom implementation by excentos to connect an existing tracking tool via available interfaces to our consent 
 management
matomo notes
...
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
...