Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

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

Essential cookie consent

cookies Cookies that are considered essential:

...

Setting consent

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
languagexml
linenumberstrue
<!-- 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 -->

...

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
languagejs
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
languagejs
window.xcSetConsent({
	trackingConsent: true,
	essentialCookieConsent: true,
	trackingCookieConsent: false,
})


disable Disable tracking, keep all other settings:

Code Block
languagejs
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

  • matomo Matomo is able to run without cookies
  • when When opting out of matomo, the cookie mtm_consent_removed is set
    • however 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 Current implementation uses opt-out for matomo because when opt-in is required, cookie opt-in doesn' work anymore