Script execution mode (Privacy level)

For legal reasons, it might be necessary to prevent the script from loading fully (tracking visitors and/or setting any cookies) until consent is given by the visitor. We offer different options for how the script is executed to support different types of privacy levels (see below). Please check with your legal counsel to decide what's appropriate for you.

Note that we are fully GDPR compliant and do not collect or store any personal data, but due to the ePrivacy Directive you might need to choose a different execution mode than the default one.

Read more about our cookies.

 

Script execution modes (privacy levels)

This setting is found in website settings and will be the execution mode for all types of projects.

Default: In the default mode the script run the projects and starts tracking visitors straight away. It does not wait for any consent from the visitor. Cookies are used to keep track of visitors and project information. Below is the information stored in a cookie when the script is loaded with an active project for a visitor.

{
  "{webisteId}":{
    "{projectId}":[{variationId}],
    "{projectId}_ch":1,
    "rf":"",
    "lv":{lastVisitTimestamp},
    "pv":1,
    "pv_p":{
      "{projectId}":1
    },
    "tv":1,
    "tv_p":{
      "{projectId}":1
    },
    "aud_p":[{projectId}],
    "visid":"{visitorId}",
    "commid":"{communicationId}"},
  "_g":1
}

 

Tracking consent: The script run the projects and tracks the visitor but does not push the data to our database until we receive a request for this through the optIn callback (needs to be called upon on visitor consent).

The information we set in the cookie before consent does not contain any data that could be seen as personal data.

This contain the information of what project(s) and variation(s) the visitor has been allocated, and also sets the start values for number of pages visited and total visits to the website.

In this privacy mode the script waits until consent is given before the cookie gets populated with the visitorId and the data gets pushed to our database.

Below is the information set before consent.

{
  "{websiteId}":{
    "{projectId}":[{variationId}],
    "{projectId}_ch":1,
    "rf":"",
    "lv":{lastVisitTimestamp},
    "pv":1,
    "pv_p":{
    "{projectId}":1},
    "tv":1,
    "tv_p":{
      "{projectId}":1
    },
    "aud_p":[{projectId}]},
  "_g":1
}

 

Cookie consent: The script prepares in the background but does not execute i.e. no projects will run nor will we track any visitors until we receive a request for this through the optIn callback (called upon visitor consent).

There are no cookies set until consent with this mode.

Notice!

Regardless of privacy level, the implementation script needs to be loaded as fast/soon as possible for the best performance.

 

Callback

On visitor consent please activate the script by calling the following function. This will also set an optIn cookie that will make the script launch directly from now on.

if(typeof symplify !== 'undefined') {
	window.symplify.optIn(1);
} else {
  document.addEventListener("symplify-loaded", function() {
  	window.symplify.optIn(1);
  });
}

Notice that you also need to check if consent has already been given but the optin cookie (for some reason) does not exist and in that case call the optIn function. 

 

 

Was this article helpful?
0 out of 0 found this helpful