Quicklizard Help Center

# GDPR Compliance

Quicklizard's SDK generates an anonymous cross-domain visitor ID, that is added to each event you send to our servers, and can be used by our internal pricing algorithms to analyze user journey on your site.

To comply with the EU's GDPR regulations, and depending on your compliance policy, you may need to disable this behaviour, which is enabled by default, when initializing the SDK.

Please note that you can disable this behaviour on a per-user or per-site basis, depending on the opt-in / opt-out mechanisms that are in place on your site.

# SDK invocation

To disable visitor ID tracking in the SDK, please initialize the SDK with a second argument that has the boolean value false.

For example, if your client key is shoesonline, your QL.init invocation should look like this:

QL.init('shoesonline', false);

Passing false as the second argument of QL.init will tell the SDK not to create a visitor ID for the user, and not to send it along with events sent to our servers.

# Technical Details

The visitor ID used by our SDK is a random string that is generated once per visitor, and is saved in the user's browser local storage mechanism.

As such, it is not an HTTP cookie, and is not sent along with HTTP request headers at any stage. The visitor ID is completely random, and does not fingerprint the user in any way or uses any personal details (such as IP address, browser version etc.).

Furthermore, the visitor ID is not linked in any way to personal user information such as email address, physical address, username, IP, device MAC address, etc.

# Lite Version

Quicklizard provides a lite version of our SDK that does not include any user tracking code. You may use this version as an alternative to the above method, if you wish to completely disable all user tracking when using our SDK.

To use the lite version of our SDK, replace the src attribute of the SDK script tag with the following URL - //d3jdlwnuo8nsnr.cloudfront.net/sdk/v3.0/ql.lite.js

The lite version of the SDK has the exact same functionality as the standard SDK. Your implementation should be the same, regardless of which SDK version you're using.

# Usage example

<script>
  window.QLAsync = function(QL){
    var clientKey = 'CLIENT_KEY',
        productId = 'PRODUCT_ID',
        shelfPrice = 0.0,
        permalink = self.location.href;
    QL.init(clientKey);
    QL.sendProductEvent(productId, {
      price: parseFloat(shelfPrice, 10),
      permalink: permalink
    });
  }
</script>
<script src="//d3jdlwnuo8nsnr.cloudfront.net/sdk/v3.0/ql.lite.js"></script>

Please Note

The src attribute of the above <script> tag points to the lite version of the SDK:

//d3jdlwnuo8nsnr.cloudfront.net/sdk/v3.0/ql.lite.js

← Debugging the SDK →