Page History

...

• 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 current session ID

tracking cookie consent

...

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

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

...

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

<!-- begin excentos integration code -->
<script 
	src="//service.excentos.com/heroal/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)

...

• matomo is able to run without cookies
• when opting out of matomo, the cookie `mtmmtm_consent_removed` is 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